Deploy openstack-core bundle without maas (manual provider)

[Mark Shuttleworth]

On 28/09/15 09:12, Merlijn Sebrechts wrote:
>> We work around this often by having the LXC machines DHCP on the base
>> network.
>
>
> Is there a way in Juju manual provider to specify how the default
> networking for LXC machines is handled? For example, can I tell the host
> "you should bridge the LXC container to the network on interface ethx and
> give it an ip in range y.y.y.y/xx"? It would be great if I could specify
> this in environments.yaml.

We have a network model ("spaces"), and I think if we were to do a lot
of work on this we would want to find a way to bring the manual provider
into line with that thinking. In other words, you'd define spaces out of
a set of subnets, and then you'd say what space you want a service on
the LXC container to be in, and it would DHCP on the same place as the
interfaces of the host which are on that space.

But this would be a LOT of work.

I think it would be cleanest initially just to ensure that the LXC
containers attach to all the same networks that the host machine does,
and DHCP there. In the common case, each LXC container gets an interface
on the same single subnet that its host has a single interface.

Mark