[libvirt-users] Failed to access console after launching LXC through libvirt
Hi, I'm trying to manage LXC instances through OpenStack, which use libvirt as a virtualization driver layer. After launching LXC instance, I simply could not attach to the console. virsh # list Id Name State ---------------------------------- 14366 instance-00000078 running virsh # console 14366 Connected to domain instance-00000078 Escape character is ^] And it keeps stuck here. Initially I thought it could be a cgroup device config issue, and tried to "echo ‘c 5:1 rwm'
/cgroup/devices/libvirt/lxc/instance-00000078/devices.allow“, to add /dev/console access right to the container. But it does not work, console stilll not working.
Before the cgroup tweaking, devices.list are as follows [root@localhost libvirt]# cat /cgroup/devices/libvirt/lxc/instance-0000007a/devices.list c 1:3 rwm c 1:5 rwm c 1:7 rwm c 1:8 rwm c 1:9 rwm c 5:0 rwm c 5:2 rwm c 136:* rwm I'm not quite sure what kind of issue could possibly cause this console access issue. Cause I'm now using two different guest OS templates on two different host OSes. Following are some symptoms I observed. * (g) for container guest OS * (h) for host OS * NOTE: Ubuntu guest os are generated by lxc-create -t ubuntu, which is an Ubuntu 12.04 based lxc template. CentOS guest os are handcrafted by myself, taking reference of http://wiki.1tux.org/wiki/Lxc/Installation/Guest/Centos/6 1. Ubuntu (g) launched by lxc-start on Ubuntu 12.04 host, console works 2. Ubuntu (g) launched by OpenStack / libvirt on Ubuntu 12.04 host, console works 3. Ubuntu (g) launched by OpenStack / libvirt on CentOS 6.3 host, console NOT works 4. CentOS (g) launched by lxc-start on Ubuntu 12.04 host, console works 5. CentOS (g) launched by OpenStack / libvirt on Ubuntu12.04 host, console NOT works 6. CentOS (g) launched by OpenStack / libvirt on CentOS 6.3 host, console NOT works So somehow I feel it could be something related to LXC template rootfs, but Host OS do make a difference (2 vs. 3). lxc-start / libvirt also makes a difference (4 vs. 5), but that might be caused by cgroup setting. Could someone shed me some clues to further digging this issue? Thanks! -- Qiu Yu
On Fri, Nov 9, 2012 at 12:09 AM, unicell <unicell@gmail.com> wrote:
Hi,
I'm trying to manage LXC instances through OpenStack, which use libvirt as a virtualization driver layer. After launching LXC instance, I simply could not attach to the console.
virsh # list Id Name State ---------------------------------- 14366 instance-00000078 running
virsh # console 14366 Connected to domain instance-00000078 Escape character is ^]
And it keeps stuck here.
Initially I thought it could be a cgroup device config issue, and tried to "echo ‘c 5:1 rwm'
/cgroup/devices/libvirt/lxc/instance-00000078/devices.allow“, to add /dev/console access right to the container. But it does not work, console stilll not working.
Before the cgroup tweaking, devices.list are as follows
[root@localhost libvirt]# cat /cgroup/devices/libvirt/lxc/instance-0000007a/devices.list
c 1:3 rwm c 1:5 rwm c 1:7 rwm c 1:8 rwm c 1:9 rwm c 5:0 rwm c 5:2 rwm c 136:* rwm
I'm not quite sure what kind of issue could possibly cause this console access issue. Cause I'm now using two different guest OS templates on two different host OSes. Following are some symptoms I observed.
* (g) for container guest OS * (h) for host OS * NOTE: Ubuntu guest os are generated by lxc-create -t ubuntu, which is an Ubuntu 12.04 based lxc template. CentOS guest os are handcrafted by myself, taking reference of http://wiki.1tux.org/wiki/Lxc/Installation/Guest/Centos/6
1. Ubuntu (g) launched by lxc-start on Ubuntu 12.04 host, console works 2. Ubuntu (g) launched by OpenStack / libvirt on Ubuntu 12.04 host, console works 3. Ubuntu (g) launched by OpenStack / libvirt on CentOS 6.3 host, console NOT works 4. CentOS (g) launched by lxc-start on Ubuntu 12.04 host, console works 5. CentOS (g) launched by OpenStack / libvirt on Ubuntu12.04 host, console NOT works 6. CentOS (g) launched by OpenStack / libvirt on CentOS 6.3 host, console NOT works
So somehow I feel it could be something related to LXC template rootfs, but Host OS do make a difference (2 vs. 3). lxc-start / libvirt also makes a difference (4 vs. 5), but that might be caused by cgroup setting.
Could someone shed me some clues to further digging this issue? Thanks!
-- Qiu Yu
For the "Ubuntu (g) launched by OpenStack / libvirt on CentOS 6.3 host", I also tried following command and console still not working. echo "a *.* rwm"
/cgroup/devices/libvirt/lxc/instance-00000078/devices.allow
More information attached. [root@localhost ~]# ls -l /home/stack/nova_state/instances/instance-00000078/rootfs/dev/tty* crw-rw-rw- 1 root tty 5, 0 Oct 23 20:01 /home/stack/nova_state/instances/instance-00000078/rootfs/dev/tty crw------- 1 root tty 4, 0 Oct 23 20:01 /home/stack/nova_state/instances/instance-00000078/rootfs/dev/tty0 crw------- 1 root tty 4, 1 Oct 23 20:01 /home/stack/nova_state/instances/instance-00000078/rootfs/dev/tty1 crw------- 1 root tty 4, 2 Oct 23 20:01 /home/stack/nova_state/instances/instance-00000078/rootfs/dev/tty2 crw------- 1 root tty 4, 3 Oct 23 20:01 /home/stack/nova_state/instances/instance-00000078/rootfs/dev/tty3 crw------- 1 root tty 4, 4 Oct 23 20:01 /home/stack/nova_state/instances/instance-00000078/rootfs/dev/tty4 crw------- 1 root tty 4, 5 Oct 23 20:01 /home/stack/nova_state/instances/instance-00000078/rootfs/dev/tty5 crw------- 1 root tty 4, 6 Oct 23 20:01 /home/stack/nova_state/instances/instance-00000078/rootfs/dev/tty6 crw------- 1 root tty 4, 7 Oct 23 20:01 /home/stack/nova_state/instances/instance-00000078/rootfs/dev/tty7 crw------- 1 root tty 4, 8 Oct 23 20:01 /home/stack/nova_state/instances/instance-00000078/rootfs/dev/tty8 crw------- 1 root tty 4, 9 Oct 23 20:01 /home/stack/nova_state/instances/instance-00000078/rootfs/dev/tty9 [root@localhost ~]# cat /cgroup/devices/libvirt/lxc/instance-00000078/devices.list c 1:3 rwm c 1:5 rwm c 1:7 rwm c 1:8 rwm c 1:9 rwm c 5:0 rwm c 5:2 rwm c 136:* rwm c 5:1 rwm c 5:* rwm a *:* rwm [root@localhost ~]# cat /etc/libvirt/lxc/instance-00000078.xml <!-- WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE OVERWRITTEN AND LOST. Changes to this xml configuration should be made using: virsh edit instance-00000078 or other application using the libvirt API. --> <domain type='lxc'> <name>instance-00000078</name> <uuid>55f225d1-e49c-4a51-9c17-0a5dde6d1917</uuid> <memory>524288</memory> <currentMemory>524288</currentMemory> <vcpu>2</vcpu> <os> <type arch='x86_64'>exe</type> <init>/sbin/init</init> <cmdline>console=ttyS0</cmdline> </os> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/libexec/libvirt_lxc</emulator> <filesystem type='mount' accessmode='passthrough'> <source dir='/home/stack/nova_state/instances/instance-00000078/rootfs'/> <target dir='/'/> </filesystem> <interface type='bridge'> <mac address='fa:16:3e:08:4f:b9'/> <source bridge='br100'/> <filterref filter='nova-instance-instance-00000078-fa163e084fb9'> <parameter name='DHCPSERVER' value='10.48.253.1'/> <parameter name='IP' value='10.48.253.2'/> <parameter name='PROJMASK' value='255.255.255.0'/> <parameter name='PROJNET' value='10.48.253.0'/> </filterref> </interface> <console type='pty'> <target type='lxc' port='0'/> </console> </devices> </domain> -- Qiu Yu
Quoting unicell (unicell@gmail.com):
On Fri, Nov 9, 2012 at 12:09 AM, unicell <unicell@gmail.com> wrote:
Hi,
I'm trying to manage LXC instances through OpenStack, which use libvirt as a virtualization driver layer. After launching LXC instance, I simply could not attach to the console.
virsh # list Id Name State ---------------------------------- 14366 instance-00000078 running
virsh # console 14366 Connected to domain instance-00000078 Escape character is ^]
And it keeps stuck here.
Initially I thought it could be a cgroup device config issue, and tried to "echo ‘c 5:1 rwm'
/cgroup/devices/libvirt/lxc/instance-00000078/devices.allow“, to add /dev/console access right to the container. But it does not work, console stilll not working.
Before the cgroup tweaking, devices.list are as follows
[root@localhost libvirt]# cat /cgroup/devices/libvirt/lxc/instance-0000007a/devices.list
c 1:3 rwm c 1:5 rwm c 1:7 rwm c 1:8 rwm c 1:9 rwm c 5:0 rwm c 5:2 rwm c 136:* rwm
I'm not quite sure what kind of issue could possibly cause this console access issue. Cause I'm now using two different guest OS templates on two
Just a few things to help you look around: Both lxc and libvirt-lxc provide consoles by creating a pty on the host and bind-mounting that onto /dev/ttyN in the guest before starting init. Ubuntu on the host passes 'container=lxc' (or 'container=libvirt') to the container, which tells ubuntu in the container to not do some things (look for 'container' in /etc/init/*; also things like mountall accept that they should not do some things in containers). You can investigate /dev/ttyN and /dev/console in your container by looking at the pid of init in the container, and looking at /proc/$pid/root/dev/{console,tty*} That *should* show 136:* devices, but I assume that in the cases where it is not working it will show 4:* for ttyN. If you look at cat /proc/$pid/root/proc/1/mounts I expect you'll see a /dev is mounted in the container. Which hides the bind mounts which (libvirt-)lxc has set up. -serge
On Fri, Nov 9, 2012 at 10:52 PM, Serge Hallyn <serge.hallyn@canonical.com>wrote:
On Fri, Nov 9, 2012 at 12:09 AM, unicell <unicell@gmail.com> wrote:
Hi,
I'm trying to manage LXC instances through OpenStack, which use
a virtualization driver layer. After launching LXC instance, I simply could not attach to the console.
virsh # list Id Name State ---------------------------------- 14366 instance-00000078 running
virsh # console 14366 Connected to domain instance-00000078 Escape character is ^]
And it keeps stuck here.
Initially I thought it could be a cgroup device config issue, and
Quoting unicell (unicell@gmail.com): libvirt as tried to
"echo ‘c 5:1 rwm'
/cgroup/devices/libvirt/lxc/instance-00000078/devices.allow“, to add /dev/console access right to the container. But it does not work, console stilll not working.
Before the cgroup tweaking, devices.list are as follows
[root@localhost libvirt]# cat /cgroup/devices/libvirt/lxc/instance-0000007a/devices.list
c 1:3 rwm c 1:5 rwm c 1:7 rwm c 1:8 rwm c 1:9 rwm c 5:0 rwm c 5:2 rwm c 136:* rwm
I'm not quite sure what kind of issue could possibly cause this console access issue. Cause I'm now using two different guest OS templates on two
Just a few things to help you look around:
Both lxc and libvirt-lxc provide consoles by creating a pty on the host and bind-mounting that onto /dev/ttyN in the guest before starting init.
Ubuntu on the host passes 'container=lxc' (or 'container=libvirt') to the container, which tells ubuntu in the container to not do some things (look for 'container' in /etc/init/*; also things like mountall accept that they should not do some things in containers).
You can investigate /dev/ttyN and /dev/console in your container by looking at the pid of init in the container, and looking at /proc/$pid/root/dev/{console,tty*}
That *should* show 136:* devices, but I assume that in the cases where it is not working it will show 4:* for ttyN. If you look at cat /proc/$pid/root/proc/1/mounts I expect you'll see a /dev is mounted in the container. Which hides the bind mounts which (libvirt-)lxc has set up.
-serge
Serge, you're right. In console not working environment, /dev is mounted inside container. As you pointed out, it hides what (libvirt-)lxc has set up and messed up with the conosle devices. Thank you so much for providing this clue, and I'll dig into upstart scripts to look at more. I doubt there're some difference in container set up logic in 'container=lxc' and 'container=lxc-libvirt' situation, which caused the /dev/ mounting issue. More information for your reference. As you can see, launching by lxc and launching by libvirt-lxc makes a big difference here. -- console working case (started by lxc-start) -- root@localhost:/var/lib/lxc/CN/rootfs/etc/init# cat /proc/10018/root/proc/1/mounts rootfs / rootfs rw 0 0 /dev/mapper/lxcvg-lxcimages / ext3 rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=ordered 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 sysfs /sys sysfs rw,relatime 0 0 devpts /dev/lxc/console devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 devpts /dev/lxc/tty1 devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 devpts /dev/lxc/tty2 devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 devpts /dev/lxc/tty3 devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 devpts /dev/lxc/tty4 devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=666 0 0 devpts /dev/ptmx devpts rw,relatime,mode=600,ptmxmode=666 0 0 none /proc/sys/fs/binfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime 0 0 none /sys/fs/fuse/connections fusectl rw,relatime 0 0 none /sys/kernel/debug debugfs rw,relatime 0 0 none /sys/kernel/security securityfs rw,relatime 0 0 none /run tmpfs rw,nosuid,noexec,relatime,size=378636k,mode=755 0 0 none /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0 none /run/shm tmpfs rw,nosuid,nodev,relatime 0 0 root@localhost:/var/lib/lxc/CN/rootfs/etc/init# ls -l /proc/10018/root/dev/{console,tty*} lrwxrwxrwx 1 root root 11 Nov 9 23:55 /proc/10018/root/dev/console -> lxc/console crw-rw-rw- 1 root tty 5, 0 Oct 23 20:40 /proc/10018/root/dev/tty crw------- 1 root tty 4, 0 Oct 23 20:01 /proc/10018/root/dev/tty0 lrwxrwxrwx 1 root root 8 Nov 9 23:55 /proc/10018/root/dev/tty1 -> lxc/tty1 lrwxrwxrwx 1 root root 8 Nov 9 23:55 /proc/10018/root/dev/tty2 -> lxc/tty2 lrwxrwxrwx 1 root root 8 Nov 9 23:55 /proc/10018/root/dev/tty3 -> lxc/tty3 lrwxrwxrwx 1 root root 8 Nov 9 23:55 /proc/10018/root/dev/tty4 -> lxc/tty4 crw------- 1 root tty 4, 5 Oct 23 20:01 /proc/10018/root/dev/tty5 crw------- 1 root tty 4, 6 Oct 23 20:01 /proc/10018/root/dev/tty6 crw------- 1 root tty 4, 7 Oct 23 20:01 /proc/10018/root/dev/tty7 crw------- 1 root tty 4, 8 Oct 23 20:01 /proc/10018/root/dev/tty8 crw------- 1 root tty 4, 9 Oct 23 20:01 /proc/10018/root/dev/tty9 console *NOT* working case (started by libvirt) -- [root@localhost instances]# cat /proc/2086/root/proc/1/mounts rootfs / rootfs rw 0 0 devpts /dev/pts devpts rw,relatime,gid=5,mode=620,ptmxmode=666 0 0 /dev/nbd14 / ext3 rw,relatime,errors=continue,user_xattr,acl,barrier=1,data=ordered 0 0 devpts /dev/pts devpts rw,relatime,gid=5,mode=620,ptmxmode=666 0 0 devfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0 <-- * /dev is mounted here * proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 proc /proc/sys proc ro,relatime 0 0 sysfs /sys sysfs ro,relatime 0 0 /dev/sda2 /selinux ext4 ro,relatime,barrier=1,data=ordered 0 0 devpts /dev/ptmx devpts rw,relatime,gid=5,mode=620,ptmxmode=666 0 0 [root@localhost instances]# ls -l /proc/2086/root/dev/{console,tty*} lrwxrwxrwx 1 root root 10 Nov 9 23:53 /proc/2086/root/dev/console -> /dev/pts/0 lrwxrwxrwx 1 root root 10 Nov 9 23:53 /proc/2086/root/dev/tty1 -> /dev/pts/0 -- Qiu Yu
Hey Qiu Yu, I am a beginner to both lxc and openstack swift. Can you please clarify some of my doubts related to openstack swift and lxc? On 8 November 2012 21:39, unicell <unicell@gmail.com> wrote:
Hi,
I'm trying to manage LXC instances through OpenStack, which use libvirt as a virtualization driver layer. After launching LXC instance, I simply could not attach to the console.
virsh # list Id Name State ---------------------------------- 14366 instance-00000078 running
virsh # console 14366 Connected to domain instance-00000078 Escape character is ^]
And it keeps stuck here.
Initially I thought it could be a cgroup device config issue, and tried to "echo ‘c 5:1 rwm'
/cgroup/devices/libvirt/lxc/instance-00000078/devices.allow“, to add /dev/console access right to the container. But it does not work, console stilll not working.
Before the cgroup tweaking, devices.list are as follows
[root@localhost libvirt]# cat /cgroup/devices/libvirt/lxc/instance-0000007a/devices.list
c 1:3 rwm c 1:5 rwm c 1:7 rwm c 1:8 rwm c 1:9 rwm c 5:0 rwm c 5:2 rwm c 136:* rwm
I'm not quite sure what kind of issue could possibly cause this console access issue. Cause I'm now using two different guest OS templates on two different host OSes. Following are some symptoms I observed.
* (g) for container guest OS * (h) for host OS * NOTE: Ubuntu guest os are generated by lxc-create -t ubuntu, which is an Ubuntu 12.04 based lxc template. CentOS guest os are handcrafted by myself, taking reference of http://wiki.1tux.org/wiki/Lxc/Installation/Guest/Centos/6
1. Ubuntu (g) launched by lxc-start on Ubuntu 12.04 host, console works 2. Ubuntu (g) launched by OpenStack / libvirt on Ubuntu 12.04 host, console works 3. Ubuntu (g) launched by OpenStack / libvirt on CentOS 6.3 host, console NOT works 4. CentOS (g) launched by lxc-start on Ubuntu 12.04 host, console works 5. CentOS (g) launched by OpenStack / libvirt on Ubuntu12.04 host, console NOT works 6. CentOS (g) launched by OpenStack / libvirt on CentOS 6.3 host, console NOT works
So somehow I feel it could be something related to LXC template rootfs, but Host OS do make a difference (2 vs. 3). lxc-start / libvirt also makes a difference (4 vs. 5), but that might be caused by cgroup setting.
Could someone shed me some clues to further digging this issue? Thanks!
-- Qiu Yu
------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
-- Best Regards, Sujay M Final year B.Tech Computer Engineering NITK Surathkal contact: +918971897571
Hey Qiu Yu, I am a beginner to both lxc and openstack swift. Can you please clarify some of my doubts related to openstack swift and lxc? 1. I want to set up a small cloud storage environment in my laptop. I mean i need to host storage services for some clients and i want to virtualize this environment. Is openstack swift enough for the above purpose or should i install nova, glance and swift? On 8 November 2012 22:10, Sujay M <sujay.m17@gmail.com> wrote:
Hey Qiu Yu,
I am a beginner to both lxc and openstack swift. Can you please clarify some of my doubts related to openstack swift and lxc?
On 8 November 2012 21:39, unicell <unicell@gmail.com> wrote:
Hi,
I'm trying to manage LXC instances through OpenStack, which use libvirt as a virtualization driver layer. After launching LXC instance, I simply could not attach to the console.
virsh # list Id Name State ---------------------------------- 14366 instance-00000078 running
virsh # console 14366 Connected to domain instance-00000078 Escape character is ^]
And it keeps stuck here.
Initially I thought it could be a cgroup device config issue, and tried to "echo ‘c 5:1 rwm'
/cgroup/devices/libvirt/lxc/instance-00000078/devices.allow“, to add /dev/console access right to the container. But it does not work, console stilll not working.
Before the cgroup tweaking, devices.list are as follows
[root@localhost libvirt]# cat /cgroup/devices/libvirt/lxc/instance-0000007a/devices.list
c 1:3 rwm c 1:5 rwm c 1:7 rwm c 1:8 rwm c 1:9 rwm c 5:0 rwm c 5:2 rwm c 136:* rwm
I'm not quite sure what kind of issue could possibly cause this console access issue. Cause I'm now using two different guest OS templates on two different host OSes. Following are some symptoms I observed.
* (g) for container guest OS * (h) for host OS * NOTE: Ubuntu guest os are generated by lxc-create -t ubuntu, which is an Ubuntu 12.04 based lxc template. CentOS guest os are handcrafted by myself, taking reference of http://wiki.1tux.org/wiki/Lxc/Installation/Guest/Centos/6
1. Ubuntu (g) launched by lxc-start on Ubuntu 12.04 host, console works 2. Ubuntu (g) launched by OpenStack / libvirt on Ubuntu 12.04 host, console works 3. Ubuntu (g) launched by OpenStack / libvirt on CentOS 6.3 host, console NOT works 4. CentOS (g) launched by lxc-start on Ubuntu 12.04 host, console works 5. CentOS (g) launched by OpenStack / libvirt on Ubuntu12.04 host, console NOT works 6. CentOS (g) launched by OpenStack / libvirt on CentOS 6.3 host, console NOT works
So somehow I feel it could be something related to LXC template rootfs, but Host OS do make a difference (2 vs. 3). lxc-start / libvirt also makes a difference (4 vs. 5), but that might be caused by cgroup setting.
Could someone shed me some clues to further digging this issue? Thanks!
-- Qiu Yu
------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
-- Best Regards,
Sujay M Final year B.Tech Computer Engineering NITK Surathkal
contact: +918971897571
-- Best Regards, Sujay M Final year B.Tech Computer Engineering NITK Surathkal contact: +918971897571
On Fri, Nov 9, 2012 at 12:52 AM, Sujay M <sujay.m17@gmail.com> wrote:
Hey Qiu Yu,
I am a beginner to both lxc and openstack swift. Can you please clarify some of my doubts related to openstack swift and lxc?
1. I want to set up a small cloud storage environment in my laptop. I mean i need to host storage services for some clients and i want to virtualize this environment. Is openstack swift enough for the above purpose or should i install nova, glance and swift?
Well, this might be kind of off topic to this list. Let me make it short. :) Swift is for object storage, similar to Amazon S3. While Nova-vol service (component inside Nova) is for block storage, similar to Amazon EBS. And in latest OpenStack Folsom release, nova volume has bee forked to openstack cinder project, to address the block storage functionality. While glance is for VM image service. So, it really depends on your needs, swift or cinder. Usually, cinder works together with nova. Swift is much more independent. -- Qiu Yu
Thanks Qiu Yu, I want object storage so I'll be using swift. Can i use lxc for virtualization in swift? How to do this? On 9 November 2012 06:33, unicell <unicell@gmail.com> wrote:
On Fri, Nov 9, 2012 at 12:52 AM, Sujay M <sujay.m17@gmail.com> wrote:
Hey Qiu Yu,
I am a beginner to both lxc and openstack swift. Can you please clarify some of my doubts related to openstack swift and lxc?
1. I want to set up a small cloud storage environment in my laptop. I mean i need to host storage services for some clients and i want to virtualize this environment. Is openstack swift enough for the above purpose or should i install nova, glance and swift?
Well, this might be kind of off topic to this list. Let me make it short. :)
Swift is for object storage, similar to Amazon S3. While Nova-vol service (component inside Nova) is for block storage, similar to Amazon EBS. And in latest OpenStack Folsom release, nova volume has bee forked to openstack cinder project, to address the block storage functionality. While glance is for VM image service.
So, it really depends on your needs, swift or cinder. Usually, cinder works together with nova. Swift is much more independent.
-- Qiu Yu
-- Best Regards, Sujay M Final year B.Tech Computer Engineering NITK Surathkal contact: +918971897571
On Fri, Nov 9, 2012 at 3:30 PM, Sujay M <sujay.m17@gmail.com> wrote:
Thanks Qiu Yu,
I want object storage so I'll be using swift. Can i use lxc for virtualization in swift? How to do this?
LXC can works together with openstack nova. You can find a simple instruction here: http://wiki.openstack.org/LXC -- Qiu Yu
participants (3)
-
Serge Hallyn -
Sujay M -
unicell