How to specify range or direct ip for amphora IP
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
octavia |
New
|
Undecided
|
Unassigned |
Bug Description
There is an complexity (issue) with current processing allocation ip addresses by amphora vms.
For example for topology:
LB amphora - VM (in the lb network)
Octavia allocates 2 or 3 IP addresses from lb network (1 for VIP, 1 or 2 (active standby LB) for amphora VRRPs):
- Address for VIP could be specified on creation step.
- however Amphora addresses are not under control of user flow.
It makes difficult to control network, because ip could be randomly allocated from whole lb network and also be re-allocated during failover.
For another case, when VM exist in the different network (f.e. net1) and user connect it to LB, an extra ip be allocated from net1. And again it's not possible to say which ip be allocated.
The main question of the current "bug" is:
- is it possible to set range or direct ip for amphora VRRP IP(s)?
Or maybe there is some guideline: how correctly configure VM and LB network to avoid taking random IPs from VM networks.
This is right that the VRRP IPs are (randomly) reallocated during a failover, but I don't see why it could be an issue there, what's the impact on your network?
There's no way to specify an IP address for those VRRP IPs.
Another approach would be to use the multivip (additional vips) feature, you can create a LB with an IPv6 subnet in vip_subnet_id, and an IPv4 subnet as an additional vip.
With this method, 3 IP addresses are allocated on the IPv6 subnet (2 VRRP IPs + a VIP) and only one IP address on the IPv4 subnet (a VIP).