<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Tim,<br>
<br>
We sure we can fix it and we know how. The only problem is to
somehow get a hand with reviewing and approvals speed? Is there any
remedy for this? I've asked Michael already above in the thread, but
I don't presume that it's possible even to allow one of us to become
core reviewer for EC2 part of the nova? Or is it?<br>
<br>
Best regards,<br>
Alex Levine<br>
<br>
<div class="moz-cite-prefix">On 1/30/15 10:57 PM, Tim Bell wrote:<br>
</div>
<blockquote
cite="mid:5D7F9996EA547448BC6C54C8C5AAF4E5010271A184@CERNXCHG41.cern.ch"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
span.im
{mso-style-name:im;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoPlainText">Alex,<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Many thanks for the constructive
approach. I've added an item to the list for the Ops meetup in
March to see who would be interested to help.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">As discussed on the change, it is likely
that there would need to be some additional Nova APIs added to
support the full EC2 semantics. Thus, there would need to
support from the Nova team to enable these additional
functions. Having tables in the EC2 layer which get out of
sync with those in the Nova layer would be a significant
problem in production.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">I think this would merit a good slot in
the Vancouver design sessions so we can also discuss
documentation, migration, packaging, configuration management,
scaling, HA, etc.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Tim<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm
0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"
lang="EN-US">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"
lang="EN-US"> matt [<a class="moz-txt-link-freetext" href="mailto:matt@nycresistor.com">mailto:matt@nycresistor.com</a>]
<br>
<b>Sent:</b> 30 January 2015 20:44<br>
<b>To:</b> Alexandre Levine<br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:foundation@lists.openstack.org">foundation@lists.openstack.org</a>; OpenStack
Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [OpenStack Foundation]
[openstack-dev] Finding people to work on the EC2 API
in Nova<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">+1 cloudscaling has been pretty
involved in ec2 support for openstack for a long while
now.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Fri, Jan 30, 2015 at 2:27 PM,
Alexandre Levine <<a moz-do-not-send="true"
href="mailto:alevine@cloudscaling.com" target="_blank">alevine@cloudscaling.com</a>>
wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC
1.0pt;padding:0cm 0cm 0cm
6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal">Michael,<br>
<br>
Our team can take the effort. We're the ones doing the
stackforge EC2 API and we can maintain the nova's EC2
in acceptable state for the time being as well.<br>
If you can give us any permissions and leverage to not
just contribute fixes and tests but also have a say in
approval of those (maybe to just one of us) then it'll
be fast. Otherwise it'll happen in due time but our
previous attempts to contribute some fixes for EC2 API
in nova took usually more than half a year to get
through.<br>
<br>
Best regards<br>
Alex Levine<br>
<br>
<span class="im">On 1/30/15 3:01 AM, Michael Still
wrote:<o:p></o:p></span></p>
<blockquote style="border:none;border-left:solid #CCCCCC
1.0pt;padding:0cm 0cm 0cm
6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal" style="margin-bottom:12.0pt">Hi,<br>
<br>
as you might have read on openstack-dev, the Nova
EC2 API<br>
implementation is in a pretty sad state. I wont
repeat all of those<br>
details here -- you can read the thread on
openstack-dev for detail.<br>
<br>
However, we got here because no one is maintaining
the code in Nova<br>
for the EC2 API. This is despite repeated calls over
the last 18<br>
months (at least).<br>
<br>
So, does the Foundation have a role here? The Nova
team has failed to<br>
find someone to help us resolve these issues. Can
the board perhaps<br>
find resources as the representatives of some of the
largest<br>
contributors to OpenStack? Could the Foundation
employ someone to help<br>
us our here?<br>
<br>
I suspect the correct plan is to work on getting the
stackforge<br>
replacement finished, and ensuring that it is
feature compatible with<br>
the Nova implementation. However, I don't want to
preempt the design<br>
process -- there might be other ways forward here.<br>
<br>
I feel that a continued discussion which just
repeats the last 18<br>
months wont actually fix the situation -- its time
to "break out" of<br>
that mode and find other ways to try and get someone
working on this<br>
problem.<br>
<br>
Thoughts welcome.<br>
<br>
Michael<o:p></o:p></p>
</blockquote>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">_______________________________________________<br>
Foundation mailing list<br>
<a moz-do-not-send="true"
href="mailto:Foundation@lists.openstack.org"
target="_blank">Foundation@lists.openstack.org</a><br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation"
target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation</a><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>