So you're always welcome to do more testing :), but I'm sure that right now LXC containers only get host-local IP addresses, and are not bridged to the outside network anywhere but on MaaS.
John =:-> On Tue, Aug 19, 2014 at 6:56 PM, Richard Harding <[email protected] > wrote: > Thanks for the correction. You're right, in the testing we were checking > expose directly. We also did a test (not in this script) around two > services where one was on the root and one was in a container, but even > that's not a fair case of 'routable' as that might work while two units on > different machines would not. > > We'll update and do some more testing. > > On Tue, 19 Aug 2014, John Meinel wrote: > > > "expose" is different because it is about making the service available > > outside of the cloud. The issue with route able containers is that they > > aren't route able even within the cloud. > > At this point only MaaS has route able containers. > > > > John > > =:-> > > On Aug 19, 2014 4:56 PM, "Richard Harding" <[email protected]> > > wrote: > > > > > On Tue, 19 Aug 2014, Richard Harding wrote: > > > > > > > Right now I'm hesitant to enable creating containers in Machine View > for > > > > anything but MAAS. > > > > > > Just to clarify, after having some more coffee we can warn users that > > > expose services that have units in containers in the GUI and it should > help > > > raise warning to users about the routing issues for now. It's after the > > > user has set things up, but it should allow us to allow containers in > most > > > providers. > > > > > > -- > > > > > > Rick > > > > > > > > > -- > > > Juju-dev mailing list > > > [email protected] > > > Modify settings or unsubscribe at: > > > https://lists.ubuntu.com/mailman/listinfo/juju-dev > > > >
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
