The LXC cluster does not require a zone of it's own, so you should be able to run an LXC cluster with other clusters. Regarding the LXC resource manager issue, it sounds like you're missing something during server initialization.
Under the hood, LXC uses Libvirt and leverages most of the KVM Libvirt code. So any networking abilities that were possible with KVM should work with LXC. I'm not too familiar with OVS + Cloudstack, so maybe someone from the community can help there. -Phong On Wed, Oct 9, 2013 at 10:09 AM, Chip Childers <chip.child...@sungard.com>wrote: > Adding Phong, who was the original author of the LXC plugin. Phong, can > you help Francois out? > > -chip > > On Wed, Oct 09, 2013 at 10:04:31AM -0400, Francois Gaudreault wrote: > > I posted on the users list, but no one responded. I am trying here :) > > > > In addition to this, I tried to add an LXC cluster in an existing > > Zone, and I got an error about the LXC resource manager not being > > found. > > > > > >I do have some questions regarding LXC containers and the > > >networking. First, should I put the LXC clusters on a separate > > >zone or I can use an existing zone (which I built for Xen) and > > >just create a new LXC cluster? Second, I saw in the doc that > > >bridges are manually created... what happens if I have > > >hundreds/thousands of guests VLANs? Will the agent automate that > > >part (planning to use OVS here)? > > > > > Thanks! > > > > -- > > Francois Gaudreault > > Architecte de Solution Cloud | Cloud Solutions Architect > > fgaudrea...@cloudops.com > > 514-629-6775 > > - - - > > CloudOps > > 420 rue Guy > > Montréal QC H3J 1S6 > > www.cloudops.com > > @CloudOps_ > > > > >
