<div dir="ltr">I am concerned that the wording of item #1 in this list is legislating from current practice, and in effect would stifle some important types of innovation and improvement in our architecture.<div><br></div>
<div>I'm struggling a bit to come up with an improved alternative, but I think the issue is essentially with the definition of a plugin as residing behind common code that implements an API. In particular, I don't think plugins necessarily live behind APIs, for example, I could imagine a plugin implementing a periodic cleanup task on a worker node. I can also imagine an application or framework that would enable plugins to directly expose HTTP api routes--in such a case there would be no common code implementing the API controller in the common sense of the term. </div>
<div><br></div><div>Can we use a more generic definition of plugin? To me, a plugin is a library component that implements a defined interface and can be loaded into an existing application via that application's proper configuration settings. That definition doesn't restrict the sense of a plugin to any specific technological flavor.<br>
<div>
<br></div><div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jul 23, 2013 at 6:53 AM, <span dir="ltr"><<a href="mailto:Rob_Hirschfeld@dell.com" target="_blank">Rob_Hirschfeld@dell.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple"><div><p>Board & TC,<u></u><u></u></p><p><u></u> <u></u></p><p>We has a meeting on 7/15 to continue the dialog that I felt was highly productive and incorporated the feedback you’d provided on the email lists.<span> </span>As a consequence, we’ve improved the language and expanded the number of positions to 12.<span> </span><span> </span>We tried to add new at the bottom but there were edits to every position during discussion.<u></u><u></u></p>
<p><u></u> <u></u></p><p>I’m including the positions below, but I encourage you to review on the etherpad, fix typos and make adjustments.<span> </span>Of course, dialog on email is welcome too!<u></u><u></u></p><p><u></u> <u></u></p>
<p>OSCON Face to Face Discussions are our next step before the next board meeting and expanding to the Community.<u></u><u></u></p><p><u></u> <u></u></p><p>* OSCON Wednesday 4PM just before OpenStack birthday party in Expo Hall (watch Twitter for info)<u></u><u></u></p>
<p>* OSCON Thursday 8PM at Birds of a Feather session (just after the "Distro Smackdown")<u></u><u></u></p><p><u></u> <u></u></p><p>Of course, I'm happy to have 1x1 discussions about this too.<span> </span>I’ve started a blog series to try an capture the background and process: <a href="http://wp.me/pF6d2-CN" target="_blank">http://wp.me/pF6d2-CN</a> <u></u><u></u></p>
<p><u></u> <u></u></p><p>Here are the current positions:<u></u><u></u></p><p><u></u> <u></u></p><p class="MsoNormal" style="margin-left:.25in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>1.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">SINGLE API / MULTIPLE IMPLEMENTATION MODEL (aka PLUG-IN) DESIRED FOR PROJECTS<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>1.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">OpenStack will require an open source reference base plug-in implementation for projects (if not part of OpenStack, license model for reference plug-in must be compatible).<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>2.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">Definition of a plug-in: alternate backend implementations with a common API framework that uses common _code_ to implement the API<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>3.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">This expects that projects (where technically feasible) are expected to implement a plug-in architecture. <u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>4.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">This is already in place for several projects and addresses around ecosystem support, enabling innovation<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>5.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">Reference plug-ins are, by definition, the complete capability set. It is not acceptable to have "core" features that are not functional in the reference plug-in<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.25in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>2.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">API EXTENSION MODEL EXPECTED FOR PROJECTS<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>1.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">OpenStack will follow architectures patterns that enable API extensions.<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>2.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">This will enable plug-ins to offer innovative or differentiated features without forcing changes to the reference plug-in implementation<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>3.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">This will enable the reference to expand without forcing other plug-ins to match all features and recertify<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.25in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>3.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">COMMUNITY MAINTAINED TESTS (TEMPEST?) USED AS BASIS FOR OPENSTACK MARK<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>1.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">Vendor OpenStack implementations must achieve 100% of must-have coverage? <u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>2.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">Implemented tests can be flagged as may-have requires list [Joshua McKenty]<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>3.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">Certifiers will be required to disclose their testing gaps.<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>4.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">This will put a lot of pressure on the Tempest project<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>5.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">Maintenance of the testing suite to become a core Foundation responsibility. This may require additional resources<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.25in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>4.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">VALIDIBLE REMOTE SELF-CERTIFICATION (ON DEMAND TESTING) <u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>1.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">Plug-in certification is driven by Tempest self-certification model <u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>2.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">Self-certifiers are required to publish their results<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>3.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">Self-certified are required to publish enough information that a 3rd party could build the reference implementation to pass the tests. <u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>4.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">Self-certified must include the operating systems that have been certified<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>5.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">It is prefered for self-certified implementation to reference an OpenStack reference architecture "flavor" instead of defining their own reference. (a way to publish and agree on flavors is needed)<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>6.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">The Foundation needs to define a mechanism of dispute resolution. (A trust but verify model) <u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.25in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>5.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""> SUBSTITUTE PLUG-IN IMPLEMENTATIONS OK<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>1.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">If a vendor plug-in passes all relevant tests then it can be considered a full substitute for the reference plug-in<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>2.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">If a vendor plug-in does NOT pass all relevant test then the vendor is required to include the open source reference in the implementation.<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>3.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">From the may have pick list - must have all must haves. Must haves are 'core' See number 12<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.25in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>6.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">TESTING CERTIFICATION BY PLUG-IN IF >1 REFERENCE PLUG-IN<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>1.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">Looking forward to having multiple reference plug-ins, Tempest may to distinguish between multiple reference plug-ins.<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>2.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">You can pass certification by passing just one reference test suite + the project tests. <u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>3.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">The objective for this position is to allow for future OpenStack functions that requires breaking changes to implementation<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.25in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>7.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">OPENSTACK DEFINITIONS APPLY EQUALLY TO ALL DEPLOYMENTS<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>1.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">There should not be multiple definitions of OpenStack depending on the operator (public, private, community, etc)<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>2.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">While expected that each <span>deployement</span> is <span>identifical</span>, the differences must be quantifiable.<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.25in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>8.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">DISCOVERABLITY OF COMPABILITY (VARIATION IS OK)<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>1.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">Implementations and products are allowed to have variation based on publication of <span>compatabliity</span><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>2.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">Consumers must have a way to determine how the system is different from reference (posted, discovered, <span>etc</span>)<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>3.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">Testing must respond in an appropriate way on BOTH pass and fail (the wrong return rejects the entire suite)<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>4.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">We are NOT stating which projects are required in this position<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.25in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>9.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">MUST USE OPENSTACK API IMPLEMENTATION CODE<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>1.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">Implementation's claiming the OpenStack Mark must use the API framework code<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>2.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">You are not OpenStack, if you pass all the tests but do not use the API framework<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>3.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">This prevents people from using the API without joining the community<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>4.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">This also surfaces bit-rot in "PLUGINS" to the larger community<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>5.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">This behavior improves interoperability because there is more shared code between implementation<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.25in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>10.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">API CONSUMERS SELF-CERTIFY AGAINST THE REFERENCE IMPLEMENTATION<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>1.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">As an ecosystem partner, you have a need to make a "works against OpenStack" statement that is supportable<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>2.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">API consumer can claim working against the OpenStack API if it works against any implementation passing all the "must have" tests(YES)<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>3.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">API consumers can state they are working against the OpenStack API with some "may have" items as requirements <u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>4.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">API consumers are expected to write tests that validate their required behaviors (submitted as "may have" tests)<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>5.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">The TC will decide which tests are elevated from <span>may</span>-have to must-have<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.25in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>11.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">THE "MUST-HAVE" TESTS DEFINE "OPENSTACK CORE"<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>1.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">We are NOT defining which items are on the list in this effort, just making the position that it is how we will define core<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>2.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">May-have tests include items in the integrated release, but which are not core.<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>3.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">We will have a process by which tests are elevated from <span>may</span> to must lists<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>4.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">Potentially: the User Committee will nominate tests that elevated to the board<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>5.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">Must haves - must comply with the Core criteria defined from the <span>IncUp</span> committee results<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>6.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">The OpenStack board owns the responsibility to define 'core' - to approve 'musts'<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>7.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">Projects in Incubation or pre-Incubation are not to be included in the 'may' list<u></u><u></u></span></p>
<p class="MsoNormal" style="line-height:12.0pt"><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">12. SPIDER AND CORE DEFINE A SUBSET OF ALL OPENSTACK TRADEMARKS<u></u><u></u></span></p><p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt">
<u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>1.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">a. There may be other marks that are managed separately by the foundation, and available for the platform ecosystem as per the Boards discretion<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>2.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">"OpenStack API Compatible " MARK NOT GRANTED<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>3.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">This topic is difficult to close at this time and requires a breath of testing that does not yet exist<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:12.0pt"><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><span>4.<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">This is a temporary working position that may be revisited<u></u><u></u></span></p>
<p><u></u> <u></u></p><p><u></u> <u></u></p><p><span>Rob<u></u><u></u></span></p><p><span>______________________________<u></u><u></u></span></p><p><span>Rob Hirschfeld<u></u><u></u></span></p><p><span>Sr. Distinguished Cloud Solution Architect<u></u><u></u></span></p>
<p><span>Dell | Cloud Edge, Data Center Solutions<u></u><u></u></span></p><p><span>blog <a href="http://robhirschfeld.com" target="_blank">robhirschfeld.com</a>, twitter @zehicle<u></u><u></u></span></p><p><span>Please note, I am based in the CENTRAL (-6) time zone <u></u><u></u></span></p>
<p><span><u></u> <u></u></span></p><p><u></u> <u></u></p></div></div><br>_______________________________________________<br>
OpenStack-TC mailing list<br>
<a href="mailto:OpenStack-TC@lists.openstack.org" target="_blank">OpenStack-TC@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc</a><br>
<br></blockquote></div><br></div></div></div>