Marking as invalid. Routed mode for load balancers is planned so ability
to specify the VIP on different subnet then the pool is an important
part of the API
** Changed in: neutron
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1177200
Title:
subnets in load balancer models are confusing
Status in OpenStack Neutron (virtual network service):
Invalid
Bug description:
~$ quantum subnet-list
+--------------------------------------+------+-------------+--------------------------------------------+
| id | name | cidr |
allocation_pools |
+--------------------------------------+------+-------------+--------------------------------------------+
| 131740ac-8ef0-4e8e-b571-2246e05d470a | | 10.0.2.0/24 | {"start":
"10.0.2.2", "end": "10.0.2.254"} |
| 193dc2ec-9893-423a-a59f-77eca753f197 | | 30.0.0.0/16 | {"start":
"30.0.1.0", "end": "30.0.1.254"} |
+--------------------------------------+------+-------------+--------------------------------------------+
quantum lb-pool-create --lb-method ROUND_ROBIN --name mypool
--protocol HTTP --subnet-id 131740ac-8ef0-4e8e-b571-2246e05d470a
[question] what does mean by this subnet-id in above command?
quantum lb-member-create --address 30.0.1.2 --protocol-port 80 mypool
[question] can I add a IP which does not belong to the pool's subnet?
quantum lb-vip-create --name myvip --protocol-port 80 --protocol HTTP
--subnet-id 193dc2ec-9893-423a-a59f-77eca753f197 mypool
[question] If vip subnet is not the same as the pool subnet, I am assuming a
l3 agent is needed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1177200/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp