Hi:
Recently I have some study on linux container(lxc), which is a light
weight OS level
virtualization.
With the previous knowledge of tapdisk, I have an assumption that, I may
could
use the vhd for each container to seperate the storage of all containers, or
even in
later days, vhd is stored in distributed storage, container could be migrated.
Build filesystem on tapdev and mount it under some directory, put the
rootfs of
container into that dir, and start the lxc, I haven''t try this, will
try later.
I post my idea here, hope someone has one forsee comments.
Thanks.
--_03bf71ed-babc-49bf-a771-6d6657d47ac6_
Content-Type: text/html; charset="gb2312"
Content-Transfer-Encoding: 8bit
<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:微软雅黑
}
--></style></head>
<body class=''hmmessage''><div
dir=''ltr''>
Hi:<BR>
<BR>
Recently I have some study on
linux container(lxc), which is a light weight OS level<BR>
virtualization.<BR>
<BR>
With the previous knowledge of tapdisk,
I have an assumption that, I may could<BR>
use the vhd for each container to seperate the storage of all containers, or
even in <BR>
later days, vhd is stored in distributed storage, container could be
migrated.<BR>
<BR>
Build filesystem on tapdev
and mount it under some directory, put the rootfs of <BR>
container into that dir, and start the lxc, I haven''t try this, will
try later.<BR>
<BR>
I post my idea here, hope someone has
one forsee comments.<BR>
<BR>
Thanks.<BR>
<BR>
</div></body>
</html>
--_03bf71ed-babc-49bf-a771-6d6657d47ac6_--
--===============6119489830975497569=Content-Type: text/plain;
charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
--===============6119489830975497569==--
On Sat, Jan 07, 2012 at 12:17:23PM +0800, MaoXiaoyun wrote:> > Hi: > > Recently I have some study on linux container(lxc), which is a light weight OS level > virtualization. > > With the previous knowledge of tapdisk, I have an assumption that, I may could > use the vhd for each container to seperate the storage of all containers, or even in > later days, vhd is stored in distributed storage, container could be migrated. > > Build filesystem on tapdev and mount it under some directory, put the rootfs ofHow would you "mount" a tapdev filesystem? But more interestingly, how would you migrate your tap disk? Is it on NFS or OCFS2 or iSCSI? If so, why not just expand the filesystem on an iSCSI disk and mount it on other machines and "migrate it".> container into that dir, and start the lxc, I haven''t try this, will try later.I am not really sure how one would freeze and migrate the processes? Does the cgroups have that functionality?> > I post my idea here, hope someone has one forsee comments. > > Thanks. >> _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel
在 2012-1-10，0:09，Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>> On Sat, Jan 07, 2012 at 12:17:23PM +0800, MaoXiaoyun wrote: >> >> Hi: >> >> Recently I have some study on linux container(lxc), which is a light weight OS level >> virtualization. >> >> With the previous knowledge of tapdisk, I have an assumption that, I may could >> use the vhd for each container to seperate the storage of all containers, or even in >> later days, vhd is stored in distributed storage, container could be migrated. >> >> Build filesystem on tapdev and mount it under some directory, put the rootfs of > > How would you "mount" a tapdev filesystem?When a tapdisk starts,there is a tapdev device under /dev/tapdevX, X is sth like a,b,c,... . Mkfs.ext3 on this device and mount it to /mnt/tapdevX, finally bind mount to LXC .> > But more interestingly, how would you migrate your tap disk? Is it on NFS or OCFS2 > or iSCSI? If so, why not just expand the filesystem on an iSCSI disk and mount it > on other machines and "migrate it".We have hadoop for the storage, VHD in HDFS is logical, which can,t directly mounted.> >> container into that dir, and start the lxc, I haven't try this, will try later. > > I am not really sure how one would freeze and migrate the processes? Does the > cgroups have that functionality? >Close local tapdisk, start it on remote host, reopen the VHD on HDFS. lxc supports supports freeze the processes in container, i,m not sure, wehther live migrate could be implemented in future. Thanks.>> >> I post my idea here, hope someone has one forsee comments. >> >> Thanks. >> > >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Apparently Analagous Threads
- BLKTAPCTRL[2375]: blktapctrl_linux.c:86: blktap0 open failed
- [PATCH 00 of 18] [v2] tools: fix bugs and build errors triggered by -O2 -Wall -Werror
- [PATCH] blktap2: fix makefile of vhd for parallel make
- [PATCH 1/2] 4.1.2 blktap2 cleanup fixes.
- [Q] VmError: Disk isn''t accessible with tap2:tapdisk:vhd