Chapter 2. Process Description
The Block Storage service’s settings are stored in
/etc/cinder/cinder.conf; these settings include back end definitions. Most third-party back ends usable with (or even supported by) the Block Storage service provide setup instructions that involve editing
/etc/cinder/cinder.conf settings. As mentioned in Chapter 1, Introduction, doing so will configure the Block Storage service; however, those settings will get overwritten in future Overcloud updates.
Regardless, any documentation relating to manual configuration through
/etc/cinder/cinder.conf is still useful for Overcloud deployments. The Director, after all, applies the same configuration to
/etc/cinder/cinder.conf, albeit through heat. As such, planning the back end configuration requires that you:
- Thoroughly plan the Block Storage back end configuration you want, and
Map out the resulting
/etc/cinder/cinder.conffile for this configuration.
Once you map out the resulting
/etc/cinder/cinder.conf file, create the environment file that will orchestrate the back end settings. environment file describes this step in greater detail, using the sample file
/home/stack/templates/custom-env.yaml. Having the environment file handy will help ensure that the back end settings persist through future Overcloud updates.