3d9b1e43a6
Every day Rally step by step closer to the point where Rally is going to be generic framework and it would be possible to split Rally & Rally OpenStack Plugins One of the blockers for doing this is certification & samples directories and their contents. Current apporach creates a lot of confusion: - Rally Users are running samples against production - Rally samples are actually not that usefull, because creating from them tasks takes a lot of time - Rally Users don't know what certification task is and how to use it - Samples are hard to ship/find in packaged way (when rally is installed) - Samples are going to be impossible to ship after the split - We have to keep hunderds of yaml/json files in actual state in our repo (extra work for developers) Proposed approach is to: - Create mechansim CLI command that generates samples using plugin names - Rename certification -> tasks - Put in tasks directory pre created and tested tasks for different use cases: key performance metrics, functional testing, load testing of key functionality, ha Testing - Remove samples as they are not needed anymore Change-Id: I4c45224c3af637d17dab0edea038c69a2bae8b1a
2.3 KiB
2.3 KiB
OpenStack Certification Task
How To Validate & Run Task
To validate task with your own parameters run:
$ rally task validate task.yaml --task-args-file task_arguments.yamlTo start task with your own parameters run:
$ rally task start task.yaml --task-args-file task_arguments.yamlTask Arguments
File task_arguments.yaml contains all task options:
| Name | Description |
|---|---|
| service_list | List of services which should be tested |
| smoke | Dry run without load from 1 user |
| use_existing_users | In case of testing cloud with r/o Keystone e.g. AD |
| image_name | Images name that exist in cloud |
| flavor_name | Flavor name that exist in cloud |
| glance_image_location | URL of image that is used to test Glance upload |
| users_amount | Expected amount of users |
| tenants_amount | Expected amount of tenants |
| controllers_amount | Amount of OpenStack API nodes (controllers) |
All options have default values, hoverer user should change them to reflect configuration and size of tested OpenStack cloud.