openstack/kayobe
Code Issues Proposed changes

Fix Bifrost database backup instructions

Browse Source 
Bifrost uses a combined Ironic service instead of API and conductor
services since the Yoga release [1].

[1] https://review.opendev.org/c/openstack/bifrost/+/820390

Change-Id: I80a7ea06620c69ff2ba2ab8fe78b990ef3c151ec
This commit is contained in:
Pierre Riteau 2024-04-04 12:41:06 +02:00
parent b87ac863ae
commit 449fc91986
1 changed files with 4 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/source/administration/seed.rst
View File

@ -113,8 +113,7 @@ Backup
It should be safe to keep services running during the backup, but for maximum
safety they may optionally be stopped::
docker exec -it bifrost_deploy \
systemctl stop ironic-api ironic-conductor ironic-inspector
docker exec -it bifrost_deploy systemctl stop ironic ironic-inspector
Then, to perform the backup::
@ -123,8 +122,7 @@ Then, to perform the backup::
If the services were stopped prior to the backup, start them again::
docker exec -it bifrost_deploy \
systemctl start ironic-api ironic-conductor ironic-inspector
docker exec -it bifrost_deploy systemctl start ironic ironic-inspector
Restore
^^^^^^^
@ -132,8 +130,7 @@ Restore
Prior to restoring the database, the Ironic and Ironic Inspector services
should be stopped::
docker exec -it bifrost_deploy \
systemctl stop ironic-api ironic-conductor ironic-inspector
docker exec -it bifrost_deploy systemctl stop ironic ironic-inspector
The database may then safely be restored::
@ -142,8 +139,7 @@ The database may then safely be restored::
Finally, start the Ironic and Ironic Inspector services again::
docker exec -it bifrost_deploy \
systemctl start ironic-api ironic-conductor ironic-inspector
docker exec -it bifrost_deploy systemctl start ironic ironic-inspector
Running Commands
================