Open Stack

Another question about this, Kyle:

once merged, will there be a place where to read these approved specs, or
should we run it locally? I tried to find the approved *nova-specs *in
docs.openstack.org, but I couldn't find them.

Regards,
jaume


On 21 April 2014 09:02, Mandeep Dhami <dhami at noironetworks.com> wrote:

>
> Got it. Thanks.
>
> Regards,
> Mandeep
>
>
> On Sun, Apr 20, 2014 at 11:49 PM, Mike Scherbakov <
> mscherbakov at mirantis.com> wrote:
>
>> That's because spec was proposed to the juno/ folder. Look at
>> https://raw.githubusercontent.com/openstack/neutron-specs/master/doc/source/index.rst,
>> if spec is in juno/ folder, then contents shows it as approved one.
>>
>> 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...
>>
>>
>> On Mon, Apr 21, 2014 at 10:43 AM, Kevin Benton <blak111 at gmail.com> wrote:
>>
>>> Yes. It shows up in the approved section since it's just a build of the
>>> patch as-is.
>>>
>>> The link is titled gate-neutron-specs-docs in the message from Jenkins.
>>>
>>> --
>>> Kevin Benton
>>>
>>>
>>> On Sun, Apr 20, 2014 at 11:37 PM, Mandeep Dhami <dhami at noironetworks.com
>>> > wrote:
>>>
>>>> Just for clarification. Jenkins link in the description puts the
>>>> generated HTML in the section "Juno approved specs" even tho' the
>>>> blueprint is still being reviewed. Am I looking at the right link?
>>>>
>>>> Regards,
>>>> Mandeep
>>>>
>>>>
>>>> On Sun, Apr 20, 2014 at 10:54 PM, Mike Scherbakov <
>>>> mscherbakov at mirantis.com> wrote:
>>>>
>>>>> Yes, thanks, that's exactly what I was looking for!
>>>>>
>>>>>
>>>>> On Mon, Apr 21, 2014 at 12:03 AM, Kyle Mestery <
>>>>> mestery at noironetworks.com> wrote:
>>>>>
>>>>>> On Sat, Apr 19, 2014 at 5:11 PM, Mike Scherbakov
>>>>>> <mscherbakov at mirantis.com> wrote:
>>>>>> > Hi Kyle,
>>>>>> > I built template and it looks awesome. We are considering to use
>>>>>> same
>>>>>> > approach for Fuel.
>>>>>> >
>>>>>> > My assumption is that spec will be on review for a negotiation
>>>>>> time, which
>>>>>> > is going to be quite a while. In my opinion, it is not always very
>>>>>> > convenient to read spec in gerrit.
>>>>>> >
>>>>>> Agreed, though for some specs, this is actually an ok way to do
>>>>>> reviews.
>>>>>>
>>>>>> > Did you guys have any thoughts on auto-build these specs into html
>>>>>> on every
>>>>>> > patch upload? So we could go somewhere and see built results,
>>>>>> without a
>>>>>> > requirement to fetch neutron-specs, and run tox? The possible
>>>>>> drawback is
>>>>>> > that reader won't see gerrit comments..
>>>>>> >
>>>>>> I followed what Nova was going and committed code into
>>>>>> openstack-infra/config which allows for some jenkins jobs to run when
>>>>>> we commit to the neutron-specs gerrit. [1]. As an example, look at
>>>>>> this commit here [2]. If you look at the latest Jenkins run, you'll
>>>>>> see a link which takes you to an HTML generated document [3] which you
>>>>>> can review in lieu of the raw restructured text in gerrit. That will
>>>>>> actually generate all the specs in the repository, so you'll see the
>>>>>> "Example Spec" along with the Nuage one I used for reference here.
>>>>>>
>>>>>> Hope that helps!
>>>>>> Kyle
>>>>>>
>>>>>> [1] https://review.openstack.org/#/c/88069/
>>>>>> [2] https://review.openstack.org/#/c/88690/
>>>>>> [3]
>>>>>> http://docs-draft.openstack.org/90/88690/3/check/gate-neutron-specs-docs/fe4282a/doc/build/html/
>>>>>>
>>>>>> > Thanks,
>>>>>> >
>>>>>> >
>>>>>> > On Sat, Apr 19, 2014 at 12:08 AM, Kyle Mestery <
>>>>>> mestery at noironetworks.com>
>>>>>> > wrote:
>>>>>> >>
>>>>>> >> Hi folks:
>>>>>> >>
>>>>>> >> I just wanted to let people know that we've merged a few patches
>>>>>> [1]
>>>>>> >> to the neutron-specs repository over the past week which have
>>>>>> updated
>>>>>> >> the template.rst file. Specifically, Nachi has provided some
>>>>>> >> instructions for using Sphinx diagram tools in lieu of
>>>>>> asciiflow.com.
>>>>>> >> Either approach is fine for any Neutron BP submissions, but Nachi's
>>>>>> >> patch has some examples of using both approaches. Bob merged a
>>>>>> patch
>>>>>> >> which shows an example of defining REST APIs with attribute tables.
>>>>>> >>
>>>>>> >> Just an update for anyone proposing BPs for Juno at the moment.
>>>>>> >>
>>>>>> >> Thanks!
>>>>>> >> Kyle
>>>>>> >>
>>>>>> >> [1]
>>>>>> >>
>>>>>> https://review.openstack.org/#/q/status:merged+project:openstack/neutron-specs,n,z
>>>>>> >>
>>>>>> >> _______________________________________________
>>>>>> >> OpenStack-dev mailing list
>>>>>> >> OpenStack-dev at lists.openstack.org
>>>>>> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> > --
>>>>>> > Mike Scherbakov
>>>>>> > #mihgen
>>>>>> >
>>>>>> > _______________________________________________
>>>>>> > OpenStack-dev mailing list
>>>>>> > OpenStack-dev at lists.openstack.org
>>>>>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>>> >
>>>>>>
>>>>>> _______________________________________________
>>>>>> OpenStack-dev mailing list
>>>>>> OpenStack-dev at lists.openstack.org
>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Mike Scherbakov
>>>>> #mihgen
>>>>>
>>>>> _______________________________________________
>>>>> OpenStack-dev mailing list
>>>>> OpenStack-dev at lists.openstack.org
>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> OpenStack-dev mailing list
>>>> OpenStack-dev at lists.openstack.org
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Kevin Benton
>>>
>>> _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>>
>> --
>> Mike Scherbakov
>> #mihgen
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140422/95ff0351/attachment.html>