Deploy Openstack Cinder with EMC ViPR Part 1

Previous blog posts have focused on deploying and setting up EMC ViPR. This blog will focus on setting up Openstack Cinder to use EMC ViPR for block storage. There are 3 blogs focused on this:

Part 1 Prep Host

Part 2 Install Cinder Driver for EMC ViPR HERE

Part 3 Order storage and mount it in Openstack HERE

OpenStack is a cloud operating system that controls large pools of compute, storage, and networking resources throughout a datacenter, all managed through a dashboard that gives administrators control while empowering their users to provision resources through a web interface. Openstack is made up of multiple projects for compute (Nova), network (Neutron), Object (Swift), and block (Cinder). Cinder provides an infrastructure for managing volumes in OpenStack. In my lab I am using a CentOS 6.4 image with Havana installed. I used packstack for the install, in a single node configuration.

Part 1 Prep Host

On the Openstack host, install multipath software. This is a requirement for physical hosts to access ViPR yum install device-mapper-multipath
Once installed, turn the service on and set it to turn on at boot service multipathd start chkconfig multipathd on
In my lab I’m using CentOS. This is not supported by ViPR so I edit the redhat-release file to make it appear as a true Red Hat OS
Add the host on the ViPR web page under Physical Assets, Hosts. Click the add button
Enter the information, FQDN, Port, Username and password for the host. Click Save
Validate that the host can connect NOTE: Once you have validated the host, remove it from ViPR. There is a script you run while setting up the ViPR Cinder driver that does this part. These steps were done for validating the host compatibility with ViPR

Comments

[Sayaji]

Hi,
I tried changing the /etc/redhat-release file on my centos machine. But Vipr still complains that the machine is not compatible. Did you change anything else to make it look like redhat.

[jim]

Hi Sayaji,
Editing the /etc/redhat-release file has worked for me. I have used this:

Red Hat Enterprise Linux Server release 6.3 (Santiago)

while using CentOs 6.4.
When I tried to change the /etc/redhat-release to 6.4 it threw errors so I've stuck with 6.3. This should be OK as it's just a version check and doesn't have and impact on functionality. Note that doing this isn't supported by EMC but has worked for me in the lab.