Show Table of Contents
6.5. Launch the Block Storage Services
To enable the Block Storage functionality at least one instance of each of the three services must be started:
- The API service (
openstack-cinder-api). - The scheduler service (
openstack-cinder-scheduler). - The volume service (
openstack-cinder-volume).
The services do not need to be located on the same system, but must be configured to communicate using the same message broker and database instance. When the services are running, the API accepts incoming volume requests, the scheduler assigns them as appropriate, and the volume service actions them.
Procedure 6.9. Launching Block Storage Services
- Log in as the
rootuser on each server where you intend to run the API, start the API service, and configure it to start at boot time:#systemctl start openstack-cinder-api.service#systemctl enable openstack-cinder-api.service - Log in as the
rootuser on each server where you intend to run the scheduler, start the scheduler service, and configure it to start at boot time:#systemctl start openstack-cinder-scheduler.service#systemctl enable openstack-cinder-scheduler.service - Log in as the
rootuser on each server to which Block Storage has been attached, start the volume service, and configure it to start at boot time:#systemctl start openstack-cinder-volume.service#systemctl enable openstack-cinder-volume.service
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.