Appendix A. Deployment migration options

Prerequisites

1. Check the stores that are available through the Image service by using the glance stores-info command. In the following example, three stores are available: central, dcn1, and dcn2. These correspond to glance stores at the central location and edge sites, respectively:

     $ glance stores-info
     +----------+----------------------------------------------------------------------------------+
     | Property | Value                                                                            |
     +----------+----------------------------------------------------------------------------------+
     | stores   | [{"default": "true", "id": "central", "description": "central rbd glance         |
     |          | store"}, {"id": "dcn0", "description": "dcn0 rbd glance store"},                 |
     |          | {"id": "dcn1", "description": "dcn1 rbd glance store"}]                          |
     +----------+----------------------------------------------------------------------------------+

1. Add the desired subnets to undercloud.conf as shown in Configuring routed spine-leaf in the undercloud.
2. Re-run the undercloud installation command, openstack undercloud install.

3. Add the desired additional networks and roles to the overcloud templates, network_data.yaml and roles_data.yaml respectively.

   Note

   If you are using the {{network.name}}InterfaceRoutes parameter in the network configuration file, then you’ll need to ensure that the NetworkDeploymentActions parameter includes the value UPDATE.

     NetworkDeploymentActions: ['CREATE','UPDATE'])

4. Finally, re-run the overcloud installation script that includes all relevant heat templates for your cloud deployment.

Procedure

1. Create a backup of a volume in the first DCN site:

   $ cinder --os-volume-api-version 3.51 backup-create --name <volume_backup> --availability-zone <az_central> <edge_volume>

   • Replace <volume_backup> with a name for the volume backup.
   • Replace <az_central> with the name of the central availability zone that hosts the cinder-backup service.

   • Replace <edge_volume> with the name of the volume that you want to back up.

     Note

     If you experience issues with Ceph keyrings, you might need to restart the cinder-backup container so that the keyrings copy from the host to the container successfully.

2. Restore the backup to a new volume in the second DCN site:

   $ cinder --os-volume-api-version 3.51 create --availability-zone <az_2> --name <new_volume> --backup-id <volume_backup> <volume_size>

   • Replace <az_2> with the name of the availability zone where you want to restore the backup.
   • Replace <new_volume> with a name for the new volume.
   • Replace <volume_backup> with the name of the volume backup that you created in the previous step.
   • Replace <volume_size> with a value in GB equal to or greater than the size of the original volume.

Procedure

1. If this site is provisioned with Red Hat Ceph Storage, you must first remove the glance store, Ceph configuration, and associated permissions associated with the edge location you are removing. If you have not deployed storage at the edge, you can proceed to step 2:

   1. Log in to Red Hat Openstack Platform director and source the RC credentials file for the central site:

      source /home/stack/centralrc

   2. Delete all images associated with the stack:

      glance stores-delete --store dcn2 <IMAGE>

      Replace <_IMAGE_> with the name of the image that you want to delete.

   3. Remove the stanza associated with the stack from the dcn_ceph_external.yaml file. In this example, remove the dcn2 configuration.

      ...
          - cluster: "dcn1"
            fsid: "e70c3c80-4eca-4f1a-8cbb-3e9753b401c9"
            external_cluster_mon_ips: "172.23.2.58, 172.23.2.153, 172.23.2.32"
            keys:
              - name: "client.external"
                caps:
                  mgr: "allow *"
                  mon: "profile rbd"
                  osd: "profile rbd pool=vms, profile rbd pool=volumes, profile rbd pool=images"
                key: "AQD4Ae9gAAAAABAAeeG5N0E3Jka7bXRDhB8CtQ=="
                mode: "0600"
            dashboard_enabled: false
            ceph_conf_overrides:
              client:
                keyring: /etc/ceph/dcn1.client.external.keyring
      -   - cluster: "dcn2"
      -     fsid: "c699978c-876d-4c65-984f-2179d22244ea"
      -     external_cluster_mon_ips: "172.23.3.239, 172.23.3.99, 172.23.3.67"
      -     keys:
      -      - name: "client.external"
      -        caps:
      -          mgr: "allow *"
      -           mon: "profile rbd"
      -           osd: "profile rbd pool=vms, profile rbd pool=volumes, profile rbd pool=images"
      -         key: "AQA1Du9gAAAAABAAMOBAczLIw1SzBR7vxwYqJg=="
      -         mode: "0600"
      -     dashboard_enabled: false
      -     ceph_conf_overrides:
      -       client:
      -         keyring: /etc/ceph/dcn2.client.external.keyring

   4. Remove the stanza associated with the stack from the glance_update.yaml file. In this example, remove the dcn2 configuration.

      parameter_defaults:
        GlanceMultistoreConfig:
          dcn0:
            GlanceBackend: rbd
            GlanceStoreDescription: 'dcn0 rbd glance store'
            CephClientUserName: 'openstack'
            CephClusterName: dcn0
          dcn1:
            GlanceBackend: rbd
            GlanceStoreDescription: 'dcn1 rbd glance store'
            CephClientUserName: 'openstack'
            CephClusterName: dcn1
      -   dcn2:
      -     GlanceBackend: rbd
      -     GlanceStoreDescription: 'dcn2 rbd glance store'
      -     CephClientUserName: 'openstack'
      -     CephClusterName: dcn2

   5. Delete files in /etc/ceph that relate to the site you are removing. Perform this step on each Controller node.

      source /home/stack/stackrc
      for i in $(openstack server list | awk '/controller/ {print $8}' | cut -d= -f2); do
           ssh heat-admin@${i} sudo -E \
           rm -f /etc/ceph/dcn2.conf /etc/ceph/dcn2.client.openstack.keyring
      done

   6. Disable the cinder-volume service for the stack:

      1. Identify the cinder-volume service for the stack that you want to delete:

         source /home/stack/centralrc
         VOLUME_HOST=openstack volume service list --service cinder-volume

      2. Disable the cinder-volume service

         openstack volume service set --disable ${VOLUME_HOST} cinder-volume

      3. Remove the cinder-volume service from the cinder_api container on one of the Controller nodes at the central location:

         ssh heat-admin@CONTROLLER_IP sudo podman exec cinder_api cinder-manage service remove cinder-volume ${VOLUME_HOST}

2. If you use OVS, clean the neutron agents for the stack that you deleted:

   1. Identify the UUIDs of the network agents:

      source /home/stack/centralrc
      openstack network agent list

   2. Use the UUIDs from the previous step to identify the network agents to delete. Run the following command for each UUID:

      openstack network agent delete $UUID

      Note

      You cannot delete OVN agents.

3. Delete the compute services associated with the stack:

   1. Find the IDs of the compute services associated with dcn2. You can use the unique hostnames for this step. If the hostnames include the stacknames, you can use grep to list only the compute services that you want to delete:

      source /home/stack/centralrc
      openstack compute service list | grep dcn2

   2. Use the IDs shown in the first field to delete the compute services. Run the following command for each ID:

      openstack compute service delete <ID>

4. Delete the host aggregate associated with the site:

   source /home/stack/centralrc
   openstack aggregate delete dcn2

5. Remove the subnets for the stack that you want to delete from the /home/stack/central/network/network_data.yaml file:

     - name: Tenant
       name_lower: tenant
       vip: false  # Tenant network does not use VIPs
       vlan: 1189
       ip_subnet: '172.19.1.0/24'
       allocation_pools: [{'start': '172.19.1.4', 'end': '172.19.1.250'}]
       gateway_ip: '172.19.1.254'
       subnets:
         tenant_leaf1:
           vlan: 1179
           ip_subnet: '172.19.2.0/24'
           allocation_pools: [{'start': '172.19.2.4', 'end': '172.19.2.250'}]
           gateway_ip: '172.19.2.254'
   -     tenant_leaf2:
   -       vlan: 1169
   -       ip_subnet: '172.19.3.0/24'
   -       allocation_pools: [{'start': '172.19.3.4', 'end': '172.19.3.250'}]
   -       gateway_ip: '172.19.3.254

6. Delete the stack:

   source /home/stack/stackrc
   openstack overcloud delete -y dcn2

7. Optional: Delete the bare metal nodes from the decommissioned site:

   1. List the nodes and identify those associated with the deleted stack dcn2

      source /home/stack/stackrc
      openstack baremetal node list

   2. Use the node UUIDs from the previous step to remove each node from ironic:

      openstack baremetal node delete $UUID