settingsLogin | Registersettings

[OpenStack-DefCore] Definition of core

0 votes

Hi all,

at the contributors meetup for QA we have been discussing about whether
to keep the heat tests that are meant to be for interoperability in
tempest tree or not. An interesting discussion arised from that.

We are having a discussion (with gmann and oomichi) about whether heat
could be considered core project or not (if it was core, there would be
no problem). They have shared this post with us as the definition they
are using of "core project" they are using:
https://dague.net/2014/08/26/openstack-as-layers/

Can someone clarify whether this definition is still valid or whether we
don't use it anymore? Is there any more up to date definition? Any
comment or clarification welcome.

Cheers,
Gema

--
Gema Gomez-Solano
Tech Lead, SDI
Linaro Ltd
IRC: gema@#linaro on irc.freenode.net


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
asked Oct 28, 2016 in defcore-committee by gema.gomez-solano_at (400 points)  

5 Responses

0 votes

On Oct 28, 2016, at 3:15 PM, Gema Gomez gema.gomez-solano@linaro.org wrote:

Hi all,

at the contributors meetup for QA we have been discussing about whether
to keep the heat tests that are meant to be for interoperability in
tempest tree or not. An interesting discussion arised from that.

We are having a discussion (with gmann and oomichi) about whether heat
could be considered core project or not (if it was core, there would be
no problem). They have shared this post with us as the definition they
are using of "core project" they are using:
https://dague.net/2014/08/26/openstack-as-layers/

Can someone clarify whether this definition is still valid or whether we
don't use it anymore? Is there any more up to date definition? Any
comment or clarification welcome.

The Defcore/Interop Working Group scores capabilities against a set of
criteria, and if the score is high enough the capability is considered
for inclusion into the DefCore/Interop guidelines. [1]

After an advisory period, a capability can become required, at which
point a product that obtains the “OpenStack Powered” trademark
against that guideline is required to provide that capability.

Any project that provides a required DefCore capability could be
considered “core” in that regard, but the coreness of that project
and capability may or may not match up with current opinions on
what a core OpenStack project is.

As far as I know, there is no official TC definition of what a core project is.

-Chris

[1] http://git.openstack.org/cgit/openstack/defcore/tree/doc/source/process/CoreCriteria.rst

Cheers,
Gema

--
Gema Gomez-Solano
Tech Lead, SDI
Linaro Ltd
IRC: gema@#linaro on irc.freenode.net


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
responded Oct 28, 2016 by chris_at_openstack.o (3,260 points)   2 3
0 votes

Thanks for bringing this up.

So as per current Tempest Scope, tests for 6 projects (nova, cinder, swift, neutron, keystone, glance) can be in Tempest tree and other are via plugin.

Currently heat is out of those 6 projects.

This was something we discussed in Atlanta [1]. These 6 projects was first list which QA considered to make in tree tests and others in plugin etc. Also this can be always extended but we need some clear criteria may be based on TC guidelines
etc before extension.

I feel that criteria plays key role in future too if any project ask to add their tests in QA.

problem). They have shared this post with us as the definition they are using
of "core project" they are using:
https://dague.net/2014/08/26/openstack-as-layers/

QA is not defining what "Core project" is and I do think we are based on any assumption also. That blog link was given as reference to understand the layer structure of component which is very nice to look into (There is no definition of "Core project" there).

.. [1] https://etherpad.openstack.org/p/YVR-QA-in-the-big-tent

Thanks & Regards,
Ghanshyam Mann

-----Original Message-----
From: Gema Gomez [mailto:gema.gomez-solano@linaro.org]
Sent: 28 October 2016 15:15
To: defcore-committee@lists.openstack.org
Subject: [OpenStack-DefCore] Definition of core

Hi all,

at the contributors meetup for QA we have been discussing about whether
to keep the heat tests that are meant to be for interoperability in tempest
tree or not. An interesting discussion arised from that.

We are having a discussion (with gmann and oomichi) about whether heat
could be considered core project or not (if it was core, there would be no
problem). They have shared this post with us as the definition they are using
of "core project" they are using:
https://dague.net/2014/08/26/openstack-as-layers/

Can someone clarify whether this definition is still valid or whether we don't
use it anymore? Is there any more up to date definition? Any comment or
clarification welcome.

Cheers,
Gema

--
Gema Gomez-Solano
Tech Lead, SDI
Linaro Ltd
IRC: gema@#linaro on irc.freenode.net


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
responded Oct 28, 2016 by ghanshyam.mann_at_ne (940 points)   1
0 votes

Excerpts from Gema Gomez's message of 2016-10-28 15:15:19 +0200:

Hi all,

at the contributors meetup for QA we have been discussing about whether
to keep the heat tests that are meant to be for interoperability in
tempest tree or not. An interesting discussion arised from that.

We are having a discussion (with gmann and oomichi) about whether heat
could be considered core project or not (if it was core, there would be
no problem). They have shared this post with us as the definition they
are using of "core project" they are using:
https://dague.net/2014/08/26/openstack-as-layers/

Can someone clarify whether this definition is still valid or whether we
don't use it anymore? Is there any more up to date definition? Any
comment or clarification welcome.

Cheers,
Gema

The TC has specified that tests related to DefCore capabilities should
be located in the tempest tree [1]. Before those tests are used by
DefCore, they can be located in the project tree or a separate tempest
plugin tree. When DefCore identifies them as related to a capability it
is interested in including in its specification, the tests should be
moved to Tempest.

Doug

[1] http://governance.openstack.org/resolutions/20160504-defcore-test-location.html


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
responded Nov 1, 2016 by Doug_Hellmann (87,520 points)   3 4 4
0 votes

2016-10-28 6:15 GMT-07:00 Gema Gomez gema.gomez-solano@linaro.org:

at the contributors meetup for QA we have been discussing about whether
to keep the heat tests that are meant to be for interoperability in
tempest tree or not. An interesting discussion arised from that.

We are having a discussion (with gmann and oomichi) about whether heat
could be considered core project or not (if it was core, there would be
no problem). They have shared this post with us as the definition they
are using of "core project" they are using:
https://dague.net/2014/08/26/openstack-as-layers/

Can someone clarify whether this definition is still valid or whether we
don't use it anymore? Is there any more up to date definition? Any
comment or clarification welcome.

No, we didn't show the above brog as the concrete definition of core projects.
The brog's content was the first step of "big-tent" which allows new
projects creations as possible.
That means we are needing the definition of core projects for the
interoperability, IIUC.
I believe many people understand the technical background.

Current core projects are showed on
https://www.openstack.org/software/project-navigator/ as "Core
Services ( 6 Results )".
Isn't the definition also official yet?

Thanks
Ken Ohmichi



Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
responded Nov 7, 2016 by Ken'ichi_Ohmichi (8,640 points)   2 3 3
0 votes

2016-11-01 6:52 GMT-07:00 Doug Hellmann doug@doughellmann.com:

Excerpts from Gema Gomez's message of 2016-10-28 15:15:19 +0200:

Hi all,

at the contributors meetup for QA we have been discussing about whether
to keep the heat tests that are meant to be for interoperability in
tempest tree or not. An interesting discussion arised from that.

We are having a discussion (with gmann and oomichi) about whether heat
could be considered core project or not (if it was core, there would be
no problem). They have shared this post with us as the definition they
are using of "core project" they are using:
https://dague.net/2014/08/26/openstack-as-layers/

Can someone clarify whether this definition is still valid or whether we
don't use it anymore? Is there any more up to date definition? Any
comment or clarification welcome.

Cheers,
Gema

The TC has specified that tests related to DefCore capabilities should
be located in the tempest tree 1. Before those tests are used by
DefCore, they can be located in the project tree or a separate tempest
plugin tree. When DefCore identifies them as related to a capability it
is interested in including in its specification, the tests should be
moved to Tempest.

Yes, I agree with Doug here.
Then we (QA team) are proposing the separate repo1 of tempest-plugin
tests for verifying different versions of OpenStack APIs with the same
tests from the interoperability POV also.
If separating that, it will be easy to move the corresponding tests
into Tempest.

Thanks
Ken Ohmichi



Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
responded Nov 7, 2016 by Ken'ichi_Ohmichi (8,640 points)   2 3 3
...