Ask Your Question

FloatingIP public subnet association within Heat

asked 2016-08-17 00:16:23 -0500

thomasb gravatar image

updated 2016-08-18 15:17:31 -0500

rbowen gravatar image

I am working with a usecase to segmentate the FloatingIP pool of an External Network into logical buckets. I am trying an approach of dividing the FloatingIP pool using multiple subnets within a single External Network.

Using OpenStack CLI there appears to be a way to create a FloatingIP specifying both the floating network and also passing in a subnet. It appears to allocate the correct FloatingIP address within the desired subnet:

neutron floatingip-create d882e796-8ce3-4509-8037-0c808ecb4c18 --subnet f63ed3d9-aeb8-4336-a55d-95c7d282272d

Within the Heat Specification, I cannot see away to associate a FloatingIP with the Public subnet - only a floating network. If the floating network has many subnets, it appears to allocate IPs from the last created subnet only.

Is there a way to pass into Heat the desired subnet within the floating network when creating a FloatingIP?

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2016-09-20 13:17:54 -0500

zaneb gravatar image

I raised a bug to add support for this.

In the meantime, you _might_ be able to handle this by specifying it in the value_specs property, which is a sort of catch-all for parameters to the neutron client that are not directly modelled in Heat.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools


Asked: 2016-08-17 00:16:23 -0500

Seen: 122 times

Last updated: Sep 20 '16