<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Yes, I understand it perfectly, Cristopher, and cannot agree more.
It's just more work to reach this right now than use what's present.
Still in my opinion even in a mid-run just till IceHouse release it
might be less work overall. <br>
I'm going to think it over.<br>
<br>
Alex<br>
<br>
<div class="moz-cite-prefix">10.12.2013 17:47, Christopher Yeoh
пишет:<br>
</div>
<blockquote
cite="mid:CANCY3eeV8nLGyryL7o5vDm2MAsGNMy-_Wc8iZtQm4OLJOEE9uQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Tue, Dec 10, 2013 at 11:36 PM,
Alexandre Levine <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:alevine@cloudscaling.com" target="_blank">alevine@cloudscaling.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Russell,<br>
<br>
I'm a little confused about importing it into stackforge
repository. Please clarify it for me.<br>
Right now our code is a part of nova itself, adding lots
of files and changing several of existing, namely:
service.py, cmd/api.py, setup.cfg, api-paste.ini and
nova.conf.sample. This is only the core. Also our
functional code for some marginal GCE API functionality
has to use database (to store naming translation).<br>
So for creating the stackforge repository we have 3
different options with different costs in terms of
additional labor:<br>
1. Create the copy of nova and add GCE as a part of it. -
I don't fill it to be a customary way for such additions
but it'll be the least costly for us.<br>
2. Separate our code from nova leaving it its part still.
Stackforge repository will contain only GCE code. It'd be
installed after the nova is installed, create another nova
service, change api-paste.ini and nova.conf, create tables
in nova DB (or create its own DB, I'm not sure here). This
will require some changes for the present code but not
many though.<br>
3. Completely separate GCE and make it a standalone
service using nova via REST. The most costly options for
us now. Still doable as well.<br>
<br>
</blockquote>
<div><br>
</div>
<div>In the long run I suspect that option 3 will probably
be the least work for everyone. Why be dependent on
changes to Nova's internal APIs unless you really have to
when you have the alternative of being dependent on a much
more stable REST API?<br>
<br>
</div>
<div>Chris<br>
</div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Alex<br>
<br>
06.12.2013 22:43, Russell Bryant пишет:
<div class="im HOEnZb"><br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
On 12/02/2013 02:06 PM, Eric Windisch wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
What more is needed from the blueprint or the patch
authors to proceed?<br>
</blockquote>
I finally got back to looking at this. Here is how I
would like to<br>
proceed with GCE.<br>
<br>
1) Stackforge<br>
<br>
It seems like this code is pretty self contained. I'd
like to see it<br>
imported into a stackforge repository. Then, I'd like
to see jenkins<br>
jobs showing that both the unit tests and the
functional tests written<br>
for this are passing. It will also help keep the code
up to date with<br>
Nova while it's not in the main tree.<br>
<br>
2) Support from nova-core<br>
<br>
Taking on a new API in Nova has a significant ongoing
maintenance<br>
impact. I'm assuming that the submitters are willing
to help maintain<br>
the code. We also need commitment from some subset of
nova-core to<br>
review this code.<br>
<br>
So, what do folks from nova-core think? Are you on
board with<br>
maintaining this API?<br>
<br>
</blockquote>
<br>
<br>
</div>
<div class="HOEnZb">
<div class="h5">
_______________________________________________<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>
</div>
</div>
</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>
</body>
</html>