Installing VIM Overcloud

The following image displays the processes in the Overcloud installation and configuration:

Prerequisites

Ensure you are logged into the NPS toolkit VM as the root user.
Before installing the VIM Overcloud, ensure that the VIM Undercloud is in the CONFIGURED state.

Procedure

To upload and check the status of Overcloud images to Undercloud Glance, run the following commands.

To upload the Overcloud images, run the following command:
```
nps deploy -s  vim_overcloud -a create-images
```
To check the status of the create-images operation, run the following command:
```
nps show --data vim --node overcloud
```
Wait until the status is displayed as IMAGES_UPLOADED or IMAGES_UPLOAD_FAILED.

If the state is displayed as IMAGES_UPLOADED, log in to the Undercloud VM and view the list of Overcloud images that are uploaded using the following command:

source stackrc
openstack image list

Following is a sample output:

(undercloud) [stack@undercloud ~]$ openstack image list
+--------------------------------------+------------------------+--------+
| ID                                   | Name                   | Status |
+--------------------------------------+------------------------+--------+
| 6babb582-a5f4-4827-b9f8-b30484dfaf69 | bm-deploy-kernel       | active |
| 08ee9350-02f5-4217-8027-4d0ab7e60636 | bm-deploy-ramdisk      | active |
| 8b692ee3-3f51-47ed-9223-0a6077c957a5 | overcloud-full         | active |
| 6d10c6ec-6599-438d-b718-003cce8a18df | overcloud-full-initrd  | active |
| 035635f7-5f67-485a-8907-5c7d62f5818a | overcloud-full-vmlinuz | active |
+--------------------------------------+------------------------+--------+

If the state is displayed as IMAGES_UPLOAD_FAILED, analyze the nps-rhosp-<topology_name>-ansible.log and the nps-rhosp-cli-<topology_name>-date.log files in the /var/nps/logs/<topology_name>/ directory of the NPS toolkit VM. Based on the log files, complete the corrective actions.
To perform the create-images operation again, run the following command:
```
nps deploy -s vim_undercloud -a create-images
```

To configure and check the Undercloud VM as a local repository for the container images, run the following command:
1. To configure the Undercloud VM, run the following command:
```
nps deploy -s  vim_overcloud -a create-registry
```
2. To check the status of the create-registry operation, run the following command:
```
nps show --data vim --node overcloud
```
  Wait until the status is displayed as REGISTRY_CONFIGURED or REGISTRY_CONFIGURATION_FAILED.
  - If the state is displayed as REGISTRY_CONFIGURATION_FAILED, analyze the nps-rhosp-<topology_name>-ansible.log and the nps-rhosp-cli-<topology_name>-date.log files in the /var/nps/logs/<topology_name>/ directory of the NPS toolkit VM. Based on the log files, complete the corrective actions.
  - To perform the create-registry operation again, run the command:
    nps deploy -s vim_overcloud -a create-registry

To create or update and check flavors operation:

To create or update flavors, run the following command:
```
nps deploy -s  vim_overcloud -a update-flavors
```

To check the status of the update-flavors operation, run the following command:

nps show --data vim --node overcloud

Wait until the status is displayed as FLAVORS_UPDATED or FLAVOR_UPDATE_FAILED.

If the state is displayed as FLAVORS_UPDATED, log in to the Undercloud VM and verify that the flavors are created in the Undercloud using the following command:

source stackrc
openstack flavor list

Following is a sample output:

(undercloud) [stack@undercloud ~]$ openstack flavor list
+--------------------------------------+---------------------+------+------+-----------+-------+-----------+
| ID                                   | Name                |  RAM | Disk | Ephemeral | VCPUs | Is Public |
+--------------------------------------+---------------------+------+------+-----------+-------+-----------+
| 1f26187e-800e-42f4-97cc-e6ec5251cf32 | block-storage       | 4096 |   40 |         0 |     1 | True      |
| 2726082b-7667-4111-9f5c-6f1780d1c371 | controller          | 4096 |   40 |         0 |     4 | True      |
| 2cb189f1-e72b-439e-9d39-fc1069c45afd | computeovsdpdksriov | 4096 |   40 |         0 |     4 | True      |
| 368beec5-ebc4-4988-85b1-8938e97e4e04 | baremetal           | 4096 |   40 |         0 |     1 | True      |
| 5045d1b3-8cb2-4116-af42-36d816af4fd2 | control             | 4096 |   40 |         0 |     1 | True      |
| c649261e-c4af-489b-bc4f-10d0369a35a6 | swift-storage       | 4096 |   40 |         0 |     1 | True      |
| c9865ed7-6c92-417e-bc19-a64e4610d3c7 | compute             | 4096 |   40 |         0 |     1 | True      |
| e5dc2311-9907-442f-ae0d-3dd731f61bc2 | ceph-storage        | 4096 |   40 |         0 |     1 | True      |
+--------------------------------------+---------------------+------+------+-----------+-------+-----------+

If the state is displayed as FLAVOR_UPDATE_FAILED, analyze the nps-rhosp-<topology_name>-ansible.log and the nps-rhosp-cli-<topology_name>-date.log files in the /var/nps/logs/<topology_name>/ directory of the NPS toolkit VM. Based on the log files, complete the corrective actions.
To perform the update-flavors operation again, run the following command:
```
nps deploy -s vim_overcloud -a update-flavors
```

To register and verify the nodes to the Ironic service:

To register the nodes to the Ironic service, run the following command:
```
nps deploy -s  vim_overcloud -a register-nodes
```

To check the status of the register-nodes operation, run the following command:

nps show --data vim --node overcloud

Wait until the status is displayed as NODES_REGISTERED, NODES_REGISTER_PARTIAL, or NODES_REGISTER_FAILED.

If the state is displayed as NODES_REGISTERED, log in to the Undercloud VM and verify that the nodes are registered with the Ironic service using the following command:

source stackrc
openstack baremetal node list

Following is a sample output:

(undercloud) [stack@undercloud ~]$ openstack baremetal node list
+--------------------------------------+------+---------------+-------------+--------------------+-------------+
| UUID                                 | Name | Instance UUID | Power State | Provisioning State | Maintenance |
+--------------------------------------+------+---------------+-------------+--------------------+-------------+
| 8b3ce097-176d-486a-b2bf-ad7af7d2a2a1 | None | None          | power off   | manageable         | False       |
| 06f6c3b8-7fea-4913-808b-35bb6673e493 | None | None          | power off   | manageable         | False       |
| 8efd9a86-baea-401c-99ff-8ad42492fdcf | None | None          | power off   | manageable         | False       |
| 06a624df-dde2-4b5f-be52-8f39f364fce0 | None | None          | power off   | manageable         | False       |
| 91295ecd-926d-4a64-be16-6ef3bff1d6f6 | None | None          | power off   | manageable         | False       |
| f11877fd-c986-4414-aa64-8322b0c6e4ff | None | None          | power off   | manageable         | False       |
| c2ed263d-c31d-4051-b0bd-f0acd36e90d6 | None | None          | power off   | manageable         | False       |
| 67c3f9dd-6e12-4e2c-b178-dbf503099f98 | None | None          | power off   | manageable         | False       |
+--------------------------------------+------+---------------+-------------+--------------------+-------------+

If the state is displayed as NODES_REGISTER_PARTIAL or NODES_REGISTER_FAILED, analyze the nps-rhosp-<topology_name>-ansible.log and the nps-rhosp-cli-<topology_name>-date.log files in the /var/nps/logs/<topology_name>/ directory of the NPS toolkit VM. Based on the log files, complete the corrective actions.
NOTE:
For more details, see Improper Registration of the Nodes.
To perform the register-nodes operation again, run the following command:
```
nps deploy -s vim_overcloud -a register-nodes
```

To introspect and check the registered nodes:

To introspect the registered nodes, run the following command:
```
nps deploy -s  vim_overcloud -a introspect-nodes
```

To check the status of the introspect-nodes operation, run the following command:

nps show --data vim --node overcloud

Wait until the status is displayed as NODES_INTROSPECTED, NODES_INTROSPECTED_PARTIAL, or NODES_INTROSPECTION_FAILED.

If the state is displayed as NODES_INTROSPECTED, log in to the Undercloud VM and verify that the nodes are introspected using the following command:

source stackrc
openstack baremetal introspection list

Following is a sample output:

(undercloud) [stack@undercloud ~]$ openstack baremetal introspection list
+--------------------------------------+---------------------+---------------------+-------+
| UUID                                 | Started at          | Finished at         | Error |
+--------------------------------------+---------------------+---------------------+-------+
| 67c3f9dd-6e12-4e2c-b178-dbf503099f98 | 2020-05-27T06:58:07 | 2020-05-27T07:04:21 | None  |
| c2ed263d-c31d-4051-b0bd-f0acd36e90d6 | 2020-05-27T06:58:06 | 2020-05-27T07:05:50 | None  |
| 06a624df-dde2-4b5f-be52-8f39f364fce0 | 2020-05-27T06:58:03 | 2020-05-27T07:04:19 | None  |
| f11877fd-c986-4414-aa64-8322b0c6e4ff | 2020-05-27T06:58:02 | 2020-05-27T07:02:18 | None  |
| 91295ecd-926d-4a64-be16-6ef3bff1d6f6 | 2020-05-27T06:58:00 | 2020-05-27T07:04:17 | None  |
| 8efd9a86-baea-401c-99ff-8ad42492fdcf | 2020-05-27T06:57:55 | 2020-05-27T07:05:21 | None  |
| 06f6c3b8-7fea-4913-808b-35bb6673e493 | 2020-05-27T06:57:49 | 2020-05-27T07:02:29 | None  |
| 8b3ce097-176d-486a-b2bf-ad7af7d2a2a1 | 2020-05-27T06:57:43 | 2020-05-27T07:02:23 | None  |
+--------------------------------------+---------------------+---------------------+-------+

If the state is displayed as NODES_INTROSPECTED_PARTIAL or NODES_INTROSPECTION_FAILED, analyze the nps-rhosp-<topology_name>-ansible.log and the nps-rhosp-cli-<topology_name>-date.log files in the /var/nps/logs/<topology_name>/ directory of the NPS toolkit VM. Based on the log files, complete the corrective actions.
To perform the introspect-nodes operation again, see Node introspection fails with clean failed message.

To tag and check the nodes with the appropriate profiles:

To tag the nodes with the appropriate profiles, run the following command:
```
nps deploy -s  vim_overcloud -a tag-nodes
```

To check the status of the tag-nodes operation, run the following command:

nps show --data vim --node overcloud

Wait until the status is displayed as PROFILES_UPDATED, PROFILES_UPDATED_PARTIAL, or PROFILES_UPDATE_FAILED.

If the state is displayed as PROFILES_UPDATED, log in to the Undercloud VM and verify that the profiles are updated using the following command:

source stackrc
openstack overcloud profiles list

Following is a sample output:

(undercloud) [stack@undercloud ~]$ openstack overcloud profiles list
+--------------------------------------+-----------+-----------------+---------------------+-------------------+
| Node UUID                            | Node Name | Provision State | Current Profile     | Possible Profiles |
+--------------------------------------+-----------+-----------------+---------------------+-------------------+
| 8b3ce097-176d-486a-b2bf-ad7af7d2a2a1 |           | available       | ceph-storage        |                   |
| 06f6c3b8-7fea-4913-808b-35bb6673e493 |           | available       | ceph-storage        |                   |
| 06a624df-dde2-4b5f-be52-8f39f364fce0 |           | available       | controller          |                   |
| 91295ecd-926d-4a64-be16-6ef3bff1d6f6 |           | available       | controller          |                   |
| f11877fd-c986-4414-aa64-8322b0c6e4ff |           | available       | ceph-storage        |                   |
| 67c3f9dd-6e12-4e2c-b178-dbf503099f98 |           | available       | controller          |                   |
| fac59932-eac4-4893-8f6f-0d19290af73d |           | available       | computeovsdpdksriov |                   |
| 8876265c-3e75-4f5c-871f-eb118ff0122e |           | available       | computeovsdpdksriov |                   |
+--------------------------------------+-----------+-----------------+---------------------+-------------------+
(undercloud) [stack@undercloud ~]$

If the state is displayed as PROFILES_UPDATED_PARTIAL or PROFILES_UPDATE_FAILED, analyze the nps-rhosp-<topology_name>-ansible.log and the nps-rhosp-cli-<topology_name>-date.log files in the /var/nps/logs/<topology_name>/ directory of the NPS toolkit VM. Based on the log files, complete the corrective actions.
To perform the tag-nodes operation again, run the following command:
```
nps deploy -s vim_overcloud -a tag-nodes
```

To create and verify the Overcloud installation templates
1. To create the Overcloud installation templates, run the following command:
```
nps deploy -s  vim_overcloud -a create-templates
```
2. To check the status of the create-templates operation, run the following command:
```
nps show --data vim --node overcloud
```
  Wait until the status is displayed as TEMPLATES_CREATED or TEMPLATES_CREATION_FAILED.
  - If the state is displayed as TEMPLATES_CREATED, log in to the Undercloud VM and verify that the templates are created by executing the following command:
```
cd /home/stack/templates
```
    Verify that the templates are available in the /home/stack/templates directory.
  - If the state is displayed as TEMPLATES_CREATION_FAILED, analyze the nps-rhosp-<topology_name>-ansible.log and the nps-rhosp-cli-<topology_name>-date.log files in the /var/nps/logs/<topology_name>/ directory of the NPS toolkit VM. Based on the log files, complete the corrective actions.
  - To perform the create-templates operation again, run the following command:
```
nps deploy -s vim_overcloud -a create-templates
```
To install and check Overcloud.
1. To install Overcloud, run the following command:
```
nps deploy -s  vim_overcloud -a overcloud-install
```
2. To check the status of the overcloud-install operation, run the following command:
```
nps show --data vim --node overcloud
```
  Wait until the status is displayed as OVERCLOUD_INSTALLED or OVERCLOUD_INSTALL_FAILED.
  - If the state is displayed as OVERCLOUD_INSTALLED, from the Undercloud VM, record the administrator user name (OS_USERNAME) and the administrator password (OS_PASSWORD) from the /home/stack/overcloudrc file. Record the URL of the dashboard from the /home/stack/overcloudrc/overcloud_install.log file.
  - Open the Overcloud dashboard URL in a browser and log in using the administrator user name and password. Verify that all the services are running.
  - If the state is displayed as OVERCLOUD_INSTALL_FAILED, analyze the following log files:
    - The nps-rhosp-<topology_name>-ansible.log and the nps-rhosp-cli-<topology_name>-date.log files in the /var/nps/logs/<topology_name>/ directory of the NPS toolkit VM.
    - The overcloud-install.log file in the /home/stack/ directory in the Undercloud VM.
    Based on the log files, complete the corrective actions.
  - To perform the overcloud-install operation again, see Overcloud installation fails.