openvz supports virtual Ethernet 
device(http://wiki.openvz.org/Virtual_Ethernet_device), which acts as a normal 
Linux network device: you can add iptables/ipaddress etc on it. The current 
network model supported by Cloudstack should work on openvz.

> -----Original Message-----
> From: codeoedoc [mailto:codeoe...@gmail.com]
> Sent: Wednesday, June 20, 2012 6:42 PM
> To: Edison Su
> Cc: cloudstack-dev@incubator.apache.org
> Subject: Re: Status on cloudstack/openvz integration
> 
> Hi Edison,
> 
> In your previous post
> (http://sourceforge.net/mailarchive/message.php?msg_id=28028656), you
> mentioned four bullets on the support of openvz in cloudstack. Have
> you thought about the networking portion of the integration? Will it
> affect networking on the host, on the virtual router, as well as the
> security enforcement (security group)? Could you please provide some
> suggestions in this front?

> 
> Thanks,
> Xin
> 
> On Thu, Jun 21, 2012 at 4:26 AM, Edison Su <edison...@citrix.com> wrote:
> > Hi Xin,
> >   Not sure is there other people working on or having interest in
> integrating openvz with CloudStack? AFAIK, openvz is not in the roadmap
> yet.
> >
> >> -----Original Message-----
> >> From: Xin Liu [mailto:codeoe...@gmail.com]
> >> Sent: Wednesday, June 20, 2012 8:15 AM
> >> To: Edison Su
> >> Subject: Status on cloudstack/openvz integration
> >>
> >> Hi Edision,
> >>
> >> and am very interested in having openvz supported in cloudstack. I
> saw
> >> in the maillist:
> >> http://sourceforge.net/mailarchive/message.php?msg_id=28028656  that
> >> there might be official support from citrix.
> >>
> >> Would you please let me know if there is any status change on this
> new
> >> feature? Is it in the roadmap? If so, when will it be ready? I don't
> >> see it in github yet. Also, it seems in the maillist you mentioned
> >> openvz will be using local file system. Could you please confirm on
> >> this?
> >>
> >> I apologize for this abrupt email. I only found the above maillist
> and
> >> thought you might be the right person to ask.
> >>
> >> Thanks for your time.
> >> codeoedoc

Reply via email to