openstack/whitebox-tempest-plugin
Code Issues Proposed changes

README: Update with roadmap

Browse Source 
Provide a roadmap detailing how we see this progressing towards the
future.

Change-Id: I2852cc4afe1b5a59d225888b6132325ac3989881
This commit is contained in:
Stephen Finucane 2017-12-13 15:06:41 +00:00 committed by Artom Lifshitz
parent d3baed9755
commit 360e7586e8
1 changed files with 29 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
README.rst
View File

@ -20,7 +20,8 @@ nodes running in the overcloud.
Most tests have specific hardware requirements. These are documented in the
tests themselves and the tests should fast-fail if these hardware requirements
are not met. You will require multiple nodes to run these tests and will need
to manually specify which test to run on which node.
to manually specify which test to run on which node. For more information on
our plans here, refer to :ref:`roadmap`.
For more information on TripleO/Director, refer to the `Red Hat OpenStack
Platform documentation`__.
@ -73,3 +74,30 @@ Importing classes from ``tempest.api.*`` could be dangerous since future
version of Tempest could break.
__ http://docs.openstack.org/developer/tempest/plugin.html
.. _roadmap:
Roadmap
-------
The different tests found here all have different hardware requirements, and
these requirements often conflict. For example, a test that requires a host
without HyperThreading enabled cannot be used for a test that requires
HyperThreading. As a result, it's not possible to have one "master
configuration" that can be used to run all tests. Instead, different tests must
be run on different nodes.
At present, this plugin exists in isolation and the running of individual tests
on nodes, along with the configuration of said nodes, remains a manual process.
However, the end goal for this project is to be able to kick run this test
suite of against *N* overcloud nodes, where each node has a different hardware
configuration and *N* is the total number of different hardware configurations
required (one for real-time, one for SR-IOV, etc.). Each node would have a
different profile__ and host aggregates would likely be used to ensure each
test runs on its preferred hardware. To get here, we should probably provide a
recipe along with hardware configuration steps.
This being said, the above is way off yet. For now, we're focussed on getting
the tests in place so we can stop doing all this stuff by hand.
__ http://tripleo.org/install/advanced_deployment/profile_matching.html