openstack/openstack-manuals
Code Issues Proposed changes

Config Reference: Update changes for Liberty

Browse Source 
Regenerate all changes file with changes between kilo and Liberty.

Change-Id: I80d8f1b2170aa1c85e352c3572bf106d50c3f7dc
This commit is contained in:
Andreas Jaeger
2015-10-14 14:20:07 +02:00
parent d3e7f2e446
commit ab261dbc0c
12 changed files with 1569 additions and 148 deletions
Download Patch File Download Diff File Expand all files Collapse all files

58
doc/config-reference/conf-changes/ceilometer.xml
View File

@@ -32,10 +32,18 @@
<td>[DEFAULT] magnum_control_exchange = magnum</td>
<td>(StrOpt) Exchange name for Magnum notifications.</td>
</tr>
<tr>
<td>[DEFAULT] password = </td>
<td>(StrOpt) Password for Redis server (optional).</td>
</tr>
<tr>
<td>[DEFAULT] pipeline_polling_interval = 20</td>
<td>(IntOpt) Polling interval for pipeline file configuration in seconds.</td>
</tr>
<tr>
<td>[DEFAULT] port = 6379</td>
<td>(IntOpt) Use this port to connect to redis host.</td>
</tr>
<tr>
<td>[DEFAULT] refresh_event_pipeline_cfg = False</td>
<td>(BoolOpt) Refresh Event Pipeline configuration on-the-fly.</td>
@@ -48,6 +56,26 @@
<td>[DEFAULT] rpc_conn_pool_size = 30</td>
<td>(IntOpt) Size of RPC connection pool.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_poll_timeout = 1</td>
<td>(IntOpt) The default number of seconds that poll should wait. Poll raises timeout exception when timeout expired.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_all_req_rep = True</td>
<td>(BoolOpt) Use REQ/REP pattern for all methods CALL/CAST/FANOUT.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_concurrency = eventlet</td>
<td>(StrOpt) Type of concurrency used. Either "native" or "eventlet"</td>
</tr>
<tr>
<td>[DEFAULT] watch_log_file = False</td>
<td>(BoolOpt) (Optional) Uses logging handler designed to watch file system. When log file is moved or removed this handler will open a new log file with specified path instantaneously. It makes sense only if log-file option is specified and Linux platform is used. This option is ignored if log_config_append is set.</td>
</tr>
<tr>
<td>[DEFAULT] zmq_use_broker = True</td>
<td>(BoolOpt) Shows whether zmq-messaging uses broker or not.</td>
</tr>
<tr>
<td>[alarm] alarm_max_actions = -1</td>
<td>(IntOpt) Maximum count of actions for each state of an alarm, non-positive number means no limit.</td>
@@ -176,6 +204,26 @@
<td>[notification] workers = 1</td>
<td>(IntOpt) Number of workers for notification service, default value is 1.</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] password = </td>
<td>(StrOpt) Password for message broker authentication</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_config_dir = </td>
<td>(StrOpt) Path to directory that contains the SASL configuration</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_config_name = </td>
<td>(StrOpt) Name of configuration file (without .conf suffix)</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_mechanisms = </td>
<td>(StrOpt) Space separated list of acceptable SASL mechanisms</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] username = </td>
<td>(StrOpt) User name for message broker authentication</td>
</tr>
<tr>
<td>[oslo_messaging_qpid] send_single_reply = False</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in the Mitaka release.</td>
@@ -223,6 +271,11 @@
<td>%(asctime)s.%(msecs)03d %(process)d TRACE %(name)s %(instance)s</td>
<td>%(asctime)s.%(msecs)03d %(process)d ERROR %(name)s %(instance)s</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_matchmaker</td>
<td>local</td>
<td>redis</td>
</tr>
<tr>
<td>[DEFAULT] use_syslog_rfc_format</td>
<td>False</td>
@@ -233,6 +286,11 @@
<td>False</td>
<td>True</td>
</tr>
<tr>
<td>[matchmaker_redis] password</td>
<td>None</td>
<td></td>
</tr>
<tr>
<td>[notification] disable_non_metric_meters</td>
<td>False</td>

266
doc/config-reference/conf-changes/cinder.xml
View File

@@ -1,7 +1,7 @@
<?xml version='1.0' encoding='UTF-8'?>
<section xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="cinder-conf-changes-liberty">
<!-- Warning: Do not edit this file. It is automatically generated and your changes will be overwritten. The tool to do so lives in the openstack-doc-tools repository. -->
<title>New, updated and deprecated options in Liberty for OpenStack Block Storage</title>
<title>New, updated, and deprecated options in Liberty for OpenStack Block Storage</title>
<table>
<caption>New options</caption>
<col width="50%"/>
@@ -12,10 +12,18 @@
<td>(Type) Help string</td>
</tr>
</thead>
<tr>
<td>[DEFAULT] allow_availability_zone_fallback = False</td>
<td>(BoolOpt) If the requested Cinder availability zone is unavailable, fall back to the value of default_availability_zone, then storage_availability_zone, instead of failing.</td>
</tr>
<tr>
<td>[DEFAULT] backup_posix_path = $state_path/backup</td>
<td>(StrOpt) Path specifying where to store backups.</td>
</tr>
<tr>
<td>[DEFAULT] backup_service_inithost_offload = False</td>
<td>(BoolOpt) Offload pending backup delete during backup service startup.</td>
</tr>
<tr>
<td>[DEFAULT] backup_swift_ca_cert_file = None</td>
<td>(StrOpt) Location of the CA certificate file to use for swift client requests.</td>
@@ -56,6 +64,14 @@
<td>[DEFAULT] cb_auth_group = None</td>
<td>(StrOpt) This corresponds to the discovery authentication group in CloudByte storage. Chap users are added to this group. Driver uses the first user found for this group. Default value is None.</td>
</tr>
<tr>
<td>[DEFAULT] cb_confirm_volume_delete_retries = 3</td>
<td>(IntOpt) Will confirm a successful volume deletion in CloudByte storage by making this many number of attempts.</td>
</tr>
<tr>
<td>[DEFAULT] cb_confirm_volume_delete_retry_interval = 5</td>
<td>(IntOpt) A retry value in seconds. Will be used by the driver to check if volume deletion was successful in CloudByte storage.</td>
</tr>
<tr>
<td>[DEFAULT] cinder_internal_tenant_project_id = None</td>
<td>(StrOpt) ID of the project which will be used as the Cinder internal tenant.</td>
@@ -69,20 +85,28 @@
<td>(BoolOpt) Enable HTTPS SC certificate verification.</td>
</tr>
<tr>
<td>[DEFAULT] dothill_backend_name = OpenStack</td>
<td>(StrOpt) VDisk or Pool name to use for volume creation.</td>
<td>[DEFAULT] dothill_api_protocol = https</td>
<td>(StrOpt) DotHill API interface protocol.</td>
</tr>
<tr>
<td>[DEFAULT] dothill_backend_type = None</td>
<td>(StrOpt) linear (for VDisk) or realstor (for Pool).</td>
<td>[DEFAULT] dothill_backend_name = A</td>
<td>(StrOpt) Pool or Vdisk name to use for volume creation.</td>
</tr>
<tr>
<td>[DEFAULT] dothill_backend_type = virtual</td>
<td>(StrOpt) linear (for Vdisk) or virtual (for Pool).</td>
</tr>
<tr>
<td>[DEFAULT] dothill_iscsi_ips = </td>
<td>(ListOpt) List of comma separated target iSCSI IP addresses.</td>
<td>(ListOpt) List of comma-separated target iSCSI IP addresses.</td>
</tr>
<tr>
<td>[DEFAULT] dothill_wbi_protocol = None</td>
<td>(StrOpt) DotHill web interface protocol.</td>
<td>[DEFAULT] dothill_verify_certificate = False</td>
<td>(BoolOpt) Whether to verify DotHill array SSL certificate.</td>
</tr>
<tr>
<td>[DEFAULT] dothill_verify_certificate_path = None</td>
<td>(StrOpt) DotHill array SSL certificate path.</td>
</tr>
<tr>
<td>[DEFAULT] drbdmanage_redundancy = 1</td>
@@ -104,6 +128,14 @@
<td>[DEFAULT] flashsystem_iscsi_portid = 0</td>
<td>(IntOpt) Default iSCSI Port ID of FlashSystem. (Default port is 0.)</td>
</tr>
<tr>
<td>[DEFAULT] glusterfs_backup_mount_point = $state_path/backup_mount</td>
<td>(StrOpt) Base dir containing mount point for gluster share.</td>
</tr>
<tr>
<td>[DEFAULT] glusterfs_backup_share = None</td>
<td>(StrOpt) GlusterFS share in &lt;hostname|ipv4addr|ipv6addr&gt;:&lt;gluster_vol_name&gt; format. Eg: 1.2.3.4:backup_vol</td>
</tr>
<tr>
<td>[DEFAULT] hgst_net = Net 1 (IPv4)</td>
<td>(StrOpt) Space network name to use for data transfer</td>
@@ -133,20 +165,28 @@
<td>(IntOpt) Timeout until a resource lock is released, in seconds. The value must be between 0 and 7200.</td>
</tr>
<tr>
<td>[DEFAULT] hpmsa_backend_name = OpenStack</td>
<td>(StrOpt) VDisk or Pool name to use for volume creation.</td>
<td>[DEFAULT] hpmsa_api_protocol = https</td>
<td>(StrOpt) HPMSA API interface protocol.</td>
</tr>
<tr>
<td>[DEFAULT] hpmsa_backend_type = None</td>
<td>(StrOpt) linear (for VDisk) or realstor (for Pool).</td>
<td>[DEFAULT] hpmsa_backend_name = A</td>
<td>(StrOpt) Pool or Vdisk name to use for volume creation.</td>
</tr>
<tr>
<td>[DEFAULT] hpmsa_backend_type = virtual</td>
<td>(StrOpt) linear (for Vdisk) or virtual (for Pool).</td>
</tr>
<tr>
<td>[DEFAULT] hpmsa_iscsi_ips = </td>
<td>(ListOpt) List of comma separated target iSCSI IP addresses.</td>
<td>(ListOpt) List of comma-separated target iSCSI IP addresses.</td>
</tr>
<tr>
<td>[DEFAULT] hpmsa_wbi_protocol = None</td>
<td>(StrOpt) HPMSA web interface protocol.</td>
<td>[DEFAULT] hpmsa_verify_certificate = False</td>
<td>(BoolOpt) Whether to verify HPMSA array SSL certificate.</td>
</tr>
<tr>
<td>[DEFAULT] hpmsa_verify_certificate_path = None</td>
<td>(StrOpt) HPMSA array SSL certificate path.</td>
</tr>
<tr>
<td>[DEFAULT] hpxp_async_copy_check_interval = 10</td>
@@ -224,6 +264,26 @@
<td>[DEFAULT] ignore_pool_full_threshold = False</td>
<td>(BoolOpt) Force LUN creation even if the full threshold of pool is reached.</td>
</tr>
<tr>
<td>[DEFAULT] image_upload_use_cinder_backend = False</td>
<td>(BoolOpt) If set to True, upload-to-image in raw format will create a cloned volume and register its location to the image service, instead of uploading the volume content. The cinder backend and locations support must be enabled in the image service, and glance_api_version must be set to 2.</td>
</tr>
<tr>
<td>[DEFAULT] image_upload_use_internal_tenant = False</td>
<td>(BoolOpt) If set to True, the image volume created by upload-to-image will be placed in the internal tenant. Otherwise, the image volume is created in the current context's tenant.</td>
</tr>
<tr>
<td>[DEFAULT] image_volume_cache_enabled = False</td>
<td>(BoolOpt) Enable the image volume cache for this backend.</td>
</tr>
<tr>
<td>[DEFAULT] image_volume_cache_max_count = 0</td>
<td>(IntOpt) Max number of entries allowed in the image volume cache. 0 =&gt; unlimited.</td>
</tr>
<tr>
<td>[DEFAULT] image_volume_cache_max_size_gb = 0</td>
<td>(IntOpt) Max size of the image volume cache for this backend in GB. 0 =&gt; unlimited.</td>
</tr>
<tr>
<td>[DEFAULT] infortrend_cli_max_retries = 5</td>
<td>(IntOpt) Maximum retry time for cli. Default is 5.</td>
@@ -265,27 +325,43 @@
<td>(StrOpt) Sets the target-specific flags for the iSCSI target. Only used for tgtadm to specify backing device flags using bsoflags option. The specified string is passed as is to the underlying tool.</td>
</tr>
<tr>
<td>[DEFAULT] lenovo_backend_name = OpenStack</td>
<td>(StrOpt) VDisk or Pool name to use for volume creation.</td>
<td>[DEFAULT] lenovo_api_protocol = https</td>
<td>(StrOpt) Lenovo api interface protocol.</td>
</tr>
<tr>
<td>[DEFAULT] lenovo_backend_type = None</td>
<td>(StrOpt) linear (for VDisk) or realstor (for Pool).</td>
<td>[DEFAULT] lenovo_backend_name = A</td>
<td>(StrOpt) Pool or Vdisk name to use for volume creation.</td>
</tr>
<tr>
<td>[DEFAULT] lenovo_backend_type = virtual</td>
<td>(StrOpt) linear (for VDisk) or virtual (for Pool).</td>
</tr>
<tr>
<td>[DEFAULT] lenovo_iscsi_ips = </td>
<td>(ListOpt) List of comma separated target iSCSI IP addresses.</td>
<td>(ListOpt) List of comma-separated target iSCSI IP addresses.</td>
</tr>
<tr>
<td>[DEFAULT] lenovo_wbi_protocol = None</td>
<td>(StrOpt) Lenovo web interface protocol.</td>
<td>[DEFAULT] lenovo_verify_certificate = False</td>
<td>(BoolOpt) Whether to verify Lenovo array SSL certificate.</td>
</tr>
<tr>
<td>[DEFAULT] lenovo_verify_certificate_path = None</td>
<td>(StrOpt) Lenovo array SSL certificate path.</td>
</tr>
<tr>
<td>[DEFAULT] managed_replication_target = True</td>
<td>(BoolOpt) There are two types of target configurations managed (replicate to another configured backend) or unmanaged (replicate to a device not managed by Cinder).</td>
</tr>
<tr>
<td>[DEFAULT] management_ips = </td>
<td>(StrOpt) List of Management IP addresses (separated by commas)</td>
</tr>
<tr>
<td>[DEFAULT] netapp_enable_multiattach = True</td>
<td>[DEFAULT] nas_volume_prov_type = thin</td>
<td>(StrOpt) Provisioning type that will be used when creating volumes.</td>
</tr>
<tr>
<td>[DEFAULT] netapp_enable_multiattach = False</td>
<td>(BoolOpt) This option specifies whether the driver should allow operations that require multiple attachments to a volume. An example would be live migration of servers that have volumes attached. When enabled, this backend is limited to 256 total volumes in order to guarantee volumes can be accessed by more than one host.</td>
</tr>
<tr>
@@ -296,14 +372,30 @@
<td>[DEFAULT] netapp_lun_ostype = None</td>
<td>(StrOpt) This option defines the type of operating system that will access a LUN exported from Data ONTAP; it is assigned to the LUN at the time it is created.</td>
</tr>
<tr>
<td>[DEFAULT] netapp_lun_space_reservation = enabled</td>
<td>(StrOpt) This option determines if storage space is reserved for LUN allocation. If enabled, LUNs are thick provisioned. If space reservation is disabled, storage space is allocated on demand.</td>
</tr>
<tr>
<td>[DEFAULT] netapp_pool_name_search_pattern = (.+)</td>
<td>(StrOpt) This option is used to restrict provisioning to the specified pools. Specify the value of this option to be a regular expression which will be applied to the names of objects from the storage backend which represent pools in Cinder. This option is only utilized when the storage protocol is configured to use iSCSI or FC.</td>
</tr>
<tr>
<td>[DEFAULT] os_privileged_user_auth_url = None</td>
<td>(StrOpt) Auth URL associated with the OpenStack privileged account.</td>
</tr>
<tr>
<td>[DEFAULT] password = </td>
<td>(StrOpt) Password for Redis server (optional).</td>
</tr>
<tr>
<td>[DEFAULT] per_volume_size_limit = -1</td>
<td>(IntOpt) Max size allowed per volume, in gigabytes</td>
</tr>
<tr>
<td>[DEFAULT] port = 6379</td>
<td>(IntOpt) Use this port to connect to redis host.</td>
</tr>
<tr>
<td>[DEFAULT] query_volume_filters = name, status, metadata, availability_zone</td>
<td>(ListOpt) Volume filter options which non-admin user could use to query volumes. Default values are: ['name', 'status', 'metadata', 'availability_zone']</td>
@@ -320,10 +412,42 @@
<td>[DEFAULT] rbd_cluster_name = ceph</td>
<td>(StrOpt) The name of ceph cluster</td>
</tr>
<tr>
<td>[DEFAULT] replication_devices = None</td>
<td>(ListOpt) List of k/v pairs representing a replication target for this backend device. For unmanaged the format is: {'key-1'='val1' 'key-2'='val2'...},{...} and for managed devices its simply a list of valid configured backend_names that the driver supports replicating to: backend-a,bakcend-b...</td>
</tr>
<tr>
<td>[DEFAULT] rpc_conn_pool_size = 30</td>
<td>(IntOpt) Size of RPC connection pool.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_poll_timeout = 1</td>
<td>(IntOpt) The default number of seconds that poll should wait. Poll raises timeout exception when timeout expired.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_all_req_rep = True</td>
<td>(BoolOpt) Use REQ/REP pattern for all methods CALL/CAST/FANOUT.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_concurrency = eventlet</td>
<td>(StrOpt) Type of concurrency used. Either "native" or "eventlet"</td>
</tr>
<tr>
<td>[DEFAULT] sf_enable_volume_mapping = True</td>
<td>(BoolOpt) Create an internal mapping of volume IDs and account. Optimizes lookups and performance at the expense of memory, very large deployments may want to consider setting to False.</td>
</tr>
<tr>
<td>[DEFAULT] sf_svip = None</td>
<td>(StrOpt) Overrides default cluster SVIP with the one specified. This is required or deployments that have implemented the use of VLANs for iSCSI networks in their cloud.</td>
</tr>
<tr>
<td>[DEFAULT] sheepdog_store_address = 127.0.0.1</td>
<td>(StrOpt) IP address of sheep daemon.</td>
</tr>
<tr>
<td>[DEFAULT] sheepdog_store_port = 7000</td>
<td>(IntOpt) Port of sheep daemon.</td>
</tr>
<tr>
<td>[DEFAULT] sio_force_delete = False</td>
<td>(BoolOpt) Whether to allow force delete.</td>
@@ -372,14 +496,6 @@
<td>[DEFAULT] storage_vnx_pool_names = None</td>
<td>(StrOpt) Comma-separated list of storage pool names to be used.</td>
</tr>
<tr>
<td>[DEFAULT] storpool_replication = 3</td>
<td>(IntOpt) The default StorPool chain replication value. Used when creating a volume with no specified type if storpool_template is not set. Also used for calculating the apparent free space reported in the stats.</td>
</tr>
<tr>
<td>[DEFAULT] storpool_template = None</td>
<td>(StrOpt) The StorPool template for volumes with no type.</td>
</tr>
<tr>
<td>[DEFAULT] tintri_api_version = v310</td>
<td>(StrOpt) API version for the storage system</td>
@@ -436,6 +552,10 @@
<td>[DEFAULT] vzstorage_used_ratio = 0.95</td>
<td>(FloatOpt) Percent of ACTUAL usage of the underlying volume before no new volumes can be allocated to the volume destination.</td>
</tr>
<tr>
<td>[DEFAULT] watch_log_file = False</td>
<td>(BoolOpt) (Optional) Uses logging handler designed to watch file system. When log file is moved or removed this handler will open a new log file with specified path instantaneously. It makes sense only if log-file option is specified and Linux platform is used. This option is ignored if log_config_append is set.</td>
</tr>
<tr>
<td>[DEFAULT] xtremio_array_busy_retry_count = 5</td>
<td>(IntOpt) Number of retries in case array is busy</td>
@@ -444,6 +564,18 @@
<td>[DEFAULT] xtremio_array_busy_retry_interval = 5</td>
<td>(IntOpt) Interval between retries in case array is busy</td>
</tr>
<tr>
<td>[DEFAULT] zfssa_cache_directory = os-cinder-cache</td>
<td>(StrOpt) Name of directory inside zfssa_nfs_share where cache volumes are stored.</td>
</tr>
<tr>
<td>[DEFAULT] zfssa_cache_project = os-cinder-cache</td>
<td>(StrOpt) Name of ZFSSA project where cache volumes are stored.</td>
</tr>
<tr>
<td>[DEFAULT] zfssa_enable_local_cache = True</td>
<td>(BoolOpt) Flag to enable local caching: True, False.</td>
</tr>
<tr>
<td>[DEFAULT] zfssa_initiator = </td>
<td>(StrOpt) iSCSI initiator IQNs. (comma separated)</td>
@@ -488,6 +620,10 @@
<td>[DEFAULT] zfssa_project = None</td>
<td>(StrOpt) Project name.</td>
</tr>
<tr>
<td>[DEFAULT] zfssa_replication_ip = </td>
<td>(StrOpt) IP address used for replication data. (maybe the same as data ip)</td>
</tr>
<tr>
<td>[DEFAULT] zfssa_target_group = tgt-grp</td>
<td>(StrOpt) iSCSI target group name.</td>
@@ -508,6 +644,10 @@
<td>[DEFAULT] zfssa_target_user = </td>
<td>(StrOpt) iSCSI target CHAP user (name).</td>
</tr>
<tr>
<td>[DEFAULT] zmq_use_broker = True</td>
<td>(BoolOpt) Shows whether zmq-messaging uses broker or not.</td>
</tr>
<tr>
<td>[cors] allow_credentials = True</td>
<td>(BoolOpt) Indicate that the actual request can include user credentials</td>
@@ -556,9 +696,33 @@
<td>[cors.subdomain] max_age = 3600</td>
<td>(IntOpt) Maximum cache age of CORS preflight requests.</td>
</tr>
<tr>
<td>[keystone_authtoken] region_name = None</td>
<td>(StrOpt) The region in which the identity server can be found.</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] password = </td>
<td>(StrOpt) Password for message broker authentication</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_config_dir = </td>
<td>(StrOpt) Path to directory that contains the SASL configuration</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_config_name = </td>
<td>(StrOpt) Name of configuration file (without .conf suffix)</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_mechanisms = </td>
<td>(StrOpt) Space separated list of acceptable SASL mechanisms</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] username = </td>
<td>(StrOpt) User name for message broker authentication</td>
</tr>
<tr>
<td>[oslo_messaging_qpid] send_single_reply = False</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in M release.</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in the Mitaka release.</td>
</tr>
<tr>
<td>[oslo_messaging_rabbit] kombu_reconnect_timeout = 60</td>
@@ -566,7 +730,7 @@
</tr>
<tr>
<td>[oslo_messaging_rabbit] send_single_reply = False</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in M release.</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in the Mitaka release.</td>
</tr>
<tr>
<td>[oslo_middleware] secure_proxy_ssl_header = X-Forwarded-Proto</td>
@@ -616,6 +780,11 @@
<td>%(asctime)s.%(msecs)03d %(process)d TRACE %(name)s %(instance)s</td>
<td>%(asctime)s.%(msecs)03d %(process)d ERROR %(name)s %(instance)s</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_matchmaker</td>
<td>local</td>
<td>redis</td>
</tr>
<tr>
<td>[DEFAULT] storwize_svc_npiv_compatibility_mode</td>
<td>False</td>
@@ -631,6 +800,21 @@
<td>False</td>
<td>True</td>
</tr>
<tr>
<td>[DEFAULT] vmware_volume_folder</td>
<td>cinder-volumes</td>
<td>Volumes</td>
</tr>
<tr>
<td>[DEFAULT] volume_driver</td>
<td>cinder.volume.drivers.lvm.LVMISCSIDriver</td>
<td>cinder.volume.drivers.lvm.LVMVolumeDriver</td>
</tr>
<tr>
<td>[matchmaker_redis] password</td>
<td>None</td>
<td></td>
</tr>
<tr>
<td>[oslo_messaging_rabbit] heartbeat_timeout_threshold</td>
<td>0</td>
@@ -663,6 +847,14 @@
<td>[DEFAULT] datera_api_token</td>
<td>None</td>
</tr>
<tr>
<td>[DEFAULT] glusterfs_sparsed_volumes</td>
<td>[DEFAULT] nas_volume_prov_type</td>
</tr>
<tr>
<td>[DEFAULT] glusterfs_qcow2_volumes</td>
<td>[DEFAULT] nas_volume_prov_type</td>
</tr>
<tr>
<td>[DEFAULT] eqlx_use_chap</td>
<td>[DEFAULT] use_chap_auth</td>
@@ -675,6 +867,14 @@
<td>[DEFAULT] enable_v1_api</td>
<td>None</td>
</tr>
<tr>
<td>[DEFAULT] netapp_volume_list</td>
<td>[DEFAULT] netapp_pool_name_search_pattern</td>
</tr>
<tr>
<td>[DEFAULT] netapp_storage_pools</td>
<td>[DEFAULT] netapp_pool_name_search_pattern</td>
</tr>
<tr>
<td>[DEFAULT] host</td>
<td>[DEFAULT] backend_host</td>

107
doc/config-reference/conf-changes/glance.xml
View File

@@ -1,7 +1,7 @@
<?xml version='1.0' encoding='UTF-8'?>
<section xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="glance-conf-changes-liberty">
<!-- Warning: Do not edit this file. It is automatically generated and your changes will be overwritten. The tool to do so lives in the openstack-doc-tools repository. -->
<title>New, updated and deprecated options in Liberty for OpenStack Image service</title>
<title>New, updated, and deprecated options in Liberty for OpenStack Image service</title>
<table>
<caption>New options</caption>
<col width="50%"/>
@@ -13,17 +13,53 @@
</tr>
</thead>
<tr>
<td>[DEFAULT] enable_v3_api = True</td>
<td>[DEFAULT] enable_v3_api = False</td>
<td>(BoolOpt) Deploy the v3 OpenStack Objects API.</td>
</tr>
<tr>
<td>[DEFAULT] executor_thread_pool_size = 64</td>
<td>(IntOpt) Size of executor thread pool.</td>
</tr>
<tr>
<td>[DEFAULT] max_request_id_length = 64</td>
<td>(IntOpt) Limits request ID length.</td>
</tr>
<tr>
<td>[DEFAULT] password = </td>
<td>(StrOpt) Password for Redis server (optional).</td>
</tr>
<tr>
<td>[DEFAULT] port = 6379</td>
<td>(IntOpt) Use this port to connect to redis host.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_conn_pool_size = 30</td>
<td>(IntOpt) Size of RPC connection pool.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_poll_timeout = 1</td>
<td>(IntOpt) The default number of seconds that poll should wait. Poll raises timeout exception when timeout expired.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_all_req_rep = True</td>
<td>(BoolOpt) Use REQ/REP pattern for all methods CALL/CAST/FANOUT.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_concurrency = eventlet</td>
<td>(StrOpt) Type of concurrency used. Either "native" or "eventlet"</td>
</tr>
<tr>
<td>[DEFAULT] scrub_pool_size = 1</td>
<td>(IntOpt) The size of thread pool to be used for scrubbing images. The default is one, which signifies serial scrubbing. Any value above one indicates the max number of images that may be scrubbed in parallel.</td>
</tr>
<tr>
<td>[DEFAULT] watch_log_file = False</td>
<td>(BoolOpt) (Optional) Uses logging handler designed to watch file system. When log file is moved or removed this handler will open a new log file with specified path instantaneously. It makes sense only if log-file option is specified and Linux platform is used. This option is ignored if log_config_append is set.</td>
</tr>
<tr>
<td>[DEFAULT] zmq_use_broker = True</td>
<td>(BoolOpt) Shows whether zmq-messaging uses broker or not.</td>
</tr>
<tr>
<td>[cors] allow_credentials = True</td>
<td>(BoolOpt) Indicate that the actual request can include user credentials</td>
@@ -72,9 +108,57 @@
<td>[cors.subdomain] max_age = 3600</td>
<td>(IntOpt) Maximum cache age of CORS preflight requests.</td>
</tr>
<tr>
<td>[glance_store] rados_connect_timeout = 0</td>
<td>(IntOpt) Timeout value (in seconds) used when connecting to ceph cluster. If value &lt;= 0, no timeout is set and default librados value is used.</td>
</tr>
<tr>
<td>[glance_store] s3_store_enable_proxy = False</td>
<td>(BoolOpt) Enable the use of a proxy.</td>
</tr>
<tr>
<td>[glance_store] s3_store_proxy_host = None</td>
<td>(StrOpt) Address or hostname for the proxy server.</td>
</tr>
<tr>
<td>[glance_store] s3_store_proxy_password = None</td>
<td>(StrOpt) The password to use when connecting over a proxy.</td>
</tr>
<tr>
<td>[glance_store] s3_store_proxy_port = 8080</td>
<td>(IntOpt) The port to use when connecting over a proxy.</td>
</tr>
<tr>
<td>[glance_store] s3_store_proxy_user = None</td>
<td>(StrOpt) The username to connect to the proxy.</td>
</tr>
<tr>
<td>[keystone_authtoken] region_name = None</td>
<td>(StrOpt) The region in which the identity server can be found.</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] password = </td>
<td>(StrOpt) Password for message broker authentication</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_config_dir = </td>
<td>(StrOpt) Path to directory that contains the SASL configuration</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_config_name = </td>
<td>(StrOpt) Name of configuration file (without .conf suffix)</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_mechanisms = </td>
<td>(StrOpt) Space separated list of acceptable SASL mechanisms</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] username = </td>
<td>(StrOpt) User name for message broker authentication</td>
</tr>
<tr>
<td>[oslo_messaging_qpid] send_single_reply = False</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in M release.</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in the Mitaka release.</td>
</tr>
<tr>
<td>[oslo_messaging_rabbit] kombu_reconnect_timeout = 60</td>
@@ -82,7 +166,7 @@
</tr>
<tr>
<td>[oslo_messaging_rabbit] send_single_reply = False</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in M release.</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in the Mitaka release.</td>
</tr>
<tr>
<td>[oslo_middleware] max_request_body_size = 114688</td>
@@ -125,11 +209,21 @@
<td>sha1</td>
<td>sha256</td>
</tr>
<tr>
<td>[DEFAULT] host</td>
<td>localhost</td>
<td>127.0.0.1</td>
</tr>
<tr>
<td>[DEFAULT] logging_exception_prefix</td>
<td>%(asctime)s.%(msecs)03d %(process)d TRACE %(name)s %(instance)s</td>
<td>%(asctime)s.%(msecs)03d %(process)d ERROR %(name)s %(instance)s</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_matchmaker</td>
<td>local</td>
<td>redis</td>
</tr>
<tr>
<td>[DEFAULT] use_syslog_rfc_format</td>
<td>False</td>
@@ -140,6 +234,11 @@
<td>False</td>
<td>True</td>
</tr>
<tr>
<td>[matchmaker_redis] password</td>
<td>None</td>
<td></td>
</tr>
<tr>
<td>[oslo_messaging_rabbit] heartbeat_timeout_threshold</td>
<td>0</td>

105
doc/config-reference/conf-changes/heat.xml
View File

@@ -1,7 +1,7 @@
<?xml version='1.0' encoding='UTF-8'?>
<section xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="heat-conf-changes-liberty">
<!-- Warning: Do not edit this file. It is automatically generated and your changes will be overwritten. The tool to do so lives in the openstack-doc-tools repository. -->
<title>New, updated and deprecated options in Liberty for Orchestration</title>
<title>New, updated, and deprecated options in Liberty for Orchestration</title>
<table>
<caption>New options</caption>
<col width="50%"/>
@@ -21,13 +21,41 @@
<td>(IntOpt) Size of executor thread pool.</td>
</tr>
<tr>
<td>[DEFAULT] hidden_stack_tags = </td>
<td>[DEFAULT] hidden_stack_tags = data-processing-cluster</td>
<td>(ListOpt) Stacks containing these tag names will be hidden. Multiple tags should be given in a comma-delimited list (eg. hidden_stack_tags=hide_me,me_too).</td>
</tr>
<tr>
<td>[DEFAULT] password = </td>
<td>(StrOpt) Password for Redis server (optional).</td>
</tr>
<tr>
<td>[DEFAULT] port = 6379</td>
<td>(IntOpt) Use this port to connect to redis host.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_conn_pool_size = 30</td>
<td>(IntOpt) Size of RPC connection pool.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_poll_timeout = 1</td>
<td>(IntOpt) The default number of seconds that poll should wait. Poll raises timeout exception when timeout expired.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_all_req_rep = True</td>
<td>(BoolOpt) Use REQ/REP pattern for all methods CALL/CAST/FANOUT.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_concurrency = eventlet</td>
<td>(StrOpt) Type of concurrency used. Either "native" or "eventlet"</td>
</tr>
<tr>
<td>[DEFAULT] watch_log_file = False</td>
<td>(BoolOpt) (Optional) Uses logging handler designed to watch file system. When log file is moved or removed this handler will open a new log file with specified path instantaneously. It makes sense only if log-file option is specified and Linux platform is used. This option is ignored if log_config_append is set.</td>
</tr>
<tr>
<td>[DEFAULT] zmq_use_broker = True</td>
<td>(BoolOpt) Shows whether zmq-messaging uses broker or not.</td>
</tr>
<tr>
<td>[cache] backend = dogpile.cache.null</td>
<td>(StrOpt) Dogpile.cache backend module. It is recommended that Memcache with pooling (oslo_cache.memcache_pool) or Redis (dogpile.cache.redis) be used in production deployments. Small workloads (single process) like devstack can use the dogpile.cache.memory backend.</td>
@@ -80,6 +108,10 @@
<td>[cache] proxies = </td>
<td>(ListOpt) Proxy classes to import that will affect the way the dogpile.cache backend functions. See the dogpile.cache documentation on changing-backend-behavior.</td>
</tr>
<tr>
<td>[clients_keystone] auth_uri = </td>
<td>(StrOpt) Unversioned keystone url in format like http://0.0.0.0:5000.</td>
</tr>
<tr>
<td>[constraint_validation_cache] caching = True</td>
<td>(BoolOpt) Toggle to enable/disable caching when Orchestration Engine validates property constraints of stack.During property validation with constraints Orchestration Engine caches requests to other OpenStack services. Please note that the global toggle for oslo.cache(enabled=True in [cache] group) must be enabled to use this feature.</td>
@@ -136,14 +168,6 @@
<td>[cors.subdomain] max_age = 3600</td>
<td>(IntOpt) Maximum cache age of CORS preflight requests.</td>
</tr>
<tr>
<td>[eventlet_opts] client_socket_timeout = 900</td>
<td>(IntOpt) Timeout for client connections' socket operations. If an incoming connection is idle for this number of seconds it will be closed. A value of '0' means wait forever.</td>
</tr>
<tr>
<td>[eventlet_opts] wsgi_keep_alive = True</td>
<td>(BoolOpt) If False, closes the client socket connection explicitly.</td>
</tr>
<tr>
<td>[heat_api] tcp_keepidle = 600</td>
<td>(IntOpt) The value for the socket option TCP_KEEPIDLE. This is the time in seconds that the connection must be idle before TCP starts sending keepalive probes.</td>
@@ -156,9 +180,33 @@
<td>[heat_api_cloudwatch] tcp_keepidle = 600</td>
<td>(IntOpt) The value for the socket option TCP_KEEPIDLE. This is the time in seconds that the connection must be idle before TCP starts sending keepalive probes.</td>
</tr>
<tr>
<td>[keystone_authtoken] region_name = None</td>
<td>(StrOpt) The region in which the identity server can be found.</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] password = </td>
<td>(StrOpt) Password for message broker authentication</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_config_dir = </td>
<td>(StrOpt) Path to directory that contains the SASL configuration</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_config_name = </td>
<td>(StrOpt) Name of configuration file (without .conf suffix)</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_mechanisms = </td>
<td>(StrOpt) Space separated list of acceptable SASL mechanisms</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] username = </td>
<td>(StrOpt) User name for message broker authentication</td>
</tr>
<tr>
<td>[oslo_messaging_qpid] send_single_reply = False</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in M release.</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in the Mitaka release.</td>
</tr>
<tr>
<td>[oslo_messaging_rabbit] kombu_reconnect_timeout = 60</td>
@@ -166,7 +214,7 @@
</tr>
<tr>
<td>[oslo_messaging_rabbit] send_single_reply = False</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in M release.</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in the Mitaka release.</td>
</tr>
<tr>
<td>[oslo_middleware] secure_proxy_ssl_header = X-Forwarded-Proto</td>
@@ -188,6 +236,14 @@
<td>[oslo_versionedobjects] fatal_exception_format_errors = False</td>
<td>(BoolOpt) Make exception message format errors fatal</td>
</tr>
<tr>
<td>[trustee] auth_plugin = None</td>
<td>(StrOpt) Name of the plugin to load</td>
</tr>
<tr>
<td>[trustee] auth_section = None</td>
<td>(StrOpt) Config Section from which to load plugin specific options</td>
</tr>
</table>
<table>
<caption>New default values</caption>
@@ -216,16 +272,16 @@
<td></td>
<td>None</td>
</tr>
<tr>
<td>[DEFAULT] instance_user</td>
<td>ec2-user</td>
<td></td>
</tr>
<tr>
<td>[DEFAULT] logging_exception_prefix</td>
<td>%(asctime)s.%(msecs)03d %(process)d TRACE %(name)s %(instance)s</td>
<td>%(asctime)s.%(msecs)03d %(process)d ERROR %(name)s %(instance)s</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_matchmaker</td>
<td>local</td>
<td>redis</td>
</tr>
<tr>
<td>[DEFAULT] use_syslog_rfc_format</td>
<td>False</td>
@@ -239,7 +295,12 @@
<tr>
<td>[heat_api] workers</td>
<td>0</td>
<td>4</td>
<td>8</td>
</tr>
<tr>
<td>[matchmaker_redis] password</td>
<td>None</td>
<td></td>
</tr>
<tr>
<td>[oslo_messaging_rabbit] heartbeat_timeout_threshold</td>
@@ -257,10 +318,6 @@
<td>New Option</td>
</tr>
</thead>
<tr>
<td>[DEFAULT] use_syslog</td>
<td>None</td>
</tr>
<tr>
<td>[DEFAULT] rpc_thread_pool_size</td>
<td>[DEFAULT] executor_thread_pool_size</td>
@@ -269,5 +326,9 @@
<td>[DEFAULT] log_format</td>
<td>None</td>
</tr>
<tr>
<td>[DEFAULT] use_syslog</td>
<td>None</td>
</tr>
</table>
</section>

184
doc/config-reference/conf-changes/ironic.xml
View File

@@ -1,7 +1,7 @@
<?xml version='1.0' encoding='UTF-8'?>
<section xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="ironic-conf-changes-liberty">
<!-- Warning: Do not edit this file. It is automatically generated and your changes will be overwritten. The tool to do so lives in the openstack-doc-tools repository. -->
<title>New, updated and deprecated options in Liberty for Bare metal service</title>
<title>New, updated, and deprecated options in Liberty for Bare metal service</title>
<table>
<caption>New options</caption>
<col width="50%"/>
@@ -16,13 +16,45 @@
<td>[DEFAULT] executor_thread_pool_size = 64</td>
<td>(IntOpt) Size of executor thread pool.</td>
</tr>
<tr>
<td>[DEFAULT] password = </td>
<td>(StrOpt) Password for Redis server (optional).</td>
</tr>
<tr>
<td>[DEFAULT] port = 6379</td>
<td>(IntOpt) Use this port to connect to redis host.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_conn_pool_size = 30</td>
<td>(IntOpt) Size of RPC connection pool.</td>
</tr>
<tr>
<td>[agent] agent_erase_devices_iterations = 1</td>
<td>(IntOpt) Number of iterations to be run for erasing devices.</td>
<td>[DEFAULT] rpc_poll_timeout = 1</td>
<td>(IntOpt) The default number of seconds that poll should wait. Poll raises timeout exception when timeout expired.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_all_req_rep = True</td>
<td>(BoolOpt) Use REQ/REP pattern for all methods CALL/CAST/FANOUT.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_concurrency = eventlet</td>
<td>(StrOpt) Type of concurrency used. Either "native" or "eventlet"</td>
</tr>
<tr>
<td>[DEFAULT] watch_log_file = False</td>
<td>(BoolOpt) (Optional) Uses logging handler designed to watch file system. When log file is moved or removed this handler will open a new log file with specified path instantaneously. It makes sense only if log-file option is specified and Linux platform is used. This option is ignored if log_config_append is set.</td>
</tr>
<tr>
<td>[DEFAULT] zmq_use_broker = True</td>
<td>(BoolOpt) Shows whether zmq-messaging uses broker or not.</td>
</tr>
<tr>
<td>[agent] manage_agent_boot = True</td>
<td>(BoolOpt) Whether Ironic will manage booting of the agent ramdisk. If set to False, you will need to configure your mechanism to allow booting the agent ramdisk.</td>
</tr>
<tr>
<td>[agent] memory_consumed_by_agent = 0</td>
<td>(IntOpt) The memory size in MiB consumed by agent when it is booted on a bare metal node. This is used for checking if the image can be downloaded and deployed on the bare metal node after booting agent ramdisk. This may be set according to the memory consumed by the agent ramdisk image.</td>
</tr>
<tr>
<td>[agent] post_deploy_get_power_state_retries = 6</td>
@@ -32,6 +64,18 @@
<td>[agent] post_deploy_get_power_state_retry_interval = 5</td>
<td>(IntOpt) Amount of time (in seconds) to wait between polling power state after trigger soft poweroff.</td>
</tr>
<tr>
<td>[api] public_endpoint = None</td>
<td>(StrOpt) Public URL to use when building the links to the API resources (for example, "https://ironic.rocks:6384"). If None the links will be built using the request's host URL. If the API is operating behind a proxy, you will want to change this to represent the proxy's URL. Defaults to None.</td>
</tr>
<tr>
<td>[cimc] action_interval = 10</td>
<td>(IntOpt) Amount of time in seconds to wait in between power operations</td>
</tr>
<tr>
<td>[cimc] max_retry = 6</td>
<td>(IntOpt) Number of times a power operation needs to be retried</td>
</tr>
<tr>
<td>[cisco_ucs] action_interval = 5</td>
<td>(IntOpt) Amount of time in seconds to wait in between power operations</td>
@@ -40,6 +84,66 @@
<td>[cisco_ucs] max_retry = 6</td>
<td>(IntOpt) Number of times a power operation needs to be retried</td>
</tr>
<tr>
<td>[conductor] clean_callback_timeout = 1800</td>
<td>(IntOpt) Timeout (seconds) to wait for a callback from the ramdisk doing the cleaning. If the timeout is reached the node will be put in the "clean failed" provision state. Set to 0 to disable timeout.</td>
</tr>
<tr>
<td>[cors] allow_credentials = True</td>
<td>(BoolOpt) Indicate that the actual request can include user credentials</td>
</tr>
<tr>
<td>[cors] allow_headers = Content-Type, Cache-Control, Content-Language, Expires, Last-Modified, Pragma</td>
<td>(ListOpt) Indicate which header field names may be used during the actual request.</td>
</tr>
<tr>
<td>[cors] allow_methods = GET, POST, PUT, DELETE, OPTIONS</td>
<td>(ListOpt) Indicate which methods can be used during the actual request.</td>
</tr>
<tr>
<td>[cors] allowed_origin = None</td>
<td>(StrOpt) Indicate whether this resource may be shared with the domain received in the requests "origin" header.</td>
</tr>
<tr>
<td>[cors] expose_headers = Content-Type, Cache-Control, Content-Language, Expires, Last-Modified, Pragma</td>
<td>(ListOpt) Indicate which headers are safe to expose to the API. Defaults to HTTP Simple Headers.</td>
</tr>
<tr>
<td>[cors] max_age = 3600</td>
<td>(IntOpt) Maximum cache age of CORS preflight requests.</td>
</tr>
<tr>
<td>[cors.subdomain] allow_credentials = True</td>
<td>(BoolOpt) Indicate that the actual request can include user credentials</td>
</tr>
<tr>
<td>[cors.subdomain] allow_headers = Content-Type, Cache-Control, Content-Language, Expires, Last-Modified, Pragma</td>
<td>(ListOpt) Indicate which header field names may be used during the actual request.</td>
</tr>
<tr>
<td>[cors.subdomain] allow_methods = GET, POST, PUT, DELETE, OPTIONS</td>
<td>(ListOpt) Indicate which methods can be used during the actual request.</td>
</tr>
<tr>
<td>[cors.subdomain] allowed_origin = None</td>
<td>(StrOpt) Indicate whether this resource may be shared with the domain received in the requests "origin" header.</td>
</tr>
<tr>
<td>[cors.subdomain] expose_headers = Content-Type, Cache-Control, Content-Language, Expires, Last-Modified, Pragma</td>
<td>(ListOpt) Indicate which headers are safe to expose to the API. Defaults to HTTP Simple Headers.</td>
</tr>
<tr>
<td>[cors.subdomain] max_age = 3600</td>
<td>(IntOpt) Maximum cache age of CORS preflight requests.</td>
</tr>
<tr>
<td>[deploy] erase_devices_iterations = 1</td>
<td>(IntOpt) Number of iterations to be run for erasing devices.</td>
</tr>
<tr>
<td>[deploy] erase_devices_priority = None</td>
<td>(IntOpt) Priority to run in-band erase devices via the Ironic Python Agent ramdisk. If unset, will use the priority set in the ramdisk (defaults to 10 for the GenericHardwareManager). If set to 0, will not run during cleaning.</td>
</tr>
<tr>
<td>[deploy] http_root = /httpboot</td>
<td>(StrOpt) ironic-conductor node's HTTP root path.</td>
@@ -56,6 +160,18 @@
<td>[drac] client_retry_delay = 5</td>
<td>(IntOpt) In case there is a communication failure, the DRAC client is going to wait for as many seconds as defined in this setting before resending the request.</td>
</tr>
<tr>
<td>[iboot] max_retry = 3</td>
<td>(IntOpt) Maximum retries for iBoot operations</td>
</tr>
<tr>
<td>[iboot] retry_interval = 1</td>
<td>(IntOpt) Time between retry attempts for iBoot operations</td>
</tr>
<tr>
<td>[ilo] use_web_server_for_images = False</td>
<td>(BoolOpt) Set this to True to use http web server to host floppy images and generated boot ISO. This requires http_root and http_url to be configured in the [deploy] section of the config file. If this is set to False, then Ironic will use Swift to host the floppy images and generated boot_iso.</td>
</tr>
<tr>
<td>[inspector] enabled = False</td>
<td>(BoolOpt) whether to enable inspection using ironic-inspector</td>
@@ -96,9 +212,33 @@
<td>[irmc] remote_image_user_password = None</td>
<td>(StrOpt) Password of remote_image_user_name</td>
</tr>
<tr>
<td>[keystone_authtoken] region_name = None</td>
<td>(StrOpt) The region in which the identity server can be found.</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] password = </td>
<td>(StrOpt) Password for message broker authentication</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_config_dir = </td>
<td>(StrOpt) Path to directory that contains the SASL configuration</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_config_name = </td>
<td>(StrOpt) Name of configuration file (without .conf suffix)</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_mechanisms = </td>
<td>(StrOpt) Space separated list of acceptable SASL mechanisms</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] username = </td>
<td>(StrOpt) User name for message broker authentication</td>
</tr>
<tr>
<td>[oslo_messaging_qpid] send_single_reply = False</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in M release.</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in the Mitaka release.</td>
</tr>
<tr>
<td>[oslo_messaging_rabbit] kombu_reconnect_timeout = 60</td>
@@ -106,7 +246,15 @@
</tr>
<tr>
<td>[oslo_messaging_rabbit] send_single_reply = False</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in M release.</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in the Mitaka release.</td>
</tr>
<tr>
<td>[oslo_middleware] max_request_body_size = 114688</td>
<td>(IntOpt) The maximum body size for each request, in bytes.</td>
</tr>
<tr>
<td>[oslo_middleware] secure_proxy_ssl_header = X-Forwarded-Proto</td>
<td>(StrOpt) The HTTP Header that will be used to determine what the original request protocol scheme was, even if it was hidden by an SSL termination proxy.</td>
</tr>
<tr>
<td>[oslo_versionedobjects] fatal_exception_format_errors = False</td>
@@ -135,6 +283,11 @@
<td>%(asctime)s.%(msecs)03d %(process)d TRACE %(name)s %(instance)s</td>
<td>%(asctime)s.%(msecs)03d %(process)d ERROR %(name)s %(instance)s</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_matchmaker</td>
<td>local</td>
<td>redis</td>
</tr>
<tr>
<td>[DEFAULT] tempdir</td>
<td>None</td>
@@ -150,6 +303,11 @@
<td>False</td>
<td>True</td>
</tr>
<tr>
<td>[matchmaker_redis] password</td>
<td>None</td>
<td></td>
</tr>
<tr>
<td>[oslo_messaging_rabbit] heartbeat_timeout_threshold</td>
<td>0</td>
@@ -166,6 +324,14 @@
<td>New Option</td>
</tr>
</thead>
<tr>
<td>[agent] agent_pxe_append_params</td>
<td>None</td>
</tr>
<tr>
<td>[agent] agent_erase_devices_priority</td>
<td>[deploy] erase_devices_priority</td>
</tr>
<tr>
<td>[DEFAULT] rpc_thread_pool_size</td>
<td>[DEFAULT] executor_thread_pool_size</td>
@@ -174,9 +340,17 @@
<td>[DEFAULT] log_format</td>
<td>None</td>
</tr>
<tr>
<td>[agent] agent_pxe_config_template</td>
<td>None</td>
</tr>
<tr>
<td>[DEFAULT] use_syslog</td>
<td>None</td>
</tr>
<tr>
<td>[agent] manage_tftp</td>
<td>[agent] manage_agent_boot</td>
</tr>
</table>
</section>

89
doc/config-reference/conf-changes/keystone.xml
View File

@@ -1,7 +1,7 @@
<?xml version='1.0' encoding='UTF-8'?>
<section xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="keystone-conf-changes-liberty">
<!-- Warning: Do not edit this file. It is automatically generated and your changes will be overwritten. The tool to do so lives in the openstack-doc-tools repository. -->
<title>New, updated and deprecated options in Liberty for OpenStack Identity</title>
<title>New, updated, and deprecated options in Liberty for OpenStack Identity</title>
<table>
<caption>New options</caption>
<col width="50%"/>
@@ -16,10 +16,42 @@
<td>[DEFAULT] executor_thread_pool_size = 64</td>
<td>(IntOpt) Size of executor thread pool.</td>
</tr>
<tr>
<td>[DEFAULT] host = 127.0.0.1</td>
<td>(StrOpt) Host to locate redis.</td>
</tr>
<tr>
<td>[DEFAULT] password = </td>
<td>(StrOpt) Password for Redis server (optional).</td>
</tr>
<tr>
<td>[DEFAULT] port = 6379</td>
<td>(IntOpt) Use this port to connect to redis host.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_conn_pool_size = 30</td>
<td>(IntOpt) Size of RPC connection pool.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_poll_timeout = 1</td>
<td>(IntOpt) The default number of seconds that poll should wait. Poll raises timeout exception when timeout expired.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_all_req_rep = True</td>
<td>(BoolOpt) Use REQ/REP pattern for all methods CALL/CAST/FANOUT.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_concurrency = eventlet</td>
<td>(StrOpt) Type of concurrency used. Either "native" or "eventlet"</td>
</tr>
<tr>
<td>[DEFAULT] watch_log_file = False</td>
<td>(BoolOpt) (Optional) Uses logging handler designed to watch file system. When log file is moved or removed this handler will open a new log file with specified path instantaneously. It makes sense only if log-file option is specified and Linux platform is used. This option is ignored if log_config_append is set.</td>
</tr>
<tr>
<td>[DEFAULT] zmq_use_broker = True</td>
<td>(BoolOpt) Shows whether zmq-messaging uses broker or not.</td>
</tr>
<tr>
<td>[cors] allow_credentials = True</td>
<td>(BoolOpt) Indicate that the actual request can include user credentials</td>
@@ -72,9 +104,33 @@
<td>[endpoint_policy] enabled = True</td>
<td>(BoolOpt) Enable endpoint_policy functionality.</td>
</tr>
<tr>
<td>[keystone_authtoken] region_name = None</td>
<td>(StrOpt) The region in which the identity server can be found.</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] password = </td>
<td>(StrOpt) Password for message broker authentication</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_config_dir = </td>
<td>(StrOpt) Path to directory that contains the SASL configuration</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_config_name = </td>
<td>(StrOpt) Name of configuration file (without .conf suffix)</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_mechanisms = </td>
<td>(StrOpt) Space separated list of acceptable SASL mechanisms</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] username = </td>
<td>(StrOpt) User name for message broker authentication</td>
</tr>
<tr>
<td>[oslo_messaging_qpid] send_single_reply = False</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in M release.</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in the Mitaka release.</td>
</tr>
<tr>
<td>[oslo_messaging_rabbit] kombu_reconnect_timeout = 60</td>
@@ -82,12 +138,24 @@
</tr>
<tr>
<td>[oslo_messaging_rabbit] send_single_reply = False</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in M release.</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in the Mitaka release.</td>
</tr>
<tr>
<td>[oslo_middleware] secure_proxy_ssl_header = X-Forwarded-Proto</td>
<td>(StrOpt) The HTTP Header that will be used to determine what the original request protocol scheme was, even if it was hidden by an SSL termination proxy.</td>
</tr>
<tr>
<td>[tokenless_auth] issuer_attribute = SSL_CLIENT_I_DN</td>
<td>(StrOpt) The issuer attribute that is served as an IdP ID for the X.509 tokenless authorization along with the protocol to look up its corresponding mapping. It is the environment variable in the WSGI environment that references to the issuer of the client certificate.</td>
</tr>
<tr>
<td>[tokenless_auth] protocol = x509</td>
<td>(StrOpt) The protocol name for the X.509 tokenless authorization along with the option issuer_attribute below can look up its corresponding mapping.</td>
</tr>
<tr>
<td>[tokenless_auth] trusted_issuer = []</td>
<td>(MultiStrOpt) The list of trusted issuers to further filter the certificates that are allowed to participate in the X.509 tokenless authorization. If the option is absent then no certificates will be allowed. The naming format for the attributes of a Distinguished Name(DN) must be separated by a comma and contain no spaces. This configuration option may be repeated for multiple values. For example: trusted_issuer=CN=john,OU=keystone,O=openstack trusted_issuer=CN=mary,OU=eng,O=abc</td>
</tr>
</table>
<table>
<caption>New default values</caption>
@@ -116,6 +184,11 @@
<td>%(asctime)s.%(msecs)03d %(process)d TRACE %(name)s %(instance)s</td>
<td>%(asctime)s.%(msecs)03d %(process)d ERROR %(name)s %(instance)s</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_matchmaker</td>
<td>local</td>
<td>redis</td>
</tr>
<tr>
<td>[DEFAULT] use_syslog_rfc_format</td>
<td>False</td>
@@ -191,6 +264,16 @@
<td>keystone.identity.id_generators.sha256.Generator</td>
<td>sha256</td>
</tr>
<tr>
<td>[ldap] user_attribute_ignore</td>
<td>default_project_id, tenants</td>
<td>default_project_id</td>
</tr>
<tr>
<td>[matchmaker_redis] password</td>
<td>None</td>
<td></td>
</tr>
<tr>
<td>[oauth1] driver</td>
<td>keystone.contrib.oauth1.backends.sql.OAuth1</td>

83
doc/config-reference/conf-changes/manila.xml
View File

@@ -32,6 +32,10 @@
<td>[DEFAULT] enable_pre_hooks = False</td>
<td>(BoolOpt) Whether to enable pre hooks or not.</td>
</tr>
<tr>
<td>[DEFAULT] executor_thread_pool_size = 64</td>
<td>(IntOpt) Size of executor thread pool.</td>
</tr>
<tr>
<td>[DEFAULT] glusterfs_share_layout = None</td>
<td>(StrOpt) Specifies GlusterFS share layout, that is, the method of associating backing GlusterFS resources to shares.</td>
@@ -124,6 +128,10 @@
<td>[DEFAULT] osapi_share_workers = 1</td>
<td>(IntOpt) Number of workers for OpenStack Share API service.</td>
</tr>
<tr>
<td>[DEFAULT] password = </td>
<td>(StrOpt) Password for Redis server (optional).</td>
</tr>
<tr>
<td>[DEFAULT] periodic_hooks_interval = 300.0</td>
<td>(FloatOpt) Interval in seconds between execution of periodic hooks. Used when option 'enable_periodic_hooks' is set to True. Default is 300.</td>
@@ -132,6 +140,26 @@
<td>[DEFAULT] pool_weight_multiplier = 1.0</td>
<td>(FloatOpt) Multiplier used for weighing pools which have existing share servers. Negative numbers mean to spread vs stack.</td>
</tr>
<tr>
<td>[DEFAULT] port = 6379</td>
<td>(IntOpt) Use this port to connect to redis host.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_conn_pool_size = 30</td>
<td>(IntOpt) Size of RPC connection pool.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_poll_timeout = 1</td>
<td>(IntOpt) The default number of seconds that poll should wait. Poll raises timeout exception when timeout expired.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_all_req_rep = True</td>
<td>(BoolOpt) Use REQ/REP pattern for all methods CALL/CAST/FANOUT.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_concurrency = eventlet</td>
<td>(StrOpt) Type of concurrency used. Either "native" or "eventlet"</td>
</tr>
<tr>
<td>[DEFAULT] suppress_post_hooks_errors = False</td>
<td>(BoolOpt) Whether to suppress post hook errors (allow driver's results to pass through) or not.</td>
@@ -176,6 +204,10 @@
<td>[DEFAULT] wsgi_keep_alive = True</td>
<td>(BoolOpt) If False, closes the client socket connection explicitly. Setting it to True to maintain backward compatibility. Recommended setting is set it to False.</td>
</tr>
<tr>
<td>[DEFAULT] zmq_use_broker = True</td>
<td>(BoolOpt) Shows whether zmq-messaging uses broker or not.</td>
</tr>
<tr>
<td>[cors] allow_credentials = True</td>
<td>(BoolOpt) Indicate that the actual request can include user credentials</td>
@@ -228,6 +260,38 @@
<td>[keystone_authtoken] region_name = None</td>
<td>(StrOpt) The region in which the identity server can be found.</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] password = </td>
<td>(StrOpt) Password for message broker authentication</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_config_dir = </td>
<td>(StrOpt) Path to directory that contains the SASL configuration</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_config_name = </td>
<td>(StrOpt) Name of configuration file (without .conf suffix)</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_mechanisms = </td>
<td>(StrOpt) Space separated list of acceptable SASL mechanisms</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] username = </td>
<td>(StrOpt) User name for message broker authentication</td>
</tr>
<tr>
<td>[oslo_messaging_qpid] send_single_reply = False</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in the Mitaka release.</td>
</tr>
<tr>
<td>[oslo_messaging_rabbit] kombu_reconnect_timeout = 60</td>
<td>(IntOpt) How long to wait before considering a reconnect attempt to have failed. This value should not be longer than rpc_response_timeout.</td>
</tr>
<tr>
<td>[oslo_messaging_rabbit] send_single_reply = False</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in the Mitaka release.</td>
</tr>
<tr>
<td>[oslo_middleware] max_request_body_size = 114688</td>
<td>(IntOpt) The maximum body size for each request, in bytes.</td>
@@ -286,6 +350,11 @@
<td>0.0.0.0</td>
<td>::</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_matchmaker</td>
<td>local</td>
<td>redis</td>
</tr>
<tr>
<td>[DEFAULT] scheduler_default_filters</td>
<td>AvailabilityZoneFilter, CapacityFilter, CapabilitiesFilter</td>
@@ -301,6 +370,16 @@
<td>False</td>
<td>True</td>
</tr>
<tr>
<td>[matchmaker_redis] password</td>
<td>None</td>
<td></td>
</tr>
<tr>
<td>[oslo_messaging_rabbit] heartbeat_timeout_threshold</td>
<td>0</td>
<td>60</td>
</tr>
</table>
<table>
<caption>Deprecated options</caption>
@@ -340,6 +419,10 @@
<td>[DEFAULT] sql_idle_timeout</td>
<td>[database] idle_timeout</td>
</tr>
<tr>
<td>[DEFAULT] rpc_thread_pool_size</td>
<td>[DEFAULT] executor_thread_pool_size</td>
</tr>
<tr>
<td>[DEFAULT] db_backend</td>
<td>[database] backend</td>

223
doc/config-reference/conf-changes/neutron.xml
View File

@@ -1,7 +1,7 @@
<?xml version='1.0' encoding='UTF-8'?>
<section xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="neutron-conf-changes-liberty">
<!-- Warning: Do not edit this file. It is automatically generated and your changes will be overwritten. The tool to do so lives in the openstack-doc-tools repository. -->
<title>New, updated and deprecated options in Liberty for OpenStack Networking</title>
<title>New, updated, and deprecated options in Liberty for OpenStack Networking</title>
<table>
<caption>New options</caption>
<col width="50%"/>
@@ -12,13 +12,17 @@
<td>(Type) Help string</td>
</tr>
</thead>
<tr>
<td>[DEFAULT] dns_domain = openstacklocal</td>
<td>(StrOpt) Domain to use for building the hostnames</td>
</tr>
<tr>
<td>[DEFAULT] dnsmasq_base_log_dir = None</td>
<td>(StrOpt) Base log dir for dnsmasq logging. The log contains DHCP and DNS log information and is useful for debugging issues with either DHCP or DNS. If this section is null, disable dnsmasq log.</td>
</tr>
<tr>
<td>[DEFAULT] ebtables_path = $state_path/ebtables-</td>
<td>(StrOpt) Location of temporary ebtables table files.</td>
<td>[DEFAULT] enable_new_agents = True</td>
<td>(BoolOpt) Agent starts with admin_state_up=False when enable_new_agents=False. In the case, user's resources will not be scheduled automatically to the agent until admin changes admin_state_up to True.</td>
</tr>
<tr>
<td>[DEFAULT] enable_snat_by_default = True</td>
@@ -32,30 +36,118 @@
<td>[DEFAULT] executor_thread_pool_size = 64</td>
<td>(IntOpt) Size of executor thread pool.</td>
</tr>
<tr>
<td>[DEFAULT] force_metadata = False</td>
<td>(BoolOpt) Force to use DHCP to get Metadata on all networks.</td>
</tr>
<tr>
<td>[DEFAULT] ipam_driver = None</td>
<td>(StrOpt) IPAM driver to use.</td>
</tr>
<tr>
<td>[DEFAULT] password = </td>
<td>(StrOpt) Password for Redis server (optional).</td>
</tr>
<tr>
<td>[DEFAULT] pd_confs = $state_path/pd</td>
<td>(StrOpt) Location to store IPv6 PD files.</td>
</tr>
<tr>
<td>[DEFAULT] pd_dhcp_driver = dibbler</td>
<td>(StrOpt) Service to handle DHCPv6 Prefix delegation.</td>
</tr>
<tr>
<td>[DEFAULT] port = 6379</td>
<td>(IntOpt) Use this port to connect to redis host.</td>
</tr>
<tr>
<td>[DEFAULT] prefix_delegation_driver = dibbler</td>
<td>(StrOpt) Driver used for ipv6 prefix delegation. This needs to be an entry point defined in the neutron.agent.linux.pd_drivers namespace. See setup.cfg for entry points included with the neutron source.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_conn_pool_size = 30</td>
<td>(IntOpt) Size of RPC connection pool.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_poll_timeout = 1</td>
<td>(IntOpt) The default number of seconds that poll should wait. Poll raises timeout exception when timeout expired.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_all_req_rep = True</td>
<td>(BoolOpt) Use REQ/REP pattern for all methods CALL/CAST/FANOUT.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_concurrency = eventlet</td>
<td>(StrOpt) Type of concurrency used. Either "native" or "eventlet"</td>
</tr>
<tr>
<td>[DEFAULT] vendor_pen = 8888</td>
<td>(StrOpt) A decimal value as Vendor's Registered Private Enterprise Number as required by RFC3315 DUID-EN.</td>
</tr>
<tr>
<td>[DEFAULT] watch_log_file = False</td>
<td>(BoolOpt) (Optional) Uses logging handler designed to watch file system. When log file is moved or removed this handler will open a new log file with specified path instantaneously. It makes sense only if log-file option is specified and Linux platform is used. This option is ignored if log_config_append is set.</td>
</tr>
<tr>
<td>[DEFAULT] zmq_use_broker = True</td>
<td>(BoolOpt) Shows whether zmq-messaging uses broker or not.</td>
</tr>
<tr>
<td>[AGENT] agent_type = Open vSwitch agent</td>
<td>(StrOpt) Selects the Agent Type reported</td>
</tr>
<tr>
<td>[AGENT] drop_flows_on_start = False</td>
<td>(BoolOpt) Reset flow table on start. Setting this to True will cause brief traffic interruption.</td>
</tr>
<tr>
<td>[AGENT] log_agent_heartbeats = False</td>
<td>(BoolOpt) Log agent heartbeats</td>
</tr>
<tr>
<td>[NOVA] node_override_vif_ib_hostdev = </td>
<td>(ListOpt) Nova compute nodes to manually set VIF type to ib_hostdev</td>
<td>[AGENT] tunnel_csum = False</td>
<td>(BoolOpt) Set or un-set the tunnel header checksum on outgoing IP packet carrying GRE/VXLAN tunnel.</td>
</tr>
<tr>
<td>[LINUX_BRIDGE] bridge_mappings = </td>
<td>(ListOpt) List of &lt;physical_network&gt;:&lt;physical_bridge&gt;</td>
</tr>
<tr>
<td>[OVS] datapath_type = system</td>
<td>(StrOpt) OVS datapath to use.</td>
</tr>
<tr>
<td>[OVS] of_connect_timeout = 30</td>
<td>(IntOpt) Timeout in seconds to wait for the local switch connecting the controller. Used only for 'native' driver.</td>
</tr>
<tr>
<td>[OVS] of_interface = ovs-ofctl</td>
<td>(StrOpt) OpenFlow interface to use.</td>
</tr>
<tr>
<td>[OVS] of_listen_address = 127.0.0.1</td>
<td>(IPOpt) Address to listen on for OpenFlow connections. Used only for 'native' driver.</td>
</tr>
<tr>
<td>[OVS] of_listen_port = 6633</td>
<td>(IntOpt) Port to listen on for OpenFlow connections. Used only for 'native' driver.</td>
</tr>
<tr>
<td>[OVS] of_request_timeout = 10</td>
<td>(IntOpt) Timeout in seconds to wait for a single OpenFlow request. Used only for 'native' driver.</td>
</tr>
<tr>
<td>[QUOTAS] quota_rbac_entry = 10</td>
<td>(IntOpt) Default number of RBAC entries allowed per tenant. A negative value means unlimited.</td>
</tr>
<tr>
<td>[QUOTAS] track_quota_usage = True</td>
<td>(BoolOpt) Keep in track in the database of current resourcequota usage. Plugins which do not leverage the neutron database should set this flag to False</td>
</tr>
<tr>
<td>[agent] extensions = </td>
<td>(ListOpt) Extensions list to use</td>
</tr>
<tr>
<td>[cors] allow_credentials = True</td>
<td>(BoolOpt) Indicate that the actual request can include user credentials</td>
@@ -105,72 +197,44 @@
<td>(IntOpt) Maximum cache age of CORS preflight requests.</td>
</tr>
<tr>
<td>[dvs] api_retry_count = 10</td>
<td>(IntOpt) The number of times we retry on failures, e.g., socket error, etc.</td>
</tr>
<tr>
<td>[dvs] dvs_name = None</td>
<td>(StrOpt) The name of the preconfigured DVS.</td>
</tr>
<tr>
<td>[dvs] host_ip = None</td>
<td>(StrOpt) Hostname or IP address for connection to VMware VC host.</td>
</tr>
<tr>
<td>[dvs] host_password = None</td>
<td>(StrOpt) Password for connection to VMware VC host.</td>
</tr>
<tr>
<td>[dvs] host_port = 443</td>
<td>(IntOpt) Port for connection to VMware VC host.</td>
</tr>
<tr>
<td>[dvs] host_username = None</td>
<td>(StrOpt) Username for connection to VMware VC host.</td>
</tr>
<tr>
<td>[dvs] task_poll_interval = 0.5</td>
<td>(FloatOpt) The interval used for polling of remote tasks.</td>
<td>[keystone_authtoken] region_name = None</td>
<td>(StrOpt) The region in which the identity server can be found.</td>
</tr>
<tr>
<td>[ml2] external_network_type = None</td>
<td>(StrOpt) Default network type for external networks when no provider attributes are specified. By default it is None, which means that if provider attributes are not specified while creating external networks then they will have the same type as tenant networks. Allowed values for external_network_type config option depend on the network type values configured in type_drivers config option.</td>
</tr>
<tr>
<td>[nsx_v3] nsx_manager = None</td>
<td>(StrOpt) IP address of the NSX manager</td>
<td>[ml2_type_geneve] max_header_size = 50</td>
<td>(IntOpt) Geneve encapsulation header size is dynamic, this value is used to calculate the maximum MTU for the driver.this is the sum of the sizes of the outer ETH + IP + UDP + GENEVE header sizes</td>
</tr>
<tr>
<td>[nsx_v3] nsx_password = default</td>
<td>(StrOpt) Password for the NSX manager</td>
<td>[ml2_type_geneve] vni_ranges = </td>
<td>(ListOpt) Comma-separated list of &lt;vni_min&gt;:&lt;vni_max&gt; tuples enumerating ranges of Geneve VNI IDs that are available for tenant network allocation</td>
</tr>
<tr>
<td>[nsx_v3] nsx_user = admin</td>
<td>(StrOpt) User name for the NSX manager</td>
<td>[oslo_messaging_amqp] password = </td>
<td>(StrOpt) Password for message broker authentication</td>
</tr>
<tr>
<td>[nsxv] dhcp_lease_time = 86400</td>
<td>(IntOpt) DHCP default lease time.</td>
<td>[oslo_messaging_amqp] sasl_config_dir = </td>
<td>(StrOpt) Path to directory that contains the SASL configuration</td>
</tr>
<tr>
<td>[nsxv] edge_appliance_password = None</td>
<td>(StrOpt) Password to configure for Edge appliance login</td>
<td>[oslo_messaging_amqp] sasl_config_name = </td>
<td>(StrOpt) Name of configuration file (without .conf suffix)</td>
</tr>
<tr>
<td>[nsxv] edge_appliance_user = None</td>
<td>(StrOpt) Username to configure for Edge appliance login</td>
<td>[oslo_messaging_amqp] sasl_mechanisms = </td>
<td>(StrOpt) Space separated list of acceptable SASL mechanisms</td>
</tr>
<tr>
<td>[nsxv] locking_coordinator_url = None</td>
<td>(StrOpt) A URL to a locking mechanism coordinator</td>
</tr>
<tr>
<td>[nsxv] metadata_initializer = True</td>
<td>(BoolOpt) If True, the server instance will attempt to initialize the metadata infrastructure</td>
<td>[oslo_messaging_amqp] username = </td>
<td>(StrOpt) User name for message broker authentication</td>
</tr>
<tr>
<td>[oslo_messaging_qpid] send_single_reply = False</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in M release.</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in the Mitaka release.</td>
</tr>
<tr>
<td>[oslo_messaging_rabbit] kombu_reconnect_timeout = 60</td>
@@ -178,7 +242,7 @@
</tr>
<tr>
<td>[oslo_messaging_rabbit] send_single_reply = False</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in M release.</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in the Mitaka release.</td>
</tr>
<tr>
<td>[oslo_middleware] secure_proxy_ssl_header = X-Forwarded-Proto</td>
@@ -196,6 +260,14 @@
<td>[oslo_policy] policy_file = policy.json</td>
<td>(StrOpt) The JSON file that defines policies.</td>
</tr>
<tr>
<td>[oslo_versionedobjects] fatal_exception_format_errors = False</td>
<td>(BoolOpt) Make exception message format errors fatal</td>
</tr>
<tr>
<td>[qos] notification_drivers = message_queue</td>
<td>(ListOpt) Drivers list to use to send the update notification</td>
</tr>
</table>
<table>
<caption>New default values</caption>
@@ -234,11 +306,31 @@
<td>%(asctime)s.%(msecs)03d %(process)d TRACE %(name)s %(instance)s</td>
<td>%(asctime)s.%(msecs)03d %(process)d ERROR %(name)s %(instance)s</td>
</tr>
<tr>
<td>[DEFAULT] network_scheduler_driver</td>
<td>neutron.scheduler.dhcp_agent_scheduler.ChanceScheduler</td>
<td>neutron.scheduler.dhcp_agent_scheduler.WeightScheduler</td>
</tr>
<tr>
<td>[DEFAULT] router_delete_namespaces</td>
<td>False</td>
<td>True</td>
</tr>
<tr>
<td>[DEFAULT] router_scheduler_driver</td>
<td>neutron.scheduler.l3_agent_scheduler.ChanceScheduler</td>
<td>neutron.scheduler.l3_agent_scheduler.LeastRoutersScheduler</td>
</tr>
<tr>
<td>[DEFAULT] rpc_workers</td>
<td>0</td>
<td>1</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_matchmaker</td>
<td>local</td>
<td>redis</td>
</tr>
<tr>
<td>[DEFAULT] use_syslog_rfc_format</td>
<td>False</td>
@@ -254,21 +346,26 @@
<td>False</td>
<td>True</td>
</tr>
<tr>
<td>[NOVA] vif_types</td>
<td>unbound, binding_failed, ovs, ivs, bridge, 802.1qbg, 802.1qbh, hyperv, midonet, mlnx_direct, hostdev, hw_veb, dvs, other, distributed, vrouter</td>
<td>unbound, binding_failed, ovs, ivs, bridge, 802.1qbg, 802.1qbh, hyperv, midonet, ib_hostdev, hw_veb, dvs, other, distributed, vrouter</td>
</tr>
<tr>
<td>[OVSVAPP] report_interval</td>
<td>4</td>
<td>30</td>
</tr>
<tr>
<td>[QUOTAS] quota_driver</td>
<td>neutron.db.quota_db.DbQuotaDriver</td>
<td>neutron.db.quota.driver.DbQuotaDriver</td>
</tr>
<tr>
<td>[matchmaker_redis] password</td>
<td>None</td>
<td></td>
</tr>
<tr>
<td>[ml2] type_drivers</td>
<td>local, flat, vlan, gre, vxlan</td>
<td>local, flat, vlan, gre, vxlan, geneve</td>
</tr>
<tr>
<td>[ml2_sriov] agent_required</td>
<td>False</td>
<td>True</td>
</tr>
<tr>
<td>[oslo_messaging_rabbit] heartbeat_timeout_threshold</td>
<td>0</td>
@@ -293,6 +390,10 @@
<td>[DEFAULT] rpc_thread_pool_size</td>
<td>[DEFAULT] executor_thread_pool_size</td>
</tr>
<tr>
<td>[ml2_sriov] agent_required</td>
<td>None</td>
</tr>
<tr>
<td>[DEFAULT] log_format</td>
<td>None</td>

163
doc/config-reference/conf-changes/nova.xml
View File

@@ -1,7 +1,7 @@
<?xml version='1.0' encoding='UTF-8'?>
<section xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="nova-conf-changes-liberty">
<!-- Warning: Do not edit this file. It is automatically generated and your changes will be overwritten. The tool to do so lives in the openstack-doc-tools repository. -->
<title>New, updated and deprecated options in Liberty for OpenStack Compute</title>
<title>New, updated, and deprecated options in Liberty for OpenStack Compute</title>
<table>
<caption>New options</caption>
<col width="50%"/>
@@ -12,14 +12,42 @@
<td>(Type) Help string</td>
</tr>
</thead>
<tr>
<td>[DEFAULT] console_allowed_origins = </td>
<td>(ListOpt) Allowed Origin header hostnames for access to console proxy servers</td>
</tr>
<tr>
<td>[DEFAULT] executor_thread_pool_size = 64</td>
<td>(IntOpt) Size of executor thread pool.</td>
</tr>
<tr>
<td>[DEFAULT] max_concurrent_live_migrations = 1</td>
<td>(IntOpt) Maximum number of live migrations to run concurrently. This limit is enforced to avoid outbound live migrations overwhelming the host/network and causing failures. It is not recommended that you change this unless you are very sure that doing so is safe and stable in your environment.</td>
</tr>
<tr>
<td>[DEFAULT] password = </td>
<td>(StrOpt) Password for Redis server (optional).</td>
</tr>
<tr>
<td>[DEFAULT] port = 6379</td>
<td>(IntOpt) Use this port to connect to redis host.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_conn_pool_size = 30</td>
<td>(IntOpt) Size of RPC connection pool.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_poll_timeout = 1</td>
<td>(IntOpt) The default number of seconds that poll should wait. Poll raises timeout exception when timeout expired.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_all_req_rep = True</td>
<td>(BoolOpt) Use REQ/REP pattern for all methods CALL/CAST/FANOUT.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_concurrency = eventlet</td>
<td>(StrOpt) Type of concurrency used. Either "native" or "eventlet"</td>
</tr>
<tr>
<td>[DEFAULT] secure_proxy_ssl_header = None</td>
<td>(StrOpt) The HTTP header used to determine the scheme for the original request, even if it was removed by an SSL terminating proxy. Typical value is "HTTP_X_FORWARDED_PROTO".</td>
@@ -28,6 +56,18 @@
<td>[DEFAULT] update_resources_interval = 0</td>
<td>(IntOpt) Interval in seconds for updating compute resources. A number less than 0 means to disable the task completely. Leaving this at the default of 0 will cause this to run at the default periodic interval. Setting it to any positive value will cause it to run at approximately that number of seconds.</td>
</tr>
<tr>
<td>[DEFAULT] use_rootwrap_daemon = False</td>
<td>(BoolOpt) Start and use a daemon that can run the commands that need to be run with root privileges. This option is usually enabled on nodes that run nova compute processes</td>
</tr>
<tr>
<td>[DEFAULT] watch_log_file = False</td>
<td>(BoolOpt) (Optional) Uses logging handler designed to watch file system. When log file is moved or removed this handler will open a new log file with specified path instantaneously. It makes sense only if log-file option is specified and Linux platform is used. This option is ignored if log_config_append is set.</td>
</tr>
<tr>
<td>[DEFAULT] zmq_use_broker = True</td>
<td>(BoolOpt) Shows whether zmq-messaging uses broker or not.</td>
</tr>
<tr>
<td>[cors] allow_credentials = True</td>
<td>(BoolOpt) Indicate that the actual request can include user credentials</td>
@@ -84,6 +124,34 @@
<td>[hyperv] power_state_event_polling_interval = 2</td>
<td>(IntOpt) Instance power state change event polling frequency.</td>
</tr>
<tr>
<td>[keystone_authtoken] region_name = None</td>
<td>(StrOpt) The region in which the identity server can be found.</td>
</tr>
<tr>
<td>[libvirt] live_migration_completion_timeout = 800</td>
<td>(IntOpt) Time to wait, in seconds, for migration to successfully complete transferring data before aborting the operation. Value is per GiB of guest RAM + disk to be transferred, with lower bound of a minimum of 2 GiB. Should usually be larger than downtime delay * downtime steps. Set to 0 to disable timeouts.</td>
</tr>
<tr>
<td>[libvirt] live_migration_downtime = 500</td>
<td>(IntOpt) Maximum permitted downtime, in milliseconds, for live migration switchover. Will be rounded up to a minimum of 100ms. Use a large value if guest liveness is unimportant.</td>
</tr>
<tr>
<td>[libvirt] live_migration_downtime_delay = 75</td>
<td>(IntOpt) Time to wait, in seconds, between each step increase of the migration downtime. Minimum delay is 10 seconds. Value is per GiB of guest RAM + disk to be transferred, with lower bound of a minimum of 2 GiB per device</td>
</tr>
<tr>
<td>[libvirt] live_migration_downtime_steps = 10</td>
<td>(IntOpt) Number of incremental steps to reach max downtime value. Will be rounded up to a minimum of 3 steps</td>
</tr>
<tr>
<td>[libvirt] live_migration_progress_timeout = 150</td>
<td>(IntOpt) Time to wait, in seconds, for migration to make forward progress in transferring data before aborting the operation. Set to 0 to disable timeouts.</td>
</tr>
<tr>
<td>[libvirt] remote_filesystem_transport = ssh</td>
<td>(StrOpt) Use ssh or rsync transport for creating, copying, removing files on the remote host.</td>
</tr>
<tr>
<td>[mks] enabled = False</td>
<td>(BoolOpt) Enable MKS related features</td>
@@ -92,9 +160,41 @@
<td>[mks] mksproxy_base_url = http://127.0.0.1:6090/</td>
<td>(StrOpt) Location of MKS web console proxy, in the form "http://127.0.0.1:6090/"</td>
</tr>
<tr>
<td>[osapi_v21] enabled = True</td>
<td>(BoolOpt) DEPRECATED: Whether the V2.1 API is enabled or not. This option will be removed in the near future.</td>
</tr>
<tr>
<td>[osapi_v21] extensions_blacklist = </td>
<td>(ListOpt) DEPRECATED: A list of v2.1 API extensions to never load. Specify the extension aliases here. This option will be removed in the near future. After that point you have to run all of the API.</td>
</tr>
<tr>
<td>[osapi_v21] extensions_whitelist = </td>
<td>(ListOpt) DEPRECATED: If the list is not empty then a v2.1 API extension will only be loaded if it exists in this list. Specify the extension aliases here. This option will be removed in the near future. After that point you have to run all of the API.</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] password = </td>
<td>(StrOpt) Password for message broker authentication</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_config_dir = </td>
<td>(StrOpt) Path to directory that contains the SASL configuration</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_config_name = </td>
<td>(StrOpt) Name of configuration file (without .conf suffix)</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_mechanisms = </td>
<td>(StrOpt) Space separated list of acceptable SASL mechanisms</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] username = </td>
<td>(StrOpt) User name for message broker authentication</td>
</tr>
<tr>
<td>[oslo_messaging_qpid] send_single_reply = False</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in M release.</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in the Mitaka release.</td>
</tr>
<tr>
<td>[oslo_messaging_rabbit] kombu_reconnect_timeout = 60</td>
@@ -102,7 +202,7 @@
</tr>
<tr>
<td>[oslo_messaging_rabbit] send_single_reply = False</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in M release.</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in the Mitaka release.</td>
</tr>
<tr>
<td>[oslo_middleware] secure_proxy_ssl_header = X-Forwarded-Proto</td>
@@ -178,6 +278,11 @@
<td>['nova.compute.monitors.all_monitors']</td>
<td>None</td>
</tr>
<tr>
<td>[DEFAULT] cpu_allocation_ratio</td>
<td>16.0</td>
<td>0.0</td>
</tr>
<tr>
<td>[DEFAULT] default_log_levels</td>
<td>amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, sqlalchemy=WARN, suds=INFO, oslo.messaging=INFO, iso8601=WARN, requests.packages.urllib3.connectionpool=WARN, urllib3.connectionpool=WARN, websocket=WARN, requests.packages.urllib3.util.retry=WARN, urllib3.util.retry=WARN, keystonemiddleware=WARN, routes.middleware=WARN, stevedore=WARN</td>
@@ -188,6 +293,26 @@
<td>%(asctime)s.%(msecs)03d %(process)d TRACE %(name)s %(instance)s</td>
<td>%(asctime)s.%(msecs)03d %(process)d ERROR %(name)s %(instance)s</td>
</tr>
<tr>
<td>[DEFAULT] osapi_compute_extension</td>
<td>['nova.api.openstack.compute.contrib.standard_extensions']</td>
<td>['nova.api.openstack.compute.legacy_v2.contrib.standard_extensions']</td>
</tr>
<tr>
<td>[DEFAULT] ram_allocation_ratio</td>
<td>1.5</td>
<td>0.0</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_matchmaker</td>
<td>local</td>
<td>redis</td>
</tr>
<tr>
<td>[DEFAULT] scheduler_default_filters</td>
<td>RetryFilter, AvailabilityZoneFilter, RamFilter, ComputeFilter, ComputeCapabilitiesFilter, ImagePropertiesFilter, ServerGroupAntiAffinityFilter, ServerGroupAffinityFilter</td>
<td>RetryFilter, AvailabilityZoneFilter, RamFilter, DiskFilter, ComputeFilter, ComputeCapabilitiesFilter, ImagePropertiesFilter, ServerGroupAntiAffinityFilter, ServerGroupAffinityFilter</td>
</tr>
<tr>
<td>[DEFAULT] use_syslog_rfc_format</td>
<td>False</td>
@@ -209,9 +334,9 @@
<td>True</td>
</tr>
<tr>
<td>[osapi_v3] enabled</td>
<td>False</td>
<td>True</td>
<td>[matchmaker_redis] password</td>
<td>None</td>
<td></td>
</tr>
<tr>
<td>[oslo_messaging_rabbit] heartbeat_timeout_threshold</td>
@@ -237,6 +362,10 @@
<td>[DEFAULT] vnc_keymap</td>
<td>[vnc] keymap</td>
</tr>
<tr>
<td>[osapi_v21] extensions_whitelist</td>
<td>None</td>
</tr>
<tr>
<td>[ironic] admin_auth_token</td>
<td>None</td>
@@ -261,10 +390,18 @@
<td>[neutron] admin_username</td>
<td>None</td>
</tr>
<tr>
<td>[DEFAULT] ssl_ca_file</td>
<td>[ssl] ca_file</td>
</tr>
<tr>
<td>[neutron] auth_strategy</td>
<td>None</td>
</tr>
<tr>
<td>[osapi_v21] enabled</td>
<td>None</td>
</tr>
<tr>
<td>[DEFAULT] novncproxy_base_url</td>
<td>[vnc] novncproxy_base_url</td>
@@ -281,6 +418,10 @@
<td>[neutron] admin_tenant_id</td>
<td>None</td>
</tr>
<tr>
<td>[DEFAULT] ssl_cert_file</td>
<td>[ssl] cert_file</td>
</tr>
<tr>
<td>[DEFAULT] log_format</td>
<td>None</td>
@@ -289,6 +430,10 @@
<td>[DEFAULT] vncserver_proxyclient_address</td>
<td>[vnc] vncserver_proxyclient_address</td>
</tr>
<tr>
<td>[osapi_v21] extensions_blacklist</td>
<td>None</td>
</tr>
<tr>
<td>[workarounds] destroy_after_evacuate</td>
<td>None</td>
@@ -298,7 +443,7 @@
<td>None</td>
</tr>
<tr>
<td>[osapi_v3] enabled</td>
<td>[DEFAULT] osapi_compute_ext_list</td>
<td>None</td>
</tr>
<tr>
@@ -317,6 +462,10 @@
<td>[DEFAULT] share_dhcp_address</td>
<td>None</td>
</tr>
<tr>
<td>[DEFAULT] ssl_key_file</td>
<td>[ssl] key_file</td>
</tr>
<tr>
<td>[libvirt] remove_unused_kernels</td>
<td>None</td>

108
doc/config-reference/conf-changes/sahara.xml
View File

@@ -1,7 +1,7 @@
<?xml version='1.0' encoding='UTF-8'?>
<section xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="sahara-conf-changes-liberty">
<!-- Warning: Do not edit this file. It is automatically generated and your changes will be overwritten. The tool to do so lives in the openstack-doc-tools repository. -->
<title>New, updated and deprecated options in Liberty for Data Processing service</title>
<title>New, updated, and deprecated options in Liberty for Data Processing service</title>
<table>
<caption>New options</caption>
<col width="50%"/>
@@ -24,10 +24,50 @@
<td>[DEFAULT] executor_thread_pool_size = 64</td>
<td>(IntOpt) Size of executor thread pool.</td>
</tr>
<tr>
<td>[DEFAULT] heat_stack_tags = data-processing-cluster</td>
<td>(ListOpt) List of tags to be used during operating with stack.</td>
</tr>
<tr>
<td>[DEFAULT] host = 127.0.0.1</td>
<td>(StrOpt) Host to locate redis.</td>
</tr>
<tr>
<td>[DEFAULT] password = </td>
<td>(StrOpt) Password for Redis server (optional).</td>
</tr>
<tr>
<td>[DEFAULT] port = 6379</td>
<td>(IntOpt) Use this port to connect to redis host.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_conn_pool_size = 30</td>
<td>(IntOpt) Size of RPC connection pool.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_poll_timeout = 1</td>
<td>(IntOpt) The default number of seconds that poll should wait. Poll raises timeout exception when timeout expired.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_all_req_rep = True</td>
<td>(BoolOpt) Use REQ/REP pattern for all methods CALL/CAST/FANOUT.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_concurrency = eventlet</td>
<td>(StrOpt) Type of concurrency used. Either "native" or "eventlet"</td>
</tr>
<tr>
<td>[DEFAULT] watch_log_file = False</td>
<td>(BoolOpt) (Optional) Uses logging handler designed to watch file system. When log file is moved or removed this handler will open a new log file with specified path instantaneously. It makes sense only if log-file option is specified and Linux platform is used. This option is ignored if log_config_append is set.</td>
</tr>
<tr>
<td>[DEFAULT] zmq_use_broker = True</td>
<td>(BoolOpt) Shows whether zmq-messaging uses broker or not.</td>
</tr>
<tr>
<td>[cinder] endpoint_type = internalURL</td>
<td>(StrOpt) Endpoint type for cinder client requests</td>
</tr>
<tr>
<td>[cors] allow_credentials = True</td>
<td>(BoolOpt) Indicate that the actual request can include user credentials</td>
@@ -76,6 +116,18 @@
<td>[cors.subdomain] max_age = 3600</td>
<td>(IntOpt) Maximum cache age of CORS preflight requests.</td>
</tr>
<tr>
<td>[heat] endpoint_type = internalURL</td>
<td>(StrOpt) Endpoint type for heat client requests</td>
</tr>
<tr>
<td>[keystone] endpoint_type = internalURL</td>
<td>(StrOpt) Endpoint type for keystone client requests</td>
</tr>
<tr>
<td>[keystone_authtoken] region_name = None</td>
<td>(StrOpt) The region in which the identity server can be found.</td>
</tr>
<tr>
<td>[manila] api_insecure = True</td>
<td>(BoolOpt) Allow to perform insecure SSL requests to manila.</td>
@@ -88,9 +140,45 @@
<td>[manila] ca_file = None</td>
<td>(StrOpt) Location of ca certificates file to use for manila client requests.</td>
</tr>
<tr>
<td>[neutron] endpoint_type = internalURL</td>
<td>(StrOpt) Endpoint type for neutron client requests</td>
</tr>
<tr>
<td>[nova] endpoint_type = internalURL</td>
<td>(StrOpt) Endpoint type for nova client requests</td>
</tr>
<tr>
<td>[object_store_access] public_identity_ca_file = None</td>
<td>(StrOpt) Location of ca certificate file to use for identity client requests via public endpoint</td>
</tr>
<tr>
<td>[object_store_access] public_object_store_ca_file = None</td>
<td>(StrOpt) Location of ca certificate file to use for object-store client requests via public endpoint</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] password = </td>
<td>(StrOpt) Password for message broker authentication</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_config_dir = </td>
<td>(StrOpt) Path to directory that contains the SASL configuration</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_config_name = </td>
<td>(StrOpt) Name of configuration file (without .conf suffix)</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_mechanisms = </td>
<td>(StrOpt) Space separated list of acceptable SASL mechanisms</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] username = </td>
<td>(StrOpt) User name for message broker authentication</td>
</tr>
<tr>
<td>[oslo_messaging_qpid] send_single_reply = False</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in M release.</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in the Mitaka release.</td>
</tr>
<tr>
<td>[oslo_messaging_rabbit] kombu_reconnect_timeout = 60</td>
@@ -98,7 +186,7 @@
</tr>
<tr>
<td>[oslo_messaging_rabbit] send_single_reply = False</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in M release.</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in the Mitaka release.</td>
</tr>
<tr>
<td>[oslo_middleware] secure_proxy_ssl_header = X-Forwarded-Proto</td>
@@ -112,6 +200,10 @@
<td>[retries] retry_after = 10</td>
<td>(IntOpt) Time between the retries to client (in seconds).</td>
</tr>
<tr>
<td>[swift] endpoint_type = internalURL</td>
<td>(StrOpt) Endpoint type for swift client requests</td>
</tr>
</table>
<table>
<caption>New default values</caption>
@@ -140,6 +232,11 @@
<td>%(asctime)s.%(msecs)03d %(process)d TRACE %(name)s %(instance)s</td>
<td>%(asctime)s.%(msecs)03d %(process)d ERROR %(name)s %(instance)s</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_matchmaker</td>
<td>local</td>
<td>redis</td>
</tr>
<tr>
<td>[DEFAULT] use_syslog_rfc_format</td>
<td>False</td>
@@ -150,6 +247,11 @@
<td>False</td>
<td>True</td>
</tr>
<tr>
<td>[matchmaker_redis] password</td>
<td>None</td>
<td></td>
</tr>
<tr>
<td>[oslo_messaging_rabbit] heartbeat_timeout_threshold</td>
<td>0</td>

4
doc/config-reference/conf-changes/swift.xml
View File

@@ -1,6 +1,6 @@
<?xml version='1.0' encoding='UTF-8'?>
<section xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="swift-conf-changes-liberty">
<!-- Warning: Do not edit this file. It is automatically generated and your changes will be overwritten. The tool to do so lives in the openstack-doc-tools repository. -->
<title>New, updated and deprecated options in Liberty for OpenStack Object Storage</title>
<para>There are no new, updated and deprecated options in Liberty for OpenStack Object Storage.</para>
<title>New, updated, and deprecated options in Liberty for OpenStack Object Storage</title>
<para>There are no new, updated, and deprecated options in Liberty for OpenStack Object Storage.</para>
</section>

327
doc/config-reference/conf-changes/trove.xml
View File

@@ -1,7 +1,7 @@
<?xml version='1.0' encoding='UTF-8'?>
<section xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="trove-conf-changes-liberty">
<!-- Warning: Do not edit this file. It is automatically generated and your changes will be overwritten. The tool to do so lives in the openstack-doc-tools repository. -->
<title>New, updated and deprecated options in Liberty for Database service</title>
<title>New, updated, and deprecated options in Liberty for Database service</title>
<table>
<caption>New options</caption>
<col width="50%"/>
@@ -24,10 +24,122 @@
<td>[DEFAULT] nova_proxy_admin_tenant_id = </td>
<td>(StrOpt) Admin tenant ID used to connect to Nova.</td>
</tr>
<tr>
<td>[DEFAULT] password = </td>
<td>(StrOpt) Password for Redis server (optional).</td>
</tr>
<tr>
<td>[DEFAULT] port = 6379</td>
<td>(IntOpt) Use this port to connect to redis host.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_conn_pool_size = 30</td>
<td>(IntOpt) Size of RPC connection pool.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_poll_timeout = 1</td>
<td>(IntOpt) The default number of seconds that poll should wait. Poll raises timeout exception when timeout expired.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_all_req_rep = True</td>
<td>(BoolOpt) Use REQ/REP pattern for all methods CALL/CAST/FANOUT.</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_concurrency = eventlet</td>
<td>(StrOpt) Type of concurrency used. Either "native" or "eventlet"</td>
</tr>
<tr>
<td>[DEFAULT] timeout_wait_for_service = 120</td>
<td>(IntOpt) Maximum time (in seconds) to wait for a service to become alive.</td>
</tr>
<tr>
<td>[DEFAULT] watch_log_file = False</td>
<td>(BoolOpt) (Optional) Uses logging handler designed to watch file system. When log file is moved or removed this handler will open a new log file with specified path instantaneously. It makes sense only if log-file option is specified and Linux platform is used. This option is ignored if log_config_append is set.</td>
</tr>
<tr>
<td>[DEFAULT] zmq_use_broker = True</td>
<td>(BoolOpt) Shows whether zmq-messaging uses broker or not.</td>
</tr>
<tr>
<td>[cassandra] root_controller = trove.extensions.common.service.DefaultRootController</td>
<td>(StrOpt) Root controller implementation for cassandra.</td>
</tr>
<tr>
<td>[couchbase] root_controller = trove.extensions.common.service.DefaultRootController</td>
<td>(StrOpt) Root controller implementation for couchbase.</td>
</tr>
<tr>
<td>[couchdb] root_controller = trove.extensions.common.service.DefaultRootController</td>
<td>(StrOpt) Root controller implementation for couchdb.</td>
</tr>
<tr>
<td>[db2] root_controller = trove.extensions.common.service.DefaultRootController</td>
<td>(StrOpt) Root controller implementation for db2.</td>
</tr>
<tr>
<td>[keystone_authtoken] region_name = None</td>
<td>(StrOpt) The region in which the identity server can be found.</td>
</tr>
<tr>
<td>[mariadb] backup_incremental_strategy = {'InnoBackupEx': 'InnoBackupExIncremental'}</td>
<td>(DictOpt) Incremental Backup Runner based on the default strategy. For strategies that do not implement an incremental backup, the runner will use the default full backup.</td>
</tr>
<tr>
<td>[mariadb] backup_namespace = trove.guestagent.strategies.backup.mysql_impl</td>
<td>(StrOpt) Namespace to load backup strategies from.</td>
</tr>
<tr>
<td>[mariadb] backup_strategy = InnoBackupEx</td>
<td>(StrOpt) Default strategy to perform backups.</td>
</tr>
<tr>
<td>[mariadb] device_path = /dev/vdb</td>
<td>(StrOpt) Device path for volume if volume support is enabled.</td>
</tr>
<tr>
<td>[mariadb] mount_point = /var/lib/mysql</td>
<td>(StrOpt) Filesystem path for mounting volumes if volume support is enabled.</td>
</tr>
<tr>
<td>[mariadb] replication_namespace = trove.guestagent.strategies.replication.mysql_binlog</td>
<td>(StrOpt) Namespace to load replication strategies from.</td>
</tr>
<tr>
<td>[mariadb] replication_strategy = MysqlBinlogReplication</td>
<td>(StrOpt) Default strategy for replication.</td>
</tr>
<tr>
<td>[mariadb] restore_namespace = trove.guestagent.strategies.restore.mysql_impl</td>
<td>(StrOpt) Namespace to load restore strategies from.</td>
</tr>
<tr>
<td>[mariadb] root_controller = trove.extensions.common.service.DefaultRootController</td>
<td>(StrOpt) Root controller implementation for mysql.</td>
</tr>
<tr>
<td>[mariadb] root_on_create = False</td>
<td>(BoolOpt) Enable the automatic creation of the root user for the service during instance-create. The generated password for the root user is immediately returned in the response of instance-create as the 'password' field.</td>
</tr>
<tr>
<td>[mariadb] tcp_ports = 3306</td>
<td>(ListOpt) List of TCP ports and/or port ranges to open in the security group (only applicable if trove_security_groups_support is True).</td>
</tr>
<tr>
<td>[mariadb] udp_ports = </td>
<td>(ListOpt) List of UDP ports and/or port ranges to open in the security group (only applicable if trove_security_groups_support is True).</td>
</tr>
<tr>
<td>[mariadb] usage_timeout = 400</td>
<td>(IntOpt) Maximum time (in seconds) to wait for a Guest to become active.</td>
</tr>
<tr>
<td>[mariadb] volume_support = True</td>
<td>(BoolOpt) Whether to provision a Cinder volume for datadir.</td>
</tr>
<tr>
<td>[mongodb] add_members_timeout = 300</td>
<td>(IntOpt) Maximum time to wait (in seconds) for a replica set initialization process to complete.</td>
</tr>
<tr>
<td>[mongodb] configsvr_port = 27019</td>
<td>(IntOpt) Port for instances running as config servers.</td>
@@ -44,9 +156,37 @@
<td>[mongodb] mongodb_port = 27017</td>
<td>(IntOpt) Port for mongod and mongos instances.</td>
</tr>
<tr>
<td>[mongodb] root_controller = trove.extensions.common.service.DefaultRootController</td>
<td>(StrOpt) Root controller implementation for mongodb.</td>
</tr>
<tr>
<td>[mysql] root_controller = trove.extensions.common.service.DefaultRootController</td>
<td>(StrOpt) Root controller implementation for mysql.</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] password = </td>
<td>(StrOpt) Password for message broker authentication</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_config_dir = </td>
<td>(StrOpt) Path to directory that contains the SASL configuration</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_config_name = </td>
<td>(StrOpt) Name of configuration file (without .conf suffix)</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] sasl_mechanisms = </td>
<td>(StrOpt) Space separated list of acceptable SASL mechanisms</td>
</tr>
<tr>
<td>[oslo_messaging_amqp] username = </td>
<td>(StrOpt) User name for message broker authentication</td>
</tr>
<tr>
<td>[oslo_messaging_qpid] send_single_reply = False</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in M release.</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in the Mitaka release.</td>
</tr>
<tr>
<td>[oslo_messaging_rabbit] kombu_reconnect_timeout = 60</td>
@@ -54,7 +194,127 @@
</tr>
<tr>
<td>[oslo_messaging_rabbit] send_single_reply = False</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in M release.</td>
<td>(BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in the Mitaka release.</td>
</tr>
<tr>
<td>[percona] root_controller = trove.extensions.common.service.DefaultRootController</td>
<td>(StrOpt) Root controller implementation for percona.</td>
</tr>
<tr>
<td>[postgresql] root_controller = trove.extensions.common.service.DefaultRootController</td>
<td>(StrOpt) Root controller implementation for postgresql.</td>
</tr>
<tr>
<td>[pxc] api_strategy = trove.common.strategies.cluster.experimental.pxc.api.PXCAPIStrategy</td>
<td>(StrOpt) Class that implements datastore-specific API logic.</td>
</tr>
<tr>
<td>[pxc] backup_incremental_strategy = {'InnoBackupEx': 'InnoBackupExIncremental'}</td>
<td>(DictOpt) Incremental Backup Runner based on the default strategy. For strategies that do not implement an incremental backup, the runner will use the default full backup.</td>
</tr>
<tr>
<td>[pxc] backup_namespace = trove.guestagent.strategies.backup.mysql_impl</td>
<td>(StrOpt) Namespace to load backup strategies from.</td>
</tr>
<tr>
<td>[pxc] backup_strategy = InnoBackupEx</td>
<td>(StrOpt) Default strategy to perform backups.</td>
</tr>
<tr>
<td>[pxc] cluster_support = True</td>
<td>(BoolOpt) Enable clusters to be created and managed.</td>
</tr>
<tr>
<td>[pxc] device_path = /dev/vdb</td>
<td>(StrOpt) Device path for volume if volume support is enabled.</td>
</tr>
<tr>
<td>[pxc] guestagent_strategy = trove.common.strategies.cluster.experimental.pxc.guestagent.PXCGuestAgentStrategy</td>
<td>(StrOpt) Class that implements datastore-specific Guest Agent API logic.</td>
</tr>
<tr>
<td>[pxc] ignore_users = os_admin, root, clusterrepuser</td>
<td>(ListOpt) Users to exclude when listing users.</td>
</tr>
<tr>
<td>[pxc] min_cluster_member_count = 3</td>
<td>(IntOpt) Minimum number of members in PXC cluster.</td>
</tr>
<tr>
<td>[pxc] mount_point = /var/lib/mysql</td>
<td>(StrOpt) Filesystem path for mounting volumes if volume support is enabled.</td>
</tr>
<tr>
<td>[pxc] replication_namespace = trove.guestagent.strategies.replication.mysql_gtid</td>
<td>(StrOpt) Namespace to load replication strategies from.</td>
</tr>
<tr>
<td>[pxc] replication_strategy = MysqlGTIDReplication</td>
<td>(StrOpt) Default strategy for replication.</td>
</tr>
<tr>
<td>[pxc] replication_user = slave_user</td>
<td>(StrOpt) Userid for replication slave.</td>
</tr>
<tr>
<td>[pxc] restore_namespace = trove.guestagent.strategies.restore.mysql_impl</td>
<td>(StrOpt) Namespace to load restore strategies from.</td>
</tr>
<tr>
<td>[pxc] root_controller = trove.extensions.common.service.DefaultRootController</td>
<td>(StrOpt) Root controller implementation for pxc.</td>
</tr>
<tr>
<td>[pxc] root_on_create = False</td>
<td>(BoolOpt) Enable the automatic creation of the root user for the service during instance-create. The generated password for the root user is immediately returned in the response of instance-create as the 'password' field.</td>
</tr>
<tr>
<td>[pxc] taskmanager_strategy = trove.common.strategies.cluster.experimental.pxc.taskmanager.PXCTaskManagerStrategy</td>
<td>(StrOpt) Class that implements datastore-specific task manager logic.</td>
</tr>
<tr>
<td>[pxc] tcp_ports = 3306, 4444, 4567, 4568</td>
<td>(ListOpt) List of TCP ports and/or port ranges to open in the security group (only applicable if trove_security_groups_support is True).</td>
</tr>
<tr>
<td>[pxc] udp_ports = </td>
<td>(ListOpt) List of UDP ports and/or port ranges to open in the security group (only applicable if trove_security_groups_support is True).</td>
</tr>
<tr>
<td>[pxc] usage_timeout = 450</td>
<td>(IntOpt) Maximum time (in seconds) to wait for a Guest to become active.</td>
</tr>
<tr>
<td>[pxc] volume_support = True</td>
<td>(BoolOpt) Whether to provision a Cinder volume for datadir.</td>
</tr>
<tr>
<td>[redis] api_strategy = trove.common.strategies.cluster.experimental.redis.api.RedisAPIStrategy</td>
<td>(StrOpt) Class that implements datastore-specific API logic.</td>
</tr>
<tr>
<td>[redis] cluster_support = True</td>
<td>(BoolOpt) Enable clusters to be created and managed.</td>
</tr>
<tr>
<td>[redis] guestagent_strategy = trove.common.strategies.cluster.experimental.redis.guestagent.RedisGuestAgentStrategy</td>
<td>(StrOpt) Class that implements datastore-specific Guest Agent API logic.</td>
</tr>
<tr>
<td>[redis] replication_namespace = trove.guestagent.strategies.replication.experimental.redis_sync</td>
<td>(StrOpt) Namespace to load replication strategies from.</td>
</tr>
<tr>
<td>[redis] root_controller = trove.extensions.common.service.DefaultRootController</td>
<td>(StrOpt) Root controller implementation for redis.</td>
</tr>
<tr>
<td>[redis] taskmanager_strategy = trove.common.strategies.cluster.experimental.redis.taskmanager.RedisTaskManagerStrategy</td>
<td>(StrOpt) Class that implements datastore-specific task manager logic.</td>
</tr>
<tr>
<td>[vertica] root_controller = trove.extensions.vertica.service.VerticaRootController</td>
<td>(StrOpt) Root controller implementation for Vertica.</td>
</tr>
</table>
<table>
@@ -69,11 +329,21 @@
<td>New default value</td>
</tr>
</thead>
<tr>
<td>[DEFAULT] cluster_usage_timeout</td>
<td>675</td>
<td>36000</td>
</tr>
<tr>
<td>[DEFAULT] default_log_levels</td>
<td>amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, sqlalchemy=WARN, suds=INFO, oslo.messaging=INFO, iso8601=WARN, requests.packages.urllib3.connectionpool=WARN, urllib3.connectionpool=WARN, websocket=WARN, keystonemiddleware=WARN, routes.middleware=WARN, stevedore=WARN</td>
<td>amqp=WARN, amqplib=WARN, boto=WARN, qpid=WARN, sqlalchemy=WARN, suds=INFO, oslo.messaging=INFO, iso8601=WARN, requests.packages.urllib3.connectionpool=WARN, urllib3.connectionpool=WARN, websocket=WARN, requests.packages.urllib3.util.retry=WARN, urllib3.util.retry=WARN, keystonemiddleware=WARN, routes.middleware=WARN, stevedore=WARN, taskflow=WARN</td>
</tr>
<tr>
<td>[DEFAULT] ignore_dbs</td>
<td>lost+found, #mysql50#lost+found, mysql, information_schema</td>
<td>mysql, information_schema, performance_schema</td>
</tr>
<tr>
<td>[DEFAULT] logging_exception_prefix</td>
<td>%(asctime)s.%(msecs)03d %(process)d TRACE %(name)s %(instance)s</td>
@@ -82,13 +352,23 @@
<tr>
<td>[DEFAULT] notification_service_id</td>
<td>{'vertica': 'a8d805ae-a3b2-c4fd-gb23-b62cee5201ae', 'db2': 'e040cd37-263d-4869-aaa6-c62aa97523b5', 'postgresql': 'ac277e0d-4f21-40aa-b347-1ea31e571720', 'mysql': '2f3ff068-2bfb-4f70-9a9d-a6bb65bc084b', 'couchbase': 'fa62fe68-74d9-4779-a24e-36f19602c415', 'mongodb': 'c8c907af-7375-456f-b929-b637ff9209ee', 'couchdb': 'f0a9ab7b-66f7-4352-93d7-071521d44c7c', 'redis': 'b216ffc5-1947-456c-a4cf-70f94c05f7d0', 'cassandra': '459a230d-4e97-4344-9067-2a54a310b0ed'}</td>
<td>{'vertica': 'a8d805ae-a3b2-c4fd-gb23-b62cee5201ae', 'db2': 'e040cd37-263d-4869-aaa6-c62aa97523b5', 'percona': 'fd1723f5-68d2-409c-994f-a4a197892a17', 'postgresql': 'ac277e0d-4f21-40aa-b347-1ea31e571720', 'mysql': '2f3ff068-2bfb-4f70-9a9d-a6bb65bc084b', 'couchbase': 'fa62fe68-74d9-4779-a24e-36f19602c415', 'mongodb': 'c8c907af-7375-456f-b929-b637ff9209ee', 'couchdb': 'f0a9ab7b-66f7-4352-93d7-071521d44c7c', 'redis': 'b216ffc5-1947-456c-a4cf-70f94c05f7d0', 'cassandra': '459a230d-4e97-4344-9067-2a54a310b0ed'}</td>
<td>{'mongodb': 'c8c907af-7375-456f-b929-b637ff9209ee', 'percona': 'fd1723f5-68d2-409c-994f-a4a197892a17', 'mysql': '2f3ff068-2bfb-4f70-9a9d-a6bb65bc084b', 'pxc': '75a628c3-f81b-4ffb-b10a-4087c26bc854', 'db2': 'e040cd37-263d-4869-aaa6-c62aa97523b5', 'cassandra': '459a230d-4e97-4344-9067-2a54a310b0ed', 'mariadb': '7a4f82cc-10d2-4bc6-aadc-d9aacc2a3cb5', 'postgresql': 'ac277e0d-4f21-40aa-b347-1ea31e571720', 'couchbase': 'fa62fe68-74d9-4779-a24e-36f19602c415', 'couchdb': 'f0a9ab7b-66f7-4352-93d7-071521d44c7c', 'redis': 'b216ffc5-1947-456c-a4cf-70f94c05f7d0', 'vertica': 'a8d805ae-a3b2-c4fd-gb23-b62cee5201ae'}</td>
</tr>
<tr>
<td>[DEFAULT] report_interval</td>
<td>10</td>
<td>30</td>
</tr>
<tr>
<td>[DEFAULT] rpc_zmq_matchmaker</td>
<td>local</td>
<td>redis</td>
</tr>
<tr>
<td>[DEFAULT] usage_timeout</td>
<td>600</td>
<td>900</td>
</tr>
<tr>
<td>[DEFAULT] use_syslog_rfc_format</td>
<td>False</td>
@@ -99,6 +379,11 @@
<td>False</td>
<td>True</td>
</tr>
<tr>
<td>[matchmaker_redis] password</td>
<td>None</td>
<td></td>
</tr>
<tr>
<td>[mongodb] backup_namespace</td>
<td>None</td>
@@ -119,6 +404,36 @@
<td>0</td>
<td>60</td>
</tr>
<tr>
<td>[redis] backup_namespace</td>
<td>None</td>
<td>trove.guestagent.strategies.backup.experimental.redis_impl</td>
</tr>
<tr>
<td>[redis] backup_strategy</td>
<td>None</td>
<td>RedisBackup</td>
</tr>
<tr>
<td>[redis] replication_strategy</td>
<td>None</td>
<td>RedisSyncReplication</td>
</tr>
<tr>
<td>[redis] restore_namespace</td>
<td>None</td>
<td>trove.guestagent.strategies.restore.experimental.redis_impl</td>
</tr>
<tr>
<td>[redis] tcp_ports</td>
<td>6379</td>
<td>6379, 16379</td>
</tr>
<tr>
<td>[redis] volume_support</td>
<td>False</td>
<td>True</td>
</tr>
</table>
<table>
<caption>Deprecated options</caption>
@@ -138,10 +453,6 @@
<td>[DEFAULT] rpc_thread_pool_size</td>
<td>[DEFAULT] executor_thread_pool_size</td>
</tr>
<tr>
<td>[DEFAULT] nova_proxy_admin_tenant_name</td>
<td>[DEFAULT] nova_proxy_admin_tenant_id</td>
</tr>
<tr>
<td>[DEFAULT] log_format</td>
<td>None</td>