<html><head></head><body 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><div><div>...</div></div></div><span id="OLK_SRC_BODY_SECTION"><div><br></div><blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"><div><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><div dir="auto"><div>On "production-grade":</div><div id="AppleMailSignature"><br></div><div>I'd be (strongly) in favor of defining a target deployment configuration and size which we find representative of the minimum bar for "production-grade." Anything less concrete and specific becomes more nuisance than help. I'd hope that specs might look
like the following:</div><div><br></div><div>- tests must be run against an OpenStack-certified cloud containing at minimum 20 compute nodes, 1 TB block storage, 1 TB object storage</div><div>- tests must demonstrate service responsiveness, stability, and reliability while VMs, compute volumes, object store objects, and networks are created/destroyed at a rate of 50/second in any combination while maintaining 99.9%+ service availability, <1%
error rate, and response latency of <100ms </div><div>- tests must demonstrate service resiliency when faced with common component failures such as: compute node failure, storage failure, network failure, etc.</div></div></div></blockquote></span><div><br></div><div>The scale could be defined on the basis of the survey data. The reference implementation should be able to address at least X% of deployments. I can think of at least one project which was not suitable for use at a reasonable size configuration and not being able to demonstrate this would have saved a lot of grief in the ops community as well as ensuring the project addressed the issue early.</div><div><br></div><span id="OLK_SRC_BODY_SECTION"><blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"><div><div dir="auto"><div><br></div><div>(all numbers here are to show the level of specificity needed, are completely made up, and should be chosen more appropriately than that)</div><div><br></div><div>I also think these are things that we should be regularly testing for core OpenStack services, and that I'd be happy to see as part of DefCore someday.</div><div><br></div><div>--j</div><br><blockquote type="cite"><span id="OLK_SRC_BODY_SECTION"><blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"><div><div><div dir="ltr"><div class="gmail_extra"><div><br></div><div>For a time many projects used SQLite as a reference implementation for testing DB functionality, and have moved away from that (completely? I'm not sure) as we all agree it really is not a production-grade implementation. That is an easy example, but
as a community we have crossed this bridge multiple times already and will be able to do it again.</div></div></div></div></div></blockquote></span><div><br></div><div>This could also be covered by needing scaleable as well as fully-functional and production grade. Again, it would be subjective but it would avoid reference implementations that only work at devstack scale.</div><div><br></div><div>Tim</div><div><br></div><span id="OLK_SRC_BODY_SECTION"><blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"><div><div><div dir="ltr"><div class="gmail_extra"><div><br></div><div>dt</div><div><br></div>
-- <br><div class="gmail_signature"><br>
Dean Troyer<br><a href="mailto:dtroyer@gmail.com" target="_blank">dtroyer@gmail.com</a><br></div></div></div></div></div></blockquote></span></blockquote><blockquote type="cite"><div><span>__________________________________________________________________________</span><br><span>OpenStack Development Mailing List (not for usage questions)</span><br><span>Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe</span><br><span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></span><br></div></blockquote></div></div></blockquote></span></body></html>