Using blade servers with attached storage for compute nodes

asked 2013-03-28 10:39:29 -0600

ianrossi gravatar image

updated 2013-04-12 09:40:55 -0600

My question is similar to question 49 on this site, but not the same.

Background: We want to deploy Openstack on blade servers and use attached storage for ephemeral disks on the compute node. We also want to also deploy Cinder (volume storage) on a blade server in the same way, using attached storage also for persistent volumes.

I'm aware that you can specify LVM as the ephemeral disk (or image type) and specify the LVM group to be used (according to the Openstack documentation on nova.conf).

Question: Would we mount the attached storage as an LVM volume (in an LVM group) on the compute node host OS and then just specify that LVM volume using libvirt_images_volume_group=GROUPNAME in nova.conf?

edit retag flag offensive close merge delete


Are you interested in live migration also ? This may change the approach you want to take.

tim-bell gravatar imagetim-bell ( 2013-03-28 13:10:39 -0600 )edit

1 answer

Sort by ยป oldest newest most voted

answered 2013-04-12 08:22:42 -0600

gfidente gravatar image

If I understand correctly the question, you want to use the attched storage available on the Compute nodes to host the live VMs images (ephemeral storage).

If you do not share the attached storage shared between the nodes, you can achieve it by:

  • mounting the local storage under the libvirt's storage pool mountpoint
  • setup the local storage as an LVM vg and then configure libvirt_images_type=lvm and libvirt_images_volume_group=GROUPNAME

If you do share the attached storage between the nodes, the only option I see is:

  • a shared/distributed file system, like gluster or ceph, mounted under the libvirt's storage pool mountpoint
edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools



Asked: 2013-03-28 10:39:29 -0600

Seen: 690 times

Last updated: Apr 12 '13