[OpenStack-DefCore] Scale.4 Summary, Scale.5 2/18 @ 9am PT & F2F 2/20 in Austin

Robert Esker esker at me.com
Tue Feb 17 22:27:02 UTC 2015


Rob et al,

What’s the address for the Friday F2F?  Is there a meeting invite I might have missed?

Thanks,
Rob Esker


> On Feb 11, 2015, at 1:39 PM, Hirschfeld, Rob <rob at zehicle.com> wrote:
> 
> ## Summary (by Rob Hirschfeld)
> 
> Great turn out and discussions (over 16 people on the roll)
> we continue to plan weekly meetings until we're granted Liberty (sorry, release puns)
> Egle Sigler appointed co-chair by unanimous consent
> Set 2/20 in Austin for Face to Face meeting (https://etherpad.openstack.org/p/DefCoreScale.F2F) <https://etherpad.openstack.org/p/DefCoreScale.F2F)>
> agenda will be discussed on mailing list
> Proposed using github.com/openstack/defcore for DefCore artifacts – Chris Hoge will lead
> Capabilities are having weekly meetings Wed @ 11 PT (updates in notes)
> We began to review the process document and found some places where it needed to be updated
> Next meeting will focus on process review
> 
> 
> Copied from: https://etherpad.openstack.org/p/DefCoreScale.4
> 
> 
> 
> 
> ## Roll call
> 
> Mark T. Voelker (VMware)
> Chris Lee (DreamHost)
> Vince Brunssen (IBM)
> Egle Sigler (Rackspace)
> Joe Savak (Rackspace)
> Will Auld (Intel)
> VanL (Rackspace)
> AlanClark(SUSE)
> Rob Hirschfeld (RackN, CoChair)
> Phil Estes (IBM)
> Chris Hoge (OpenStack Foundation)
> Thierry Carrez (OpenStack Foundation) (lurking at the beginning)
> Shamail Tahir (EMC)
> Sean Roberts (VMware)
> jbryce
> Russell Bryant (Red Hat)
> 
> ## Cycle.4 Agenda
> 
> selection of co-chair
> review f2f > https://etherpad.openstack.org/p/DefCoreScale.F2F <https://etherpad.openstack.org/p/DefCoreScale.F2F>
> Location of repository for Defcore standards, process documents, and tools.
> Brief summary of capabilities meetings to date
> capabilities controversial items list
> collecting vendor feedback from Capabilities testing
> discuss process document > https://docs.google.com/document/d/1rekLXVuyXUxV1zWWxvpVaaS_8MSxGUqUp0bvC1C2prU/edit?usp=sharing <https://docs.google.com/document/d/1rekLXVuyXUxV1zWWxvpVaaS_8MSxGUqUp0bvC1C2prU/edit?usp=sharing>
> 
> Capabilities Meeting @ 11 PT > call in info?
> ## Selection of Co-Chair
> 
> DECISION: Egle accepted as Co-chair by unanimous consent
> 
> ## Face 2 Face Agenda
> ACTION: Settled on DateTBD: Location (preference is the Foundation HQ)
> https://etherpad.openstack.org/p/DefCoreScale.F2F <https://etherpad.openstack.org/p/DefCoreScale.F2F>
> 
> ## Location of DefCore artifacts
> They are currently in Refstack – that is not proving to be a very clear or logical place for the community.
> So far, expectation is they are Gerrit review items and should be in the openstack git namespace (refstack is stackforge)openstack/defcore sounds like a sane optionhttp://git.openstack.org/cgit/openstack/governance/tree/reference/technical-committee-repos.yaml <http://git.openstack.org/cgit/openstack/governance/tree/reference/technical-committee-repos.yaml> (each repo below openstack/ needs a parent team, so adding it in that file makes it accounted for, but defcore committee would have full approval rights there of course)example repo: https://github.com/openstack/governance <https://github.com/openstack/governance>< suggestion is to use openstack/defcore
> Google docs for draft, approval on git ?
> DefCore Co-Chairs would be cores (+2) with the ability to allow other contributors (as cores +2)OpenStack Board would be listed as the team owning the DefCore repo.list it in reference/board-repos.yaml instead so that it's clearly a board-owned repo.
> Current location: https://github.com/stackforge/refstack/tree/master/defcore <https://github.com/stackforge/refstack/tree/master/defcore>
> ACTION: [ Chris H to own proposal & creating the repo ]
> 
> propose to openstackdev mailing list for comment
> work with tc to create board ownership list (in openstack/governance repo)
> create openstack/defcore repository as part of board ownership list with co-chairs as core members
> 
> ## Capabilities Meetings
> 
> 2 meetings so far
> Andrew Hately & Catherine D (RefStack Core) from IBM has a preliminary test list
> https://github.com/stackforge/refstack/tree/master/defcore <https://github.com/stackforge/refstack/tree/master/defcore>
> Icehouse: https://github.com/stackforge/refstack/blob/master/defcore/icehousecore.json <https://github.com/stackforge/refstack/blob/master/defcore/icehousecore.json>
> Juno: https://github.com/stackforge/refstack/blob/master/defcore/junocore.json <https://github.com/stackforge/refstack/blob/master/defcore/junocore.json>
> Todd Moore going through icehouse
> Grooming for controversial items (eliminate the consensus items quickly)
> Reaching out to PTLs to see if capabilities need to be rescored
> Capabilities review/grouping needs to be based on the changes to the list
> Missing Areas! Keystone ?? need to create more tests ??
> https://etherpad.openstack.org/p/keystone-defcore <https://etherpad.openstack.org/p/keystone-defcore>
> 
> - Meeting information:
> Icehouse Capabilities Googlesheet:
> https://docs.google.com/spreadsheet/ccc?key=0Ags6GY_6T6qqdDBFOUNfdGs1VF85NmU3WjZXeFd3bGc&usp=sharing <https://docs.google.com/spreadsheet/ccc?key=0Ags6GY_6T6qqdDBFOUNfdGs1VF85NmU3WjZXeFd3bGc&usp=sharing>
> Anyone with that link has the ability to edit.
> 
> 
> Capabilities Call-in information:
> 855.600.7225 (primary call-in)
> 212.231.7004 (secondary call-in)
> 4625040# (conference code)
> https://etherpad.openstack.org/p/defcore-capabilities-feb-11-2015 <https://etherpad.openstack.org/p/defcore-capabilities-feb-11-2015>
> 
> Weekly meetings, Wed 11-11:30am PST
> 
> Side Note: Refstack like next week 2/18 in South Bay afternoon
> 
> 
> ## DefCore Process
> 
> https://docs.google.com/document/d/1rekLXVuyXUxV1zWWxvpVaaS_8MSxGUqUp0bvC1C2prU/edit#heading=h.gqn73w9yzkli <https://docs.google.com/document/d/1rekLXVuyXUxV1zWWxvpVaaS_8MSxGUqUp0bvC1C2prU/edit#heading=h.gqn73w9yzkli>
> needs to be updated from TC feedback on long term ownership of capabilities
> needs to be reviewed, fully prepped for the F2F by next week's meeting
> tags likely the way to define groupings
> TC will start the tag groups first, then defcore take over long term
> TC Delegates are Russell, Thierry, and Monty
> _______________________________________________
> 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/20150217/0d3f488a/attachment.html>


More information about the Defcore-committee mailing list