<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">04.12.2013 11:57, Christopher Yeoh
пишет:<br>
</div>
<blockquote
cite="mid:CANCY3eezdmWVqf3EMRmJC2CHA5Ae7boki=7TjDTGceWCKRH0gQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Wed, Dec 4, 2013 at 5:22 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">
<div text="#000000" bgcolor="#FFFFFF"> It is not a problem
to update the code in given direction when the decision
is made. As I understood right now it's not about the
code - that's why I'd canceled the code review until the
blueprint is accepted - it's more about architecture and
procedures such as which tests should be obligatory and
alike. <br>
<br>
My vision of architecture when we'd started the project
was: <br>
Yes, eventually GCE API as well as EC2 should be a
separate service because of the following reasons:<br>
1. It covers wider functionality than compute - in fact
it covers almost the whole cloud. That's why both EC2
and GCE have to go to Neutron, Cinder and other services
out of the nova boundaries to perform tasks not related
to compute at all.<br>
2. Nova is quite big already and has lots of services.
It'll be great to disintegrate it a little bit for
simplicity, loose coupling and such other reasons. <br>
<br>
But:<br>
As long as EC2 is in the nova other alike APIs might
stay there as well. And it is rather a different task to
separate them from it. <br>
</div>
</blockquote>
<div><br>
</div>
<div>It does add a small amount of overhead to making
changes to internal Nova apis as in addition to making the
appropriate changes to the native Nova API and EC2,
patches will also have to modify the GCE API as well.<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Agree.<br>
<br>
<blockquote
cite="mid:CANCY3eezdmWVqf3EMRmJC2CHA5Ae7boki=7TjDTGceWCKRH0gQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> <br>
The thing is - we can make GCE API a separate service
but we need to be told about that. Some decisions should
be made so that we could react or we won't have time and
might miss even Icehouse.<br>
<br>
</div>
</blockquote>
<div><br>
</div>
<div>Apologies if I've missed an answer to this question
before, but would it be possible to sit the GCE API on top
of the Nova REST API which has much higher guarantees of
stability compared to the internal Nova APIs?<br>
</div>
<div><br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
It is totally possible to sit the GCE API on top of the Nova,
Neutron, Cinder and other REST APIs. In fact It is already on top of
other REST APIs except for Nova services which we'd implemented as
it's done in EC2 for uniformity's sake.<br>
<br>
<blockquote
cite="mid:CANCY3eezdmWVqf3EMRmJC2CHA5Ae7boki=7TjDTGceWCKRH0gQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>Chris<br>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
Best regards,<br>
Alex Levine<br>
<br>
<br>
<blockquote
cite="mid:CANCY3eezdmWVqf3EMRmJC2CHA5Ae7boki=7TjDTGceWCKRH0gQ@mail.gmail.com"
type="cite">
<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>