Hi All,

QA had discussion in Dublin PTG about interop adds-on tests location. First
of all thanks all (specially markvoelker, dhellmann, mugsie) for joining
the sessions. and I am glad we conclude the things and agreed on solution.

Discussion was carry forward from the ML discussion [1] and to get the
agreement about interop adds-on program tests location.

Till now only 2 projects (heat and designate) are in list of adds-on
program from interop side. After discussion and points from all stack
holders, QA team agreed to host these 2 projects interop tests.  Tests from
both projects are not much as of now and QA team can accommodate to host
their interop tests.

Along with that agreement we had few more technical points to consider
while moving designate and heat interop tests in Tempest repo. All the
interop tests going to be added in Tempest must to be Tempest like tests.
Tempest like tests here means tests written using Tempest interfaces and
guidelines. For example, heat has their tests in heat-tempest-plugin based
on gabbi and to move heat interop tests to Tempest those have to be written
as Tempest like test. This is because if we accept non-tempest like tests
in Tempest then, it will be too difficult to maintain by Tempest team.

Projects (designate and heat) and QA team will work closely to move interop
tests to Tempest repo which might needs some extra work of standardizing
their tests and interface used by them like service clients etc.

In future, if there are more new interop adds-on program proposal then, we
need to analyse the situation again regarding QA team bandwidth. TC or QA
or interop team needs to raise the resource requirement to Board of
Directors before any more new adds-on program is being proposed. If QA team
has less resource and less review bandwitdh then we cannot accept the more
interop programs till QA get more resource to maintain new interop tests.

Overall Summary:
- QA team agreed to host the interop tests for heat and designate in
Tempest repo.
- Existing TC resolution needs to be adjust about the QA team resource
bandwidth requirement. If there is going to be more adds-on program
proposal then, QA team will not accept the new interop tests if QA team
bandwidth issue still exist that time also.
- Tempest will document the clear process about interop tests addition and
other more care items etc.
- Projects team to make their tests and interface as Tempest like tests and
stable interfaces standards. Tempest team will closely work and help
Designate and Heat on this.

Action Items:
- mugsie to abandon https://review.openstack.org/#/c/521602 with quick
summary of discussion here at PTG
- markvoelker to write up clarification to InteropWG process stating that
tests should be moved into Tempest before being proposed to the BoD
- markvoelker to work with gmann before next InteropWG+BoD discussion to
frame up a note about resourcing testing for add-on/vertical programs
- dhellmann to adjust the TC resolution for resource requirement in QA when
new adds-on program is being proposed
- project teams to convert  interop test and  framework as per tempest like
tests and propose to add to tempest repo.
- gmann to define process in QA about interop tests addition and
maintainance

We have added this as one of the monitoring/helping item for QA to make
sure it is done without delay.  Let's work together to finish this
activity.

Discussion Details:
https://etherpad.openstack.org/p/qa-rocky-ptg-Interop-test-for-adds-on-project

..1
http://lists.openstack.org/pipermail/openstack-dev/2018-January/126146.html


-gmann
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to