+1
2013/8/21 Swapnil Kulkarni <swapnilkulkarni2...@gmail.com> > Hello, > > I think the cause is you are running stack.sh everytime you restart > devstack which clears the configuration. rejoin-stack.sh can help for your > cause. > > Before proceeding for running the script please associate the vg file with > a loop device with following command with root > > losetup /dev/loop2 /opt/stack/data/stack-volumes-backing-file > > Please use rejoin-stack.sh script located at your devstack installation > directory or /opt/stack/devstack > > Best Regards, > Swapnil Kulkarni > swapnilkulkarni2...@gmail.com > > > > On Wed, Aug 21, 2013 at 12:37 PM, Batsayan Das <batsayan....@tcs.com>wrote: > >> Hi, >> >> I launch the openstack by running stack.sh as mentioned in >> http://devstack.org/guides/single-machine.html >> >> I created some images and instances in devstack using dashboard. When I >> reboot Host machine and run stack.sh again, those images and instance got >> lost, and I am not able to see those images and instances that I already >> created using dashboard. >> >> My question is >> >> 1. Is this what is expected from host reboot? >> 2. What I need to do to retain images and instances between multiple host >> reboots. >> >> The thread >> http://www.mail-archive.com/openstack@lists.launchpad.net/msg08453.htmlsays >> to use the switch --start_guests_on_host_boot >> --resume_guests_state_on_host_boot. I am not sure how I should use these , >> which config files should have those switched enabled when I launch the >> devstack by simply running stack.sh >> >> I guess I need to pass some parameters or need to do **something** >> before running to stack.sh so that it does not destroy already crested >> instances and images. As I understand stack.sh reinitialize all the stuffs >> >> Looking for any help. >> >> Regards, >> Batsayan Das >> Tata Consultancy Services >> Mailto: batsayan....@tcs.com >> Website: http://www.tcs.com >> ____________________________________________ >> Experience certainty. IT Services >> Business Solutions >> Consulting >> ____________________________________________ >> >> =====-----=====-----===== >> Notice: The information contained in this e-mail >> message and/or attachments to it may contain >> confidential or privileged information. If you are >> not the intended recipient, any dissemination, use, >> review, distribution, printing or copying of the >> information contained in this e-mail message >> and/or attachments to it are strictly prohibited. If >> you have received this communication in error, >> please notify us by reply e-mail or telephone and >> immediately and permanently delete the message >> and any attachments. Thank you >> >> >> _______________________________________________ >> Mailing list: >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> Post to : openstack@lists.openstack.org >> Unsubscribe : >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> >> > > _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack@lists.openstack.org > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > > -- Lawrency Meng mail: mengql112...@gmail.com _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openst...@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
