On Tue, Nov 18, 2014 at 2:31 AM, Pasquale Porreca <
pasquale.porr...@dektech.com.au> wrote:
> Thank you very much Christopher
>
> On 11/17/14 12:15, Christopher Yeoh wrote:
>
>> Yes, sorry documentation has been on our todo list for too long. Could I
>> get you to submit a bug report about the lac
Thank you very much Christopher
On 11/17/14 12:15, Christopher Yeoh wrote:
Yes, sorry documentation has been on our todo list for too long. Could
I get you to submit a bug report about the lack of developer
documentation for api plugins? It might hurry us up :-)
I reported as a bug and subscr
On Mon, Nov 17, 2014 at 7:30 PM, Pasquale Porreca <
pasquale.porr...@dektech.com.au> wrote:
> Thank you for the clarification, yes I know about the
> blueprint/specification, I submitted yet them and the spec is currently
> under review :)
>
> I noticed there are several steps one has always to d
Thank you for the clarification, yes I know about the
blueprint/specification, I submitted yet them and the spec is currently
under review :)
I noticed there are several steps one has always to do to enable and
make a v3 api to work and pass the tests. It would be awesome to have a
guideline
On Thu, Nov 13, 2014 at 12:14 AM, Pasquale Porreca <
pasquale.porr...@dektech.com.au> wrote:
> Hello
>
> I am working on an api for a new feature in nova, but I am wondering what
> is the correct way to add a new extension: should it be supported by v2, v3
> or both?
>
>
You need now to have at le
Do you have a blueprint for the new feature? If you want it accepted
upstream, you'll need a blueprint and spec:
https://wiki.openstack.org/wiki/Blueprints#Spec_.2B_Blueprints_lifecycle
On Wed, Nov 12, 2014 at 2:44 PM, Pasquale Porreca <
pasquale.porr...@dektech.com.au> wrote:
> Hello
>
> I am
