Tempest plugin for validation of Airship components.
Go to file
pradeepkumarks 04d58a9c03 Implementation of Shipyard API functional tests
As part of this patchset we have implemented the following GET Shipyard
API functional tests to ascertain based on some of the response
parameters obtained.
We have also assumed that some of the create/POST operations are not
performed yet which we will be taking in our next patchset

1. Test_actions
   list actions
   get action
   get action step

2. Airflow monitoring
   get workflow list
   get workflow

3. Document staging
   get collection list
   get collection
   get collection id
   get collection version buffer
   get collection version committed
   get collection version successful site action
   get collection version last site action
   get renderedconfigdocs
   get renderedconfigdocs version buffer
   get renderedconfigdocs version committed
   get renderedconfigdocs version successful site action
   get renderedconfigdocs version last site action
   get collection compare two revisions doc

4. Log retrieval
   get action step logs

5. Site Status
   get site statuses
   get site statuses node provision status
   get site statuses node power status
   get site statuses both filters together

Change-Id: Idd2ecaedf3c7e7fe07b68869e437b8d385cec8cd
2019-01-18 20:05:38 +05:30
airship_tempest_plugin Implementation of Shipyard API functional tests 2019-01-18 20:05:38 +05:30
README.rst Cleanup clients, add documenation, and fix 2 tests 2018-08-24 17:33:47 -04:00
requirements.txt Implementation of Shipyard API functional tests 2019-01-18 20:05:38 +05:30
setup.cfg Framework for Airship Tempest Plugin 2018-08-17 13:40:11 -04:00
setup.py Framework for Airship Tempest Plugin 2018-08-17 13:40:11 -04:00
test-requirements.txt Add Additional RBAC Test Coverage for Shipyard 2018-08-21 16:25:32 -04:00
tox.ini Add Additional RBAC Test Coverage for Shipyard 2018-08-21 16:25:32 -04:00

README.rst

Tempest Integration of airship-tempest-plugin

Purpose:

The purpose of this plugin is to provide automated tests for all OpenStack Airship components.

DISCALIMER:

This initial implementation is just to meet the first use case which is RBAC testing. For RBAC testing, we only need to hit the API endpoint and check role permission to the API being tested. Some of the REST clients will need to be rewritten if functional testing is desired. Those that need to be rewritten are documented in each service client code.

Environment Information:

Testing can be done in a airship-in-a-bottle environment. Please refer to [0] and [1]. Tempest and Tempest plugin installation can be done in a Python virtual environment.

FAQ:

Patrole Supporting Documentation:

Patrole documentation for requirements driven approach that is used: https://github.com/openstack/patrole/blob/master/doc/source/framework/requirements_authority.rst Patrole role-overriding: https://github.com/openstack/patrole/blob/master/doc/source/framework/rbac_utils.rst#role-overriding Patrole under-permission exception: https://github.com/openstack/patrole/blob/master/patrole_tempest_plugin/rbac_exceptions.py#L51 Patrole over-permission exception: https://github.com/openstack/patrole/blob/master/patrole_tempest_plugin/rbac_exceptions.py#L44

Future Considerations: ---------------------Will the airship-tempest-plugin continue to live here: https://github.com/att-comdev/airship-tempest-plugin or will it be moved under OpenStack? Will there exist a RBAC gate for all Airship projects?

[0] https://github.com/openstack/airship-in-a-bottle [1] https://www.airshipit.org/