Automate allocation of fip and static ip for loadbalancer vip

Bug #1588107 reported by Subrahmanyam Ongole
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Group Based Policy

Bug Description

One of the use cases is to be able to automate allocation of floating IP for loadbalancer vip_ip for N-S traffic and static IP for E-W traffic. The following are the available constructs in NSP (Network Service Policy) to fulfill the intent

1. ip-single self-subnet
2. ip-single nat-pool
3. ip-pool nat-pool

2n'd option above just creates a floating IP which the consumer could directly use. It doesn't allocate a local ip.

3rd option assigns a floating ip to each PT in a group.

None of the options above address the usecase.

Revision history for this message
Sumit Naiksatam (snaiksat) wrote :

Per discussion in the IRC meeting, it will be helpful if you can confirm that:
"2n'd option above just creates a floating IP which the consumer could directly use. It doesn't allocate a local ip." is indeed the case.

Changed in group-based-policy:
status: New → Incomplete
Revision history for this message
Harald Jensås (harald-jensas) wrote :


I am looking at the same:

With type=ip_single,name=vip_ip,value=nat_pool I get:
nat_pool fip_maps: [{"floatingip_id": "5bc31b37-5578-44e5-b054-a716ecb5686f",
                     "service_policy_id": "ebf0f54b-b8dc-4701-aa6c-cb64d996c335",
                     "policy_target_group_id": "b3362268-0a3c-4203-ae24-91e0e250deb2"}]

However I do not see how I can use the floatingip_id in a Heat loadbalancer template.
 Should'nt we get the subnet of the PTG and IP address of the floating_ip to pass as parameters to LBaaS template?

Also, the chain_mapping does not handle the "ip-pool nat-pool" case at all.
Would it not make sense to handle "ip-pool nat-pool" and return the "subnet_id" of the PTG to pass as parameter to OS::Neutron::LBaaS::LoadBalancer?

Revision history for this message
Subrahmanyam Ongole (osms69) wrote :

Are you using NFP?

One option you may want to try is as follows using a variant of the template

a) Update template and create a PT in the provider group.
b) Use the PT ip address for Vip address in HaproxyPool resource. Ref. template
c) Use "ip-single, nat-pool" network service policy to allocate a floating ip for vip. This needs to be done at service launch time.
d) Update template and associate floating ip. You have floating-ip allocated in step c) and static ip allocated in step a) above.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.