Fwd: How to do network segregation with Juju deployment ?

[Daniel Bidwell]

Does the --networks=... actually bring up the maas nodes?

That would be simpler then doing "juju machine add ..." going in and
bringing up the interfaces and then doing "juju deploy .... --to n".

On Fri, 2015-08-07 at 18:52 +0300, Dimiter Naydenov wrote:
> Hi,
> 
> We're in currently developing more comprehensive networking features
> in Juju, so soon you'll be able to configure this with Juju the way
> you like it.
> 
> In the meantime, please ignore the --networks argument - it was
> implemented partially as a proof of concept and never officially
> supported or documented (it's only supported on MAAS and only for
> nodes, not LXC containers or KVM instances).
> 
> If you want to get a node from MAAS on given networks, I'd suggest to
> add tags on the nodes (e.g. tag "net_public", "net_internal") and then
> use --constraints instead:
> $ juju deploy keystone --constraints tags=net_internal,^net_public
> 
> Multiple tags can be specified in a comma-delimited list. If you
> prefix a tag with "^" it means "not this tag" (i.e. exclude nodes
> matching that tag before deciding which node to provision).
> 
> I hope this helps, and stay tuned for the upcoming networking features
> in Juju!
> 
> Cheers,
> Dimiter Naydenov
> 
> On  7.08.2015 18:16, 曾建銘 wrote:
> > Hi all,
> > 
> > I want to deploy OpenStack by Juju with network segregation. I got
> > 3 different subnets in my environment, and follow bellow steps to
> > config:
> > 
> > 1. Set interfaces information in MAAS clusters tab. 2. Set networks
> > information in MAAS networks tab. 3. Edit the network detail and
> > set connected interface cards.
> > 
> > I got two screen shots to display my current settings.
> > 
> > 
> > 
> > 
> > Then, I used below commands try to deploy keystone service in LXC
> > with multiple networks: $ juju bootstrap $ juju deploy keystone
> > --networks=net_public,net_admin,net_internal --config=config.yaml
> > --to lxc:0
> > 
> > But it stuck for a long time with allocating status, so I checked
> > the juju debug logs, then I found logs as below: "ERROR
> > juju.provisioner provisioner_task.go:630 cannot start instance for
> > machine "0/lxc/1": starting lxc containers with networks is not 
> > supported yet"
> > 
> > Is there anything I missed? Why juju told me "networks is not
> > supported yet"?
> > 
> > I have stuck with this problem for several days. If anyone have
> > one minute to give me some hints, I will be very appreciate.
> > 
> > Best Regards, Leon
> > 
> > 
> > 
> 
> 

-- 
Daniel Bidwell <drbidwell at gmail.com>