Open Stack

On 2017-04-03 17:21:24 +0200 (+0200), Alex Burmashev wrote:
> Yeah, i thought about it, but i think automatic IP assigning is only
> supported with nova-network, and i use neutron.
> 
> Moreover at least for some time nodepool definitely was assigning IPs to the
> VMs, it is starting, it is mentioned in docs, maillists and irc discussions.
> Maybe at some moment automatic floating IP assigning on a cloud became a
> must-have, but it is not mentioned in nodepool/openstack CI docs anywhere...
[...]

It's nuanced and probably confusing to track down the appropriate
documentation. Since nodepool uses os-client-config to infer network
needs from your provider, your clouds.yaml file may need to
explicitly set nat_destination on one of your networks (for example
if none or perhaps more than one have gateway_ip set in their
metadata):

    https://docs.openstack.org/developer/os-client-config/network-config.html

The os-client-config library has a bunch of default profiles for
popular public OpenStack providers, but if you've built your own or
are using one it doesn't know about yet it's possible there's a
difference in configured behavior from what it expects to be able to
guess when and where to add floating IPs.
-- 
Jeremy Stanley