Open Stack

On Wed, 2019-09-11 at 17:52 +0100, Sean Mooney wrote:
> On Wed, 2019-09-11 at 10:50 -0400, Paul Belanger wrote:
> > Greetings,
> > 
> > We use a few openstack public clouds for testing in the ansible project,
> > specifically using nodepool. We have a use case, where we need to boot 2
> > VMs on the same public subnet for testing reasons. However, the majority
> > of the clouds we are using, do not have a single subnet for their entire
> > public IP range. Up until now, we boot the 2 VMs, then hope they land
> > on the same subnet, but this isn't really efficient.
> 
> you can just specify the subnet as part of the boot request.
> so if you know the subnet ahead of time its pretty trivial to do this
> im not sure if nodepool can do that but it should not be hard to 
> since nova supports it.
> 
> at the nodepool leve you can specify the netwrok at teh pool or lable level
> https://zuul-ci.org/docs/nodepool/configuration.html#attr-providers.[openstack].pools.networks
> https://zuul-ci.org/docs/nodepool/configuration.html#attr-providers.[openstack].pools.labels.networks
> that coudl be extended to the subnet in theory.
actully i am wrong
we can olny specify the network
we can select a subnet if we pass fixed ips on that network but we cant pass the subnet uuid.
> 
> > 
> > Basically looking to see if there is a better way to handle this either
> > via openstacksdk or some other configuration we need cloud side.
> > 
> > Also note, we'd like to do this with public provider network (which we
> > don't have control over) and avoid using private network for now.
> > 
> > Paul
> > 
> 
>