status of container support in Juju
For our work on Machine View in the Juju GUI the team needs to help the user know what can and cannot be done with machines and containers. One of those things is determining if lxc or kvm containers work on various providers so the UX will not show users an option we know doesn't work. Jay wrote up a quick script [1] to test it out on each provider we support and I wanted to double check these results are expected. Provider | kvm | lxc | container is routable to client EC2 | no | yes | no Azure | no | no | - Azure w/o AS | no | yes | no HP Cloud | no | yes | no Joyent| no | yes | no Local (lxc) | no | no | - Local (kvm+aufs) | no | no | - Local (kvm-aufs) | no | yes | - I've not finished getting my MAAS setup going but I understand that it should work here. It'd be the only one that can currently create a container on a machine and then access it without needing to setup tunnels since it just grabs a DHCP address from the MAAS server. I understand that there's been work started on EC2 and routable lxc containers, but that it was put on hold to work on IPV6. So that path should be nicer in the near future. I also find a lot of references to LXC nesting [2][3] but it seems it does not work out of the box currently. If it's meant to work I can get Jay to file a bug and see if we can pull together any notes on that. Are there any plans to making lxc containers routeable in HP and Joyent? Does anyone know if lxc in lxc is meant to be supported in local out of the box? Right now I'm hesitant to enable creating containers in Machine View for anything but MAAS. I know that, in the providers that support lxc, as long as the service isn't exposed it's ok. I am worried about how to direct feedback to the user that they've deployed a scenario (mysql on the root while wordpress in a non-routable container) that we know can't work as users would expect. Please let me know if something should work that we're not seeing as working. 1: http://paste.ubuntu.com/8088459/ 2: http://s3hh.wordpress.com/2014/03/31/nested-lxc/ 3: https://www.stgraber.org/2012/05/04/lxc-in-ubuntu-12-04-lts/ -- Rick Harding Juju UI Engineering https://launchpad.net/~rharding @mitechie -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: status of container support in Juju
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 Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: status of container support in Juju
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 rick.hard...@canonical.com 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 Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev