<div dir="ltr"><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Got it. Thanks.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">
Regards,</div><div class="gmail_default" style="font-size:small">Mandeep</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Apr 20, 2014 at 11:49 PM, Mike Scherbakov <span dir="ltr"><<a href="mailto:mscherbakov@mirantis.com" target="_blank">mscherbakov@mirantis.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">That's because spec was proposed to the juno/ folder. Look at <a href="https://raw.githubusercontent.com/openstack/neutron-specs/master/doc/source/index.rst" target="_blank">https://raw.githubusercontent.com/openstack/neutron-specs/master/doc/source/index.rst</a>, if spec is in juno/ folder, then contents shows it as approved one.<div>
<br></div><div>Once merged, it means approved, right? So it is going to be Ok after merge. Though a better reminding than just "draft" in the url could be required if many start to mess it up...</div></div><div class="HOEnZb">
<div class="h5"><div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, Apr 21, 2014 at 10:43 AM, Kevin Benton <span dir="ltr"><<a href="mailto:blak111@gmail.com" target="_blank">blak111@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Yes. It shows up in the approved section since it's just a build of the patch as-is.<div><br></div><div>The link is titled gate-neutron-specs-docs in the message from Jenkins.</div><div><br></div><div>
--</div>
<div>Kevin Benton</div></div><div class="gmail_extra"><div><div><br><br><div class="gmail_quote">On Sun, Apr 20, 2014 at 11:37 PM, Mandeep Dhami <span dir="ltr"><<a href="mailto:dhami@noironetworks.com" target="_blank">dhami@noironetworks.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-size:small">Just for clarification. Jenkins link in the description puts the generated HTML in the section "<span style="color:rgb(62,67,73);font-family:Arial,sans-serif;font-size:14px;line-height:1.5em">Juno approved specs</span>" even tho' the blueprint is still being reviewed. Am I looking at the right link?</div>
<div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Regards,</div><div class="gmail_default" style="font-size:small">Mandeep</div></div><div><div>
<div class="gmail_extra">
<br><br><div class="gmail_quote">On Sun, Apr 20, 2014 at 10:54 PM, Mike Scherbakov <span dir="ltr"><<a href="mailto:mscherbakov@mirantis.com" target="_blank">mscherbakov@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Yes, thanks, that's exactly what I was looking for!</div><div class="gmail_extra"><div><div><br><br><div class="gmail_quote">On Mon, Apr 21, 2014 at 12:03 AM, Kyle Mestery <span dir="ltr"><<a href="mailto:mestery@noironetworks.com" target="_blank">mestery@noironetworks.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On Sat, Apr 19, 2014 at 5:11 PM, Mike Scherbakov<br>
<<a href="mailto:mscherbakov@mirantis.com" target="_blank">mscherbakov@mirantis.com</a>> wrote:<br>
> Hi Kyle,<br>
> I built template and it looks awesome. We are considering to use same<br>
> approach for Fuel.<br>
><br>
> My assumption is that spec will be on review for a negotiation time, which<br>
> is going to be quite a while. In my opinion, it is not always very<br>
> convenient to read spec in gerrit.<br>
><br>
</div>Agreed, though for some specs, this is actually an ok way to do reviews.<br>
<div><br>
> Did you guys have any thoughts on auto-build these specs into html on every<br>
> patch upload? So we could go somewhere and see built results, without a<br>
> requirement to fetch neutron-specs, and run tox? The possible drawback is<br>
> that reader won't see gerrit comments..<br>
><br>
</div>I followed what Nova was going and committed code into<br>
openstack-infra/config which allows for some jenkins jobs to run when<br>
we commit to the neutron-specs gerrit. [1]. As an example, look at<br>
this commit here [2]. If you look at the latest Jenkins run, you'll<br>
see a link which takes you to an HTML generated document [3] which you<br>
can review in lieu of the raw restructured text in gerrit. That will<br>
actually generate all the specs in the repository, so you'll see the<br>
"Example Spec" along with the Nuage one I used for reference here.<br>
<br>
Hope that helps!<br>
Kyle<br>
<br>
[1] <a href="https://review.openstack.org/#/c/88069/" target="_blank">https://review.openstack.org/#/c/88069/</a><br>
[2] <a href="https://review.openstack.org/#/c/88690/" target="_blank">https://review.openstack.org/#/c/88690/</a><br>
[3] <a href="http://docs-draft.openstack.org/90/88690/3/check/gate-neutron-specs-docs/fe4282a/doc/build/html/" target="_blank">http://docs-draft.openstack.org/90/88690/3/check/gate-neutron-specs-docs/fe4282a/doc/build/html/</a><br>
<div><div><br>
> Thanks,<br>
><br>
><br>
> On Sat, Apr 19, 2014 at 12:08 AM, Kyle Mestery <<a href="mailto:mestery@noironetworks.com" target="_blank">mestery@noironetworks.com</a>><br>
> wrote:<br>
>><br>
>> Hi folks:<br>
>><br>
>> I just wanted to let people know that we've merged a few patches [1]<br>
>> to the neutron-specs repository over the past week which have updated<br>
>> the template.rst file. Specifically, Nachi has provided some<br>
>> instructions for using Sphinx diagram tools in lieu of <a href="http://asciiflow.com" target="_blank">asciiflow.com</a>.<br>
>> Either approach is fine for any Neutron BP submissions, but Nachi's<br>
>> patch has some examples of using both approaches. Bob merged a patch<br>
>> which shows an example of defining REST APIs with attribute tables.<br>
>><br>
>> Just an update for anyone proposing BPs for Juno at the moment.<br>
>><br>
>> Thanks!<br>
>> Kyle<br>
>><br>
>> [1]<br>
>> <a href="https://review.openstack.org/#/q/status:merged+project:openstack/neutron-specs,n,z" target="_blank">https://review.openstack.org/#/q/status:merged+project:openstack/neutron-specs,n,z</a><br>
>><br>
>> _______________________________________________<br>
>> OpenStack-dev mailing list<br>
>> <a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">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>
><br>
><br>
><br>
> --<br>
> Mike Scherbakov<br>
> #mihgen<br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">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>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">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>
</div></div></blockquote></div><br><br clear="all"><div><br></div></div></div><span><font color="#888888">-- <br><div dir="ltr"><div>Mike Scherbakov</div><div>#mihgen</div></div>
</font></span></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">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></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">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></blockquote></div><br><br clear="all"><div><br></div>-- <br></div></div><span><font color="#888888"><div>Kevin Benton</div>
</font></span></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">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></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><div>Mike Scherbakov</div><div>#mihgen</div></div>
</div>
</div></div><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>
<br></blockquote></div><br></div>