#, fuzzy
msgid ""
msgstr ""
"MIME-Version: 1.0\n"
"Content-Transfer-Encoding: 8bit\n"
"Content-Type: text/plain; charset=UTF-8\n"

msgctxt "38eed1188d5fdc88a64b3e038749cc7c"
msgid ".. _tempest-configuration:"
msgstr ""

msgctxt "239ca68ecb0961cc253f0fce961eb844"
msgid "Tempest Configuration Guide"
msgstr ""

msgctxt "4dcf2c829d789f43c9906c270494160c"
msgid "==========================="
msgstr ""

msgctxt "13579cde9cbd4ff82daf435eac4ec17c"
msgid ""
"This guide is a starting point for configuring Tempest. It aims to elaborate"
msgstr ""

msgctxt "395a64b644becbb64be7d8566141c743"
msgid ""
"on and explain some of the mandatory and common configuration settings and "
"how"
msgstr ""

msgctxt "50b406b303522caac1c3f801b4583e16"
msgid ""
"they are used in conjunction. The source of truth on each option is the "
"sample"
msgstr ""

msgctxt "185908ed923cdf5bff657c25f93066e8"
msgid ""
"config file which explains the purpose of each individual option. You can "
"see"
msgstr ""

msgctxt "a43b0a87cbd810478103874ce0ca8492"
msgid "the sample config file here: :ref:`tempest-sampleconf`"
msgstr ""

msgctxt "64c039bcfb5864d85ad21e23ac015ce1"
msgid "Auth/Credentials"
msgstr ""

msgctxt "5308b029d868fe6befab9623287a1d29"
msgid "----------------"
msgstr ""

msgctxt "309cfe75e116abb77c8a91e8cf575b76"
msgid ""
"Tempest currently has two different ways in configuration to provide "
"credentials"
msgstr ""

msgctxt "a0b6d0a7542ae3cd9ff90e7f9257ea20"
msgid ""
"to use when running Tempest. One is a traditional set of configuration "
"options"
msgstr ""

msgctxt "d11c1bcbbbd138aa4eef1bd5ab7a26c2"
msgid ""
"in the tempest.conf file. These options are clearly labelled in the "
"``identity``"
msgstr ""

msgctxt "c955664a3cc88346a15b638f0c0711f4"
msgid ""
"section and let you specify a set of credentials for a regular user, a "
"global"
msgstr ""

msgctxt "16a5468eedd0959c0edcb5b32a78de8d"
msgid ""
"admin user, and an alternate user, consisting of a username, password, and"
msgstr ""

msgctxt "b5b39df10f0d27e3c820a2137355d7f1"
msgid "project/tenant name."
msgstr ""

msgctxt "014d706195cc33bc245f7265a92147c2"
msgid ""
"The other method to provide credentials is using the accounts.yaml file. "
"This"
msgstr ""

msgctxt "50d4f293a5de225fac861a0c33bcfc5c"
msgid ""
"file is used to specify an arbitrary number of users available to run tests"
msgstr ""

msgctxt "313952dbb03237e2fd288df84fe14e94"
msgid ""
"with. You can specify the location of the file in the ``auth`` section in "
"the"
msgstr ""

msgctxt "c3b4ee3cba7bfd56cc6f40bdfd16ff2c"
msgid ""
"tempest.conf file. To see the specific format used in the file please refer "
"to"
msgstr ""

msgctxt "5b772854b0cbe3e22cb32a7afd2027bc"
msgid ""
"the accounts.yaml.sample file included in Tempest.  Eventually the config"
msgstr ""

msgctxt "9912531226e0c947fb20906b19c6a1a4"
msgid ""
"options for providing credentials to Tempest will be deprecated and removed "
"in"
msgstr ""

msgctxt "6969bc689d186f00eb1d48b74faf0b0e"
msgid "favor of the accounts.yaml file."
msgstr ""

msgctxt "fdb87e18f31d4d702e4d13b49be0782e"
msgid "Keystone Connection Info"
msgstr ""

msgctxt "55e5c511c0d3ae21760571e063123d3a"
msgid "^^^^^^^^^^^^^^^^^^^^^^^^"
msgstr ""

msgctxt "56a9582fb31353d4347994e457f8fd0e"
msgid ""
"In order for Tempest to be able to talk to your OpenStack deployment you "
"need"
msgstr ""

msgctxt "a8c33c6c8e368ed640e226f902199afa"
msgid ""
"to provide it with information about how it communicates with keystone."
msgstr ""

msgctxt "6306b7713f8c062d6ab78796adb67f35"
msgid ""
"This involves configuring the following options in the ``identity`` section:"
msgstr ""

msgctxt "266f878fb93a9b9d726f31127588cbf3"
msgid " #. ``auth_version``"
msgstr ""

msgctxt "389e990710f6bbf960eed83941a54609"
msgid " #. ``uri``"
msgstr ""

msgctxt "c3af410a087f5ea7c5185654edbda48b"
msgid " #. ``uri_v3``"
msgstr ""

msgctxt "7f7d512e7dbe565533dc9a4c21bf872a"
msgid ""
"The ``auth_version`` option is used to tell Tempest whether it should be "
"using"
msgstr ""

msgctxt "4bcb185e686ee2598e8de0045d043c22"
msgid ""
"keystone's v2 or v3 api for communicating with keystone. (except for the"
msgstr ""

msgctxt "664f8eb2e22c856c4c7e5bc0a59dc2d0"
msgid ""
"identity api tests which will test a specific version) The two uri options "
"are"
msgstr ""

msgctxt "ce166679212be97c4a4ea2d20b350be0"
msgid ""
"used to tell Tempest the url of the keystone endpoint. The ``uri`` option is"
msgstr ""

msgctxt "66d4e298de2f3a7ba2d313a6b5eb2eec"
msgid ""
"used for keystone v2 request and ``uri_v3`` is used for keystone v3. You "
"want to"
msgstr ""

msgctxt "6b3823edf7d15065b38f9ce394530ff5"
msgid ""
"ensure that which ever version you set for ``auth_version`` has its uri "
"option"
msgstr ""

msgctxt "f808beab327d8a3fa24160a540453c0b"
msgid "defined."
msgstr ""

msgctxt "d0adbbda2c3f98ad746847bf7da6df66"
msgid "Credential Provider Mechanisms"
msgstr ""

msgctxt "e6e3d1fdd3153d78be4901a45288bba6"
msgid "^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^"
msgstr ""

msgctxt "0ad268ebd3414141673abeab52450d30"
msgid ""
"Tempest currently also has three different internal methods for providing"
msgstr ""

msgctxt "af9a68b038e353477782b4b34f057c57"
msgid ""
"authentication to tests: dynamic credentials, locking test accounts, and"
msgstr ""

msgctxt "2c559dbb4b55ee498ac4c68f97b1e526"
msgid ""
"non-locking test accounts. Depending on which one is in use the "
"configuration"
msgstr ""

msgctxt "e3469be868f668bf822682c3c574edfb"
msgid "of Tempest is slightly different."
msgstr ""

msgctxt "cc879e3647d0765b68b97b5bc1c5bf1c"
msgid "Dynamic Credentials"
msgstr ""

msgctxt "4a5f95f4846e5a7a60fd709839efca11"
msgid "\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\""
msgstr ""

msgctxt "88e42099eecfd8991a3263fe4034e5d4"
msgid ""
"Dynamic Credentials (formerly known as Tenant isolation) was originally "
"created"
msgstr ""

msgctxt "41f13869376e6b33ef0ee98019d39046"
msgid ""
"to enable running Tempest in parallel.  For each test class it creates a "
"unique"
msgstr ""

msgctxt "7c18726397bd1636d79eb03175bd45d1"
msgid ""
"set of user credentials to use for the tests in the class. It can create up "
"to"
msgstr ""

msgctxt "d93616967900cecfa02c13cc5abb0cb5"
msgid ""
"three sets of username, password, and tenant/project names for a primary "
"user,"
msgstr ""

msgctxt "3594ef4d116621e073d55b7c4e828b91"
msgid ""
"an admin user, and an alternate user.  To enable and use dynamic credentials "
"you"
msgstr ""

msgctxt "ba5ce0be20fd0bba8062c0273c3c5ef2"
msgid "only need to configure two things:"
msgstr ""

msgctxt "8bf859c7024f5a0f9af7400090bac82b"
msgid " #. A set of admin credentials with permissions to create users and"
msgstr ""

msgctxt "e749fe51cba8388e3f3647d71e19f69b"
msgid ""
"    tenants/projects. This is specified in the ``auth`` section with the"
msgstr ""

msgctxt "eb6169046d99e58e58d3fd8203b9538b"
msgid ""
"    ``admin_username``, ``admin_tenant_name``, ``admin_domain_name`` and"
msgstr ""

msgctxt "0af1ec09b2225a000eb7fefebef6fb81"
msgid "    ``admin_password`` options"
msgstr ""

msgctxt "64b9497512d55555229ab3171676f2eb"
msgid " #. To enable dynamic credentials in the ``auth`` section with the"
msgstr ""

msgctxt "64d9b3a80f77a60941a77506f6e016e9"
msgid "    ``use_dynamic_credentials`` option."
msgstr ""

msgctxt "c40c8ae3d6a4163c930fb247bea3ee3d"
msgid ""
"This is also currently the default credential provider enabled by Tempest, "
"due"
msgstr ""

msgctxt "ceb7a1f0596417b221f52e395ef44fa9"
msgid "to its common use and ease of configuration."
msgstr ""

msgctxt "a9954ed6f960ca312ba970670eb72bc7"
msgid ""
"It is worth pointing out that depending on your cloud configuration you "
"might"
msgstr ""

msgctxt "ff3c07d9679044b995b7a03d69e5a58a"
msgid ""
"need to assign a role to each of the users created by Tempest's dynamic"
msgstr ""

msgctxt "dfe1c9b9f84014898391e0fe4fbb36c9"
msgid ""
"credentials.  This can be set using the ``tempest_roles`` option. It takes "
"in a"
msgstr ""

msgctxt "abd785235250ddc0dab0a2cc7258d291"
msgid ""
"list of role names each of which will be assigned to each of the users "
"created"
msgstr ""

msgctxt "54d72463f69cf16b5812423e6ad08ed7"
msgid ""
"by dynamic credentials. This option will not have any effect when Tempest is "
"not"
msgstr ""

msgctxt "79296f120d86ed2f3551fcd63a7d0af8"
msgid "configured to use dynamic credentials."
msgstr ""

msgctxt "9d48bc0b2b7895de991adc7991011b70"
msgid "Pre-Provisioned Credentials (aka accounts.yaml or accounts file)"
msgstr ""

msgctxt "76196c064822f0b7b13a1d5d2cb790cb"
msgid "\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\""
msgstr ""

msgctxt "1f25da84c63bc4700215a09e1eb5e775"
msgid ""
"For a long time using dynamic credentials was the only method available if "
"you"
msgstr ""

msgctxt "fc2cd6e6080138413f9f8a810cf62d50"
msgid ""
"wanted to enable parallel execution of Tempest tests. However, this was"
msgstr ""

msgctxt "61f1b22f172dddec2b94b505ced1d1ff"
msgid ""
"insufficient for certain use cases because of the admin credentials "
"requirement"
msgstr ""

msgctxt "4f960e4f06f346b6ee7be6ea8fcf52e7"
msgid ""
"to create the credential sets on demand. To get around that the accounts."
"yaml"
msgstr ""

msgctxt "0cbbb80fa57fc473f8155d27e59028bf"
msgid ""
"file was introduced and with that a new internal credential provider to "
"enable"
msgstr ""

msgctxt "72d5e99d7ae82261a05db41b5c9383c2"
msgid ""
"using the list of credentials instead of creating them on demand. With "
"locking"
msgstr ""

msgctxt "df091bec4efc1dd4919fa14c764a4ecc"
msgid ""
"test accounts each test class will reserve a set of credentials from the"
msgstr ""

msgctxt "8aca8a84a8bebf43aec42b7c7228ff50"
msgid ""
"accounts.yaml before executing any of its tests so that each class is "
"isolated"
msgstr ""

msgctxt "a9d6548541a3441f37b2b31ec95c0177"
msgid "like with dynamic credentials."
msgstr ""

msgctxt "fe34c53dae0b485fb2b19a4d0d0029a4"
msgid "To enable and use locking test accounts you need do a few things:"
msgstr ""

msgctxt "7b4ff909960545028d33560952a6841c"
msgid ""
" #. Create an accounts.yaml file which contains the set of pre-existing"
msgstr ""

msgctxt "191d40797a3851ba448bcfcb9bbafd60"
msgid ""
"    credentials to use for testing. To make sure you don't have a "
"credentials"
msgstr ""

msgctxt "5bdce73a3b5ede2d3cb26a5c9cf2cb2f"
msgid ""
"    starvation issue when running in parallel make sure you have at least "
"two"
msgstr ""

msgctxt "4ec316ccccdf9f2bde1a06d4114d2c9c"
msgid ""
"    times the number of worker processes you are using to execute Tempest"
msgstr ""

msgctxt "f2ea79f89472b4cac23ac99852eb1958"
msgid ""
"    available in the file. (If running serially the worker count is 1.)"
msgstr ""

msgctxt "d44ccb062f7daba4a1a1464e7fb90ecf"
msgid ""
"    You can check the accounts.yaml.sample file packaged in Tempest for the "
"yaml"
msgstr ""

msgctxt "23466484fb4629fc3c23d743fd2a376b"
msgid "    format."
msgstr ""

msgctxt "83684121d34edafb5ac9d6575dc39852"
msgid ""
" #. Provide Tempest with the location of your accounts.yaml file with the"
msgstr ""

msgctxt "81bc0770675a0645c61fdf86b9a0faa5"
msgid "    ``test_accounts_file`` option in the ``auth`` section"
msgstr ""

msgctxt "5b1b6d0971afdc8549e3eebea215a33a"
msgid ""
"    *NOTE: Be sure to use a full path for the file; otherwise Tempest will"
msgstr ""

msgctxt "1fff0f36804d34b62974c013020099f1"
msgid "    likely not find it.*"
msgstr ""

msgctxt "746dc023f8a1cf23539909c33bbd63e9"
msgid " #. Set ``use_dynamic_credentials = False`` in the ``auth`` group"
msgstr ""

msgctxt "fc30b8c1dfc5f32b8d53c49b8387727c"
msgid ""
"It is worth pointing out that each set of credentials in the accounts.yaml"
msgstr ""

msgctxt "8e68e61942758791d92822ef46d8bf66"
msgid ""
"should have a unique tenant. This is required to provide proper isolation"
msgstr ""

msgctxt "29905671113c9db3d9e928474876d259"
msgid ""
"to the tests using the credentials, and failure to do this will likely cause"
msgstr ""

msgctxt "a8644ccbc367dc42f84dde884ea04281"
msgid "unexpected failures in some tests."
msgstr ""

msgctxt "367125007fdbbacdc1911cbdde89555c"
msgid "Legacy Credentials (aka credentials config options)"
msgstr ""

msgctxt "e437f5916673cb7ba3335618b932f193"
msgid "\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\""
msgstr ""

msgctxt "e4db60a7a9c49a262feb457c571763e3"
msgid ""
"**Starting in the Liberty release this mechanism was deprecated; it will be"
msgstr ""

msgctxt "99cf8d0382f4faa9413a47058199ccb7"
msgid "removed in a future release.**"
msgstr ""

msgctxt "9c4953347c7f7f4668027ed7566b8278"
msgid ""
"When Tempest was refactored to allow for locking test accounts, the original"
msgstr ""

msgctxt "3966ea09f39db0e20bb9cf92a4f13fb2"
msgid ""
"non-tenant isolated case was converted to internally work similarly to the"
msgstr ""

msgctxt "49ae87f4ab421dac193514aad937a02f"
msgid ""
"accounts.yaml file. This mechanism was then called the legacy test accounts"
msgstr ""

msgctxt "f2be458b1367372653d572b69ae8944c"
msgid ""
"provider. To use the legacy test accounts provider you can specify the sets "
"of"
msgstr ""

msgctxt "828441d975b8a8b921b52441b0e38c60"
msgid ""
"credentials in the configuration file as detailed above with following nine"
msgstr ""

msgctxt "74204183bc9371551cae22bd175e9971"
msgid "options in the ``identity`` section:"
msgstr ""

msgctxt "70960630e9083fd6d485c0203462e789"
msgid " #. ``username``"
msgstr ""

msgctxt "a65c2b1f4b974a8bdf0faf13216af804"
msgid " #. ``password``"
msgstr ""

msgctxt "3524e82783c73385b5cd4b8a45ac4416"
msgid " #. ``tenant_name``"
msgstr ""

msgctxt "6f9f4559c1d4d8f9d067e787473cc0ba"
msgid " #. ``admin_username``"
msgstr ""

msgctxt "7f4e5b10962191b46421929f2d0bf168"
msgid " #. ``admin_password``"
msgstr ""

msgctxt "35cb7ef1b34e4bd695081cb22192b006"
msgid " #. ``admin_tenant_name``"
msgstr ""

msgctxt "0c87da40e525e0da1dfb25e1e4ab43cc"
msgid " #. ``alt_username``"
msgstr ""

msgctxt "6f19e935e2d0ed317620578fe8b5ea72"
msgid " #. ``alt_password``"
msgstr ""

msgctxt "802235c02526d02286a4bd3dd5c100ff"
msgid " #. ``alt_tenant_name``"
msgstr ""

msgctxt "eedeb648f662e151e551b7a3b521a8cf"
msgid "If using Identity API v3, use the ``domain_name`` option to specify a"
msgstr ""

msgctxt "fffcbe538f1866cc1c9167d336ded2dd"
msgid "domain other than the default domain.  The ``auth_version`` setting is"
msgstr ""

msgctxt "2b585d05d5bf168b93ddffe32307a0fc"
msgid ""
"used to switch between v2 (``v2``) or v3 (``v3``) versions of the Identity"
msgstr ""

msgctxt "273df5ff8d9ee497e8e3cad7d948787c"
msgid "API."
msgstr ""

msgctxt "76c1d772202425c313355c7663eb20b3"
msgid "And in the ``auth`` section:"
msgstr ""

msgctxt "6264b58d2f27f83f23510326868f5d61"
msgid " #. ``use_dynamic_credentials = False``"
msgstr ""

msgctxt "92c02d3e4b5bc9e8cc8003af95614543"
msgid " #. Comment out ``test_accounts_file`` or keep it empty."
msgstr ""

msgctxt "aea91cd721b33b71a67f6370ba0fdb6b"
msgid ""
"It only makes sense to use this if parallel execution isn't needed, since"
msgstr ""

msgctxt "2b39cfcc840aeef6af7fa21f5e49b746"
msgid ""
"Tempest won't be able to properly isolate tests using this. Additionally, "
"using"
msgstr ""

msgctxt "6e7b1987d1e381bb4e5271250d30e20e"
msgid "the traditional config options for credentials is not able to provide"
msgstr ""

msgctxt "e61ade626b9e29bc2ae553f6cf73afc8"
msgid ""
"credentials to tests requiring specific roles on accounts. This is because "
"the"
msgstr ""

msgctxt "be318eed3e78e0523a1276523fd1dd9c"
msgid ""
"config options do not give sufficient flexibility to describe the roles "
"assigned"
msgstr ""

msgctxt "66a711383a3e10d0dfc02515360d5e46"
msgid ""
"to a user for running the tests. There are additional limitations with "
"regard to"
msgstr ""

msgctxt "7d373c22c60ee8c29c9ed5b481764947"
msgid ""
"network configuration when using this credential provider mechanism - see "
"the"
msgstr ""

msgctxt "14ee1a9f6fcd1a55fe968c23e84778fd"
msgid "`Networking`_ section below."
msgstr ""

msgctxt "a623a8d0366bf079411aa30be45b2d10"
msgid "Compute"
msgstr ""

msgctxt "1f686eebbbe0a41c94b938e7114cf2c3"
msgid "-------"
msgstr ""

msgctxt "ae68068bee8d0538805f47429367bc7e"
msgid "Flavors"
msgstr ""

msgctxt "a72a8c9030eeee4587ca75cc40362d68"
msgid "^^^^^^^"
msgstr ""

msgctxt "5f3cae50de75c47a92ee69bc1add9b70"
msgid ""
"For Tempest to be able to create servers you need to specify flavors that it"
msgstr ""

msgctxt "a7cfe7fd8f3835b838f2a45588d3c859"
msgid ""
"can use to boot the servers with. There are two options in the Tempest "
"config"
msgstr ""

msgctxt "17bfaf3ceb55f0e4f64af0afb1d00a53"
msgid "for doing this:"
msgstr ""

msgctxt "900976c0334fcacf2d0253de8a58a508"
msgid " #. ``flavor_ref``"
msgstr ""

msgctxt "14cef326308faab23fe799008cf0d8c9"
msgid " #. ``flavor_ref_alt``"
msgstr ""

msgctxt "5d76596263353cda5821658a866d8019"
msgid ""
"Both of these options are in the ``compute`` section of the config file and "
"take"
msgstr ""

msgctxt "35b5623480f32c63ca0fffda5091106a"
msgid ""
"in the flavor id (not the name) from nova. The ``flavor_ref`` option is what"
msgstr ""

msgctxt "a86d7f2a01c902a679bc213eb3aadd0b"
msgid ""
"will be used for booting almost all of the guests; ``flavor_ref_alt`` is "
"only"
msgstr ""

msgctxt "967d728e0963633af9dfeb27fa07a448"
msgid ""
"used in tests where two different-sized servers are required (for example, a"
msgstr ""

msgctxt "a5e784fc9c324bc58dcc1121a71d6ce6"
msgid "resize test)."
msgstr ""

msgctxt "060c34621297c6c1726d439354353ace"
msgid ""
"Using a smaller flavor is generally recommended. When larger flavors are "
"used,"
msgstr ""

msgctxt "df9ef5d7cf8a02b4253d9703b8fb3ca2"
msgid ""
"the extra time required to bring up servers will likely affect total run "
"time"
msgstr ""

msgctxt "911f570c10fa589e66deb35df08d2917"
msgid ""
"and probably require tweaking timeout values to ensure tests have ample time "
"to"
msgstr ""

msgctxt "5d1b14bac6839e076314df7b314abf6a"
msgid "finish."
msgstr ""

msgctxt "fff0d600f8a0b5e19e88bfb821dd1157"
msgid "Images"
msgstr ""

msgctxt "f1b45722f0a47fb6dad92e9238e8fb91"
msgid "^^^^^^"
msgstr ""

msgctxt "01d82964f5e1d2ef48608cf2b27c1ca5"
msgid ""
"Just like with flavors, Tempest needs to know which images to use for "
"booting"
msgstr ""

msgctxt "b4a923a0d2ecd760678b9b4468b2ef2c"
msgid ""
"servers. There are two options in the compute section just like with flavors:"
""
msgstr ""

msgctxt "81b6fa4ebf7b0623b45dd801c974f08f"
msgid " #. ``image_ref``"
msgstr ""

msgctxt "196bf2a48e49f343c4104fda7d14ec42"
msgid " #. ``image_ref_alt``"
msgstr ""

msgctxt "9506ae301bbf9c1beb8c7f67ffeebd9e"
msgid ""
"Both options are expecting an image id (not name) from nova. The "
"``image_ref``"
msgstr ""

msgctxt "997b5ff6a8170ffb9b5bca9ab28219b0"
msgid ""
"option is what will be used for booting the majority of servers in Tempest."
msgstr ""

msgctxt "3be402792dee7aa3332dd1ccc9e6ad8c"
msgid ""
"``image_ref_alt`` is used for tests that require two images such as rebuild. "
"If"
msgstr ""

msgctxt "3fdb52831ab5450981453bf19bbb7a21"
msgid ""
"two images are not available you can set both options to the same image id "
"and"
msgstr ""

msgctxt "8e305ed955539fd429736eebd608a07a"
msgid "those tests will be skipped."
msgstr ""

msgctxt "b3d999293bee22535fe6a427979037af"
msgid "There are also options in the ``scenario`` section for images:"
msgstr ""

msgctxt "6a6b7e23d3c90ff575ec04dc262759db"
msgid " #. ``img_file``"
msgstr ""

msgctxt "928bfcaab8911d8d573e5dede3010549"
msgid " #. ``img_dir``"
msgstr ""

msgctxt "fdd1d01e23c1c6ed3e0c04355d431d3c"
msgid " #. ``aki_img_file``"
msgstr ""

msgctxt "7a5158aaf906af891fe72f80ca0ff9f0"
msgid " #. ``ari_img_file``"
msgstr ""

msgctxt "0ac269b2a9dbcbae8a38ecf3967d6da1"
msgid " #. ``ami_img_file``"
msgstr ""

msgctxt "f850a45a5d95c21af6a35874da92c863"
msgid " #. ``img_container_format``"
msgstr ""

msgctxt "e1193fd6190a2f49aece23785ae14bb9"
msgid " #. ``img_disk_format``"
msgstr ""

msgctxt "82ec6ee56783c6a8c54b751a12031c67"
msgid ""
"However, unlike the other image options, these are used for a very small "
"subset"
msgstr ""

msgctxt "1260a1e38066eea15f39b82574ca7ae4"
msgid ""
"of scenario tests which are uploading an image. These options are used to "
"tell"
msgstr ""

msgctxt "3477b3e111b47d541f3eb507102e08e1"
msgid ""
"Tempest where an image file is located and describe its metadata for when it "
"is"
msgstr ""

msgctxt "26db2bb4924dd837c998136d41006a5d"
msgid "uploaded."
msgstr ""

msgctxt "3907a76908eca75dc4c8cde5d69f7299"
msgid ""
"The behavior of these options is a bit convoluted (which will likely be "
"fixed in"
msgstr ""

msgctxt "4132c9c4da5c8b830b0aff3ea835f7e1"
msgid ""
"future versions). You first need to specify ``img_dir``, which is the "
"directory"
msgstr ""

msgctxt "38e5e56fed2d5ce4c4ee287aeab222cf"
msgid ""
"in which Tempest will look for the image files. First it will check if the"
msgstr ""

msgctxt "6a82a78ffcb5567f20d102e5e89628e2"
msgid ""
"filename set for ``img_file`` could be found in ``img_dir``. If it is found "
"then"
msgstr ""

msgctxt "d2a6f1dda504798bce63e7108ab46566"
msgid ""
"the ``img_container_format`` and ``img_disk_format`` options are used to "
"upload"
msgstr ""

msgctxt "49ee2fb96528b6882c74bb18ab0e2ffc"
msgid ""
"that image to glance. However, if it is not found, Tempest will look for the"
msgstr ""

msgctxt "63a16d3d79217f753e493130a0b86139"
msgid ""
"three uec image file name options as a fallback. If neither is found, the "
"tests"
msgstr ""

msgctxt "97282112b5b3eab454c2d623685cab1a"
msgid "requiring an image to upload will fail."
msgstr ""

msgctxt "e43e74608235c42cb6c14b62839b6019"
msgid ""
"It is worth pointing out that using `cirros`_ is a very good choice for "
"running"
msgstr ""

msgctxt "0fd3ccdb85e6f51de168d44e7400b3d9"
msgid ""
"Tempest. It's what is used for upstream testing, they boot quickly and have "
"a"
msgstr ""

msgctxt "13de346a333b7306cac4ce1a2a3ecd3c"
msgid "small footprint."
msgstr ""

msgctxt "7107f2c58282b53a18d205154c0792d3"
msgid ".. _cirros: https://launchpad.net/cirros"
msgstr ""

msgctxt "a5fa5746370b608090b994a97b49e98b"
msgid "Networking"
msgstr ""

msgctxt "01a6651a94ab602dbfc47587d234b52c"
msgid "----------"
msgstr ""

msgctxt "acc4762634766272ab4050b084e9980b"
msgid ""
"OpenStack has a myriad of different networking configurations possible and"
msgstr ""

msgctxt "f7ab9aea4f176b28ec0adfa3463d4c8e"
msgid ""
"depending on which of the two network backends, nova-network or neutron, you "
"are"
msgstr ""

msgctxt "8bcd295c15b5394a51b7314b21f75f91"
msgid ""
"using things can vary drastically. Due to this complexity Tempest has to "
"provide"
msgstr ""

msgctxt "ea6f4f75fd61b9c668054f38598e0ead"
msgid ""
"a certain level of flexibility in its configuration to ensure it will work"
msgstr ""

msgctxt "409fc26bacb5a7d24ae5a1585eb92732"
msgid ""
"against any cloud. This ends up causing a large number of permutations in"
msgstr ""

msgctxt "9035d7c80e02c5d2d52f5df341293c3d"
msgid "Tempest's config around network configuration."
msgstr ""

msgctxt "a8bdaa65f5b641657670836fd65e2a7e"
msgid "Enabling Remote Access to Created Servers"
msgstr ""

msgctxt "e101aea560bef649bdae71e8f06ea6f8"
msgid "^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^"
msgstr ""

msgctxt "2417044aa51d6a6266c801bab527a687"
msgid ""
"When Tempest creates servers for testing, some tests require being able to"
msgstr ""

msgctxt "f0b8ef4d642634a9b60b787f7ab09d92"
msgid ""
"connect those servers. Depending on the configuration of the cloud, the "
"methods"
msgstr ""

msgctxt "f61340296cbf823b7a978ff952d2208f"
msgid ""
"for doing this can be different. In certain configurations it is required to"
msgstr ""

msgctxt "6b0ea7f00cde36c44fea438f2008ff74"
msgid ""
"specify a single network with server create calls. Accordingly, Tempest "
"provides"
msgstr ""

msgctxt "bc3f92276f68769dce902f2c744bf514"
msgid ""
"a few different methods for providing this information in configuration to "
"try"
msgstr ""

msgctxt "fe6a104eb30dced0b320dc79df6bcb73"
msgid ""
"and ensure that regardless of the cloud's configuration it'll still be able "
"to"
msgstr ""

msgctxt "ec99549d006d672326fef87f6a3a6f6c"
msgid ""
"run. This section covers the different methods of configuring Tempest to "
"provide"
msgstr ""

msgctxt "f39c71b22c5f8549a8d1537403d6eedf"
msgid "a network when creating servers."
msgstr ""

msgctxt "dfed1b0279da64127a0ad9af113f7cc7"
msgid "Fixed Network Name"
msgstr ""

msgctxt "34d7d46b36fd098aff1f2d855713da6f"
msgid "\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\""
msgstr ""

msgctxt "72088ec92cf5f6c2c0104fc191b0b109"
msgid ""
"This is the simplest method of specifying how networks should be used. You "
"can"
msgstr ""

msgctxt "4c532438439c515e7a1db760d153cdee"
msgid ""
"just specify a single network name/label to use for all server creations. "
"The"
msgstr ""

msgctxt "63239a808985ffab882c10b7237eb5db"
msgid ""
"limitation with this is that all tenants/projects and users must be able to "
"see"
msgstr ""

msgctxt "68f52eb26eea3a0d763a557dadc38e5c"
msgid ""
"that network name/label if they are to perform a network list and be able to "
"use"
msgstr ""

msgctxt "1d9e348141a4a084c649ca616877f279"
msgid "it."
msgstr ""

msgctxt "cc353d286b0c00a0d91414e0c15a104a"
msgid ""
"If no network name is assigned in the config file and none of the below"
msgstr ""

msgctxt "2cf04d4180c45bc39fcceef29321d233"
msgid ""
"alternatives are used, then Tempest will not specify a network on server"
msgstr ""

msgctxt "47d1f778d0805300dd1b7f1b2d5e920b"
msgid ""
"creations, which depending on the cloud configuration might prevent them "
"from"
msgstr ""

msgctxt "7f8fb9de9cc1115f85822847adbde293"
msgid "booting."
msgstr ""

msgctxt "7d10124b99957c64fc2b7aeaa50b13f1"
msgid "To set a fixed network name simply:"
msgstr ""

msgctxt "5719b9c016eca9f5c03b50b03c4245cb"
msgid " #. Set the ``fixed_network_name`` option in the ``compute`` group"
msgstr ""

msgctxt "209b0b3d1b799c4d7ab0449b2ceaedc5"
msgid ""
"In the case that the configured fixed network name can not be found by a "
"user"
msgstr ""

msgctxt "cadf635627e533a1d281a84d3f19e849"
msgid ""
"network list call, it will be treated like one was not provided except that "
"a"
msgstr ""

msgctxt "fdfa316db99cf3f1777dadca905e8c64"
msgid "warning will be logged stating that it couldn't be found."
msgstr ""

msgctxt "08254e53c0bc9f5d7e7204282e7903b4"
msgid "Accounts File"
msgstr ""

msgctxt "0bc5611e3d1342256e16de62b738e9a3"
msgid "\"\"\"\"\"\"\"\"\"\"\"\"\""
msgstr ""

msgctxt "abc975f83c87db1d287eb7ee2bd9c5b2"
msgid ""
"If you are using an accounts file to provide credentials for running Tempest"
msgstr ""

msgctxt "ed45ca1da8cb4bf1e1d56820c4f13e77"
msgid ""
"then you can leverage it to also specify which network should be used with"
msgstr ""

msgctxt "ebfdb596b14d835f247a2cdbdfa2edbb"
msgid ""
"server creations on a per tenant/project and user pair basis. This provides"
msgstr ""

msgctxt "4ad670e4984c137b5a41c113f1beb797"
msgid ""
"the necessary flexibility to work with more intricate networking "
"configurations"
msgstr ""

msgctxt "d423b3a70722e0337e77369c0cdedb54"
msgid "by enabling the user to specify exactly which network to use for which"
msgstr ""

msgctxt "16c4c90b374d53b0c8aee53fe571ce06"
msgid ""
"tenants/projects. You can refer to the accounts.yaml.sample file included in"
msgstr ""

msgctxt "c47bf6d130a3eb8b168a6bc994cb9052"
msgid ""
"the Tempest repo for the syntax around specifying networks in the file."
msgstr ""

msgctxt "a6d135171f5a9d8fef1e442349188cb9"
msgid ""
"However, specifying a network is not required when using an accounts file. "
"If"
msgstr ""

msgctxt "7ec137fd83cd3e50aaa3189844b378a9"
msgid ""
"one is not specified you can use a fixed network name to specify the network "
"to"
msgstr ""

msgctxt "e114db8e71f13feafeba3bf2fdedee27"
msgid ""
"use when creating servers just as without an accounts file. However, any "
"network"
msgstr ""

msgctxt "996b042850aa61bea0a23411d38fff0e"
msgid ""
"specified in the accounts file will take precedence over the fixed network "
"name"
msgstr ""

msgctxt "9c0c62d3783f514955d817c84573da77"
msgid ""
"provided. If no network is provided in the accounts file and a fixed network"
msgstr ""

msgctxt "e24b706af6472563b85899df305f9f46"
msgid ""
"name is not set then no network will be included in create server requests."
msgstr ""

msgctxt "4d0633528c7f1442697f1af09b298186"
msgid ""
"If a fixed network is provided and the accounts.yaml file also contains "
"networks"
msgstr ""

msgctxt "dbf445e5b77b286585a0a1182c0badce"
msgid ""
"this has the benefit of enabling a couple more tests which require a static"
msgstr ""

msgctxt "1e5663769fb08f01793ea182a585d9f8"
msgid ""
"network to perform operations like server lists with a network filter. If a"
msgstr ""

msgctxt "aed90bf58637709836f41bac288344ae"
msgid ""
"fixed network name is not provided these tests are skipped. Additionally, if "
"a"
msgstr ""

msgctxt "45839a3f886fff50dd88f0260624e143"
msgid ""
"fixed network name is provided it will serve as a fallback in case of a"
msgstr ""

msgctxt "ca80bd06e090030d94c9769df41e56d1"
msgid "misconfiguration or a missing network in the accounts file."
msgstr ""

msgctxt "10ba9c405b04f90b56a72d9f675e24b3"
msgid "With Dynamic Credentials"
msgstr ""

msgctxt "704fd3b8013d7539bb2842b34fbda5e0"
msgid "\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\""
msgstr ""

msgctxt "2bbf4a59df1050a95f0bc70f1c7fee97"
msgid ""
"With dynamic credentials enabled and using nova-network, your only option "
"for"
msgstr ""

msgctxt "1c1c6e6d61f647ea267b9ae5bb1fbba3"
msgid ""
"configuration is to either set a fixed network name or not.  However, in "
"most"
msgstr ""

msgctxt "9ffc9b7cc16c1c808c5df96ac80e7b95"
msgid ""
"cases it shouldn't matter because nova-network should have no problem "
"booting a"
msgstr ""

msgctxt "9d3c050d28c4a06b6789850b9c2ccdf6"
msgid ""
"server with multiple networks. If this is not the case for your cloud then "
"using"
msgstr ""

msgctxt "7b96de3e33b5ac6b684c162e257ddc49"
msgid ""
"an accounts file is recommended because it provides the necessary "
"flexibility to"
msgstr ""

msgctxt "4303dd0a2f9140867afd8db5c331fbbe"
msgid ""
"describe your configuration. Dynamic credentials is not able to dynamically"
msgstr ""

msgctxt "35306d80570a9d55ca6006964c64db23"
msgid "allocate things as necessary if neutron is not enabled."
msgstr ""

msgctxt "3d04cb8bd9090ca38fd3563e570826c5"
msgid ""
"With neutron and dynamic credentials enabled there should not be any "
"additional"
msgstr ""

msgctxt "99451a6dd1e678f894b0ff58b572b039"
msgid ""
"configuration necessary to enable Tempest to create servers with working"
msgstr ""

msgctxt "4d295c07a63729b23f876537b8cb2cfa"
msgid ""
"networking, assuming you have properly configured the ``network`` section to"
msgstr ""

msgctxt "48afc6ff76f005cb57a1d90d37db183c"
msgid ""
"work for your cloud. Tempest will dynamically create the neutron resources"
msgstr ""

msgctxt "09c9b12eb6278a814ef17c8573634aa0"
msgid ""
"necessary to enable using servers with that network. Also, just as with the"
msgstr ""

msgctxt "24b5254ff02c3fb8efb54caded96a1b9"
msgid ""
"accounts file, if you specify a fixed network name while using neutron and"
msgstr ""

msgctxt "ae6a3e237c7ea654bb0835a83f60f81c"
msgid ""
"dynamic credentials it will enable running tests which require a static "
"network"
msgstr ""

msgctxt "806860ec067739177adfb8da5b3eb4af"
msgid ""
"and it will additionally be used as a fallback for server creation. However,"
msgstr ""

msgctxt "615475ced90b59463b73648e1ff3c1e1"
msgid "unlike accounts.yaml this should never be triggered."
msgstr ""

msgctxt "f202d281a7bbb92a9534034c9d9b3733"
msgid ""
"However, there is an option ``create_isolated_networks`` to disable dynamic"
msgstr ""

msgctxt "4f738c03573f0c4230b57c52584e9d04"
msgid ""
"credentials's automatic provisioning of network resources. If this option is "
"set"
msgstr ""

msgctxt "5f9645821529d938e8eac291e1300b70"
msgid ""
"to False you will have to either rely on there only being a single/default"
msgstr ""

msgctxt "cff965b72acf2d7a6487d02703f9503b"
msgid ""
"network available for the server creation, or use ``fixed_network_name`` to"
msgstr ""

msgctxt "1c97167737f61b9ae11f14535a6131d9"
msgid "inform Tempest which network to use."
msgstr ""

msgctxt "b0472faeb62f3c8a3179ab101893a295"
msgid "Configuring Available Services"
msgstr ""

msgctxt "34e8da3d228b4a8529b8fa1819b88f68"
msgid "------------------------------"
msgstr ""

msgctxt "4b16d806a85e1117f7120b901a399125"
msgid ""
"OpenStack is really a constellation of several different projects which"
msgstr ""

msgctxt "658e038a8620ce05ca94e7a2d0939bcc"
msgid ""
"are running together to create a cloud. However which projects you're "
"running"
msgstr ""

msgctxt "8e094eb33388e3541a68612a91d8959e"
msgid ""
"is not set in stone, and which services are running is up to the deployer."
msgstr ""

msgctxt "40c08f1c002facbf4c3e447dd3831438"
msgid ""
"Tempest however needs to know which services are available so it can figure"
msgstr ""

msgctxt "0c9b15e1a7bba33af6a12975a506abdc"
msgid ""
"out which tests it is able to run and certain setup steps which differ based"
msgstr ""

msgctxt "9206f269b95434d3a16a27bf0c42dcd5"
msgid "on the available services."
msgstr ""

msgctxt "99106d63fb395e46581386cb77dc50e3"
msgid ""
"The ``service_available`` section of the config file is used to set which"
msgstr ""

msgctxt "4689ecbc2dd3c70bfb9c7419ed8dfbf7"
msgid ""
"services are available. It contains a boolean option for each service "
"(except"
msgstr ""

msgctxt "83ed5f8be26b4dc8c84712066635c6a2"
msgid ""
"for keystone which is a hard requirement) set it to True if the service is"
msgstr ""

msgctxt "d408869f99b08234ff603024c438fb44"
msgid "available or False if it is not."
msgstr ""

msgctxt "0bcfa28115476b2bcfed146f27c465c4"
msgid "Service Catalog"
msgstr ""

msgctxt "e39db447f3b6794202bab69948413ec4"
msgid "^^^^^^^^^^^^^^^"
msgstr ""

msgctxt "eea66b63d9959170b30ef117201203bb"
msgid ""
"Each project which has its own REST API contains an entry in the service"
msgstr ""

msgctxt "d3e574fa35ca4b97f38d05b6c14b5aff"
msgid ""
"catalog. Like most things in OpenStack this is also completely configurable."
msgstr ""

msgctxt "98556c1852430bf153d7dd6277b3eccd"
msgid ""
"However, for Tempest to be able to figure out which endpoints should get "
"REST"
msgstr ""

msgctxt "41d733f3cabbd2df801414e55b46d43a"
msgid ""
"API calls for each service, it needs to know how that project is defined in "
"the"
msgstr ""

msgctxt "22ede7fb73c9f4caca3275fe13b19096"
msgid ""
"service catalog. There are three options for each service section to "
"accomplish"
msgstr ""

msgctxt "fd4cc158f7c9d5e9777bee866f5bda12"
msgid "this:"
msgstr ""

msgctxt "a9716df9b77c1a4bbb455099adab8497"
msgid " #. ``catalog_type``"
msgstr ""

msgctxt "1b8a8cc36c48eeda506082a95a8be7df"
msgid " #. ``endpoint_type``"
msgstr ""

msgctxt "c9efce8d3c5fcc640773604b31ce52e8"
msgid " #. ``region``"
msgstr ""

msgctxt "a77d3542e94059bcd9ac989577955e9d"
msgid ""
"Setting ``catalog_type`` and ``endpoint_type`` should normally give Tempest"
msgstr ""

msgctxt "16933a2e96f46d89fe993b0e32b679d9"
msgid ""
"enough information to determine which endpoint it should pull from the "
"service"
msgstr ""

msgctxt "a33406379bccefc994c3102d1dee2e0c"
msgid ""
"catalog to use for talking to that particular service. However, if your "
"cloud"
msgstr ""

msgctxt "35428dc7b8e414e4c7a22768d11bd8d2"
msgid ""
"has multiple regions available and you need to specify a particular one to "
"use a"
msgstr ""

msgctxt "866d47979df132ecca004eedb1518deb"
msgid "service you can set the ``region`` option in that service's section."
msgstr ""

msgctxt "eef8099245f221b0b2632e9df017fb48"
msgid ""
"It should also be noted that the default values for these options are set"
msgstr ""

msgctxt "cfff8005791af4a2cb29431d7494fa70"
msgid ""
"to what devstack uses (which is a de facto standard for service catalog"
msgstr ""

msgctxt "9424a806f0d5ffd2f88f6d995e9e825a"
msgid ""
"entries). So often nothing actually needs to be set on these options to "
"enable"
msgstr ""

msgctxt "c75ef5dfc4f86536518863be2e9805c6"
msgid ""
"communication to a particular service. It is only if you are either not "
"using"
msgstr ""

msgctxt "b8543afa93958c83bca814aa96968440"
msgid ""
"the same ``catalog_type`` as devstack or you want Tempest to talk to a "
"different"
msgstr ""

msgctxt "f69ccff671c5042cf2b83a16c638a8d5"
msgid ""
"endpoint type instead of publicURL for a service that these need to be "
"changed."
msgstr ""

msgctxt "51e098c1d6652586979d208b2ce651d8"
msgid ".. note::"
msgstr ""

msgctxt "33bad18ad8362e743e977b4d80dddc94"
msgid ""
"    Tempest does not serve all kinds of fancy URLs in the service catalog.  "
"The"
msgstr ""

msgctxt "7f282ec27b962655661371b8dfe47c64"
msgid ""
"    service catalog should be in a standard format (which is going to be"
msgstr ""

msgctxt "6666445d48d0a54db6dfd2062b53bb82"
msgid "    standardized at the keystone level)."
msgstr ""

msgctxt "21a1913fc9bd3f85f99c3937a8584160"
msgid ""
"    Tempest expects URLs in the Service catalog in the following format:"
msgstr ""

msgctxt "9f87c5828b078cf3ed09b02e135268b3"
msgid "     * ``http://example.com:1234/<version-info>``"
msgstr ""

msgctxt "b83b22f436dcf5af0e922651844df85c"
msgid "    Examples:"
msgstr ""

msgctxt "2d58ffb504aa7a5a66740a5cc5c83886"
msgid "     * Good - ``http://example.com:1234/v2.0``"
msgstr ""

msgctxt "ff45f357ced5a675d1b7f17847adb6bf"
msgid "     * Wouldn��t work -  ``http://example.com:1234/xyz/v2.0/``"
msgstr ""

msgctxt "96ebbef9b7192386d4486477e30c1ae2"
msgid "       (adding prefix/suffix around version etc)"
msgstr ""

msgctxt "18b24403cefb390dd3f3524860724ce2"
msgid "Service Feature Configuration"
msgstr ""

msgctxt "8c3e5509ee4083cb74a7f878820ae6f7"
msgid "-----------------------------"
msgstr ""

msgctxt "3a685aa01d5a0447de8a0e2bb9faf787"
msgid ""
"OpenStack provides its deployers a myriad of different configuration options "
"to"
msgstr ""

msgctxt "730b6c202d303cd8fb5839d133696e0d"
msgid ""
"enable anyone deploying it to create a cloud tailor-made for any individual "
"use"
msgstr ""

msgctxt "b13189d937b46684866ea75e879253b9"
msgid ""
"case. It provides options for several different backend types, databases,"
msgstr ""

msgctxt "00c3d4187a472c4410c2aa95c67d71b9"
msgid ""
"message queues, etc. However, the downside to this configurability is that"
msgstr ""

msgctxt "f1796fb09ecae68ddae4303d8162541f"
msgid ""
"certain operations and features aren't supported depending on the "
"configuration."
msgstr ""

msgctxt "7527cfa32d3995db36b34fc48c0ff8d0"
msgid ""
"These features may or may not be discoverable from the API so the burden is"
msgstr ""

msgctxt "1f41b6824b0add9fed8260e57435b2f8"
msgid ""
"often on the user to figure out what is supported by the cloud they're "
"talking"
msgstr ""

msgctxt "cb153402c49949da597715180bf6793c"
msgid ""
"to.  Besides the obvious interoperability issues with this it also leaves"
msgstr ""

msgctxt "e4f2912794d168fdb707c904126e7918"
msgid ""
"Tempest in an interesting situation trying to figure out which tests are"
msgstr ""

msgctxt "e9bf21436a01bd229438062ea80c79e9"
msgid ""
"expected to work. However, Tempest tests do not rely on dynamic API "
"discovery"
msgstr ""

msgctxt "3a8fb6b46fe69a9c87c221d9eb84b2e1"
msgid ""
"for a feature (assuming one exists). Instead Tempest has to be explicitly"
msgstr ""

msgctxt "0e484b2514fc25a7fdbb72b5d18715bc"
msgid ""
"configured as to which optional features are enabled. This is in order to"
msgstr ""

msgctxt "824cb96848db2a0eceeb58fa7dbe9a0d"
msgid "prevent bugs in the discovery mechanisms from masking failures."
msgstr ""

msgctxt "d94b2cd7786322e481584e100505e11a"
msgid ""
"The service feature-enabled config sections are how Tempest addresses the"
msgstr ""

msgctxt "ab475147a3e0b93d302fb08462a52f15"
msgid ""
"optional feature question. Each service that has tests for optional features"
msgstr ""

msgctxt "4e4bafd99cdbabc59cbca80015819d63"
msgid ""
"contains one of these sections. The only options in it are boolean options"
msgstr ""

msgctxt "a619f52f2800d581a9027073f97fc732"
msgid ""
"with the name of a feature which is used. If it is set to false any test "
"which"
msgstr ""

msgctxt "d42ec49340468c0cd8f01cf52015110f"
msgid ""
"depends on that functionality will be skipped. For a complete list of all "
"these"
msgstr ""

msgctxt "8290dac90b3bce1c57a5b71a6163af43"
msgid "options refer to the sample config file."
msgstr ""

msgctxt "ce6857c71bd5bad953fab82458aae99e"
msgid "API Extensions"
msgstr ""

msgctxt "757060142914322fda0821d3aa3a83fb"
msgid "^^^^^^^^^^^^^^"
msgstr ""

msgctxt "8999f76cfc98ff02ea9c46aaa3a7161d"
msgid ""
"The service feature-enabled sections often contain an ``api-extensions`` "
"option"
msgstr ""

msgctxt "95ffc1c8813afe70f79cf58081c7f9a7"
msgid ""
"(or in the case of swift a ``discoverable_apis`` option). This is used to "
"tell"
msgstr ""

msgctxt "5356bbb1b2b775bd997aeb8e81cb1ded"
msgid ""
"Tempest which api extensions (or configurable middleware) is used in your"
msgstr ""

msgctxt "e90487123a7ee0eee92e96d9c293d412"
msgid ""
"deployment. It has two valid config states: either it contains a single "
"value"
msgstr ""

msgctxt "2d6a45ca3df0c0f086161582bb553b7f"
msgid ""
"``all`` (which is the default) which means that every api extension is "
"assumed"
msgstr ""

msgctxt "617323b7fb3b4e5aaffd8a4be8709a4f"
msgid ""
"to be enabled, or it is set to a list of each individual extension that is"
msgstr ""

msgctxt "d0b4d47bbb0a10cb7f10e9fd7b663091"
msgid "enabled for that service."
msgstr ""