|
1 |
| -============================= |
2 |
| -Hardware Inventory Management |
3 |
| -============================= |
| 1 | +===================================== |
| 2 | +Bifrost Hardware Inventory Management |
| 3 | +===================================== |
4 | 4 |
|
5 |
| -At its lowest level, hardware inventory is managed in the Bifrost service. |
| 5 | +In most deployments, hardware inventory is managed by the Bifrost service. |
6 | 6 |
|
7 | 7 | Reconfiguring Control Plane Hardware
|
8 | 8 | ====================================
|
@@ -56,7 +56,9 @@ in Bifrost:
|
56 | 56 | | da0c61af-b411-41b9-8909-df2509f2059b | example-hypervisor-01 | None | power off | enroll | False |
|
57 | 57 | +--------------------------------------+-----------------------+---------------+-------------+--------------------+-------------+
|
58 | 58 |
|
59 |
| -After editing ``${KAYOBE_CONFIG_PATH}/overcloud.yml`` to add these new hosts to |
| 59 | +After editing ``${KAYOBE_CONFIG_PATH}/overcloud.yml`` (or |
| 60 | +``${KAYOBE_CONFIG_PATH}/environments/${KAYOBE_ENVIRONMENT}/overcloud.yml`` |
| 61 | +if Kayobe environment is used) to add these new hosts to |
60 | 62 | the correct groups, import them in Kayobe's inventory with:
|
61 | 63 |
|
62 | 64 | .. code-block:: console
|
@@ -138,7 +140,7 @@ migrate as the process needs manual confirmation. You can do this with:
|
138 | 140 |
|
139 | 141 | .. code-block:: console
|
140 | 142 |
|
141 |
| - openstack # openstack server resize confirm <instance-uuid> |
| 143 | + openstack# openstack server resize confirm <instance-uuid> |
142 | 144 |
|
143 | 145 | The symptom to look out for is that the server is showing a status of ``VERIFY
|
144 | 146 | RESIZE`` as shown in this snippet of ``openstack server show <instance-uuid>``:
|
|
0 commit comments