You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Francois Gaudreault <fg...@cloudops.com> on 2013/10/09 16:04:31 UTC

Re: LXC and Networking

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
fgaudreault@cloudops.com
514-629-6775
- - -
CloudOps
420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


Re: LXC and Networking

Posted by Shanker Balan <sh...@shapeblue.com>.
On 21-Oct-2013, at 2:41 AM, Francois Gaudreault <fg...@cloudops.com> wrote:

> Shanker,
>
> We were using the nonoss build, and we had to add a line in the nonossComponentContext.xml (like the ticket says). I did not try with the oss version, maybe there is a ossComponentContext.xml somewhere... I don't know.

I rebuilt ACS 4.2 nonoss from Git. Cluster addition works now. Thanks for the tip.

> list clusters name=LXC1
count = 1
cluster:
name = LXC1
id = a723620c-2f89-487d-993b-343442906fac
allocationstate = Enabled
clustertype = CloudManaged
cpuovercommitratio = 3
hypervisortype = LXC
managedstate = Managed
memoryovercommitratio = 1
podid = 56b8baec-94f2-42b8-8483-3362c8bd0601
podname = Zone21-Pod1
zoneid = 2f328497-79bf-44dd-93a4-d5844b151437
zonename = Zone21


>
> After I got pass this issue, I am still stuck on KVM system vms not coming online properly. Something kills the VM randomly. Sometimes the Console Proxy gets some IP, sometimes not. Same for SSVM. But that's another issue :)
>

:)

Will update on the progress at my end too.


> Francois
>
> On 10/20/2013, 4:04 PM, Shanker Balan wrote:
>> On 20-Oct-2013, at 10:41 PM, Shanker Balan <sh...@shapeblue.com> wrote:
>>
>>> On 10-Oct-2013, at 2:40 AM, Francois Gaudreault <fg...@cloudops.com> wrote:
>>>
>>>> Thanks Phong about the networking answers. I will follow the KVM docs.
>>>>
>>>> Regarding the resource manager, we did compile the nonoss package on our own.  Are you saying we require an extra deps?
>>> Hi Francois,
>>>
>>> Have you been able to make progress with LXC?
>>>
>>> I just hit the "Could not find corresponding resource manager for lxc" issue too.
>>> This is with the RPMs from http://cloudstack.apt-get.eu/rhel/4.2/.
>>>
>>> It looks to me that the RPMs don't have LXC compiled in or are missing the required JAR dep.
>>>
>>> [root@csman2-1 ~]# rpm -ql cloudstack-management |grep hyperviso
>>> /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-hypervisor-baremetal-4.2.0.jar
>>> /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-hypervisor-kvm-4.2.0.jar
>>> /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-hypervisor-ovm-4.2.0.jar
>>> /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-hypervisor-ucs-4.2.0.jar
>>> /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-hypervisor-vmware-4.2.0.jar
>>> /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-hypervisor-xen-4.2.0.jar
>>>
>>>
>>> [root@csman2-1 ~]# cloudmonkey add cluster clustername=lxc hypervisor=lxc
>>> zoneid=2f328497-79bf-44dd-93a4-d5844b151437 podid=56b8baec-94f2-42b8-8483-3362c8bd0601
>>> clustertype=CloudManaged
>>> : Could not find corresponding resource manager for lxc
>>>
>>> [root@csman2-1 WEB-INF]# rpm -qa|grep cloudstack-
>>> cloudstack-management-4.2.0-1.el6.x86_64
>>> cloudstack-common-4.2.0-1.el6.x86_64
>>> cloudstack-awsapi-4.2.0-1.el6.x86_64
>>> cloudstack-cli-4.2.0-1.el6.x86_64
>>> cloudstack-usage-4.2.0-1.el6.x86_64
>>>
>>> [root@csman2-1 WEB-INF]# lsb_release -a
>>> LSB Version:    :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch
>>> Distributor ID: CentOS
>>> Description:    CentOS release 6.4 (Final)
>>> Release:        6.4
>>> Codename:       Final
>>> [root@csman2-1 WEB-INF]#
>>
>> Looks like you already have a ticket open at https://issues.apache.org/jira/browse/CLOUDSTACK-4849.
>> I can see that the LxcServerDiscoverer beam is indeed loaded but still unable to add an LXC cluster.
>>
>> 2013-10-20 15:44:13,778 INFO  [utils.component.ComponentContext] (Timer-2:null) Configuring com.cloud.hypervisor.kvm.discoverer.LxcServerDiscoverer_EnhancerByCloudStack_42c0e23d
>> 2013-10-20 15:44:17,508 INFO  [utils.component.ComponentContext] (Timer-2:null) Starting com.cloud.hypervisor.kvm.discoverer.LxcServerDiscoverer_EnhancerByCloudStack_42c0e23d
>>
>> [root@csman2-1 ~]# grep -A 6 -B 6 -i lxc /usr/share/cloudstack-management/webapps/client/WEB-INF/classes/componentContext.xml
>>   <bean id="resourceDiscoverers" class="com.cloud.utils.component.AdapterList">
>>     <property name="Adapters">
>>       <list>
>>           <ref bean="XcpServerDiscoverer"/>
>>           <ref bean="SecondaryStorageDiscoverer"/>
>>           <ref bean="KvmServerDiscoverer"/>
>>           <ref bean="LxcServerDiscoverer"/>
>>           <ref bean="BareMetalDiscoverer"/>
>>           <ref bean="OvmDiscoverer"/>
>>       </list>
>>     </property>
>>   </bean>
>>
>> Regards.
>>
>> --
>> @shankerbalan
>>
>> M: +91 98860 60539 | O: +91 (80) 67935867
>> shanker.balan@shapeblue.com | www.shapeblue.com | Twitter:@shapeblue
>> ShapeBlue Services India LLP, 22nd floor, Unit 2201A, World Trade Centre, Bangalore - 560 055
>>
>> CloudStack Bootcamp Training on 27/28 November, Bangalore
>> http://www.shapeblue.com/cloudstack-training/
>>
>>
>>
>>
>> This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>>
>
>
> --
> Francois Gaudreault
> Architecte de Solution Cloud | Cloud Solutions Architect
> fgaudreault@cloudops.com
> 514-629-6775
> - - -
> CloudOps
> 420 rue Guy
> Montréal QC  H3J 1S6
> www.cloudops.com
> @CloudOps_
>

--
@shankerbalan

M: +91 98860 60539 | O: +91 (80) 67935867
shanker.balan@shapeblue.com | www.shapeblue.com | Twitter:@shapeblue
ShapeBlue Services India LLP, 22nd floor, Unit 2201A, World Trade Centre, Bangalore - 560 055

CloudStack Bootcamp Training on 27/28 November, Bangalore
http://www.shapeblue.com/cloudstack-training/




This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: LXC and Networking

Posted by Francois Gaudreault <fg...@cloudops.com>.
Shanker,

We were using the nonoss build, and we had to add a line in the 
nonossComponentContext.xml (like the ticket says). I did not try with 
the oss version, maybe there is a ossComponentContext.xml somewhere... I 
don't know.

After I got pass this issue, I am still stuck on KVM system vms not 
coming online properly. Something kills the VM randomly. Sometimes the 
Console Proxy gets some IP, sometimes not. Same for SSVM. But that's 
another issue :)

Francois

On 10/20/2013, 4:04 PM, Shanker Balan wrote:
> On 20-Oct-2013, at 10:41 PM, Shanker Balan <sh...@shapeblue.com> wrote:
>
>> On 10-Oct-2013, at 2:40 AM, Francois Gaudreault <fg...@cloudops.com> wrote:
>>
>>> Thanks Phong about the networking answers. I will follow the KVM docs.
>>>
>>> Regarding the resource manager, we did compile the nonoss package on our own.  Are you saying we require an extra deps?
>> Hi Francois,
>>
>> Have you been able to make progress with LXC?
>>
>> I just hit the "Could not find corresponding resource manager for lxc" issue too.
>> This is with the RPMs from http://cloudstack.apt-get.eu/rhel/4.2/.
>>
>> It looks to me that the RPMs don't have LXC compiled in or are missing the required JAR dep.
>>
>> [root@csman2-1 ~]# rpm -ql cloudstack-management |grep hyperviso
>> /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-hypervisor-baremetal-4.2.0.jar
>> /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-hypervisor-kvm-4.2.0.jar
>> /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-hypervisor-ovm-4.2.0.jar
>> /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-hypervisor-ucs-4.2.0.jar
>> /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-hypervisor-vmware-4.2.0.jar
>> /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-hypervisor-xen-4.2.0.jar
>>
>>
>> [root@csman2-1 ~]# cloudmonkey add cluster clustername=lxc hypervisor=lxc
>> zoneid=2f328497-79bf-44dd-93a4-d5844b151437 podid=56b8baec-94f2-42b8-8483-3362c8bd0601
>> clustertype=CloudManaged
>> : Could not find corresponding resource manager for lxc
>>
>> [root@csman2-1 WEB-INF]# rpm -qa|grep cloudstack-
>> cloudstack-management-4.2.0-1.el6.x86_64
>> cloudstack-common-4.2.0-1.el6.x86_64
>> cloudstack-awsapi-4.2.0-1.el6.x86_64
>> cloudstack-cli-4.2.0-1.el6.x86_64
>> cloudstack-usage-4.2.0-1.el6.x86_64
>>
>> [root@csman2-1 WEB-INF]# lsb_release -a
>> LSB Version:    :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch
>> Distributor ID: CentOS
>> Description:    CentOS release 6.4 (Final)
>> Release:        6.4
>> Codename:       Final
>> [root@csman2-1 WEB-INF]#
>
> Looks like you already have a ticket open at https://issues.apache.org/jira/browse/CLOUDSTACK-4849.
> I can see that the LxcServerDiscoverer beam is indeed loaded but still unable to add an LXC cluster.
>
> 2013-10-20 15:44:13,778 INFO  [utils.component.ComponentContext] (Timer-2:null) Configuring com.cloud.hypervisor.kvm.discoverer.LxcServerDiscoverer_EnhancerByCloudStack_42c0e23d
> 2013-10-20 15:44:17,508 INFO  [utils.component.ComponentContext] (Timer-2:null) Starting com.cloud.hypervisor.kvm.discoverer.LxcServerDiscoverer_EnhancerByCloudStack_42c0e23d
>
> [root@csman2-1 ~]# grep -A 6 -B 6 -i lxc /usr/share/cloudstack-management/webapps/client/WEB-INF/classes/componentContext.xml
>    <bean id="resourceDiscoverers" class="com.cloud.utils.component.AdapterList">
>      <property name="Adapters">
>        <list>
>            <ref bean="XcpServerDiscoverer"/>
>            <ref bean="SecondaryStorageDiscoverer"/>
>            <ref bean="KvmServerDiscoverer"/>
>            <ref bean="LxcServerDiscoverer"/>
>            <ref bean="BareMetalDiscoverer"/>
>            <ref bean="OvmDiscoverer"/>
>        </list>
>      </property>
>    </bean>
>
> Regards.
>
> --
> @shankerbalan
>
> M: +91 98860 60539 | O: +91 (80) 67935867
> shanker.balan@shapeblue.com | www.shapeblue.com | Twitter:@shapeblue
> ShapeBlue Services India LLP, 22nd floor, Unit 2201A, World Trade Centre, Bangalore - 560 055
>
> CloudStack Bootcamp Training on 27/28 November, Bangalore
> http://www.shapeblue.com/cloudstack-training/
>
>
>
>
> This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>


-- 
Francois Gaudreault
Architecte de Solution Cloud | Cloud Solutions Architect
fgaudreault@cloudops.com
514-629-6775
- - -
CloudOps
420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


Re: LXC and Networking

Posted by Shanker Balan <sh...@shapeblue.com>.
On 20-Oct-2013, at 10:41 PM, Shanker Balan <sh...@shapeblue.com> wrote:

> On 10-Oct-2013, at 2:40 AM, Francois Gaudreault <fg...@cloudops.com> wrote:
>
>> Thanks Phong about the networking answers. I will follow the KVM docs.
>>
>> Regarding the resource manager, we did compile the nonoss package on our own.  Are you saying we require an extra deps?
>
> Hi Francois,
>
> Have you been able to make progress with LXC?
>
> I just hit the "Could not find corresponding resource manager for lxc" issue too.
> This is with the RPMs from http://cloudstack.apt-get.eu/rhel/4.2/.
>
> It looks to me that the RPMs don't have LXC compiled in or are missing the required JAR dep.
>
> [root@csman2-1 ~]# rpm -ql cloudstack-management |grep hyperviso
> /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-hypervisor-baremetal-4.2.0.jar
> /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-hypervisor-kvm-4.2.0.jar
> /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-hypervisor-ovm-4.2.0.jar
> /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-hypervisor-ucs-4.2.0.jar
> /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-hypervisor-vmware-4.2.0.jar
> /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-hypervisor-xen-4.2.0.jar
>
>
> [root@csman2-1 ~]# cloudmonkey add cluster clustername=lxc hypervisor=lxc
> zoneid=2f328497-79bf-44dd-93a4-d5844b151437 podid=56b8baec-94f2-42b8-8483-3362c8bd0601
> clustertype=CloudManaged
> : Could not find corresponding resource manager for lxc
>
> [root@csman2-1 WEB-INF]# rpm -qa|grep cloudstack-
> cloudstack-management-4.2.0-1.el6.x86_64
> cloudstack-common-4.2.0-1.el6.x86_64
> cloudstack-awsapi-4.2.0-1.el6.x86_64
> cloudstack-cli-4.2.0-1.el6.x86_64
> cloudstack-usage-4.2.0-1.el6.x86_64
>
> [root@csman2-1 WEB-INF]# lsb_release -a
> LSB Version:    :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch
> Distributor ID: CentOS
> Description:    CentOS release 6.4 (Final)
> Release:        6.4
> Codename:       Final
> [root@csman2-1 WEB-INF]#


Looks like you already have a ticket open at https://issues.apache.org/jira/browse/CLOUDSTACK-4849.
I can see that the LxcServerDiscoverer beam is indeed loaded but still unable to add an LXC cluster.

2013-10-20 15:44:13,778 INFO  [utils.component.ComponentContext] (Timer-2:null) Configuring com.cloud.hypervisor.kvm.discoverer.LxcServerDiscoverer_EnhancerByCloudStack_42c0e23d
2013-10-20 15:44:17,508 INFO  [utils.component.ComponentContext] (Timer-2:null) Starting com.cloud.hypervisor.kvm.discoverer.LxcServerDiscoverer_EnhancerByCloudStack_42c0e23d

[root@csman2-1 ~]# grep -A 6 -B 6 -i lxc /usr/share/cloudstack-management/webapps/client/WEB-INF/classes/componentContext.xml
  <bean id="resourceDiscoverers" class="com.cloud.utils.component.AdapterList">
    <property name="Adapters">
      <list>
          <ref bean="XcpServerDiscoverer"/>
          <ref bean="SecondaryStorageDiscoverer"/>
          <ref bean="KvmServerDiscoverer"/>
          <ref bean="LxcServerDiscoverer"/>
          <ref bean="BareMetalDiscoverer"/>
          <ref bean="OvmDiscoverer"/>
      </list>
    </property>
  </bean>

Regards.

--
@shankerbalan

M: +91 98860 60539 | O: +91 (80) 67935867
shanker.balan@shapeblue.com | www.shapeblue.com | Twitter:@shapeblue
ShapeBlue Services India LLP, 22nd floor, Unit 2201A, World Trade Centre, Bangalore - 560 055

CloudStack Bootcamp Training on 27/28 November, Bangalore
http://www.shapeblue.com/cloudstack-training/




This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: LXC and Networking

Posted by Shanker Balan <sh...@shapeblue.com>.
On 10-Oct-2013, at 2:40 AM, Francois Gaudreault <fg...@cloudops.com> wrote:

> Thanks Phong about the networking answers. I will follow the KVM docs.
>
> Regarding the resource manager, we did compile the nonoss package on our own.  Are you saying we require an extra deps?

Hi Francois,

Have you been able to make progress with LXC?

I just hit the "Could not find corresponding resource manager for lxc" issue too.
This is with the RPMs from http://cloudstack.apt-get.eu/rhel/4.2/.

It looks to me that the RPMs don't have LXC compiled in or are missing the required JAR dep.

[root@csman2-1 ~]# rpm -ql cloudstack-management |grep hyperviso
/usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-hypervisor-baremetal-4.2.0.jar
/usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-hypervisor-kvm-4.2.0.jar
/usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-hypervisor-ovm-4.2.0.jar
/usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-hypervisor-ucs-4.2.0.jar
/usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-hypervisor-vmware-4.2.0.jar
/usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-hypervisor-xen-4.2.0.jar


[root@csman2-1 ~]# cloudmonkey add cluster clustername=lxc hypervisor=lxc
zoneid=2f328497-79bf-44dd-93a4-d5844b151437 podid=56b8baec-94f2-42b8-8483-3362c8bd0601
clustertype=CloudManaged
: Could not find corresponding resource manager for lxc

[root@csman2-1 WEB-INF]# rpm -qa|grep cloudstack-
cloudstack-management-4.2.0-1.el6.x86_64
cloudstack-common-4.2.0-1.el6.x86_64
cloudstack-awsapi-4.2.0-1.el6.x86_64
cloudstack-cli-4.2.0-1.el6.x86_64
cloudstack-usage-4.2.0-1.el6.x86_64

[root@csman2-1 WEB-INF]# lsb_release -a
LSB Version:    :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch
Distributor ID: CentOS
Description:    CentOS release 6.4 (Final)
Release:        6.4
Codename:       Final
[root@csman2-1 WEB-INF]#

Regards.
@shankerbalan

--
@shankerbalan

M: +91 98860 60539 | O: +91 (80) 67935867
shanker.balan@shapeblue.com | www.shapeblue.com | Twitter:@shapeblue
ShapeBlue Services India LLP, 22nd floor, Unit 2201A, World Trade Centre, Bangalore - 560 055

CloudStack Bootcamp Training on 27/28 November, Bangalore
http://www.shapeblue.com/cloudstack-training/




This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: LXC and Networking

Posted by Francois Gaudreault <fg...@cloudops.com>.
Thanks Phong about the networking answers. I will follow the KVM docs.

Regarding the resource manager, we did compile the nonoss package on our 
own.  Are you saying we require an extra deps?


-- 
Francois Gaudreault
Architecte de Solution Cloud | Cloud Solutions Architect
fgaudreault@cloudops.com
514-629-6775
- - -
CloudOps
420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


Re: LXC and Networking

Posted by Phong Nguyen <pn...@apache.org>.
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 <ch...@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
> > fgaudreault@cloudops.com
> > 514-629-6775
> > - - -
> > CloudOps
> > 420 rue Guy
> > Montréal QC  H3J 1S6
> > www.cloudops.com
> > @CloudOps_
> >
> >
>

Re: LXC and Networking

Posted by Chip Childers <ch...@sungard.com>.
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
> fgaudreault@cloudops.com
> 514-629-6775
> - - -
> CloudOps
> 420 rue Guy
> Montréal QC  H3J 1S6
> www.cloudops.com
> @CloudOps_
> 
>