From 360e7586e8ae8ca95b2643057794e97f699eac2e Mon Sep 17 00:00:00 2001 From: Stephen Finucane Date: Wed, 13 Dec 2017 15:06:41 +0000 Subject: [PATCH] README: Update with roadmap Provide a roadmap detailing how we see this progressing towards the future. Change-Id: I2852cc4afe1b5a59d225888b6132325ac3989881 --- README.rst | 30 +++++++++++++++++++++++++++++- 1 file changed, 29 insertions(+), 1 deletion(-) diff --git a/README.rst b/README.rst index 468b27fa..abc0e7f8 100644 --- a/README.rst +++ b/README.rst @@ -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