On Feb 16, 2015, at 1:14 PM, Joe Topjian <[email protected]> wrote: > Hello, > > When using the APIs directly to manage instances, which API is preferable for > associating and disassociating Floating IPs? > > Nova has the "os-floating-ips" extension which works for nova-network based > environments and, as far as I can tell, Neutron-based environments. All that > is required is a Floating IP and an instance ID. > > It's also possible to associate a Floating IP to an instance by using the > Neutron API as well, but it seems more complex. Unless I'm mistaken, with the > Neutron API, the UUID of the Floating IP and the UUID of the Port of the > instance is required. If you also want to make sure that the port is able to > support that Floating IP, you must query further. > > Given the ability to skip a good number of steps, is there a case where using > os-floating-ips to associate and disassociate Floating IPs and instances on > Neutron networks is not recommended?
Isn’t the answer (as usual) it depends? If you’ve got users who need a non-trivial networking setup and need to associate a Floating IP with a Port then direct them to use the Neutron APIs (or SDKs/CLIs). I can’t think of any other use cases than associate a Floating IP with a Port off the top of my head. If you’ve got users who only need the most basic networking setup possible then direct them to use the Nova’s os-floating-ips API (or SDK/CLI). Everett _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : [email protected] Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
