<div dir="ltr"><div class="gmail_extra">Added -<div> <a href="https://github.com/devananda/ironic-specs/commit/7f34f353332ad5b26830dadc8c9f870df399feb7">https://github.com/devananda/ironic-specs/commit/7f34f353332ad5b26830dadc8c9f870df399feb7</a></div>
<div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_quote">On Sun, May 18, 2014 at 6:13 PM, Robert Collins <span dir="ltr"><<a href="mailto:robertc@robertcollins.net" target="_blank">robertc@robertcollins.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">I'd like to suggest two things.<br>
<br>
Firstly a section on scale (as opposed to performance).<br>
<br>
Secondly, I'd like to see additional hard requirements that will be<br>
added to drivers called out (e.g. a 'Driver Impact' section).<br>
<br>
-Rob<br>
<div><div class="h5"><br>
On 19 May 2014 10:03, Devananda van der Veen <<a href="mailto:devananda.vdv@gmail.com">devananda.vdv@gmail.com</a>> wrote:<br>
> Hi all,<br>
><br>
> As with several other projects, and as discussed at the summit, Ironic is<br>
> moving to a formal / specs-based design process. The reasons for this have<br>
> been well summarized in previous email threads in other projects [*], but in<br>
> short, it's because, until now, nearly all our blueprints lacked a design<br>
> specification which could be compared to the proposed code, resulting in the<br>
> code-review also being a design-review. This week, I will be resetting the<br>
> "Definition" status of all blueprints to "New", and require everything to go<br>
> through a specs review process -- yes, even the ones that were previously<br>
> approved.<br>
><br>
> I've proposed the creation of the openstack/ironic-specs repo here:<br>
> <a href="https://review.openstack.org/#/c/94113/" target="_blank">https://review.openstack.org/#/c/94113/</a><br>
><br>
> And put up an initial version on github to start the process:<br>
> <a href="https://github.com/devananda/ironic-specs" target="_blank">https://github.com/devananda/ironic-specs</a><br>
> <a href="https://github.com/devananda/ironic-specs/blob/master/specs/template.rst" target="_blank">https://github.com/devananda/ironic-specs/blob/master/specs/template.rst</a><br>
><br>
> I've begun sketching out specs proposals for some of the essential-for-juno<br>
> items, which can be found in the above repo for now, and will be proposed<br>
> for review once the openstack/ironic-specs repository is created.<br>
><br>
> For what it's worth, I based this on the Nova specs repo, with some<br>
> customization geared towards Ironic (eg, I removed "notifications" section<br>
> and added some comments regarding hardware). At this point, I'd like<br>
> feedback from other core reviewers and folks familiar with the specs<br>
> process. Please think about the types of architectural changes you look for<br>
> during code reviews and make sure the specs template addresses them, and<br>
> that they apply to Ironic.<br>
><br>
> I will focus on creating and landing the specs for items essential for<br>
> graduation first and then prioritize review of additional feature specs<br>
> based on the community feedback we received at the Juno Design Summit. I<br>
> will send another email soliciting the community members and vendors to<br>
> propose specs for the features they are working on once the initial work on<br>
> the repo is complete (hopefully before end-of-week).<br>
><br>
> Regards,<br>
> Devananda<br>
><br>
><br>
> [*] eg.:<br>
> <a href="http://lists.openstack.org/pipermail/openstack-dev/2014-April/032753.html" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/2014-April/032753.html</a><br>
><br>
</div></div>> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<span class=""><font color="#888888"><br>
<br>
<br>
--<br>
Robert Collins <<a href="mailto:rbtcollins@hp.com">rbtcollins@hp.com</a>><br>
Distinguished Technologist<br>
HP Converged Cloud<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</font></span></blockquote></div><br></div></div>