Chapter 5. Provider-specific requirements for migration

Procedure

1. In the dashboard of the OpenStack web console, click Project > API Access.

2. Expand Download OpenStack RC file and click OpenStack RC file.

   The file that is downloaded, referred to here as <openstack_rc_file>, includes the following fields used for token authentication:

   OS_AUTH_URL
   OS_PROJECT_ID
   OS_PROJECT_NAME
   OS_DOMAIN_NAME
   OS_USERNAME

3. To get the data needed for token authentication, run the following command:

   $ openstack token issue

   The output, referred to here as <openstack_token_output>, includes the token, userID, and projectID that you need for authentication using a token with user ID.

4. Create a Secret manifest similar to the following:

   • For authentication using a token with user ID:

     cat << EOF | oc apply -f -
     apiVersion: v1
     kind: Secret
     metadata:
       name: openstack-secret-tokenid
       namespace: openshift-mtv
       labels:
         createdForProviderType: openstack
     type: Opaque
     stringData:
       authType: token
       token: <token_from_openstack_token_output>
       projectID: <projectID_from_openstack_token_output>
       userID: <userID_from_openstack_token_output>
       url: <OS_AUTH_URL_from_openstack_rc_file>
     EOF

   • For authentication using a token with user name:

     cat << EOF | oc apply -f -
     apiVersion: v1
     kind: Secret
     metadata:
       name: openstack-secret-tokenname
       namespace: openshift-mtv
       labels:
         createdForProviderType: openstack
     type: Opaque
     stringData:
       authType: token
       token: <token_from_openstack_token_output>
       domainName: <OS_DOMAIN_NAME_from_openstack_rc_file>
       projectName: <OS_PROJECT_NAME_from_openstack_rc_file>
       username: <OS_USERNAME_from_openstack_rc_file>
       url: <OS_AUTH_URL_from_openstack_rc_file>
     EOF

Procedure

1. In the dashboard of the OpenStack web console, click Project > API Access.

2. Expand Download OpenStack RC file and click OpenStack RC file.

   The file that is downloaded, referred to here as <openstack_rc_file>, includes the following fields used for application credential authentication:

   OS_AUTH_URL
   OS_PROJECT_ID
   OS_PROJECT_NAME
   OS_DOMAIN_NAME
   OS_USERNAME

3. To get the data needed for application credential authentication, run the following command:

   $ openstack application credential create --role member --role reader --secret redhat forklift

   The output, referred to here as <openstack_credential_output>, includes:

   • The id and secret that you need for authentication using an application credential ID
   • The name and secret that you need for authentication using an application credential name

4. Create a Secret manifest similar to the following:

   • For authentication using the application credential ID:

     cat << EOF | oc apply -f -
     apiVersion: v1
     kind: Secret
     metadata:
       name: openstack-secret-appid
       namespace: openshift-mtv
       labels:
         createdForProviderType: openstack
     type: Opaque
     stringData:
       authType: applicationcredential
       applicationCredentialID: <id_from_openstack_credential_output>
       applicationCredentialSecret: <secret_from_openstack_credential_output>
       url: <OS_AUTH_URL_from_openstack_rc_file>
     EOF

   • For authentication using the application credential name:

     cat << EOF | oc apply -f -
     apiVersion: v1
     kind: Secret
     metadata:
       name: openstack-secret-appname
       namespace: openshift-mtv
       labels:
         createdForProviderType: openstack
     type: Opaque
     stringData:
       authType: applicationcredential
       applicationCredentialName: <name_from_openstack_credential_output>
       applicationCredentialSecret: <secret_from_openstack_credential_output>
       domainName: <OS_DOMAIN_NAME_from_openstack_rc_file>
       username: <OS_USERNAME_from_openstack_rc_file>
       url: <OS_AUTH_URL_from_openstack_rc_file>
     EOF

Procedure

1. In the vCenter Server UI, create a role that includes the set of privileges described in the table in VMware prerequisites.

2. In the vSphere inventory UI, grant privileges for users with this role to the appropriate vSphere logical objects at one of the following levels:

   1. At the user or group level: Assign privileges to the appropriate logical objects in the data center and use the Propagate to child objects option.
   2. At the object level: Apply the same role individually to all the relevant vSphere logical objects involved in the migration, for example, hosts, vSphere clusters, data centers, or networks.

Procedure

1. Create and navigate to a temporary directory:

   $ mkdir /tmp/<dir_name> && cd /tmp/<dir_name>

2. In a browser, navigate to the VMware VDDK version 8 download page.

3. Select version 8.0.1 and click Download.

   Note

   To migrate to OpenShift Virtualization 4.12, download VDDK version 7.0.3.2 from the VMware VDDK version 7 download page.

4. Save the VDDK archive file in the temporary directory.

5. Extract the VDDK archive:

   $ tar -xzf VMware-vix-disklib-<version>.x86_64.tar.gz

6. Create a Dockerfile:

   $ cat > Dockerfile <<EOF
   FROM registry.access.redhat.com/ubi8/ubi-minimal
   USER 1001
   COPY vmware-vix-disklib-distrib /vmware-vix-disklib-distrib
   RUN mkdir -p /opt
   ENTRYPOINT ["cp", "-r", "/vmware-vix-disklib-distrib", "/opt"]
   EOF

7. Build the VDDK image:

   $ podman build . -t <registry_route_or_server_path>/vddk:<tag>

8. Push the VDDK image to the registry:

   $ podman push <registry_route_or_server_path>/vddk:<tag>

9. Ensure that the image is accessible to your OpenShift Virtualization environment.

Procedure

1. Log in to the ESXi host as root.

2. Change the value of maxMemory to 1000000000 in /etc/vmware/hostd/config.xml:

   ...
         <nfcsvc>
            <path>libnfcsvc.so</path>
            <enabled>true</enabled>
            <maxMemory>1000000000</maxMemory>
            <maxStreamMemory>10485760</maxStreamMemory>
         </nfcsvc>
   ...

3. Restart hostd:

   # /etc/init.d/hostd restart

   You do not need to reboot the host.