Just to clear up a little confusion. OpenStack does support LXC as a “compute hypervisor” (i.e. it can be used instead of kvm, qemu, esxi, etc.). Be sure to check out the Compute Hypervisor Support Matrix for what features are supported on each (and whether they’ll be removed in the future).
Juju deployment on LXC as the “provider” is a different case, and likely fails for the reasons mentioned below. If you were really itching to test the new JuJu features, you could deploy an OpenStack all-in-one on a single box (currently no existing easy way to do this with Ubuntu, equivalent to Packstack), then deploy JuJu with the “OpenStack” provider, and finally deploy another OpenStack (“OpenStack on OpenStack” or “Triple O”) using the JuJu charms. It’s really sucks, but it can work. -Tim On Mar 17, 2014, at 1:05 PM, Sebastian <sebas5...@gmail.com> wrote: > Would love to see OpenStack running in my local dev environment, but also I > could use it in a dedicated server, to even use it with a juju openstack env. > > So, today we can't deploy OpenStack with all lxc, right? (sorry if thats the > wrong question, trying to catch up) > > > > Abs, > Sebas. > > > > 2014-03-17 16:50 GMT-03:00 Kapil Thangavelu <kapil.thangav...@canonical.com>: > > > > On Mon, Mar 17, 2014 at 3:37 PM, Tim Penhey <tim.pen...@canonical.com> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 18/03/14 05:35, Matt Rae wrote: > > On Mon, Mar 17, 2014 at 7:04 AM, James Page <james.p...@ubuntu.com > >> It would be interesting to know what are the blockers for this to > >> work. Using the local provider has been very convenient and it > >> would be nice to be able to deploy openstack without maas. > > > > Would switching to nova-network be a workaround for neutron? Could > > nova-compute use the virt-type="lxc" to get around the hypervisor > > issues? > > Just idly wondering, but what are the minimum kvm requirements for > nova-compute and quantum-gateway? > > hardware supports nested virt on compute (if using kvm on nova-compute lxc > should work okay), quantum is a bit of a mystery. > > Currently the juju local provider has just one container factory (used > for creating machines). It is just a simple manner of code to make it > work with both kvm and lxc. > > i noticed that limitation with the local provider, i think mixed container > usage would help, we would need to direct both to the same bridge. not sure > if that the will resolve all the issues. > > Did you realize that you can use the > local provider configured to use kvm containers? > > > /me nods > > kvm machine per openstack instance are a bit overkill, hulk smash/deploy-to > would help though but needs a bundle/deployer config with co-location for > folks to use. > > Now I've not put too much thought into this yet, and we don't have any > time before 14.04, but could be an interesting spike to show something > off at ODS. > > > i was thinking it would be nice for 14.10 to have a dev/demo on one machine > to prod workflow on openstack. tbd, there are a few other projects working on > the same. > > We could have some bundle that described an openstack local deployment > where you could go 'juju quickstart local-openstack' and have a > complete openstack deployment on your laptop in a combination of lxc > and kvm containers. > > Thoughts? > > openstack as dev or demo on local sounds awesome. > > -k > > > > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > > > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju
signature.asc
Description: Message signed with OpenPGP using GPGMail
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
