openstack/training-labs
Code Issues Proposed changes
9aae759289
training-labs/oslabs/osbash/scripts/shutdown_controller.sh

33 lines
1.1 KiB
Bash
Raw Normal View History

labs: add script to shut down controller node Add a single-purpose script to shut down the controller node from another node. Change-Id: Ic70e211a8fd3e8ad4c448045b65000be209b00de
2014-10-06 10:43:02 +02:00
#!/usr/bin/env bash
set -o errexit -o nounset
labs: make TOP_DIR more robust with blanks in path Make TOP_DIR more robust when blanks are part of the TOP_DIR path. Change-Id: I868e3406f358da24049d1e1bdbb4a8197f294a63
2015-03-15 11:29:48 +01:00
TOP_DIR=$(cd "$(dirname "$0")/.." && pwd)
labs: add script to shut down controller node Add a single-purpose script to shut down the controller node from another node. Change-Id: Ic70e211a8fd3e8ad4c448045b65000be209b00de
2014-10-06 10:43:02 +02:00
source "$TOP_DIR/config/paths"
source "$LIB_DIR/functions.guest"
indicate_current_auto
exec_logfile
labs: sleep in shutdown_controller.sh After building the cluster with the two additional snapshots on the controller VM, we end up with a dying nova-compute service. Sleeping 2+ seconds after booting into compute and before rebooting controller fixes the problem: nova-compute keeps running and its status in nova-manage service list will go to XXX and back to :-) without user intervention. Change-Id: I8ba20c77392b0966d6febfc300790cf1943f2ad5
2014-11-24 09:00:07 +01:00
# At this point in the cluster build, we just rebooted the compute VM to take
# a snapshot, and we are about to reboot the controller node for the same
# purpose.
#
# About a minute after we reboot the controller, the status of nova-compute
# (according to nova-manage service list) becomes "XXX".
#
# If we sleep for 2 seconds now, before rebooting the controller, the
# nova-compute service on the compute node will keep running and the status
# will automatically return to ":-)" after some time (may take several
# minutes). If we don't sleep here, the nova-compute service on compute will
# die within a few minutes (needs manual service restart or a compute node
# reboot).
sleep 2
labs: add script to shut down controller node Add a single-purpose script to shut down the controller node from another node. Change-Id: Ic70e211a8fd3e8ad4c448045b65000be209b00de
2014-10-06 10:43:02 +02:00
labs: sleep in shutdown_controller.sh After building the cluster with the two additional snapshots on the controller VM, we end up with a dying nova-compute service. Sleeping 2+ seconds after booting into compute and before rebooting controller fixes the problem: nova-compute keeps running and its status in nova-manage service list will go to XXX and back to :-) without user intervention. Change-Id: I8ba20c77392b0966d6febfc300790cf1943f2ad5
2014-11-24 09:00:07 +01:00
echo "Shutting down the controller node."
labs: add script to shut down controller node Add a single-purpose script to shut down the controller node from another node. Change-Id: Ic70e211a8fd3e8ad4c448045b65000be209b00de
2014-10-06 10:43:02 +02:00
ssh \
-o "UserKnownHostsFile /dev/null" \
-o "StrictHostKeyChecking no" \
Modifies osbash files to use osbash ssh keys This patch makes use of the osbash public and private keys to ssh to VM rather than the vagrant keys. This also removes the vagrant keys directory from the repository. Change-Id: I939274f188a02469c7e2cf9f9502510ea00d514e
2015-02-24 17:53:40 +05:30
-i "$HOME/.ssh/osbash_key" \
labs: add script to shut down controller node Add a single-purpose script to shut down the controller node from another node. Change-Id: Ic70e211a8fd3e8ad4c448045b65000be209b00de
2014-10-06 10:43:02 +02:00
controller-mgmt \
sudo /sbin/shutdown -P now
Copy Permalink