On Mon, Nov 24, 2014 at 11:15 AM, Edward HUANG <[email protected]> wrote: > Hi All, > I'm trying to install Openstack on a local server in my lab, and I use > devstack for the installation. > I use almost the default setting for local.conf. > And currently i encounter a problem, after I run unstack.sh, the volume > group created by stack.sh is deleted, as well as the backing file, and by > running rejoin-stack.sh, the cinder-volume cannot be restarted properly and > it reports no 'stack-volumes-lvmdriver-1' is found. > Seems to me that rejoin-stack.sh does not bring back the volume group. > So, what is the proper way to unstack.sh and then re-run Openstack to > preserve cinder storage properly? > > Best regards > Edward ZILONG HUANG > MS@ECE department, Carnegie Mellon University > http://www.andrew.cmu.edu/user/zilongh/ > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : [email protected] > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Oops.. didn't reply all I don't think:
Hi Edward, Correct, devstack uses non-persistent loopback files for Cinders VG by default and they go away on reboot. The only way to recreate in that situation is a clean stack.sh run. That being said there are two other options available to you: 1. Make the loopbacks persistent (not really worth it IMO) 2. Create a VG on your system using "real" disks and that way devstack will just use those and you'll save yourself jumping through these hoops. Thanks John _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : [email protected] Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
