[Tempest] OpenSack Powered * vs OpeStack Compatible

Ghanshyam Mann gmann at ghanshyammann.com
Tue Feb 25 15:00:42 UTC 2020

---- On Tue, 25 Feb 2020 01:16:13 -0600 prakash RAMCHANDRAN <pramchan at yahoo.com> wrote ----
 > Mark,
 > Glad you pointed to right code. Reviewed and stand corrected. My mis-underdtanding was I considered 20919.01 as first release and 2019.02 as second release of the year. However based on your comments and reference I understand that it is year.month of release , thus 2019.11 includes 'usuri' and previous 3 releases as listed pointed by you.
 >     "os_trademark_approval": {
 >       "target_approval": "2019.11",
 >       "replaces": "2019.06",
 >       "releases": ["rocky", "stein", "train", "ussuri"],
 >       "status": "approved"
 >     }
 >   },
 > That clears that I should have asked for 2019.11.
 > Few more questions on Tempedt tests.
 > I read some where that we have about 1500 Tempest tests overall. Is that correct?

Yeah, it might be little more or less but around 1500 in-tree tests in Tempest.

 > The interop code lines have gone down from 3836 lines to 3232 in train to usuri.
 > Looks contrary to growth, any comments?
 > Question then is  60 compute and 40 storage lines I see in test cases, do we have stats for Tempest tests what's the distribution of 1500 tests across Platform, compute, storage etc. Where and how can I get that. information as documented report.

Those should be counted from interop guidelines where you have mapping of capabilities with test cases.
Few or most of the capabilities have one test to verifying it or a few more than one test.
For example, "compute-flavors-list" capability is verified by two tests[2]. 
This way you can count and identify the exact number of tests per compute, storage etc.

If you would like to know about the Tempest test categorization, you can find it from the directory
structure. We have structured the tests service wise directory, for example, all compute tests under
tempest/api/compute [2].

 > Based on above should we expect decrease or increase for say 2020.05 Vancouver release?
 > How does one certify a kubernetes cluster running openstak modules, one module per docker container in a kubrrnetes  cluster using tempest say like in Airship Control Plane on k8s worker node, which is a OpenStack over kubernetes cluster.
 > Is this possible and if so what test we need to modify to test and certify a Containerized OpenStack in Airship as OpenStack Platform?

I should be verified same way via Tempest. Tempest does not reply on how OpenStack is deployed it interacts via the public
interface (where interop needs only user-facing API excluding admin API) of each service which should be accessible on
k8s cluster also. Tests are not required to modify in this case.

NOTE: we can always extend (writing new tests for current 6 services tests) Tempest for tests required for
interop capabilities either that are new or improved in the verification of existing ones. I remember
about the discussion on covering the API microversion. We keep adding new tests to cover the
new microverison where we need integration tests but we can add API tests also if interop requires those.

 > Can we even certify if for say 2019.11?
 > This should open up exciting possibilities if practical to extend OpeStack powered platform to Airship.
 > Like to hear anyone who has insight to educate us on that.
 > ThanksPrakash
 > Sent from Yahoo Mail on Android 
 >    On Mon, Feb 24, 2020 at 6:09 AM, Mark Voelker<mvoelker at vmware.com> wrote:   Hi Prakash,
 > I am curious to find out if any Distribution or Products based on Openstack  Train or Usuri are seeking the latest certifications based on 2019.02.
 > Hm, there actually isn’t a 2019.02 guideline--were you perhaps referring to 2019.06 or 2019.11?  2019.06 does cover Train but not Usuri [1], 2019.11 covers both [2].  As an FYI, the OpenStack Marketplace does list which guideline a particular product was most recently tested against (refer to https://www.openstack.org/marketplace/distros/ for example, and look for the green “TESTED” checkmark and accompanying guideline version), though this obviously doesn’t tell you what testing might be currently in flight.
 > [1] https://opendev.org/openstack/interop/src/branch/master/2019.06.json#L75[2] https://opendev.org/openstack/interop/src/branch/master/2019.11.json#L75
 > At Your Service,
 > Mark T. Voelker
 > On Feb 22, 2020, at 5:04 AM, prakash RAMCHANDRAN <pramchan at yahoo.com> wrote:
 > Hi all,
 > I am curious to find out if any Distribution or Products based on Openstack  Train or Usuri are seeking the latest certifications based on 2019.02.
 > Similarly does any Hardware Driver of Software application seeking OpenStack compatibility Logo?
 > Finally does anyone think that Open Infra Distro like Airship or StarlingX should promote Open Infra Airship or Open Infra  StarlingX powered as a new way to promote eco system surrounding them similar to OpenStack compatible drivers and software.
 > Will then Argo, customize,Metal3.io or Ironic be qualified as Open Infra Airship compatible?
 > If so how tempest can help in testing the above comments?
 > Refer to this market place below as how Distos and Products leverage OpenStack logos and branding programs.
 > https://www.openstack.org/marketplace/distros/
 > Discussions and feedback are welcome. A healthy debate as how k8s modules used in Open Infra can be certified will be a good start.
 > ThanksPrakash
 > Sent from Yahoo Mail on Android

[1] https://opendev.org/openstack/interop/src/commit/8f2e82b7db54cfff9315e5647bd2ba3dd6aacaad/2019.11.json#L260-L281
[2] https://opendev.org/openstack/tempest/src/branch/master/tempest/api/compute



More information about the openstack-discuss mailing list