⁠6.6. Launch the Block Storage Services

To bring up 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. Once the services are running, the API will accept incoming volume requests, the scheduler will assign them as appropriate, and the volume service will action them.
⁠

Procedure 6.11. Launching Block Storage Services

  1. Starting the API Service

    Log in to each server that you intend to run the API on as the root user and start the API service.
    1. Use the service command to start the API service (openstack-cinder-api). 
      # service openstack-cinder-api start
    2. Use the chkconfig command to enable the API service permanently (openstack-cinder-api). 
      # chkconfig openstack-cinder-api on

  2. Starting the Scheduler Service

    Log in to each server that you intend to run the scheduler on as the root user and start the scheduler service.
    1. Use the service command to start the scheduler (openstack-cinder-scheduler). 
      # service openstack-cinder-scheduler start
    2. Use the chkconfig command to enable the scheduler permanently (openstack-cinder-scheduler). 
      # chkconfig openstack-cinder-scheduler on

  3. Starting the Volume Service

    Log in to each server that Block Storage has been attached to as the root user and start the volume service.
    1. Use the service command to start the volume service (openstack-cinder-volume). 
      # service openstack-cinder-volume start
    2. Use the service command to start the The SCSI target daemon (tgtd). 
      # service tgtd start
    3. Use the chkconfig command to enable the volume service permanently (openstack-cinder-volume). 
      # chkconfig openstack-cinder-volume on
    4. Use the chkconfig command to enable the SCSI target daemon permanently (tgtd). 
      # chkconfig tgtd on
The volume service is running and ready to begin allocating volumes as they are requested.