Right now the intention is to work just like any other hypervisor: using VLAN or perhaps VxLAN/GRE for isolation. Live migration isn’t possible, but fast restart should be possible as long as shared storage is used. Some of the more interesting use cases are : web tier on LXC, app tier on hypervisor and DB tier on baremetal.
Of course a single LXC container on a single host should be equivalent to baremetal. From: Rohit Yadav <bhais...@apache.org<mailto:bhais...@apache.org>> Reply-To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" <dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>> Date: Tuesday, April 29, 2014 at 12:07 PM To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" <dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>> Subject: Re: [DISCUSS] LXC systemvm On Tue, Apr 29, 2014 at 11:54 PM, Chiradeep Vittal < chiradeep.vit...@citrix.com<mailto:chiradeep.vit...@citrix.com>> wrote: Hi, I was playing around with LXC and I think I have the systemvm build figured out. Currently [1] the LXC system requires a KVM/Xen-based systemvm. w00t! I¹ve tried this out on Ubuntu 14.04 (trusty) Download these 2 files: create-lxc-systemvm.sh https://gist.github.com/chiradeep/11388262 provision.rb https://gist.github.com/chiradeep/11407727#file-provision-rb Execute: ./create-lxc-systemvm.sh The Ruby script called by the shell script is used to ssh into a minimal lxc wheezy container. * Downloads a modified OEpostinstall.sh¹ from https://gist.github.com/chiradeep/11388137 This is modified from http://goo.gl/28QYa2 * Executes the postinstall script. Then the shell script tars up the rootfs. What¹s missing is fixes to cloud-early-config. This should be much easier than for other hypervisors since the host has write access to /var/cache/cmdline inside the container. I guess this is too late for 4.4, but worthwhile for 4.5. Comments? This looks great, Chiradeep can you share with us how the networking will work in case of using systemvms in LXC containers, how it will communicate with outside world and with other instances running in shared/separate LXC containers. Will we need a loadbalancer (like nginx) for reverse proxying and example or use case of a infra deployment. Lastly, will we have feature of moving containers across machines and some distributed locking service that the systemvms or agent may implement? Regards. [1] https://cwiki.apache.org/confluence/x/oJNMAg
