Blog

  • Home
  • OpenStack
  • Configuring OpenStack Compute for Cinder volume - Openstack

Configuring OpenStack Compute for Cinder volume - Openstack

  • (4.0)
  • | 1758 Ratings

We now need to tell our OpenStack Compute service about our new Cinder volume service.

Getting ready

As we are performing this setup in a multi-node environment, you will need to be logged into your controller, compute, and Cinder nodes.
This recipe assumes that you have created a .stackrc file. To create a .stackrc file, on each node you need it, open a text file .stackrc and add the following contents:

multi-node environment

To gain in-depth knowledge and be on par with practical experience, then explore  OpenStack Training course.

How to accomplish it…

In our multi-node installation, we will need to configure the controller, compute, and Cinder nodes. Thus, we have broken down the instructions in that order.

To configure your OpenStack controller node for the cinder-volume perform the following steps:

  • In our multi-node configuration, the OpenStack controller is responsible for authentication (keystone) as well as hosting the Cinder database. First, we will configure authentication:

multi-node configuration
OpenStack controller
To configure the OpenStack compute nodes for Cinder, perform the following steps:

  • Next on our list for configuration are the OpenStack compute nodes. In our scenario, there is only a single compute node to configure:

OpenStack compute nodes
OpenStack compute nodes 1

  • Next, we modify /etc/cinder/cinder.conf to configure the database, iSCSI, and RabbitMQ. Ensure conf has the following lines:

OpenStack compute nodes 2controller host

  • To wrap up, we populate the Cinder database and restart the Cinder services:

Cinder database

Explore OpenStack Sample Resumes! Download & Edit, Get Noticed by Top Employers!  Download Now!

How it works…

In our multi-node OpenStack configuration, we have to perform configuration across our environment to enable cinder-volume. On the OpenStack controller node, we created a keystone service, endpoint, and user. We additionally assigned the “Cinder” user, the admin role within the service tenant. Additionally, on the controller, we created a Cinder MySQL database and modified nova.conf to allow the use of Cinder.
On our compute nodes, the modifications were much simpler as we only needed to modify nova.conf to enable Cinder.
Finally, we configured the Cinder node itself. We did this by enabling keystone and initializing the Cinder database, and connecting the Cinder service to its MySQL database. After which we wrapped up by restarting the Cinder services.
https://docs.openstack.org/kilo/config-reference/content/section_cinder.conf.html


Related Pages:
Openstack Tutorial

Interview Questions:
Openstack Interview Questions



Subscribe For Free Demo

Free Demo for Corporate & Online Trainings.

Ravindra Savaram
About The Author

Ravindra Savaram is a Content Lead at Mindmajix.com. His passion lies in writing articles on the most popular IT platforms including Machine learning, DevOps, Data Science, Artificial Intelligence, RPA, Deep Learning, and so on. You can stay up to date on all these technologies by following him on LinkedIn and Twitter.


DMCA.com Protection Status

Close
Close