Open Stack

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

John,

This was actually discussed during a couple of DefCore meetings, so I think it’s something that is being considered (but thanks for raising it again!).  The basic premise here is that we’re not necessarily tied to a particular testing tool going forward—it’s just that Tempest is where tests for these capabilities are at today.  Bear in mind that 2015.03 is basically looking at Icehouse, which is before the functional test migrations really started gaining steam.  

At Your Service,

Mark T. Voelker
OpenStack Architect

On Feb 25, 2015, at 3:30 PM, John Dickinson <me at not.mn> wrote:

Looks like all of the tests mentioned are still focused on tempest. Since many projects are moving towards in-tree functional tests, how can those be reflected in the listed tests. For example, i'd love to also use the swift in-tree functional tests for referenced swift capabilities.

- --John






On Feb 25, 2015, at 3:11 PM, Van Lindberg <van.lindberg at rackspace.com> wrote:

Should we forward this on to the board?

From: Van Lindberg <van.lindberg at rackspace.com>
Date: Wednesday, February 25, 2015 at 1:51 PM
To: "defcore-committee at lists.openstack.org" <defcore-committee at lists.openstack.org>
Cc: Egle Sigler <egle.sigler at rackspace.com>, Adrian Otto <adrian.otto at rackspace.com>
Subject: [OpenStack-DefCore] Draft 2015.03 Spec

Hello all

Per the discussion today and at the face to face meeting last week, we have the following draft 2015.03 spec for comments and approval:

https://etherpad.openstack.org/p/defcore-draft-spec-2015.03

Notes:
- - There are two advisory sections: auth-token (which we created a placeholder for) and compute-servers-metadata (which didn’t exist in havanacore, but was in icehousecore). Because the point of this doc is “havanacore - anything possibly troublesome,” we suggested moving compute-servers-metadata to advisory for action in 2015.04.
- - This is .rst formatted and designed for human consumption. There is a linked (and also authoritative) .json file for machine consumption.
- - The .json file (draft in gdoc for easy multi-editing right now) has everything that is not mandatory or advisory removed.
- - We updated the versioning of the .json file (to 1.1), removed “status” from the top-level, and added “advisory” flags for those two items that were advisory. We also updated “core” to false for the two advisory items.
- - We need designated sections for keystone.

Thanks,
Van

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

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

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJU70URAAoJELUJLUWGN7CbqKIP+wQ8oRUsZDX5yjTOmdFS2yBV
k6CPpPHj5L7v10sMPj/HvxFvjfoAcraomShkDf/Z9IbTczvsos+uy7p6lZ9HYJyf
Mh0B5KcehMkHorsFhshVBk1ZDVLcdX6hDzAWjovyii32XZTHB6PwdxKThVLPxrdw
6d5o4xfPyUi5HIcpYQotH7b+vDZSB5h3oGM3tpo19Xybx9Gm8sR9xJAglqc8dbE/
8evK3dtFU1cqCIwBtysbYpQsNKnrcd8PShfaMF5qQKo24d4r88hk38TyJtjp5oWa
HQY29RM4Dzlhza2uBJYU7nM60gm7GhaYSA0VwJijePnnuRTh8bCvAV/JbfO+4D4W
a6EXDGx4c5iqojw7OiNkhoG/DNcQJ5OMSfeQQ302qNmmxcK8TJ3fS5UjJS7gZPiR
tZK8YgYNjlFZ6Zik8tp8qGLxbn/IskQUoisVwXcGtmgTLVHwCyqm+P+kIjghNnTc
suoABjnTXwlTi6JyDVswx5jr6LfutMlMpaTpaM8HZdXUmjX1/1QAo/+ymnv9oas7
6inknQn/N37TUQ/0uFnqmp/tAbkIkFMoV9Nd1WolCOhjsJDz0FQi2ViERcvq2dO3
RAe+DZXKh1j72LIXcwtz5K6qby8DTgzu1dTJH2/I32tm59RGqn/MSC33jfQKq3/V
T+95lTKOmYjRUoSRngIG
=Hgkk
-----END PGP SIGNATURE-----