[openstack-dev] [devstack] - suggested development workflow without ./rejoin-stack.sh ?
Timothy_Symanczyk at symantec.com
Mon May 2 22:24:07 UTC 2016
Thanks for asking this, I would also like to know what the “real” answer is.
But what I’ve found myself doing recently, since it was unwise to 100% count on rejoin-stack.sh, was to “do” everything via scripts and take periodic backups of same. You’re still only one power outage away from losing your state, but ideally a clean install and running the same scripts again could mostly recover. With that said most of what I’d been working on has a noop result if the same command is repeated multiple times (like “openstack role create”), so slowly appending to the script and just rerunning it in its entirety was a completely fine workflow. If you’re doing stuff where that’s not the case, this will not be a good solution.
From: Kevin Benton <kevin at benton.pub<mailto:kevin at benton.pub>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Monday, May 2, 2016 at 3:10 PM
To: "openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: [openstack-dev] [devstack] - suggested development workflow without ./rejoin-stack.sh ?
This patch removed the ./rejoin-stack.sh script: https://review.openstack.org/#/c/291453/
I relied on this heavily in my development VM which sees lots of restarts because of various things (VM becomes unresponsive in load testing, my laptop has a kernel panic, etc). Normally this was not a big deal because I could ./rejoin-stack.sh and pick up where I left off (all db objects, virtual interfaces, instance images, etc all intact).
Now am I correct in understanding that when this happens there is no way to restart the services in a simple manner without blowing away everything and starting over? Unless I'm missing some way to run ./stack.sh without losing previous state, this seems like a major regression (went from mostly working ./rejoin-stack.sh to nothing).
What is the recommended way to use devstack without being a power outage away from losing hours of work?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev