Configuring OpenStack Compute for Cinder volume - Openstack

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

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 the OpenStack Training Course.

How to Configure OpenStack controller node

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:

MindMajix YouTube Channel

multi-node configuration
OpenStack controller

To configure the OpenStack compute nodes for Cinder, perform the following steps:

  • Next on our list for configuration is 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!  

Multi-node OpenStack Configuration

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

Course Schedule
NameDates
OpenStack TrainingNov 02 to Nov 17View Details
OpenStack TrainingNov 05 to Nov 20View Details
OpenStack TrainingNov 09 to Nov 24View Details
OpenStack TrainingNov 12 to Nov 27View Details
Last updated: 03 Apr 2023
About Author

Ravindra Savaram is a Technical 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.

read less
  1. Share:
OpenStack Articles