[OpenStack-DefCore] Draft 2015.03 Spec

Shamail itzshamail at gmail.com
Thu Feb 26 07:26:41 UTC 2015


+1



> On Feb 26, 2015, at 1:14 AM, Rob Hirschfeld <rob at zehicle.com> wrote:
> 
> I'd like to get some +1s on the list about the new guidelines concept.
> 
> I was planning a write up tomorrow (Thurs) morning.  If you were on the call today and liked what we talked about, please send a +1 on this thread and we'll accelerate reporting to the board.
> 
> Let's plan to tell the board on Friday that we'll present capabilities for a vote.
> 
> 
>> On 02/25/2015 05:11 PM, Van Lindberg 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
> 
> -- 
>   
> 
> Rob
> ____________________________
> Rob Hirschfeld, 512-773-7522
> 
> I am in CENTRAL (-6) time
> http://robhirschfeld.com
> twitter: @zehicle, github: cloudedge & ravolt 
> _______________________________________________
> Defcore-committee mailing list
> Defcore-committee at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/defcore-committee/attachments/20150226/e501a1a7/attachment-0001.html>


More information about the Defcore-committee mailing list