[Tempest Doc] Sample Configuration File

Sample Configuration File

示例配置文件

 

The following is a sample Tempest configuration for adaptation and use. It is auto-generated from Tempest when this documentation is built, so if you are having issues with an option, please compare your version of Tempest with the version of this documentation.

 

如下是適應和使用的Tempest配置示例。 在構建本文檔時，它是從Tempest自動生成的，所以若是您遇到選項問題，請將您的Tempest版本與本文檔的版本進行比較。

 

[DEFAULT]

 

#

# From oslo.log

#

 

# If set to true, the logging level will be set to DEBUG instead of the default INFO level. (boolean value)

# 若是設置爲true，則日誌記錄級別將設置爲DEBUG而不是默認的INFO級別。（參數類型：布爾）

# Note: This option can be changed without restarting.

# 注意：能夠在不從新啓動的狀況下更改此選項。

#debug = false

 

# The name of a logging configuration file. This file is appended to any existing logging configuration files. For details about logging configuration files, see the Python logging module documentation.

Note that when logging configuration files are used then all logging configuration is set in the configuration file and other logging configuration options are ignored (for example, log-date-format). (string value)

# 日誌配置文件的名稱。此文件將附加到任何現有的日誌記錄配置文件。有關記錄配置文件的詳細信息，請參閱Python日誌記錄模塊文檔。請注意，使用日誌記錄配置文件時，將在配置文件中設置全部日誌記錄配置，並忽略其餘日誌記錄配置選項（例如，log-date-format）。

# Note: This option can be changed without restarting. Deprecated group/name - [DEFAULT]/log_config

# 注意：能夠在不從新啓動的狀況下更改此選項。 不推薦使用group/name - [DEFAULT]/log_config

#log_config_append = <None>

 

# Defines the format string for %%(asctime)s in log records. Default: %(default)s . This option is ignored if log_config_append is set. (string value)

# 在日誌記錄中定義%%（asctime）s, 用來格式化字符串。 默認值：％（default）s。 若是設置了log_config_append，則忽略此選項。

#log_date_format = %Y-%m-%d %H:%M:%S

 

# (Optional) Name of log file to send logging output to. If no default is set, logging will go to stderr as defined by use_stderr. This option is ignored if log_config_append is set. (string value)

# （可選）要將日誌記錄輸出發送到的日誌文件的名稱。 若是未設置默認值，則日誌記錄將按照use_stderr的定義轉到stderr。 若是設置了log_config_append，則忽略此選項。

# Deprecated group/name - [DEFAULT]/logfile

# 不推薦使用 group/name - [DEFAULT]/logfile

#log_file = <None>

 

# (Optional) The base directory used for relative log_file  paths. This option is ignored if log_config_append is set. (string value)

# （可選）用於相對log_file路徑的基本目錄。 若是設置了log_config_append，則忽略此選項。

# Deprecated group/name - [DEFAULT]/logdir

# 不推薦使用 group/name - [DEFAULT]/logdir

#log_dir = <None>

 

# 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. (boolean value)

# 使用專門用於監視文件系統的日誌處理程序。 移動或刪除日誌文件時，此處理程序將當即打開具備指定路徑的新日誌文件。 只有在指定了log_file選項並使用Linux平臺時纔有意義。 若是設置了log_config_append，則忽略此選項。

#watch_log_file = false

 

# Use syslog for logging. Existing syslog format is DEPRECATED and will be changed later to honor RFC5424. This option is ignored if log_config_append is set. (boolean value)

# 使用syslog進行日誌記錄。 現有的syslog格式是DEPRECATED，稍後將更改以符合RFC5424。 若是設置了log_config_append，則忽略此選項。

#use_syslog = false

 

# Enable journald for logging. If running in a systemd environment you may wish to enable journal support. Doing so will use the journal native protocol which includes structured metadata in addition to log messages.This option is ignored if log_config_append is set. (boolean value)

# 啓用日誌記錄。 若是在系統環境中運行，您可能但願啓用日記支持。 這樣作將使用日誌原生協議，其中包括除日誌消息以外的結構化元數據。若是設置了log_config_append，則忽略此選項。

#use_journal = false

 

# Syslog facility to receive log lines. This option is ignored if log_config_append is set. (string value)

# 用於接收日誌行的Syslog工具。 若是設置了log_config_append，則忽略此選項。

#syslog_log_facility = LOG_USER

 

# Use JSON formatting for logging. This option is ignored if log_config_append is set. (boolean value)

# 使用JSON格式進行日誌記錄。 若是設置了log_config_append，則忽略此選項。

#use_json = false

 

# Log output to standard error. This option is ignored if log_config_append is set. (boolean value)

# 將輸出記錄到標準錯誤。 若是設置了log_config_append，則忽略此選項。

#use_stderr = false

 

# Log output to Windows Event Log. (boolean value)

# 將輸出記錄到Windows事件日誌。

#use_eventlog = false

 

# The amount of time before the log files are rotated. This option is ignored unless log_rotation_type is setto "interval". (integer value)

# 日誌文件旋轉以前將有大量時間。 除非將log_rotation_type設置爲「interval」，不然將忽略此選項。

#log_rotate_interval = 1

 

# Rotation interval type. The time of the last file change (or the time when the service was started) is used when scheduling the next rotation. (string value)

# 旋轉間隔類型。 在安排下一輪旋轉時使用上次文件更改的時間。（或服務開始的時間）

# Possible values:

# Seconds - <No description provided>

# Minutes - <No description provided>

# Hours - <No description provided>

# Days - <No description provided>

# Weekday - <No description provided>

# Midnight - <No description provided>

#log_rotate_interval_type = days

 

# Maximum number of rotated log files. (integer value)

# 最大旋轉日誌文件數。

#max_logfile_count = 30

 

# Log file maximum size in MB. This option is ignored if "log_rotation_type" is not set to "size". (integer value)

# 日誌文件最大大小（MB）。 若是「log_rotation_type」未設置爲「size」，則忽略此選項。

#max_logfile_size_mb = 200

 

# Log rotation type. (string value) 日誌旋轉類型

# Possible values: 可能值

# interval - Rotate logs at predefined time intervals. 以預約義的時間間隔來旋轉日誌。

# size - Rotate logs once they reach a predefined size. 一旦達到預約義的大小，就旋轉日誌。

# none - Do not rotate log files. 不旋轉日誌文件

#log_rotation_type = none

 

# Format string to use for log messages with context. Used by oslo_log.formatters. ContextFormatter (string value)

# 格式化字符串以用於具備上下文的日誌消息。 由oslo_log.formatters.ContextFormatter使用。

#logging_context_format_string = %(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [%(request_id)s %(user_identity)s] %(instance)s%(message)s

 

# Format string to use for log messages when context is undefined. Used by oslo_log.formatters.ContextFormatter (string value)

# 未定義上下文時用於日誌消息的格式字符串。 由oslo_log.formatters.ContextFormatter使用

#logging_default_format_string = %(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [-] %(instance)s%(message)s

 

# Additional data to append to log message when logging level for the message is DEBUG. Used by oslo_log.formatters.ContextFormatter (string value)

# 在記錄消息級別時附加到日誌消息的附加數據是DEBUG。 由oslo_log.formatters.ContextFormatter使用（字符串值）

#logging_debug_format_suffix = %(funcName)s %(pathname)s:%(lineno)d

 

# Prefix each line of exception output with this format. Used by oslo_log.formatters.ContextFormatter (string value)

# 使用此格式爲每行異常輸出添加前綴。 由oslo_log.formatters.ContextFormatter使用

#logging_exception_prefix = %(asctime)s.%(msecs)03d %(process)d ERROR %(name)s %(instance)s

 

# Defines the format string for %(user_identity)s that is used in logging_context_format_string. Used by oslo_log.formatters.ContextFormatter (string value)

# 定義logging_context_format_string中使用的％（user_identity）的格式字符串。 由oslo_log.formatters.ContextFormatter使用

#logging_user_identity_format = %(user)s %(tenant)s %(domain)s %(user_domain)s %(project_domain)s

 

# List of package logging levels in logger=LEVEL pairs. This option is ignored if log_config_append is set. (list value)

# logger = LEVEL對中的包日誌記錄級別列表。 若是設置了log_config_append，則忽略此選項。

#default_log_levels = amqp=WARN,amqplib=WARN,boto=WARN,qpid=WARN,sqlalchemy=WARN,suds=INFO,oslo.messaging=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,keystoneauth=WARN,oslo.cache=INFO,oslo_policy=INFO,dogpile.core.dogpile=INFO

 

# Enables or disables publication of error events. (boolean value)

# 啓用或禁用錯誤事件的發佈。

#publish_errors = false

 

# The format for an instance that is passed with the log message. (string value)

# 與日誌消息一塊兒傳遞的實例的格式。

#instance_format = "[instance: %(uuid)s] "

 

# The format for an instance UUID that is passed with the log message. (string value)

# 與日誌消息一塊兒傳遞的實例UUID的格式。

#instance_uuid_format = "[instance: %(uuid)s] "

 

# Interval, number of seconds, of log rate limiting. (integer value)

# 日誌速率限制的間隔，秒數。

#rate_limit_interval = 0

 

# Maximum number of logged messages per rate_limit_interval. (integer value)

# 每一個rate_limit_interval的最大記錄消息數。

#rate_limit_burst = 0

 

# Log level name used by rate limiting: CRITICAL, ERROR, INFO, WARNING, DEBUG or empty string. Logs with level greater or equal to rate_limit_except_level are not filtered. An empty string means that all levels are filtered. (string value)

# 速率限制使用的日誌級別名稱：CRITICAL，ERROR，INFO，WARNING，DEBUG或空字符串。 級別大於或等於rate_limit_except_level的日誌不會被過濾。 空字符串表示過濾全部級別。

#rate_limit_except_level = CRITICAL

 

# Enables or disables fatal status of deprecations. (boolean value)

# 啓用或禁用fatal_deprecations狀態。

#fatal_deprecations = false

 

#

# From tempest.config

#

 

# Whether to pause a test in global teardown. 是否在全局清理資源的過程當中暫停測試。

#

# The best use case is investigating used resources of one test. 最好的用例是調查一個測試使用的資源。

# A test can be run as follows: 一個測試可按以下運行

#  $ ostestr --pdb TEST_ID

# or

#  $ python -m testtools.run TEST_ID (boolean value)

#pause_teardown = false

 

 

[auth]

 

#

# From tempest.config

#

 

# Path to the yaml file that contains the list of credentials to use for running tests. If used when running in parallel you have to make sure sufficient credentials are provided in the accounts file. For example if no tests with roles are being run it requires at least `2 * CONC` distinct accounts configured in  the `test_accounts_file`, with CONC == the number of concurrent test processes. (string value)

# yaml文件的路徑，其中包含用於運行測試的憑據列表。若是在並行運行時使用，則必須確保在賬戶文件中提供了足夠的憑據。例如，若是沒有運行帶角色的測試，則至少須要在`test_accounts_file`中配置「2 * CONC」不一樣的賬戶，CONC ==併發測試進程的數量。（言簡意賅的說，就是指accounts裏存放不一樣的帳戶，可用來併發執行任務）

#test_accounts_file = <None>

 

# Allows test cases to create/destroy projects and users. This option requires that OpenStack Identity API admin credentials are known. If false, isolated test cases and parallel execution, can still be achieved configuring a list of test accounts (boolean value)

# 容許測試用例建立/銷燬項目和用戶。 此選項要求已知OpenStack Identity API管理憑據。 若是錯誤，隔離測試用例和並行執行，仍然能夠實現配置測試賬戶列表。

#use_dynamic_credentials = true

 

# Roles to assign to all users created by tempest (list value) 給由tempest建立的全部用戶分配角色

#tempest_roles =

 

# Default domain used when getting v3 credentials. This is the name keystone uses for v2 compatibility. (string value)

# 獲取v3憑據時使用的默認域。 對v2使用的keystone具備兼容性。

#default_credentials_domain_name = Default

 

# If use_dynamic_credentials is set to True and Neutron is enabled. Tempest will try to create a usable network, subnet, and router when needed for each project it creates. However in some neutron configurations, like with VLAN provider networks, this doesn't work. So if set to False the isolated networks will not be created (boolean value)

# 若是use_dynamic_credentials設置爲True且啓用了Neutron。 Tempest將嘗試在其建立的每一個項目須要時建立可用的網絡，子網和路由器。 可是在某些neutron的配置中，如VLAN提供商網絡，這不起做用。 所以，若是設置爲False，則不會建立隔離的網絡

#create_isolated_networks = true

 

# Username for an administrative user. This is needed for authenticating requests made by project isolation to create users and projects (string value)

# 管理用戶的用戶名。 這是驗證項目隔離建立用戶和項目的請求所必需的

#admin_username = <None>

 

# Project name to use for an administrative user. This is needed for authenticating requests made by project isolation to create users and projects (string value)

# 用於管理用戶的項目名稱。 這是驗證項目隔離建立用戶和項目的請求所必需的

#admin_project_name = <None>

 

# Password to use for an administrative user. This is needed for authenticating requests made by project isolation to create users and projects (string value)

# 用於管理用戶的密碼。 這是驗證項目隔離建立用戶和項目的請求所必需的

#admin_password = <None>

 

# Admin domain name for authentication (Keystone V3). The same domain applies to user and project (string value)

# 用於身份驗證的管理域名（Keystone V3）。 同一個域適用於用戶和項目

#admin_domain_name = Default

 

 

[compute]

 

#

# From tempest.config

#

 

# Valid primary image reference to be used in tests. This is a required option (string value)

# 在測試中使用的第一個（主）有效鏡像的引用。 這是必需的選項

#image_ref = <None>

 

# Valid secondary image reference to be used in tests. This is a required option, but if only one image is available duplicate the value of image_ref above (string value)

# 在測試中使用的第二個（可供選擇的）有效鏡像的引用。 這是必需選項，但若是隻有一個鏡像可用，則複製上面的image_ref值

#image_ref_alt = <None>

 

# Valid image reference to be used in image certificate validation tests when enabled. This image must also have the required img_signature_* properties set. Additional details available within the following Nova documentation: https://docs.openstack.org/nova/latest/user/certificate-validation.html (string value)

# 啓用時，在鏡像驗證測試中使用的有效鏡像引用。 此鏡像還必須具備所需的img_signature_ *屬性集。 如下Nova文檔中提供了其餘詳細信息：

# https://docs.openstack.org/nova/latest/user/certificate-validation.html

#certified_image_ref = <None>

 

# A list of trusted certificates to be used when the image certificate validation compute feature is enabled. (list value)

# 一系列 trusted certificates將被使用，當compute feature 的鏡像的enable_ certificate validation屬性設置爲true.

#certified_image_trusted_certs = <None>

 

# Valid primary flavor to use in tests. (string value) 在測試中使用的第一個（主）有效flavor。

#flavor_ref = 1

 

# Valid secondary flavor to be used in tests. (string value) 在測試中使用的第二個（可供選擇的）有效flavor。

#flavor_ref_alt = 2

 

# Time in seconds between build status checks. (integer value) 檢測狀態的時間間隔，單位秒。

#build_interval = 1

 

# Timeout in seconds to wait for an instance to build. Other services that do not define build_timeout will inherit this value. (integer value)

# 等待實例構建的超時時間（以秒爲單位）。 其餘未定義build_timeout的服務將繼承此值。

#build_timeout = 300

 

# Additional wait time for clean state, when there is no OS-EXT-STS extension available (integer value)

# 當沒有可用的OS-EXT-STS擴展時，清理狀態的額外等待時間

#ready_wait = 0

 

# Name of the fixed network that is visible to all test projects. If multiple networks are available for a project, this is the network which will be used for creating servers if tempest does not create a network or a network is not specified elsewhere. It may be used for ssh validation only if floating IPs are disabled. (string value)

# 全部測試項目均可見的固定網絡的名稱。 若是項目有多個網絡可用，則若是tempest未建立網絡或未在其餘地方指定網絡，則此網絡將用於建立服務器。 當獲取不到浮動IP時，它可用於ssh驗證。

#fixed_network_name = <None>

 

# Catalog type of the Compute service. (string value) Compute服務器的目錄類型

#catalog_type = compute

 

# The compute region name to use. If empty, the value of identity.region is used instead. If no such region is found in the service catalog, the first found one is used. (string value)

# 要使用的計算區域名稱。 若是爲空，則使用identity.region的值。 若是在服務目錄中找不到這樣的區域，則使用第一個找到的區域。

#region =

 

# The endpoint type to use for the compute service. (string value)

# 用於計算服務的端點類型。

# Possible values:

# public - <No description provided>

# admin - <No description provided>

# internal - <No description provided>

# publicURL - <No description provided>

# adminURL - <No description provided>

# internalURL - <No description provided>

#endpoint_type = publicURL

 

# Expected device name when a volume is attached to an instance. Not all hypervisors guarantee that they will respect the user defined device name, tests may fail if inappropriate device name is set.(string value)

# 將卷附加到實例時的預期設備名稱。 並不是全部虛擬機管理程序都保證他們會尊重用戶定義的設備名稱，若是設置了不適當的設備名稱，測試可能會失敗。

#volume_device_name = vdb

 

# Time in seconds before a shelved instance is eligible for removing from a host.  -1 never offload, 0 offload when shelved. This configuration value should be same as nova.conf: DEFAULT.shelved_offload_time, and some tests will run for as long as the time. (integer value)

# 擱置卸載時間，擱置多久將被卸載。擱置的實例有資格從主機中刪除。-1表明永遠不卸載，0表明擱置時卸載。這個參數的值應該和nova.conf裏的DEFAULT.shelved_offload_time值相同，同時這些測試將持續此一段時間。

#shelved_offload_time = 0

 

# The minimum number of compute nodes expected. This will be utilized by some multinode specific tests to ensure that requests match the expected size of the cluster you are testing with. (integer value)

# 預期的最小計算節點數。 某些多節點特定測試將使用此方法來確保請求與您正在測試的羣集的預期大小相匹配。

#min_compute_nodes = 1

 

# Hypervisor type of the test target on heterogeneous compute environment. The value can be 'QEMU', 'xen' or something. (string value)

# 爲了測試多種多樣的計算環境，設置Hypervisor type。 值能夠是'QEMU'，'xen'等。

#hypervisor_type = <None>

 

# Lower version of the test target microversion range. The format is 'X.Y', where 'X' and 'Y' are int values. Tempest selects tests based on the range between min_microversion and max_microversion. If both values are not specified, Tempest avoids tests which require a microversion. Valid values are string with format 'X.Y' or string 'latest' (string value)

# 較低版本的測試目標微變化範圍。格式爲'X.Y'，其中'X'和'Y'爲int值。Tempest根據min_microversion和max_microversion之間的範圍選擇測試。若是未指定這兩個值，Tempest將避免須要微轉換的測試。

有效值爲格式爲「X.Y」的字符串「latest」的字符串。

#min_microversion = <None>

 

# Upper version of the test target microversion range. The format is 'X.Y', where 'X' and 'Y' are int values. Tempest selects tests based on the range between min_microversion and max_microversion. If both values are not specified, Tempest avoids tests which require a microversion. Valid values are string with format 'X.Y' or string 'latest' (string value)

# 測試目標微變化範圍的上限版本。 格式爲'X.Y'，其中'X'和'Y'爲int值。 Tempest根據min_microversion和max_microversion之間的範圍選擇測試。 若是未指定這兩個值，Tempest將避免須要微轉換的測試。 有效值爲格式爲「X.Y」的字符串或「latest」的字符串。

#max_microversion = <None>

 

# AZ to be used for Cinder and Nova. Set this parameter when the cloud has nova.conf: cinder.cross_az_attach set to false. Which means volumes attached to an instance must be in the same availability zone in Cinder as the instance availability zone in Nova. Set the common availability zone in this config which will be used to boot an instance as well as creating a volume. NOTE: If that AZ is not in Cinder (or allow_availability_zone_fallback=False in cinder.conf), the volume create request will fail and the instance will fail the build request. (string value)

# AZ用於Cinder和Nova。 當雲具備nova.conf時，設置此參數：cinder.cross_az_attach設置爲false。 這意味着附加到虛擬機中的多個卷必須位於Cinder的同一可用區中，與此同時此虛擬機在Nova中有可用域。在此配置中設置公共可用區域，該區域將用於啓動一臺虛擬機和建立一個卷（volume卷，雲硬盤； instance雲主機，虛擬機）

#compute_volume_common_az = <None>

 

 

[compute-feature-enabled]

 

#

# From tempest.config

#

 

# If false, skip disk config tests (boolean value) 若是爲false，則跳過磁盤配置測試。

#disk_config = true

 

# DEPRECATED: A list of enabled compute extensions with a special entry all which indicates every extension is enabled. Each extension should be specified with alias name. Empty list indicates all extensions are disabled (list value)

# DEPRECATED：已啓用的計算擴展的列表，其中包含一個特殊條目，表示每一個擴展都已啓用。 應使用別名指定每一個擴展名。 空列表表示禁用全部擴展

# This option is deprecated for removal. Its value may be silently ignored in the future. Reason: The Nova extensions API and mechanism is deprecated. This option will be removed when all releases supported by tempest no longer contain the Nova extensions API and mechanism.

# 不推薦使用此選項進行刪除。 它的價值可能會在未來被忽視。 緣由：不推薦使用Nova擴展API和機制。 當tempest支持的全部版本再也不包含Nova擴展API和機制時，將刪除此選項。

#api_extensions = all

 

# Does the test environment support changing the admin password? (boolean value) 測試環境是否支持更改管理員密碼？

#change_password = false

 

# Does the test environment support obtaining instance serial console output? (boolean value) 測試環境是否支持獲取雲主機串行的控制檯輸出？

#console_output = true

 

# Does the test environment support resizing? When you enable this feature, 'flavor_ref_alt' should be set and it should refer to a larger flavor than 'flavor_ref' one. (boolean value)

# 測試環境是否支持調整大小？ 啓用此功能時，應設置’flavor_ref_alt’的值大於’flavor_ref’的值。

#resize = false

 

# Does the test environment support pausing? (boolean value) 測試環境是否支持暫停？

#pause = true

 

# Does the test environment support shelving/unshelving? (boolean value) 測試環境是否支持擱置/擱置？

#shelve = true

 

# Does the test environment support suspend/resume? (boolean value) 測試環境是否支持暫停/恢復？

#suspend = true

 

# Does the test environment support cold migration? (boolean value) 測試環境是否支持冷遷移？

#cold_migration = true

 

# Does the test environment support live migration? (boolean value) 測試環境是否支持熱遷移？

#live_migration = true

 

# Does the test environment support live migrating VM back and forth between different versions of nova-compute? (boolean value)

# 測試環境是否支持在不一樣版本的nova-compute之間來回的虛擬機熱遷移？

#live_migrate_back_and_forth = false

 

# Does the test environment support metadata service? Ignored unless validation.run_validation=true. (boolean value)

# 測試環境是否支持元數據服務？ 除非validation.run_validation = true，不然忽略。

#metadata_service = true

 

# Does the test environment use block devices for live migration (boolean value) 測試環境是否使用塊設備進行熱遷移

#block_migration_for_live_migration = false

 

# Does the test environment support block migration with Cinder iSCSI volumes. Note: libvirt >= 1.2.17 is required to support this if using the libvirt compute driver. (boolean value)

# 測試環境是否支持使用Cinder iSCSI捲進行塊遷移。 注意：若是使用libvirt計算驅動程序，則須要libvirt> = 1.2.17來支持此操做。

#block_migrate_cinder_iscsi = false

 

# Enable VNC console. This configuration value should be same as nova.conf: vnc.enabled (boolean value)

# 啓用VNC控制檯。 此配置值應與nova.conf：vnc.enabled相同

#vnc_console = false

 

# Expected VNC server name (WebSockify, nginx, etc) in response header. (string value)

# 響應頭中，預期的VNC服務器名稱（WebSockify，nginx等）。

#vnc_server_header = WebSockify

 

# Enable Spice console. This configuration value should be same as nova.conf: spice.enabled (boolean value)

# 啓用Spice控制檯。 此配置值應與nova.conf：spice.enabled相同

#spice_console = false

 

# Enable RDP console. This configuration value should be same as nova.conf: rdp.enabled (boolean value)

# 啓用RDP控制檯。 此配置值應與nova.conf：rdp.enabled相同

#rdp_console = false

 

# Enable serial console. This configuration value should be the same as nova.conf: serial_console.enabled (boolean value)

# 啓用串行控制檯。 此配置值應與nova.conf：serial_console.enabled相同

#serial_console = false

 

# Does the test environment support instance rescue mode? (boolean value) 測試環境是否支持雲主機 rescue 模式？

#rescue = true

 

# Enables returning of the instance password by the relevant server API calls such as create, rebuild or rescue. This configuration value should be same as nova.conf: DEFAULT.enable_instance_password

(boolean value)

# 容許經過相關服務器API調用返回雲主機密碼，例如，建立，rebuild ，rescue。此配置值應與nova.conf：DEFAULT.enable_instance_password相同

#enable_instance_password = true

 

# Does the test environment support dynamic network interface attachment? (boolean value) 測試環境是否支持動態網絡接口附件？

#interface_attach = true

 

# Does the test environment support creating snapshot images of running instances? (boolean value)

# 測試環境是否支持正在運行的雲主機建立快照？

#snapshot = true

 

# DEPRECATED: Does the test environment have the nova cert running?(boolean value) 測試環境是否運行nova驗證？

# This option is deprecated for removal. Its value may be silently ignored in the future. Reason: On Nova side, the nova-cert service is deprecated and the service will be removed as early as Ocata.

# 不推薦使用此選項進行刪除。 它的價值可能會在未來被忽視。 緣由：在Nova方面，nova-cert服務已棄用，服務將在Ocata以前刪除。

#nova_cert = false

 

# Does the test environment support server personality (boolean value) 測試環境是否支持服務器特性

#personality = false

 

# Does the test environment support attaching an encrypted volume to a running server instance? This may depend on the combination of compute_driver in nova and the volume_driver(s) in cinder. (boolean value)

# 測試環境是否支持將加密卷附加到正在運行的雲主機服務器？ 這可能取決於nova中的compute_driver和cinder中的volume_driver的組合。

#attach_encrypted_volume = true

 

# Enable special configuration drive with metadata. (boolean value) 使用元數據啓用特殊配置驅動器

#config_drive = true

 

# A list of enabled filters that Nova will accept as hints to the scheduler when creating a server. If the default value is overridden in nova.conf by the test environment (which means that a different set of filters is enabled than what is included in Nova by default), then this option must be configured to contain the same filters that Nova uses in the test environment. A special entry 'all' indicates all filters that are included with Nova are enabled. If using 'all', be sure to enable all filters in nova.conf, as tests can fail in unpredictable ways if Nova's and Tempest's enabled filters don't match. Empty list indicates all filters are disabled. The full list of enabled filters is in nova.conf: filter_scheduler.enabled_filters. (list value) Deprecated group/name - [compute-feature-enabled]/scheduler_available_filters

# Nova在建立服務器時將接受的啓用過濾器列表做爲調度程序的提示。 若是測試環境在nova.conf中覆蓋了默認值（這意味着啓用了一組不一樣於Nova中包含的過濾器），則必須將此選項配置爲包含Nova在其中使用的相同過濾器 測試環境。 特殊條目「all」表示Nova中包含的全部過濾器均已啓用。 若是使用'all'，請確保在nova.conf中啓用全部過濾器，由於若是Nova和Tempest的啓用過濾器不匹配，測試可能會以不可預測的方式失敗。 空列表表示禁用全部過濾器。 啓用過濾器的完整列表位於nova.conf：filter_scheduler.enabled_filters。

#scheduler_enabled_filters = AvailabilityZoneFilter,ComputeFilter,ComputeCapabilitiesFilter,ImagePropertiesFilter,ServerGroupAntiAffinityFilter,ServerGroupAffinityFilter

 

# Does the test environment support in-place swapping of volumes attached to a server instance? (boolean value)

# 測試環境是否支持雲硬盤交換的鏈接到雲主機服務器？

#swap_volume = false

 

# Does the test environment support volume-backed live migration? (boolean value) 測試環境是否支持以卷(雲硬盤)備份的熱遷移？

#volume_backed_live_migration = false

 

# Does the test environment support attaching a volume to more than one instance? This depends on hypervisor and volume backend/type and compute API version 2.60. (boolean value)

# 測試環境是否支持將一個卷(雲硬盤)同時附加到多個雲主機？ 這取決於hypervisor和雲硬盤備份/類型和計算API版本2.60。

#volume_multiattach = false

 

 

[debug]

 

#

# From tempest.config

#

 

# A regex to determine which requests should be traced. 用於肯定應跟蹤哪些請求的正則表達式。

#

# This is a regex to match the caller for rest client requests to be able to selectively trace calls out of specific classes and methods. It largely exists for test development, and is not expected to be used in a real deploy of tempest. This will be matched against the discovered ClassName:method in the test environment.

# 這是一個正則表達式，用於匹配休眠客戶端請求的調用者，以便可以有選擇地跟蹤特定類和方法以外的調用。 它主要用於測試開發，而且預計不會用於Tempest的實際部署。 這將與在測試環境中發現的ClassName:method相匹配。

#

# Expected values for this field are: 該字段的預期值爲：

#

#  * ClassName:test_method_name - traces one test_method 跟蹤一個測試方法

#  * ClassName:setUp(Class) - traces specific setup functions 跟蹤特殊的setup方法

#  * ClassName:tearDown(Class) - traces specific teardown functions 跟蹤特殊的 teardown 方法

#  * ClassName:_run_cleanups - traces the cleanup functions 跟蹤 cleanup 方法

#

# If nothing is specified, this feature is not enabled. To trace everything specify .* as the regex.  (string value)

# 若是未指定任何內容，則不啓用此功能。 要跟蹤全部指定.*做爲正則表達式。

#trace_requests =

 

 

[identity]

 

 

用戶(不管是Dashboard, API Client)都須要訪問Keystone獲取服務列表，以及每一個服務的地址(Openstack中稱爲Endpoint).訪問服務的地址. Endpoint能夠理解爲訪問服務url。

 

#

# From tempest.config

#

 

# Catalog type of the Identity service. (string value) 身份服務的目錄類型。

#catalog_type = identity

 

# Set to True if using self-signed SSL certificates. (boolean value) 若是使用自簽名SSL證書，則設置爲True。

#disable_ssl_certificate_validation = false

 

# Specify a CA bundle file to use in verifying a TLS (https) server certificate. (string value) 指定用於驗證TLS（https）服務器證書的CA捆綁包文件。

#ca_certificates_file = <None>

 

# Full URI of the OpenStack Identity API (Keystone), v2 (string value)

# OpenStack 驗證的 API（Keystone）的 URI。（V2版）

#uri = <None>

 

# Full URI of the OpenStack Identity API (Keystone), v3 (string value)

# OpenStack 驗證的 API（Keystone）的 URI。（V3版）

#uri_v3 = <None>

 

# Identity API version to be used for authentication for API tests. (string value)

# Identity API版本，用於API測試的身份驗證。

#auth_version = v3

 

# The identity region name to use. Also used as the other services' region name unless they are set explicitly. If no such region is found in the service catalog, the first found one is used. (string value)

# 要使用的標識區域名稱。 除非明確設置，不然還用做其餘服務的區域名稱。 若是在服務目錄中找不到這樣的區域，則使用第一個找到的區域。

#region = RegionOne

 

# The admin endpoint type to use for OpenStack Identity (Keystone) API v2 (string value) 用於OpenStack認證的(Keystone) API（V2版本， admin endpoint type）

# Possible values:

# public - <No description provided>

# admin - <No description provided>

# internal - <No description provided>

# publicURL - <No description provided>

# adminURL - <No description provided>

# internalURL - <No description provided>

#v2_admin_endpoint_type = adminURL

 

# The public endpoint type to use for OpenStack Identity (Keystone) API v2 (string value) 用於OpenStack認證的(Keystone) API（V2版本， public endpoint type）

# Possible values:

# public - <No description provided>

# admin - <No description provided>

# internal - <No description provided>

# publicURL - <No description provided>

# adminURL - <No description provided>

# internalURL - <No description provided>

#v2_public_endpoint_type = publicURL

 

# The endpoint type to use for OpenStack Identity (Keystone) API v3. The default value adminURL is deprecated and will be modified to publicURL in the next release. (string value)

# 用於OpenStack認證的(Keystone) API（V3版本，endpoint type）。不推薦使用默認值adminURL，並在下一版本中將其修改成publicURL。

# Possible values:

# public - <No description provided>

# admin - <No description provided>

# internal - <No description provided>

# publicURL - <No description provided>

# adminURL - <No description provided>

# internalURL - <No description provided>

#v3_endpoint_type = adminURL

 

# Role required to administrate keystone. (string value) 管理keystone所需的角色。

#admin_role = admin

 

# ID of the default domain (string value) 默認域的ID

#default_domain_id = default

 

# Whether keystone identity v3 policy required a domain scoped token to use admin APIs (boolean value)

# keystone identity v3策略是否須要域範圍標記才能使用管理API

#admin_domain_scope = false

 

# The number of unsuccessful login attempts the user is allowed before having the account locked. This only takes effect when identity-feature-enabled.security_compliance is set to 'True'. For more details, refer to keystone config options keystone.conf:security_compliance.lockout_failure_attempts. This feature is disabled by default in keystone. (integer value)

# 在鎖定賬戶以前容許用戶登陸嘗試失敗的次數。 這僅在identity-feature-enabled.security_compliance設置爲「True」時生效。 有關更多詳細信息，請參閱keystone配置選項keystone.conf：security_compliance.lockout_failure_attempts。 默認狀況下，此功能在keystone中處於禁用狀態。

#user_lockout_failure_attempts = 2

 

# The number of seconds a user account will remain locked. This only takes effect when identity-feature-enabled.security_compliance is set to 'True'. For more details, refer to keystone config options keystone.conf:security_compliance.lockout_duration. Setting this option will have no effect unless you also set identity.user_lockout_failure_attempts. (integer value)

# 用戶賬戶保持鎖定的秒數。 這僅在identity-feature-enabled.security_compliance設置爲「True」時生效。 有關更多詳細信息，請參閱keystone配置選項keystone.conf：security_compliance.lockout_duration。 除非您還設置了identity.user_lockout_failure_attempts，不然設置此選項將不起做用。

#user_lockout_duration = 5

 

# The number of passwords for a user that must be unique before an old password can be reused. This only takes effect when identity-feature-enabled.security_compliance is set to 'True'. This config option corresponds to keystone.conf: security_compliance.unique_last_password_count, whose default value is 0 meaning disabling this feature. NOTE: This config option value must be same as keystone.conf: security_compliance.unique_last_password_count otherwise test might fail (integer value)

# 在重複使用舊密碼以前用戶的密碼數必須是惟一的。 這僅在identity-feature-enabled.security_compliance設置爲「True」時生效。 

此配置選項對應於keystone.conf：security_compliance.unique_last_password_count，其默認值爲0表示禁用此功能。 注意：此配置選項值必須與keystone.conf：security_compliance.unique_last_password_count相同，不然測試可能會失敗

#user_unique_last_password_count = 2

 

 

 

[identity-feature-enabled]

 

#

# From tempest.config

#

 

# Does the identity service have delegation and impersonation enabled (boolean value) 身份服務是否啓用了委派和模擬

#trust = true

 

# DEPRECATED: Is the v2 identity API enabled (boolean value) 棄用：V2版本的 API 是否容許

# This option is deprecated for removal. Its value may be silently ignored in the future. Reason: The identity v2.0 API was removed in the Queens release. Tests that exercise the v2.0 API will be removed from tempest in the v22.0.0 release. They are kept only to test stable branches.

# 不推薦使用此選項進行刪除。 它的價值可能會在未來被忽視。 緣由：Queens版本中刪除了身份v2.0 API。 在v22.0.0版本中，將從tempest中刪除運行v2.0 API的測試。 它們僅用於測試穩定的分支。

#api_v2 = false

 

# Is the v2 identity admin API available? This setting only applies if api_v2 is set to True. (boolean value) v2版 admin API是否可用？ 此設置僅在api_v2設置爲True時適用。

#api_v2_admin = true

 

# Is the v3 identity API enabled (boolean value) V3 版的 API 認證是否可用

#api_v3 = true

 

# A list of enabled identity extensions with a special entry all which indicates every extension is enabled. Empty list indicates all extensions are disabled. To get the list of extensions run: 'openstack extension list --identity' (list value)

# 已啓用的標識擴展列表，其中包含指示每一個擴展名的特殊條目。 空列表表示禁用全部擴展。 要獲取擴展名列表：'openstack extension list --identity'

#api_extensions = all

 

# Are domain specific drivers enabled? This configuration value should be same as [identity]->domain_specific_drivers_enabled in keystone.conf. (boolean value)

# 是否啓用了特定於域的驅動 此配置值應與keystone.conf中的[identity]  - > domain_specific_drivers_enabled相同。

#domain_specific_drivers = false

 

# Does the environment have the security compliance settings enabled? (boolean value) 環境是否已啓用安全合規性設置？

#security_compliance = false

 

# Is the project tags identity v3 API available? (boolean value) project_tags是否可使用 v3版 API 驗證？

#project_tags = false

 

# Does the environment have application credentials enabled? (boolean value) 環境是否啓用了應用程序憑據？

#application_credentials = false

 

# Set to True if the environment has a read-only user source. This will skip all tests that attempt to create, delete, or modify users. This should not be set to True if using dynamic credentials (boolean value)

# 若是環境具備只讀用戶來源，則設置爲True。 這將跳過嘗試建立，刪除或修改用戶的全部測試。 若是使用動態憑據，則不該將其設置爲True

#immutable_user_source = false

 

 

[image]

 

#

# From tempest.config

#

 

# Catalog type of the Image service. (string value) 鏡像服務的catalog_type

#catalog_type = image

 

# The image region name to use. If empty, the value of identity.region is used instead. If no such region is found in the service catalog, the first found one is used. (string value)

# 要使用的鏡像區域名稱。 若是爲空，則使用identity.region的值。 若是在服務目錄中找不到這樣的區域，則使用第一個找到的區域。

#region =

 

# The endpoint type to use for the image service. (string value) 鏡像服務中使用的 endpoint 類型

# Possible values:

# public - <No description provided>

# admin - <No description provided>

# internal - <No description provided>

# publicURL - <No description provided>

# adminURL - <No description provided>

# internalURL - <No description provided>

#endpoint_type = publicURL

 

# http accessible image (string value) 可得到的鏡像路徑

#http_image = http://download.cirros-cloud.net/0.3.1/cirros-0.3.1-x86_64-uec.tar.gz

 

# Timeout in seconds to wait for an image to become available. (integer value) 等待鏡像狀態變爲 available 的時間，單位爲秒。

#build_timeout = 300

 

# Time in seconds between image operation status checks. (integer value) 檢測鏡像狀態的時間間隔，單位爲秒

#build_interval = 1

 

# A list of image's container formats users can specify. (list value) 用戶能夠指定的鏡像容器格式列表。

#container_formats = ami,ari,aki,bare,ovf,ova

 

# A list of image's disk formats users can specify. (list value) 用戶能夠指定的鏡像磁盤格式列表。

#disk_formats = ami,ari,aki,vhd,vmdk,raw,qcow2,vdi,iso,vhdx

 

 

[image-feature-enabled]

 

#

# From tempest.config

#

 

# DEPRECATED: Is the v2 image API enabled (boolean value) 禁用：V2版本的鏡像api 是否可得到

# This option is deprecated for removal. Its value may be silently ignored in the future. Reason: Glance v1 APIs are deprecated and v2 APIs are current one. In future, Tempest will test v2 APIs only so this config option will be removed.

# 不推薦使用此選項進行刪除。 它的價值可能會在未來被忽視。 緣由：不推薦使用Glance API，v2 API是當前API。 未來，Tempest將僅測試v2 API，所以將刪除此配置選項。

#api_v2 = true

 

# DEPRECATED: Is the v1 image API enabled (boolean value) 禁用：V1版本的鏡像api 是否可得到

# This option is deprecated for removal. Its value may be silently ignored in the future. Reason: Glance v1 APIs are deprecated and v2 APIs are current one. In future, Tempest will test v2 APIs only so this config option will be removed.

# 不推薦使用此選項進行刪除。 它的價值可能會在未來被忽視。 緣由：不推薦使用Glance API，v2 API是當前API。 未來，Tempest將僅測試v2 API，所以將刪除此配置選項。

#api_v1 = false

 

 

[network]

 

#

# From tempest.config

#

 

# Catalog type of the Neutron service. (string value) 網絡服務的catalog_type

#catalog_type = network

 

# The network region name to use. If empty, the value of identity.region is used instead. If no such region is found in the service catalog, the first found one is used. (string value)

# 要使用的網絡區域名稱。 若是爲空，則使用identity.region的值。 若是在服務目錄中找不到這樣的區域，則使用第一個找到的區域。

#region =

 

# The endpoint type to use for the network service. (string value) 網絡服務中使用的 endpoint 類型

# Possible values:

# public - <No description provided>

# admin - <No description provided>

# internal - <No description provided>

# publicURL - <No description provided>

# adminURL - <No description provided>

# internalURL - <No description provided>

#endpoint_type = publicURL

 

# The cidr block to allocate project ipv4 subnets from (string value) 用於分配項目ipv4子網的cidr塊

#project_network_cidr = 10.100.0.0/16

 

# The mask bits for project ipv4 subnets (integer value) 項目ipv4子網的掩碼位

#project_network_mask_bits = 28

 

# The cidr block to allocate project ipv6 subnets from (string value) 用於分配項目ipv6子網的cidr塊

#project_network_v6_cidr = 2003::/48

 

# The mask bits for project ipv6 subnets (integer value) 項目ipv6子網的掩碼位

#project_network_v6_mask_bits = 64

 

# Whether project networks can be reached directly from the test client. This must be set to True when the 'fixed' connect_method is selected. (boolean value)

# 是否能夠直接從測試客戶端訪問項目網絡。 選擇「固定」connect_method時，必須將其設置爲True。

#project_networks_reachable = false

 

# Id of the public network that provides external connectivity (string value) 提供外部鏈接的公共網絡的ID

#public_network_id =

 

# Default floating network name. Used to allocate floating IPs when neutron is enabled. (string value)

# 默認浮動網絡名稱。當網絡可用時， 用於分配浮動IP。

#floating_network_name = <None>

 

# Id of the public router that provides external connectivity. This should only be used when Neutron's 'allow_overlapping_ips' is set to 'False' in neutron.conf. usually not needed past 'Grizzly’ releas (string value)

# 提供外部鏈接的公共路由器的ID。 這隻應在Neutron的'allow_overlapping_ips'在neutron.conf中設置爲'False'時使用。 一般過去'Grizzly’版本是不須要

#public_router_id =

 

# Timeout in seconds to wait for network operation to complete. (integer value) 等待網絡操做完成的時間，單位爲秒

#build_timeout = 300

 

# Time in seconds between network operation status checks. (integer value) 網絡運行狀態檢查之間的時間，單位爲秒。

#build_interval = 1

 

# DEPRECATED: List of dns servers which should be used for subnet creation (list value) 棄用：應該用於建立子網的DNS服務器列表。

# This option is deprecated for removal. Its value may be silently ignored in the future. Reason: This config option is no longer used anywhere, so it can be removed.

# 不推薦使用此選項進行刪除。 它的價值可能會在未來被忽視。 緣由：此配置選項將再也不在任何地方使用，所以能夠將其刪除。

#dns_servers = 8.8.8.8,8.8.4.4

 

# vnic_type to use when launching instances with pre-configured ports. 啓動具備預配置端口的雲主機時使用的vnic_type。

# Supported ports are: ['normal','direct','macvtap'] (string value) 支持的端口爲

# Possible values:

# <None> - <No description provided>

# normal - <No description provided>

# direct - <No description provided>

# macvtap - <No description provided>

#port_vnic_type = <None>

 

# port profile to use when launching instances with pre-configured ports. (dict value) 啓動具備預配置端口的雲主機時要使用的端口配置文件。

#port_profile =

 

# List of ip pools for subnetpools creation (list value) ip池列表子網池的建立

#default_network = 1.0.0.0/16,2.0.0.0/16

 

# The environment does not support network separation between tenants. (boolean value) 環境不支持租戶之間的網絡分離。

#shared_physical_network = false

 

 

[network-feature-enabled]

 

#

# From tempest.config

#

 

# Allow the execution of IPv6 tests (boolean value) 容許執行IPv6測試

#ipv6 = true

 

# A list of enabled network extensions with a special entry all which indicates every extension is enabled. Empty list indicates all extensions are disabled. To get the list of extensions run: 'neutron ext-list' (list value)

# 已啓用的網絡擴展列表，其中包含一個特殊條目，表示每一個擴展都已啓用。 空列表表示禁用全部擴展。 要獲取擴展名列表：'neutron ext-list'

#api_extensions = all

 

# Allow the execution of IPv6 subnet tests that use the extended IPv6 attributes ipv6_ra_mode and ipv6_address_mode (boolean value)

# 容許執行使用擴展IPv6屬性ipv6_ra_mode和ipv6_address_mode的IPv6子網測試

#ipv6_subnet_attributes = false

 

# Does the test environment support changing port admin state (boolean value) 測試環境是否支持更改端口管理狀態

#port_admin_state_change = true

 

# Does the test environment support port security? (boolean value) 測試環境是否支持端口安全性？

#port_security = false

 

# Does the test environment support floating_ips (boolean value) 測試環境是否支持floating_ips

#floating_ips = true

 

# Name of the physnet for placement based minimum bandwidth allocation. (string value) 基於最小帶寬分配的放置的physnet的名稱。

#qos_placement_physnet = <None>

 

# Base segmentation ID to create provider networks. This value will be increased in case of conflict. (string value)

# 用於建立提供商網絡的基本分段ID。 若是發生衝突，該值將增長。

#provider_net_base_segmentation_id = 3000

 

 

[object-storage]

 

#

# From tempest.config

#

 

# Catalog type of the Object-Storage service. (string value) 對象存儲服務的catalog_type

#catalog_type = object-store

 

# The object-storage region name to use. If empty, the value of identity.region is used instead. If no such region is found in the service catalog, the first found one is used. (string value)

# 要使用的對象存儲區域名稱。 若是爲空，則使用identity.region的值。 若是在服務目錄中找不到這樣的區域，則使用第一個找到的區域。

#region =

 

# The endpoint type to use for the object-store service. (string value) 對象存儲服務使用的 endpoint type

# Possible values:

# public - <No description provided>

# admin - <No description provided>

# internal - <No description provided>

# publicURL - <No description provided>

# adminURL - <No description provided>

# internalURL - <No description provided>

#endpoint_type = publicURL

 

# Number of seconds to time on waiting for a container to container synchronization complete. (integer value) 等待容器到容器同步完成的秒數。

#container_sync_timeout = 600

 

# Number of seconds to wait while looping to check the status of a container to container synchronization (integer value)

# 循環檢查容器狀態到容器同步時等待的秒數

#container_sync_interval = 5

 

# Role to add to users created for swift tests to enable creating containers (string value)

# 添加到爲快速測試建立的用戶的角色，以便可以建立容器

#operator_role = Member

 

# User role that has reseller admin (string value) 具備代理商管理員的用戶角色

#reseller_admin_role = ResellerAdmin

 

# Name of sync realm. A sync realm is a set of clusters that have agreed to allow container syncing with each other. Set the same realm name as Swift's container-sync-realms.conf (string value)

# 同步領域的名稱。 同步領域是一組已贊成容許容器彼此同步的集羣。 設置與Swift的container-sync-realms.conf文件中相同的域名

#realm_name = realm1

 

# One name of cluster which is set in the realm whose name is set in 'realm_name' item in this file. Set the same cluster name as Swift's container-sync-realms.conf (string value)

# 在域中設置的一個集羣名稱，其名稱在此文件的「realm_name」項中設置。 設置與Swift的container-sync-realms.conf相同的集羣名稱

#cluster_name = name1

 

 

[object-storage-feature-enabled]

 

#

# From tempest.config

#

 

# A list of the enabled optional discoverable apis. A single entry, all, indicates that all of these features are expected to be enabled (list value)

# 已啓用的可選發現api的列表。 單個條目all表示預計將啓用全部這些功能。

#discoverable_apis = all

 

# Execute (old style) container-sync tests (boolean value) 執行（舊式）容器同步測試

#container_sync = true

 

# Execute object-versioning tests (boolean value) 執行對象版本測試

#object_versioning = true

 

# Execute discoverability tests (boolean value) 執行可發現性測試

#discoverability = true

 

 

[oslo_concurrency]

 

#

# From oslo.concurrency

#

 

# Enables or disables inter-process locks. (boolean value) 啓用或禁用進程間鎖定。

#disable_process_locking = false

 

# Directory to use for lock files.  For security, the specified directory should only be writable by the user running the processes that need locking. Defaults to environment variable OSLO_LOCK_PATH. If external locks are used, a lock path must be set. (string value)

# 用於鎖定文件的目錄。 爲了安全起見，指定的目錄只能由運行須要鎖定的進程的用戶寫入。 默認爲環境變量OSLO_LOCK_PATH。 若是使用外部鎖，則必須設置鎖定路徑。

#lock_path = <None>

 

 

[placement]

 

#

# From tempest.config

#

 

# The endpoint type to use for the placement service. (string value) 放置服務的endpoint_type

# Possible values:

# public - <No description provided>

# admin - <No description provided>

# internal - <No description provided>

#endpoint_type = public

 

# Catalog type of the Placement service. (string value) 放置服務的 catalog_type

#catalog_type = placement

 

# The placement region name to use. If empty, the value of [identity]/region is used instead. If no such region is found in the service catalog, the first region found is used. (string value)

# 要使用的放置區域名稱。 若是爲空，則使用[identity] / region的值。 若是在服務目錄中找不到此類區域，則使用找到的第一個區域。

#region = RegionOne

 

# Lower version of the test target microversion range. The format is 'X.Y', where 'X' and 'Y' are int values. Tempest selects tests based on the range between min_microversion and max_microversion. If both values are not specified, Tempest avoids tests which require a microversion. Valid values are string with format 'X.Y' or string 'latest' (string value)

# 較低版本的測試目標微變化範圍。格式爲'X.Y'，其中'X'和'Y'爲int值。Tempest根據min_microversion和max_microversion之間的範圍選擇測試。若是未指定這兩個值，Tempest將避免須要微轉換的測試。

有效值爲格式爲「X.Y」的字符串「latest」的字符串。

#min_microversion = <None>

 

# Upper version of the test target microversion range. The format is 'X.Y', where 'X' and 'Y' are int values. Tempest selects tests based on the range between min_microversion and max_microversion. If both values are not specified, Tempest avoids tests which require a microversion. Valid values are string with format 'X.Y' or string 'latest' (string value)

# 測試目標微變化範圍的上限版本。 格式爲'X.Y'，其中'X'和'Y'爲int值。 Tempest根據min_microversion和max_microversion之間的範圍選擇測試。 若是未指定這兩個值，Tempest將避免須要微轉換的測試。 有效值爲格式爲「X.Y」的字符串或「latest」的字符串。

#max_microversion = <None>

 

 

[profiler]

 

#

# From tempest.config

#

 

# The secret key to enable OpenStack Profiler. The value should match the one configured in OpenStack services under `[profiler]/hmac_keys` property. The default empty value keeps profiling disabled (string value)

# 啓用OpenStack Profiler的密鑰。 該值應與`[profiler] / hmac_keys`屬性下的OpenStack服務中配置的值匹配。 禁止使用保留默認的空值

#key = <None>

 

 

[scenario]

 

#

# From tempest.config

#

 

# DEPRECATED: Directory containing image files (string value) 禁用：包含鏡像文件的目錄

# This option is deprecated for removal. Its value may be silently ignored in the future. 不推薦使用此選項進行刪除。 它的價值可能會在未來被忽視。

#img_dir = /opt/stack/new/devstack/files/images/cirros-0.3.1-x86_64-uec

 

# Image file name (string value) 鏡像文件名稱

# Deprecated group/name - [scenario]/qcow2_img_file 禁用 group/name - [scenario]/qcow2_img_file

#img_file = cirros-0.3.1-x86_64-disk.img

 

# Image disk format (string value) 鏡像磁盤格式

#img_disk_format = qcow2

 

# Image container format (string value) 鏡像容器格式

#img_container_format = bare

 

# Glance image properties. Use for custom images which require them (dict value) 鏡像屬性。用於須要自定義的鏡像

#img_properties = <None>

 

# DEPRECATED: AMI image file name (string value) 禁用：AMI 鏡像文件名

# This option is deprecated for removal. Its value may be silently ignored in the future. 不推薦使用此選項進行刪除。 它的價值可能會在未來被忽視。

#ami_img_file = cirros-0.3.1-x86_64-blank.img

 

# DEPRECATED: ARI image file name (string value) 禁用：ARI 鏡像文件名

# This option is deprecated for removal. Its value may be silently ignored in the future. 不推薦使用此選項進行刪除。 它的價值可能會在未來被忽視。

#ari_img_file = cirros-0.3.1-x86_64-initrd

 

# DEPRECATED: AKI image file name (string value) 禁用： AKI 鏡像文件名

# This option is deprecated for removal. Its value may be silently ignored in the future. 不推薦使用此選項進行刪除。 它的價值可能會在未來被忽視。

#aki_img_file = cirros-0.3.1-x86_64-vmlinuz

 

# DHCP client used by images to renew DCHP lease. If left empty,

update operation will be skipped. Supported clients: "udhcpc",

"dhclient" (string value)

# 用於續訂DHCP租約的DHCP客戶端的鏡像。 若是爲空，將跳過更新操做。 支持的客戶端：「udhcpc」，「dhclient」

# Possible values:

# udhcpc - <No description provided>

# dhclient - <No description provided>

# '' - <No description provided>

#dhcp_client = udhcpc

 

# The protocol used in security groups tests to check connectivity. (string value) 安全組中使用的協議測試以檢查鏈接性。

# Possible values:

# icmp - <No description provided>

# tcp - <No description provided>

# udp - <No description provided>

#protocol = icmp

 

 

[service-clients]

 

#

# From tempest.config

#

 

# Timeout in seconds to wait for the http request to return (integer value) 等待http請求返回的超時時間（以秒爲單位）

#http_timeout = 60

 

# Specify an http proxy to use. (string value) 指定要使用的http代理。

#proxy_url = <None>

 

 

[service_available]

 

#

# From tempest.config

#

 

# Whether or not cinder is expected to be available (boolean value) 是否能夠提供 cinder

#cinder = true

 

# Whether or not neutron is expected to be available (boolean value) 是否能夠提供 neutron

#neutron = false

 

# Whether or not glance is expected to be available (boolean value)

是否能夠提供 glance

#glance = true

 

# Whether or not swift is expected to be available (boolean value)

是否能夠提供 swift

#swift = true

 

# Whether or not nova is expected to be available (boolean value)

是否能夠提供 nova

#nova = true

 

 

[validation]

 

#

# From tempest.config

#

 

# Enable ssh on created servers and creation of additional validation

resources to enable remote access. In case the guest does not support ssh set it to false (boolean value)

# 在已建立的雲主機上啓用ssh並建立其餘驗證資源以啓用遠程訪問。 若是guest虛擬機不支持ssh，則將其設置爲false

#run_validation = true

 

# Enable/disable security groups. (boolean value) 容許/不容許 安全組

#security_group = true

 

# Enable/disable security group rules. (boolean value) 容許/不容許 安全組規則

#security_group_rules = true

 

# Default IP type used for validation: -fixed: uses the first IP belonging to the fixed network -floating: creates and uses a floating IP (string value)

# 用於驗證的默認IP類型：-fixed：使用屬於固定網絡的第一個IP -floating：建立並使用浮動IP

# Possible values:

# fixed - <No description provided>

# floating - <No description provided>

#connect_method = floating

 

# Default authentication method to the instance. Only ssh via keypair

is supported for now. Additional methods will be handled in a separate spec. (string value)

# 實例的默認身份驗證方法。 目前僅支持經過密鑰進行遠程登陸。 其餘方法將在單獨的規範中處理。

# Possible values:

# keypair - <No description provided>

#auth_method = keypair

 

# Default IP version for ssh connections. (integer value) ssh鏈接的默認IP版本。

 

#ip_version_for_ssh = 4

 

# Timeout in seconds to wait for ping to succeed. (integer value) 等待ping成功的超時時間（以秒爲單位）。

#ping_timeout = 120

 

# Timeout in seconds to wait for the TCP connection to be successful. (integer value) 等待TCP鏈接成功的超時時間（以秒爲單位）。

#connect_timeout = 60

 

# Timeout in seconds to wait for the ssh banner. (integer value) 等待ssh banner 的超時時間 （以秒爲單位）。

#ssh_timeout = 300

 

# User name used to authenticate to an instance. (string value) 用於對雲主機進行身份驗證的用戶名。

#image_ssh_user = root

 

# Password used to authenticate to an instance. (string value) 用於對雲主機進行身份驗證的密碼。

#image_ssh_password = password

 

# Shell fragments to use before executing a command when sshing to a guest. (string value)   在sshing到guest虛擬機時執行命令以前使用的殼片斷。

#ssh_shell_prologue = set -eu -o pipefail; PATH=$$PATH:/sbin;

 

# The packet size for ping packets originating from remote linux hosts (integer value) 來自遠程linux主機的ping數據包的數據包大小

#ping_size = 56

 

# The number of ping packets originating from remote linux hosts (integer value) 源自遠程linux主機的ping數據包的數量

#ping_count = 1

 

# Unallocated floating IP range, which will be used to test the floating IP bulk feature for CRUD operation. This block must not overlap an existing floating IP pool. (string value)

# 未分配的浮動IP範圍，用於測試CRUD操做的浮動IP批量功能。 此塊不得與現有浮動IP池重疊。

#floating_ip_range = 10.0.0.0/29

 

# Network used for SSH connections. Ignored if connect_method=floating. (string value) 用於SSH鏈接的網絡。 若是connect_method =浮動 ip，則忽略。

#network_for_ssh = public

 

 

[volume]

 

#

# From tempest.config

#

 

# Time in seconds between volume availability checks. (integer value) 卷（雲硬盤）可用性檢查之間的時間（秒）。

#build_interval = 1

 

# Timeout in seconds to wait for a volume to become available. (integer value) 等待卷可用的超時時間（以秒爲單位）。

#build_timeout = 300

 

# Catalog type of the Volume Service (string value) 雲硬盤服務的catalog_type

#catalog_type = volumev3

 

# The volume region name to use. If empty, the value of identity.region is used instead. If no such region is found in the service catalog, the first found one is used. (string value)

# 要使用的卷區域名稱。 若是爲空，則使用identity.region的值。 若是在服務目錄中找不到這樣的區域，則使用第一個找到的區域。

#region =

 

# The endpoint type to use for the volume service. (string value) 雲硬盤服務的 endpoint_type

# Possible values:

# public - <No description provided>

# admin - <No description provided>

# internal - <No description provided>

# publicURL - <No description provided>

# adminURL - <No description provided>

# internalURL - <No description provided>

#endpoint_type = publicURL

 

# A list of backend names separated by comma. The backend name must be declared in cinder.conf (list value) 由逗號分隔的後端名稱列表。 後端名稱必須在cinder.conf中聲明

#backend_names = BACKEND_1,BACKEND_2

 

# Backend protocol to target when creating volume types (string value) 建立雲硬盤類型時要定位的後端協議

#storage_protocol = iSCSI

 

# Backend vendor to target when creating volume types (string value) 後端供應商在建立雲硬盤類型時進行定位

#vendor_name = Open Source

 

# Disk format to use when copying a volume to image (string value) 將雲硬盤複製到鏡像時要使用的磁盤格式

#disk_format = raw

 

# Default size in GB for volumes created by volumes tests (integer value) 雲硬盤測試建立的雲硬盤的默認大小（以GB爲單位）

#volume_size = 1

 

# A reference to existing volume for volume manage. It contains two elements, the first is ref type (like 'source-name', 'source-id’, etc), the second is volume name template used in storage backend (list value)

# 對雲硬盤管理的現有卷的引用。 它包含兩個元素，第一個是ref類型（如'source-name'，'source-id'等），第二個是存儲後端使用的雲硬盤名稱模板

#manage_volume_ref = source-name,volume-%s

 

# A reference to existing snapshot for snapshot manage. It contains two elements, the first is ref type (like 'source-name', 'source-id', etc), the second is snapshot name template used in storage backend (list value)

# 對快照管理的現有快照的引用。 它包含兩個元素，第一個是ref類型（如'source-name'，'source-id'等），第二個是存儲後端使用的快照名稱模板

#manage_snapshot_ref = source-name,_snapshot-%s

 

# Lower version of the test target microversion range. The format is 'X.Y', where 'X' and 'Y' are int values. Tempest selects tests based on the range between min_microversion and max_microversion. If both values are not specified, Tempest avoids tests which require a microversion. Valid values are string with format 'X.Y' or string 'latest' (string value)

# 較低版本的測試目標微變化範圍。格式爲'X.Y'，其中'X'和'Y'爲int值。Tempest根據min_microversion和max_microversion之間的範圍選擇測試。若是未指定這兩個值，Tempest將避免須要微轉換的測試。

有效值爲格式爲「X.Y」的字符串「latest」的字符串。

#min_microversion = <None>

 

# Upper version of the test target microversion range. The format is 'X.Y', where 'X' and 'Y' are int values. Tempest selects tests based on the range between min_microversion and max_microversion. If both values are not specified, Tempest avoids tests which require a microversion. Valid values are string with format 'X.Y' or string 'latest' (string value)

# 測試目標微變化範圍的上限版本。 格式爲'X.Y'，其中'X'和'Y'爲int值。 Tempest根據min_microversion和max_microversion之間的範圍選擇測試。 若是未指定這兩個值，Tempest將避免須要微轉換的測試。 有效值爲格式爲「X.Y」的字符串或「latest」的字符串。

#max_microversion = <None>

 

 

[volume-feature-enabled]

 

#

# From tempest.config

#

 

# Runs Cinder multi-backend test (requires 2 backends) (boolean value) 運行Cinder多後端測試（須要2個後端）

#multi_backend = false

 

# Runs Cinder volumes backup test (boolean value) 運行Cinder卷備份測試

#backup = true

 

# Runs Cinder volume snapshot test (boolean value) 運行Cinder卷快照測試

#snapshot = true

 

# Runs Cinder volume clone test (boolean value) 運行Cinder卷克隆測試

#clone = true

 

# Runs Cinder manage snapshot tests (boolean value) 運行Cinder管理快照測試

#manage_snapshot = false

 

# Runs Cinder manage volume tests (boolean value) 運行Cinder管理批量測試

#manage_volume = false

 

# A list of enabled volume extensions with a special entry all which indicates every extension is enabled. Empty list indicates all extensions are disabled (list value)

# 已啓用的雲硬盤擴展列表，其中包含一個特殊條目，表示每一個擴展都已啓用。 空列表表示禁用全部擴展

#api_extensions = all

 

# DEPRECATED: Is the v2 volume API enabled (boolean value) 禁用：是否容許使用雲硬盤的Api （v2版本）

# This option is deprecated for removal. Its value may be silently ignored in the future. Reason: The v2 volume API has been deprecated since Pike release.Now Tempest run all the volume tests against v2 or v3 API based on CONF.volume.catalog_type which makes this config option unusable. If catalog_type is volumev2, then all the volume tests will run against v2 API. Use ``CONF.volume.catalog_type`` to run the Tempest against volume v2 or v3 API

# 不推薦使用此選項進行刪除。 它的價值可能會在未來被忽視。 緣由：自 Pike 版發佈以來，v2卷API已被棄用。如今，Tempest基於CONF.volume.catalog_type針對v2或v3 API運行全部雲硬盤測試，這使得此配置選項沒法使用。 若是catalog_type是volumev2，則全部雲硬盤測試都將針對v2 API運行。 使用``CONF.volume.catalog_type``對卷v2或v3 API運行Tempest

#api_v2 = true

 

# DEPRECATED: Is the v3 volume API enabled (boolean value) 禁用：是否容許使用雲硬盤的Api （v3版本）

# This option is deprecated for removal. Its value may be silently ignored in the future. Reason: Tempest run all the volume tests against v2 or v3 API based on CONF.volume.catalog_type which makes this config option unusable. If catalog_type is volumev3 which is default, then all the volume tests will run against v3 API. Use ``CONF.volume.catalog_type`` to run the Tempest against volume v2 or v3 API

# 不推薦使用此選項進行刪除。 它的價值可能會在未來被忽視。 緣由：Tempest基於CONF.volume.catalog_type針對v2或v3 API運行全部雲硬盤測試，這使得此配置選項沒法使用。 若是catalog_type是默認的volumev3，則全部雲硬盤測試都將針對v3 API運行。 使用``CONF.volume.catalog_type``對卷v2或v3 API運行Tempest

#api_v3 = true

 

# Does the cloud support extending the size of a volume which is currently attached to a server instance? This depends on the 3.42

volume API microversion and the 2.51 compute API microversion. Also, not all volume or compute backends support this operation. (boolean value)

# 雲是否支持擴展當前鏈接到雲主機服務器的雲硬盤大小？ 這取決於3.42雲硬盤API microversion 和2.51計算API microversion。 此外，並不是全部雲硬盤或計算後端都支持此操做。

#extend_attached_volume = false