ELB (Eru load balance) is based on openresty. In Eru architecture, we use multiple filters to determine which upstream to forward. And by using ngx_http_dyups_module, citadel can update upstream dynamically.
- update upstream dynamically
- run by eru
- custom strategies of network flow
ELB will load data from etcd when starting.
In this version, we provide two types of filter. One is for user-agent, another for path. So we design a simple protocol for describing it.
This data will store in etcd with key /$ELBNAME/rules/$domain.
For example:
{
"init": "r1",
"rules": {
"r1": {"type": "ua", "args": {"fail": "r3", "pattern": "httpie(\\S+)$", "succ": "r4"}},
"r2": {"type": "backend", "args": {"servername": "upstream1"}},
"r3": {"type": "backend", "args": {"servername": "upstream2"}},
"r4": {"type": "path", "args": {"regex": true, "pattern": "^\\/blog\\/(\\S+)$", "succ": "r2", "fail": "r3", "rewrite": false}}
},
}You can build a complex filter by multiple rules.
Upstream data also store in etcd with key /$ELBNAME/upstreams/$backend/$server.
For example
etcdctl set /ELB/upstreams/up1/127.0.0.1:8088 ""
etcdctl set /ELB/upstreams/up1/127.0.0.1:8089 ""
etcdctl set /ELB/upstreams/up2/127.0.0.1:8089 "max_fails=2 weight=10"
Use dir to store server data will help you to asynchronous active server in upstream.
ELB have two APIs for managing.
When GET this url, it will response a json which contains domain and it's rules.
For example:
GET /__erulb__/domain HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate
Connection: keep-alive
Host: 127.0.0.1:8080
User-Agent: HTTPie/0.9.9
HTTP/1.1 200 OK
Connection: keep-alive
Content-Type: application/json
Date: Mon, 25 Sep 2017 09:06:32 GMT
Server: openresty/1.11.2.5
Transfer-Encoding: chunked
{
"127.0.0.1": {
"init": "r1",
"rules": {
"r1": {
"args": {
"fail": "r3",
"pattern": "httpie(\\S+)$",
"succ": "r4"
},
"type": "ua"
},
"r2": {
"args": {
"servername": "up1"
},
"type": "backend"
},
"r3": {
"args": {
"servername": "up2"
},
"type": "backend"
},
"r4": {
"args": {
"fail": "r3",
"pattern": "^\\/blog\\/(\\S+)$",
"regex": true,
"rewrite": false,
"succ": "r2"
},
"type": "path"
}
}
}
}
If you PUT this url, you have to upload a json with domains and it's rule, then ELB will update itself with their rules. For example:
PUT /__erulb__/domain HTTP/1.1
Accept: application/json
Accept-Encoding: gzip, deflate
Connection: keep-alive
Content-Length: 305
Content-Type: application/json
Host: localhost:8080
User-Agent: HTTPie/0.9.4
{
"localhost": {
"init": "r1",
"rules": {
"r1": {
"args": {
"fail": "r3",
"pattern": "^\\/blog\\/(\\S+)$",
"regex": true,
"rewrite": false,
"succ": "r2"
},
"type": "path"
},
"r2": {
"args": {
"servername": "upstream1"
},
"type": "backend"
},
"r3": {
"args": {
"servername": "upstream2"
},
"type": "backend"
}
}
}
}
HTTP/1.1 200 OK
Connection: keep-alive
Content-Type: application/json
Date: Tue, 26 Sep 2017 15:03:03 GMT
Server: openresty/1.11.2.5
Transfer-Encoding: chunked
{
"msg": "OK"
}
Then domain localhost was added. However, if somebody restart ELB, it will lose. Don't forget to store rules in etcd.
If you use DELETE method, you can upload a json with domains, then ELB will delete those domains.
DELETE /__erulb__/domain HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate
Connection: keep-alive
Content-Length: 0
Host: localhost:8080
User-Agent: HTTPie/0.9.9
[
"localhost",
"127.0.0.1"
]
HTTP/1.1 200 OK
Connection: keep-alive
Content-Type: application/json
Date: Wed, 27 Sep 2017 06:36:30 GMT
Server: openresty/1.11.2.5
Transfer-Encoding: chunked
{
"msg": "OK"
}
Don't forget delete domains data in etcd.
If you GET this url, elb will response a json which contains upstreams and it's backends like this:
GET /__erulb__/upstream HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate
Connection: keep-alive
Host: 127.0.0.1:8080
User-Agent: HTTPie/0.9.9
HTTP/1.1 200 OK
Connection: keep-alive
Content-Type: application/json
Date: Mon, 25 Sep 2017 09:08:59 GMT
Server: openresty/1.11.2.5
Transfer-Encoding: chunked
{
"upstream1": [
{
"addr": "127.0.0.1:8089",
"fail_timeout": 10,
"max_fails": 1,
"name": "127.0.0.1:8089",
"weight": 1
},
{
"addr": "127.0.0.1:8088",
"fail_timeout": 10,
"max_fails": 1,
"name": "127.0.0.1:8088",
"weight": 1
}
],
"upstream2": [
{
"addr": "127.0.0.1:8089",
"fail_timeout": 10,
"max_fails": 2,
"name": "127.0.0.1:8089",
"weight": 10
}
]
}
If you use PUT method, you can upload a json with upstreams and it's backends, then ELB will update itself with their upstreams. For example:
PUT /__erulb__/upstream HTTP/1.1
Accept: application/json, */*
Accept-Encoding: gzip, deflate
Connection: keep-alive
Content-Length: 115
Content-Type: application/json
Host: localhost:8080
User-Agent: HTTPie/0.9.9
{
"up1": {
"127.0.0.1:8088": "",
"127.0.0.1:8089": ""
},
"up2": {
"localhost:8088": "",
"localhost:8089": ""
}
}
HTTP/1.1 200 OK
Connection: keep-alive
Content-Type: application/json
Date: Mon, 25 Sep 2017 09:10:58 GMT
Server: openresty/1.11.2.5
Transfer-Encoding: chunked
{
"msg": "OK"
}
If you use DELETE method, you can upload a json with upstreams' name, then ELB will delete those upstreams.
DELETE /__erulb__/upstream HTTP/1.1
Accept: application/json, */*
Accept-Encoding: gzip, deflate
Connection: keep-alive
Content-Length: 8
Content-Type: application/json
Host: localhost:8080
User-Agent: HTTPie/0.9.9
[
"upstream1",
"upstream2"
]
HTTP/1.1 200 OK
Connection: keep-alive
Content-Type: application/json
Date: Wed, 27 Sep 2017 06:34:51 GMT
Server: openresty/1.11.2.5
Transfer-Encoding: chunked
{
"upstream1": true,
"upstream2": true
}
Don't forget delete upstreams data in etcd.
PUT this url, in-memory data will be dumped into etcd. and next elb will load it automatically from etcd.
PUT /__erulb__/dump HTTP/1.1
Accept: application/json, */*
Accept-Encoding: gzip, deflate
Connection: keep-alive
Content-Length: 115
Content-Type: application/json
Host: localhost:8080
User-Agent: HTTPie/0.9.9
HTTP/1.1 200 OK
Connection: keep-alive
Content-Type: application/json
Date: Mon, 25 Sep 2017 09:10:58 GMT
Server: openresty/1.11.2.5
Transfer-Encoding: chunked
{
"msg": "OK"
}
ELB will read ETCD, ELBNAME and STATSD from environment.
If etcd and elbname not set, elb will use 127.0.0.1:2379 and ELB as default.
But if STATSD not set, elb will not calcuate domain status.
We suggest you to run elb by ERU, however this image can standalone running.
docker run -d --privileged \
--name eru_elb_$HOSTNAME \
--net host \
--restart always \
-e "ETCD=<IP:PORT>" \
-e "ELBNAME=<ELBNAME>" \
-e "STATSD=<IP:PORT>" \
projecteru2/elbAfter we implemented bootstrap in eru2, now you can build and deploy elb with cli tool.
- Test source code and build image
<cli_execute_path> --name <image_name> https://goo.gl/WTGT9EMake sure you can clone code by ssh protocol because libgit2 ask for it. So you need configure core with github certs. After the fresh image was named and tagged, it will be auto pushed to the remote registry which was defined in core.
- Deploy elb by eru with specific resource.
<cli_execute_path> --pod <pod_name> --entry elb --network <network_name> --image <projecteru2/elb>|<your_own_image> [--node <specify_node>] [--cpu 0.3 | --mem 1024000000] https://goo.gl/WTGT9ENow you will find elb was started.
Because overlayfs with CentOS 7 has some issue, do not compile Dockerfile on CentOS 7 with overlayfs if you use early docker befor this.