<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Joe,<br>
<br>
In regard to your first question - yes we'll be going in this
direction very soon. It's being discussed with Randy now.<br>
As for the second question - we'd love to participate in fixing it
(in fact we've done it for OCS already) and probably maintaining it
but I'm not sure what it takes and means to commit to this - we'll
discuss it as well.<br>
<br>
Best regards,<br>
Alex Levine<br>
<br>
<div class="moz-cite-prefix">24.04.2014 23:33, Joe Gordon пишет:<br>
</div>
<blockquote
cite="mid:CAHXdxOemLR29PmHVsDGwQOnu6vxcN_VQkOxXZ0KSK=+g2nZKGA@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Thu, Apr 24, 2014 at 10:10 AM,
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">Cristopher,<br>
<br>
FYI in regard to "
<div class=""><br>
<br>
Its the sort of direction that we tried to steer the GCE<br>
API folks in I<br>
cehouse, though I don't know what they ended up doing<br>
<br>
"<br>
<br>
</div>
We ended up perfectly ok. The project is on Stackforge for
some time <a moz-do-not-send="true"
href="https://github.com/stackforge/gce-api"
target="_blank">https://github.com/stackforge/gce-api</a>.
It works.<br>
I believe that this is exactly what should be done with
EC2 as well. We even considered and tried to estimate it
once.<br>
<br>
I can tell you even more that we do have lots of AWS
Tempest tests specifically to check various compatibility
issues in OpenStack. And we've created a number of fixes
for proprietary implementation of a cloud based on
OpenStack. Some of them are in EC2 layer, some are in nova
core. </blockquote>
<div><br>
</div>
<div>Any plans to contribute this to the community?</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
But anyways, I'm completely convinced that:<br>
<br>
1. Any further improvements to EC2 layer should be done
after its separation from nova. </blockquote>
<div><br>
</div>
<div>So the fundamental problem we are having with Nova's
EC2 implementation is that no one is maintaining it
upstream. If pulling EC2 out of nova into its own repo
solves this problem then wonderful. But the status quo is
untenable, Nova does not want to ship code that we know to
be broken, so we need folks interested in it to help fix
it.</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
2. EC2 should still somehow be supported by OpenStack
because as far as I know lots of people use euca2ools to
access it.</blockquote>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Best regards,<br>
Alex Levine<br>
<br>
<a moz-do-not-send="true" href="tel:24.04.2014%2019"
value="+12404201419" target="_blank">24.04.2014 19</a>:24,
Christopher Yeoh пишет:
<div class="HOEnZb">
<div class="h5"><br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
On Thu, 24 Apr 2014 09:10:19 +1000<br>
Michael Still <<a moz-do-not-send="true"
href="mailto:mikal@stillhq.com" target="_blank">mikal@stillhq.com</a>>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
These seem like the obvious places to talk to
people about helping us<br>
get this code maintained before we're forced to
drop it. Unfortunately<br>
we can't compel people to work on things, but we
can make it in their<br>
best interests.<br>
<br>
A followup question as well -- there's a proposal
to implement the<br>
Nova v2 API on top of the v3 API. Is something
similar possible with<br>
EC2? Most of the details of EC2 have fallen out of
my brain, but I'd<br>
be very interested in if such a thing is possible.<br>
</blockquote>
So there's sort of a couple of ways we suggested
doing a V2 API on top<br>
of V3 long term. The current most promising proposal
(and I think<br>
Kenichi has covered this a bit in another email) is
a very thin layer<br>
inside the Nova API code. This works well because
the V2 and V3 APIs in<br>
many areas are very closely related anyway - so
emulation is<br>
straightforward.<br>
<br>
However there is another alternative (which I don't
think is necessary<br>
for V2) and that is to have a more fuller fledged
type proxy where<br>
translation is say done between receiving V2
requests and translating<br>
them to native V3 API requests. Responses are
similarly translated but<br>
in reverse. Its the sort of direction that we tried
to steer the GCE<br>
API folks in Icehouse, though I don't know what they
ended up doing -<br>
IIRC I think they said it would be possible.<br>
<br>
Longer term I suspect its something we should
consider if we could do<br>
something like that for the EC2 API and then be able
to rip out the<br>
ec2 API specific code from the nova API part of
tree. The messiness of<br>
any UUID or state map translation perhaps could then
be handled in a<br>
very isolated manner from the core Nova code (though
I won't pretend to<br>
understand the specifics of what is required here).
I guess the<br>
critical question will be if the emulation of the
EC2 API is good<br>
enough, but as Sean points out - there are lots of
existing issues<br>
already so it may end up not perfect, but still much
better than what we<br>
have now.<br>
<br>
Chris<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>
<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>
</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>