Public bug reported: when multi neutron-lbassv2-agent exist, each loadbalnacer is scheduled randomly on creation, and once a loadbalancer is binded to a agent, it's fixed, and cann't be changed according user's needs, this is not flexible. The patch here implement functions liking "l3-agent-router-add" "l3-agent-router-remove", and can be used to remove loadbalancer from its default lbaasv2 agent, or add one loadbalancer(without hosting agent) to a specified agent. it is helpful in production environment, since it can balance the network traffic, and may also be useful in lbaas ha implemention.
Remove the loadbalancer from one agent: curl -g -i -X DELETE http://CONTROLLER:9696/v2.0/agents/0fc961f1-2279-414c-8e91-172965319276/agent-loadbalancers/4b4d8b7a-c70d-4a5c-a4cb-bb906273d1b2.json -H "User-Agent: python-neutronclient" -H "Accept: application/json" -H "X-Auth-Token: cdb8f136cacb467fb3eeecc5d331db4a" Add the loadbalancer to the agent: curl -g -i -X POST http://CONTROLLER:9696/v2.0/agents/0fc961f1-2279-414c-8e91-172965319276/agent-loadbalancers.json -H "User-Agent: python-neutronclient" -H "Content-Type: application/json" -H "Accept: application/json" -H "X-Auth-Token: e8f45c060e82447d9b07fcd3e3c7e048" -d '{"loadbalancer_id": "4b4d8b7a-c70d-4a5c-a4cb-bb906273d1b2", "provider": "haproxy"}' ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1474277 Title: [lbaas]Change lbaasv2 scheduler to support moving loadbalancer from one lbaas v2 agent to another. Status in neutron: New Bug description: when multi neutron-lbassv2-agent exist, each loadbalnacer is scheduled randomly on creation, and once a loadbalancer is binded to a agent, it's fixed, and cann't be changed according user's needs, this is not flexible. The patch here implement functions liking "l3-agent-router-add" "l3-agent-router-remove", and can be used to remove loadbalancer from its default lbaasv2 agent, or add one loadbalancer(without hosting agent) to a specified agent. it is helpful in production environment, since it can balance the network traffic, and may also be useful in lbaas ha implemention. Remove the loadbalancer from one agent: curl -g -i -X DELETE http://CONTROLLER:9696/v2.0/agents/0fc961f1-2279-414c-8e91-172965319276/agent-loadbalancers/4b4d8b7a-c70d-4a5c-a4cb-bb906273d1b2.json -H "User-Agent: python-neutronclient" -H "Accept: application/json" -H "X-Auth-Token: cdb8f136cacb467fb3eeecc5d331db4a" Add the loadbalancer to the agent: curl -g -i -X POST http://CONTROLLER:9696/v2.0/agents/0fc961f1-2279-414c-8e91-172965319276/agent-loadbalancers.json -H "User-Agent: python-neutronclient" -H "Content-Type: application/json" -H "Accept: application/json" -H "X-Auth-Token: e8f45c060e82447d9b07fcd3e3c7e048" -d '{"loadbalancer_id": "4b4d8b7a-c70d-4a5c-a4cb-bb906273d1b2", "provider": "haproxy"}' To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1474277/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
