Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
Red Hat OpenStack Platform 16.1 with Dell EMC PowerFlex family
Executive summary Product overview Deployment considerations Architecture overview RHOSP 16.1 deployment Post deployment operations
Overcloud deployment validation
Install PowerFlex SDC Package
Verify horizon access
Create volume type
Solution validation Sample environment files References

Overcloud deployment validation

Home > Storage > PowerFlex > White Papers > Red Hat OpenStack Platform 16.1 with Dell EMC PowerFlex family > Overcloud deployment validation

Overcloud deployment validation

    1. Verify overcloud status: Run the deployment status command:

    (undercloud) [stack@director ~]$ openstack overcloud status

    1. Access overcloud: The director generates a script to configure and help authenticate interactions with the overcloud from the director host. The director saves this file, overcloudrc, into the stack users home directory.
    • Run the following command to use overcloudrc file.

    (undercloud) [stack@director ~]$ source ~/overcloudrc

    (overcloud) [stack@director ~]$

    This command loads the necessary environment variables to interact with the overcloud from the director host’s CLI

    • Find the IP address of the overcloud nodes and make a note of it.

    (undercloud) [stack@director ~]$ openstack server list

    • Each node in the overcloud also contains a user called heat-admin. The undercloud ‘stack’ user has SSH access to this user on each node. Connect the node using the heat-admin user and the node’s IP address.

    (undercloud) [stack@director ~]$ ssh heat-admin@<controller/compute-ip>

    • Query the OpenStack cluster from controller and ensure that the cluster is in good health.

    [heat-admin@overcloud-controller-0 ~]$ sudo pcs status

    1. Verify cinder configuration: Check the file cinder.conf on the controller VM and verify whether all the required information related to PowerFlex exists, as mentioned in cinder.yaml or user can log into the cinder container and check the contents of /etc/cinder/cinder.conf.

    location to verify in controller VM: /var/lib/config-data/puppet-generated/cinder/etc/cinder/cinder.conf

    Example:

    [DEFAULT]

    enabled_backends=powerflex

    [Powerflex]

    Volume_driver=cinder.volume.drivers.dell_emc.powerflex.driver.PowerFlexDriver

    volume_backend_name=powerflex

    san_ip=GATEWAY_IP

    powerflex_storage_pools=Domain1:Pool1,Domain2:Pool2

    san_login=<login>

    san_password=<password>

    ……

    • If cinder.conf file has not yet been updated, you can manually update and then restart the cinder containers.

    Make changes in /var/lib/config-data/puppet-generated/cinder/etc/cinder/cinder.conf

    Restart the service:

    [heat-admin@overcloud-controller-0 ~]$ sudo podman ps | grep cinder

    [heat-admin@overcloud-controller-0 ~]$ sudo podman restart <cinder_container_ID>

    For more information on cinder configuration file with respect to PowerFlex, see Dell EMC PowerFlex Backend Deployment Guide for RHOSP 16.1.