<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>+1<br><br><br></div><div><br>On Feb 26, 2015, at 1:14 AM, Rob Hirschfeld <<a href="mailto:rob@zehicle.com">rob@zehicle.com</a>> wrote:<br><br></div><blockquote type="cite"><div>
  
    <meta content="text/html; charset=windows-1252" http-equiv="Content-Type">
  
  
    I'd like to get some +1s on the list about the new guidelines
    concept.<br>
    <br>
    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.<br>
    <br>
    Let's plan to tell the board on Friday that we'll present
    capabilities for a vote.<br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 02/25/2015 05:11 PM, Van Lindberg
      wrote:<br>
    </div>
    <blockquote cite="mid:D113B3B0.1D629%25van.lindberg@rackspace.com" type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <div>Should we forward this on to the board?</div>
      <div><br>
      </div>
      <span id="OLK_SRC_BODY_SECTION">
        <div style="font-family:Calibri; font-size:11pt;
          text-align:left; color:black; BORDER-BOTTOM: medium none;
          BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT:
          0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;
          BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
          <span style="font-weight:bold">From: </span>Van Lindberg <<a moz-do-not-send="true" href="mailto:van.lindberg@rackspace.com">van.lindberg@rackspace.com</a>><br>
          <span style="font-weight:bold">Date: </span>Wednesday,
          February 25, 2015 at 1:51 PM<br>
          <span style="font-weight:bold">To: </span>"<a moz-do-not-send="true" href="mailto:defcore-committee@lists.openstack.org">defcore-committee@lists.openstack.org</a>"
          <<a moz-do-not-send="true" href="mailto:defcore-committee@lists.openstack.org">defcore-committee@lists.openstack.org</a>><br>
          <span style="font-weight:bold">Cc: </span>Egle Sigler <<a moz-do-not-send="true" href="mailto:egle.sigler@rackspace.com">egle.sigler@rackspace.com</a>>,
          Adrian Otto <<a moz-do-not-send="true" href="mailto:adrian.otto@rackspace.com">adrian.otto@rackspace.com</a>><br>
          <span style="font-weight:bold">Subject: </span>[OpenStack-DefCore]
          Draft 2015.03 Spec<br>
        </div>
        <div><br>
        </div>
        <div>
          <div style="word-wrap: break-word; -webkit-nbsp-mode: space;
            -webkit-line-break: after-white-space; color: rgb(0, 0, 0);
            font-size: 14px; font-family: Calibri, sans-serif;">
            <div>Hello all</div>
            <div><br>
            </div>
            <div>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:</div>
            <div><br>
            </div>
            <div><a moz-do-not-send="true" href="https://etherpad.openstack.org/p/defcore-draft-spec-2015.03">https://etherpad.openstack.org/p/defcore-draft-spec-2015.03</a></div>
            <div><br>
            </div>
            <div>Notes:</div>
            <div>- 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.</div>
            <div>- This is .rst formatted and designed for human
              consumption. There is a linked (and also authoritative)
              .json file for machine consumption.</div>
            <div>- The .json file (draft in gdoc for easy multi-editing
              right now) has everything that is not mandatory or
              advisory removed.</div>
            <div>- 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.</div>
            <div>- We need designated sections for keystone.</div>
            <div><br>
            </div>
            <div>Thanks,</div>
            <div>Van</div>
            <div><br>
            </div>
          </div>
        </div>
      </span>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Defcore-committee mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Defcore-committee@lists.openstack.org">Defcore-committee@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee">http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee</a>
</pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
  

Rob
____________________________
Rob Hirschfeld, 512-773-7522

I am in CENTRAL (-6) time
<a class="moz-txt-link-freetext" href="http://robhirschfeld.com">http://robhirschfeld.com</a>
twitter: @zehicle, github: cloudedge & ravolt </pre>
  

</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Defcore-committee mailing list</span><br><span><a href="mailto:Defcore-committee@lists.openstack.org">Defcore-committee@lists.openstack.org</a></span><br><span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee">http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee</a></span><br></div></blockquote></body></html>