On 05/12/13 09:40, Kapil Thangavelu wrote: > > > > On Wed, Dec 4, 2013 at 11:58 AM, Daniel Westervelt > <[email protected] > <mailto:[email protected]>> wrote: > > > > On 12/04/2013 02:36 PM, Tim Penhey wrote: > > On 05/12/13 02:22, Daniel Westervelt wrote: > >> > >> > >> On 12/04/2013 05:51 AM, James Page wrote: > >>> Hi Tim On 04/12/13 04:44, Tim Penhey wrote: > >>>> For those who like living on the edge, we now have KVM container > >>>> support in trunk. > >>> > >>> Nice work! > >>> > >>>> It is kinda hard to confirm it fully works right now. I need to > >>>> actually test it on a MAAS install that is KVM capable. > >>> > >>>> Constraints aren't yet supported, that should be coming tomorrow > >>>> (fingers crossed). > >>> > >>>> Also landed recently is a KVM option for the local provider. > >>>> For the truly trivial, add "container: kvm" to the local > >>>> configuration. > >>> > >>> Is it possible to mix LXC and KVM containers under the local > >>> provider? > >> This is very important to many of our use cases, I eagerly await > >> confirmation that it is indeed the way it works? > > > > This was never the intention. The local provider uses containers to > > imitate machines, and only one type of container is supported for any > > given environment. > Too bad. There are many instances, especially with openstack, where you > might want to juju deploy some charms to lxc and some to kvm. Is there > some major technical challenge to adding support for this? > > > > As John mentioned, it is feasible to allow lxc within a kvm container, > nice to know but not as interested in that. deep nesting tends to hurt > my head. > > but mixed lxc/kvm machines are not supported by the local provider. > > > > However, if you main environment provider is MAAS, then you can create > > both lxc and kvm containers in those machines. > There are times when the overhead of having MAAS just for this purpose > does not seem to make sense. > > > manual provider is pretty much gold in those cases, where you want > flexible provisioning that juju doesn't natively provide. ie in this > case create some kvms and lxcs outside of juju and add-machine.
Or even use manual provisioning to add the host, and then create the containers in there... (assuming appropriate networking bridges) Tim -- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
