Open Stack

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 02/27/2015 12:18 PM, John Dickinson wrote:
> Rob, is that question directed to me? I'm not sure what a test UUID
> is.

They added UUIDs to tempest tests so that as test names or re-org'd,
the defcore mapping didn't have to implode. So I think the question is
about the feasibility of doing such a thing in the swift functional tests.

> --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
>
>>> 
> 
> 
> _______________________________________________ Defcore-committee
> mailing list Defcore-committee at lists.openstack.org 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJU8Kj7AAoJEDOQ22gEGhLwqiAQAKmVnpKIq2U3Fcm564UyVbNh
BFScZjUA2oBxHs8lX5VMZkudnf2vjmCC3k9msWH7VcGo/m3xa8Ioo+x4dryKLwA9
G3YZkiA/qe6p28jEiJ9ddInZtDFby+yobdtobVx+VuhOB6901vcw/32cFbPk1tXh
kZD0iNM6I3eWbQYO7xxgO395ccibyckW3wPdr1Xn+d88Icd3W69ujgX1i6D8MX6H
TOd6lxxpd30C2bCmuacv7mTPSBRQOHLzAioiS9a47jKc1E/jGEUO7i+Je2yEnGbM
yjF0CaBS53nTy95G6s0+h+tFuArBO2lWHN3AXgio7TWdtu+/CfF9ev6qlL9LlWvY
zD2LNLdAJdLPPmf9qqmSWxwR0pfas5kqI1DHUN7J/xUZsXvkoojBGuKmt83LPmWx
3FLJc9D7IEjaanK+Z6KkgeNh8D11lOLUcuSDV3v6b9UXpXC7YTkBV1AL2QoLvF7A
l2AK6UxTSJCv1NbDYf3YR8CI3be1pREVSut2adb0/HafHbLdZyQQ6kkT7Gjl+3cJ
T/dWVE4faLxxdIZLJ9fSk6OvxYlZPVj0qEJpAIlPLVAKQhc0doMZgoZORlMwI7T8
pyZytwFGTBNaTHPzV1okbjxnCkaNal8LxTQnEqXiCd2FQac+uls0PbVQxfNJkTUT
7ejw+U1XxFQ8nelmB08t
=FUvI
-----END PGP SIGNATURE-----