<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Thank you for the clarification, yes I know about the
blueprint/specification, I submitted yet them and the spec is
currently under review :)<br>
<br>
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 or something similar that explain these steps, but
I didn't find anything in wiki or documentation.<br>
<br>
In particular I noticed I had to modify the file
nova/nova.egg-info/entry_points.txt to make my v3 api to load, but
this file seems not to be under versioning, is this file modified
only after the changes are merged?<br>
<br>
<div class="moz-cite-prefix">On 11/16/14 23:55, Christopher Yeoh
wrote:<br>
</div>
<blockquote
cite="mid:CANCY3eeXv4FQnnOTv4Bcw=Zri-b6Dp7-2LjGk4LY_YJ_z48uHw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Thu, Nov 13, 2014 at 12:14 AM,
Pasquale Porreca <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:pasquale.porreca@dektech.com.au"
target="_blank">pasquale.porreca@dektech.com.au</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hello<br>
<br>
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?<br>
<br>
</blockquote>
<div><br>
</div>
<div>You need now to have at least a v2.1 (formerly known as
v3) extension. V2 support if you want but I think once
v2.1 is fully merged and tested (which may not be that far
away at all) we should freeze v2 and rely just on v2.1 for
new features. Otherwise the interaction between v2.1 being
exactly equivalent to v2 plus having microversion support
for v2.1 will get a bit confusing.</div>
<div> </div>
<div>As the other Chris mentioned, the first step however is
to get a nova-spec submitted which needs to fully describe
the API additions that you want to make. </div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Chris</div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
BR<br>
<br>
-- <br>
Pasquale Porreca<br>
<br>
DEK Technologies<br>
Via dei Castelli Romani, 22<br>
00040 Pomezia (Roma)<br>
<br>
Mobile <a moz-do-not-send="true"
href="tel:%2B39%203394823805" value="+393394823805"
target="_blank">+39 3394823805</a><br>
Skype paskporr<br>
<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:OpenStack-dev@lists.openstack.org"
target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a moz-do-not-send="true"
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>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Pasquale Porreca
DEK Technologies
Via dei Castelli Romani, 22
00040 Pomezia (Roma)
Mobile +39 3394823805
Skype paskporr</pre>
</body>
</html>