Open Stack

Rob, is that question directed to me? I'm not sure what a test UUID is.


--John




> On Feb 25, 2015, at 3:58 PM, Rob Hirschfeld <rob at zehicle.com> wrote:
> 
> Good question.
> Can those tests also get UUIDs?
> 
> On Feb 25, 2015 5: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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openstack.org/pipermail/defcore-committee/attachments/20150227/49fb6636/attachment.pgp>