0395353c4b
It was discovered today that the 'config-reference' directory was supposed to have been renamed to 'configuration'. The doc team was expecting it to be at that location so that they could automatically link to it from contributor/index.html . This patch just moves the directory. I am going to be submitting a subsequent patch that properly sets out the framework for the additional directories so that we don't have addition problems in the future. Change-Id: I6729aaf4593a0b089277f6d7d0aa50fee3ca340f
29 lines
1.3 KiB
ReStructuredText
29 lines
1.3 KiB
ReStructuredText
..
|
|
Warning: Do not edit this file. It is automatically generated from the
|
|
software project's code and your changes will be overwritten.
|
|
|
|
The tool to generate this file lives in openstack-doc-tools repository.
|
|
|
|
Please make any changes needed in the code, then run the
|
|
autogenerate-config-doc tool from the openstack-doc-tools repository, or
|
|
ask for help on the documentation mailing list, IRC channel or meeting.
|
|
|
|
.. _cinder-osbrick:
|
|
|
|
.. list-table:: Description of os-brick configuration options
|
|
:header-rows: 1
|
|
:class: config-ref-table
|
|
|
|
* - Configuration option = Default value
|
|
- Description
|
|
* - **[privsep_osbrick]**
|
|
-
|
|
* - ``capabilities`` = ``[]``
|
|
- (Unknown) List of Linux capabilities retained by the privsep daemon.
|
|
* - ``group`` = ``None``
|
|
- (String) Group that the privsep daemon should run as.
|
|
* - ``helper_command`` = ``None``
|
|
- (String) Command to invoke to start the privsep daemon if not using the "fork" method. If not specified, a default is generated using "sudo privsep-helper" and arguments designed to recreate the current configuration. This command must accept suitable --privsep_context and --privsep_sock_path arguments.
|
|
* - ``user`` = ``None``
|
|
- (String) User that the privsep daemon should run as.
|