이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 9. Rebooting the Overcloud
Some situations require a reboot of nodes in the undercloud and overcloud. The following procedures show how to reboot different node types. Be aware of the following notes:
- If rebooting all nodes in one role, it is advisable to reboot each node individually. This helps retain services for that role during the reboot.
- If rebooting all nodes in your OpenStack Platform environment, use the following list to guide the reboot order:
Recommended Node Reboot Order
- Reboot the director
- Reboot Controller nodes
- Reboot Ceph Storage nodes
- Reboot Compute nodes
- Reboot object Storage nodes
9.1. Rebooting the Director 링크 복사링크가 클립보드에 복사되었습니다!
링크 복사링크가 클립보드에 복사되었습니다!
To reboot the director node, follow this process:
- Reboot the node:
sudo reboot
$ sudo reboot
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Wait until the node boots.
When the node boots, check the status of all services:
sudo systemctl list-units "openstack*" "neutron*" "openvswitch*"
$ sudo systemctl list-units "openstack*" "neutron*" "openvswitch*"
Verify the existence of your Overcloud and its nodes:
source ~/stackrc nova list ironic node-list heat stack-list
$ source ~/stackrc
$ nova list
$ ironic node-list
$ heat stack-list