Tempest test accounts for parallel execution
Tempest relies on tenant isolation for parallel test executions. Test accounts are provisioned on the fly for each test class to ensure isolation. This approach requires an identity admin account being available for the provisioning.
The aim of this blueprint is to provide an alternative solution, specifically pre-provisioned accounts, and to solve the problems related to this approach: how test accounts are allocated to different test processes spawned by testr, including alt user and other test accounts, and how we can support both tenant isolation and this new implementation in tempest, and easily switch between the two.
Blueprint information
- Status:
- Complete
- Approver:
- Matthew Treinish
- Priority:
- Medium
- Drafter:
- Andrea Frittoli
- Direction:
- Approved
- Assignee:
- Andrea Frittoli
- Definition:
- Approved
- Series goal:
- Accepted for juno
- Implementation:
-
Implemented
- Milestone target:
-
juno-3
- Started by
- Matthew Treinish
- Completed by
- Andrea Frittoli
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
add bp:test-accounts
Addressed by: https:/
Add base class for all credential providers
Gerrit topic: https:/
Addressed by: https:/
Add a new credential provider to use a list of creds
Addressed by: https:/
Add Credentials Provider factory
Addressed by: https:/
Add tool to prepare fixed isolated accounts
Addressed by: https:/
Force use of Accounts for test purposes
Addressed by: https:/
Add lock_path to TempestPrivateC
Addressed by: https:/
Fix use of nonexistent class variable in accounts.py
Gerrit topic: https:/
Addressed by: https:/
Make class setup safe in compute base admin class
Addressed by: https:/
Add a NotLockingAccounts credentials provider
Addressed by: https:/
Backward compatibility to credentials in conf
Gerrit topic: https:/
