This commit fixes indentation in tempest docs. These indentations are
not necessary and it causes a weird html outputs.
Change-Id: I9c8714558a3327b7ad0b0ab0d3fdc7e770c3c75b
I've been reading our entire documentation to see where it could
be improved. It's guide good actually. While reading I've fixed
some typos, added some capitalization to project names, mostly
trivial stuff.
What's worth reviewing is the 2 paragraphs I added to the REVIEWING
guidelines.
Change-Id: I977de335119f4ff7b9aedcfbed31c264ed531ea8
After I2601433585740030ab61433f0e8ca1a919275d9f is merged,
the exception description of auth_version is no longer
true, this is to remove it.
Change-Id: I5f9d8fb852faa92708158fca7d7bc7f5ac2fd933
This commit is the start of a new doc guide for helping people figure
out how to write good tempest tests. This is just a starting point for
the document and doesn't cover every aspect of writing a test case in
tempest. Right now it just covers the setupClass phase for writing
TestCases. It will be expanded upon in future commits to give a complete
guide to writing tests in Tempest.
Change-Id: Ie0db2079163f536ae72668c8fc9129ae4c6389e2
Every few weeks we get people filing bugs because they're using creds
with pre-existing resources created in an accounts.yaml and list tests
start randomly failing. This adds documentation to say don't do that
because it breaks the isolation expectation of tests.
Change-Id: I6d31a8309d17c72748c4c6283fb6d014f7493463
Before Tempest had three different methods of providing authentication,
dynamic credentials, locking test accounts and non-locking test
accounts, currently only the first two are supported. This commit
updates a section on the configuration guide where it still mentions
three methods.
Change-Id: I532aff27a803b9fd34e994153f4183de48d91d00
Closes-Bug: 1600319
Certain identity v3 API calls require a domain scoped token when
policy.v3cloudsample.json is used.
Introduce a new config flag to tell Tempest that keystone in the
targe cloud requires domain scoped tokens for admin actions.
Modify the v3 client managers used to obtain v3 admin identity
clients to request the domain scope when the flag is turned on.
Co-authored by: Roxana Gherle <roxana.gherle@hp.com>
Change-Id: I91ca907992428a5a14fb8d48a4fad105d2906e27
This commit updates the wording and section separation for the remote
access section of the tempest configuration guide. Previously, the
details about using the validation group felt tacked on and out of
place. This attempts to correct that and make it clear what the
validation group is used for and how that's combined with the network
allocation.
Change-Id: I2f65d25e8f66944347f669dac14d77057a10975a
This commit fixes docs errors and warnings. However, 'WARNING: nonlocal
image URI found' is still remaining because it needs an ugly workaround
that is replacing it to raw html.
Change-Id: I4524c1ff4126c87979301d0fb8ac7c9eb6f2f708
This commit removes the legacy credential provider. It's been
deprecated for over a full cycle which has been sufficient time for
users to migrate off of it. Keeping this around just causes more
confusion by having a 3rd path to configuring credentials in tempest.
The credential provider was officially marked as deprecated in change
Ia5132c5cb32355d6f26b8acdd92a0e55a2c19f41
Change-Id: I8c24cd17f643083dde71ab2bd2a38417c54aeccb
Configuration docs are slightly dated now wrt admin credentials
and credential configurations in general. Fixing that.
Change-Id: Id176202d73683ef3adbcd93a77d90be6a5206f37
OpenStack has settled (a very long time ago) on project to represent
the container which has users. We should make tempest configs always
use project versions of these names. This deprecates the old tenant
versions of these names, and makes project version the prefered
option.
Change-Id: Ied68c0326cf891a4e6eb3db51dc5f43241e4b8d2
This change updates to configuration documentation on ssh validation.
Partially implements: blueprint ssh-auth-strategy
Change-Id: Ie6521d77b8ab3b61e7dfa140c7b395c06cf16eeb
Updated documentation to include information about how to configure
Identity-v3-specific account settings using the Legacy Credentials
configuration options.
Change-Id: I55abf9629ed8f8436ce4497e9790feea05669407
This patch set updates the configuration.rst file to:
- Fix a few minor typographical and grammatical errors
- Make case consistent (e.g. "tempest" vs. "Tempest")
- Make style consistent (e.g. make references to config file keywords
consistently monospace)
- Spell out numbers less than ten
- Fix a couple of minor content issues as suggested by @mtreinish.
No change in meaning or content is intended.
Change-Id: I5a23e2c39c57eec1e6dbc2a5a076b933c930f78e
In latest version, admin user infos are removed to auth section.
Correct this in the configuration doc
Change-Id: I75a605e025bb1ee8690455361e3efbc81ead8a55
This commit adds a note to the tempest configuration guide about
using a full path for the test accounts configuration option. Using
a relative path can result in the file not being found and things
failing.
Change-Id: I87901026b5865399469e5e20e5f8c6cf7336784a
This commit drops the lock_path section from the tempest config guide.
Previously setting this was required there was no default value from
the oslo lib. However, tempest recently switched to overriding the
default to use the system temp dir. So additional configuration by the
end user should not be required here anymore.
Change-Id: Ia594745ad4d8e6b701c799cbf5ac5e555c598e3f
Separate helpers methods to build credentials, credential providers and
client managers that depend on configuration. They are all moved to
the common.credentials module to achieve two objectives:
- prepare credential provider module to move to tempest-lib
- avoid circular dependencies
There are still dependencies to CONF in the credential providers,
removing all of them would make the patch too large; but there is
with this patch a single place where all relevant CONF parameters can
be looked up and passed into the credential providers.
Partially-implements: bp tempest-library
Change-Id: I351f86f0570070105bbf24f2d904e917feea6e57
Tempest does not serve all kind of fancy service cataog format.
Service catalog should be in some standard and consistant format.
This patch adds those in doc to clarify the expected format of catalogs.
Change-Id: I5fb94510c019cca2e81112fb8cf123a3dfab8daf
Renaming the isolated_creds module to dynamic_creds module, and rename
the IsolatedCreds class to DynamicCredentialProvider in preparation
to migration to tempest-lib.
Partially implements bp tempest-library
Change-Id: I78a4884e980ef7d0103639cb3792a54c69fb7761
This commit deprecates the original configuration options for
providing credentials. This mechanism of providing tempest with
credentials to run with has a lot of drawbacks and has been
superseded by using an accounts.yaml file. It has been planned
for deprecation once we had a periodic/experimental CI job setup
to run with test accounts enabled. Now that this has been done
we can start the deprecation cycle for the old options.
Change-Id: Ia5132c5cb32355d6f26b8acdd92a0e55a2c19f41
This commit fixes a few things in the tempest docs. First it fixes all
of the sphinx warnings and enables fail on warn to ensure we're using
valid sphinx everywhere. It also adds a link from the configuration
guide to the sample config file.
Change-Id: I3ad645a6bbfa46b4498e1732410743e46d6eb0cb
The indefinite article of the word "alternate" had became "a".
Fix it to "an".
Closes-Bug #1486786
Change-Id: I8d66d066f218fdb3cb70e45ebbcc6be6ae2e5925
This commit adds a new config option to the auth section,
create_isolated_networks, to disable tenant isolation from attempting
to create an isolated network stack on each created tenant. This is
needed because in certain neutron configurations the extra resource
creations are not need or not allowed.
Change-Id: I0899a43709a0cb2967376e914248d2ad4a37773a
Closes-Bug: #1447829
When using the lock testing accounts, allow_tenant_isolation
should be set as False. Now it's missing in the document.
This patch will add it.
Closes-Bug: #1454001
Change-Id: I3e1e7a31ea4c1c8b25e821df545c8674a8de38da
This commit cleans up some details in the accounts.yaml sample file
and the tempest configuration guide to provide missing details about
how to create and use an accounts file. Specifically it adds more
detailed comments to the sample file about each section, and in the
config guide it removes obsolete sections and adds some missing
details.
Change-Id: Ic11335fe1215ab0625ea2308ccc75d22a284c432
Closes-Bug: #1447851
This commit fixes several issues with the non-locking cred provider
section in the tempest config guide. It was in a state stuck between
refactors and didn't accurately describe how it should be used anymore.
Change-Id: Ibc6ca1816f6673e2c8dbd6ae3451e03914f04137
This commit adds a paragraph to the tempest configuration guide on how
to use the tempest_roles option. This was previously missing from the
tenant isolation section.
Change-Id: I1ef1649186edbeb51e1ced1bbb361b78eaef3721
This commit adds a section to the config guide on how to configure
the available services and the corresponding entries in the service
catalog for those services.
Change-Id: I70d7feb47b2df4b6caf9d38d8e79b59bb30fb894
This commit adds another section to the tempest config guide outlining
how the service feature enabled sections should be configured.
Change-Id: Iaedf744068b3f91f72144efcaab5d9eaeb9adb0c
This commit adds additional sections to the tempest configuration guide
to elaborate on the details of several required options when configuring
tempest. Specifically this covers how to set the keystone connection
info, flavors to use for testing, and image setup.
Change-Id: I5a72443a3b05e39eba2eac1c4c9a4d6eef26797d
This commit adds a networking section to the tempest configuration
guide to start explaining the various facets of networking
configuration. Right now it only contains a guide around how to
configure tempest to provide a network on server creation. Additional
subsections will be added later on.
Change-Id: Ibdfd8becce18de0ef414027d5e7c580f852607a7
This commit removes support for using an accounts.yaml file with the
non-locking provider. There is no reason the non-locking provider
would ever need to be used with an accounts.yaml file because the
locking provider supports running serially just fine. (which would be
the sole use case for accounts file with the non-locking provider)
Doing this relegates the non-locking provider to just handle the
legacy config options for providing credentials.
Removing this code path provides the advantage of removing a double
maintenance burden for the non-locking provider, in addition to
simplifying the config and user story around the cred providers. It
also turns out this config permutation was never properly tested and
didn't actually work.
Change-Id: I8088d75897589203264ae29326fe9901c3457cc3
This commit makes several needed cleanups and improvements to the
tempest readme to make things clearer and elaborate on some sections.
Also as the readme is intended to be a tempest users guide, this moves
sections which are more developer focused to the hacking guide.
Change-Id: I4180ce18268443873fe7d8d5e7d0aaebc2cd1e08
This commit adds a section to the tempest configuration guide on
configuring the lock_path for running tempest and explains why it
is needed.
Change-Id: I73913797d96f9f833e02e5b37be9c0c85b3ae959
This commit updates the auth/credentials section of the tempest
configuration guide to reflect recent changes made to the credential
providers and config file.
Change-Id: I4633ff14be1c33f780b671f0ac0c98884ecc94bc
This commit adds a new doc page to the tempest documentation to
provide a guide to configuring tempest. It currently contains one
section to elaborate on the credentials and auth options in the config
file. This doc will be expanded in the future to add details around
other pieces of tempest configuration.
Change-Id: Iaf7cefc6a5e508437e4b4620ba5bfaa221f3611b