This command has never completely worked to restart DevStack.
It periodically prompts attempts to work around this brokenness
in ways that harm other functions. Let's finally remove it.
Requiring a complete re-run of DevStack after a reboot has always
been intentional.
TODO: follow-up cleaning all of the screen hackage if this merges.
Change-Id: I2f61bb69cc110468a91dcaa4ee7653ede7048467
Currently rejoin-stack.sh can not keep the same screen service tags
as the first you deploy openstack due to that the stack-screenrc lack
proper command to configure screen's hardstatus. just delete the old
stack-screenrc so that function screen_rc can write proper initialize
command into stack-screenrc.
fix bug 1182597
Change-Id: I4cb4c6ded93a5c7b0bd39d65a754ddf86553463d
stackrc loads localrc and localrc can use functions
like enable_service and disable_service. Make sure
the functions are defined before loading stackrc.
Change-Id: Ied7bbe0d228f252902cc491b8db0738c5071f06b
Signed-off-by: Doug Hellmann <doug.hellmann@dreamhost.com>
rejoin-stack.sh would not specify screen session name which will lead
unstack.sh unable to kill the screen session started by rejoin-stack.sh
after hypervisor rebooted. So specify the session name if
rejoin-stack.sh need to start a new sreen session.
fixes bug 1182806
Change-Id: I68635887aa82fa63f3667e0f090ea2836eec7b68
* Added screen_rc function in stack.sh to save started services to stack-screenrc file
* Added rejoin-stack.sh to rejoin the current screen session or start a new session
Change-Id: I381a7832bc8a107bfbd51c5ecfbd2e9134cf0a0a
blueprint: restart-services
Dean Troyer