Update patch set 1

Browse Source

Patch Set 1:

Cool - thanks for the followup. It has given me some ideas for a topic I need to write down further thoughts on - and an area I need to expose a new abstraction for.

The use case you describe is valuable - and can be accomplished as well on non-fip clouds by pre-allocating a neutron port then providing that port to the nova boot command. However, that is not easily exposed currently.

That way, similar to how auto_ip works (if the cloud needs fips, get one, otherwise just use the IP from the server) we could have a "get_preallocated_ip" abstraction which gets a neutron port if that's how the cloud does it, and a floating ip if that's how it does it.

I'll write up a document with better thoughts than that and point you at it for your feedback.

I'm poking at this because, unfortunately, floating-ips are overloaded with two different meanings. Sometimes people actually want specific qualities of floating ips - and in those cases they must have a floating ip. But in other cases they merely want an IP (like what you describe) and the mechanism the cloud uses for that (fixed vs. floating) is not important. We don't do a good job in OpenStack of differentiating that now - but I'd like to continue to work on defining such things when I can and working to improve it.

I'll rebase this stack so that the next patch isn't blocked.

Patch-set: 1

...

This commit is contained in:

Gerrit User 2 2017-05-19 15:50:57 +00:00 committed by Gerrit Code Review

parent fafe971a9d

commit 9bdb4ce61f

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Show Stats Download Patch File Download Diff File Expand all files Collapse all files

Diff Content Not Available