<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D">Thanks to everyone for your feedback. I agree with Anthony, so will not work to recruit resources to address this in favor of higher priority features.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D">Carol<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></a></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Anthony Hobbs [mailto:ahobbs@mirantis.com]
<br>
<b>Sent:</b> Monday, February 02, 2015 11:12 AM<br>
<b>To:</b> Mark Voelker<br>
<b>Cc:</b> Cooklin, Joel R; Esker, Robert; enterprise-wg@lists.openstack.org<br>
<b>Subject:</b> Re: [Win The Enterprise-wg] [OpenStack] [Win the Enterprise] EC2 API feedback<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">I think Mark and Das hit it on the head there. It's a checkbox for managers, but due to the lack of feature parity, is not really used by the engineers. <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">My background is in utilizing AWS (I just recently started with OpenStack), but I would not want to use an AWS compatible API for OpenStack due to the parity mismatch. I'd use some middle layer as Mark suggested. I have only been at one
company that actually had two fully functional clouds (AWS and Cloud.com), and we used a 3rd party wrapper to control it (RightScale) rather than use either clouds API's.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">My "Vote" would to not prioritize AWS compatibility to allow us to focus on other issues (like our HA or upgrade stories).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Anthony Hobbs<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">SRE Operations Architect<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Mon, Feb 2, 2015 at 10:09 AM, Mark Voelker <<a href="mailto:mvoelker@vmware.com" target="_blank">mvoelker@vmware.com</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal">I’ve generally found this to usually be a “checkbox item”. E.g. customers deploying a private enterprise cloud are interested in having EC2 compatibility from the perspective that it *theoretically* allows them to hybridize workloads or
in cases where they’re not terribly familiar with all the workloads that will be running on their private cloud but want to generally make it easy for them to run on-prem vs on Amazon. From that perspective, it’s an item that shows up on wish lists more often
than it actually gets exercised, and I don’t think I’ve ever run across a situation where supporting Nova’s EC2 compatibility or not was a deal breaker. Those who are looking at repatriating workloads already heavily invested in AWS generally need more functionality
than is currently present anyway (to Das’s point). Those who are interested in using multiple clouds sometimes choose a middle layer such as Apache jClouds.<br>
<br>
At Your Service,<br>
<br>
Mark T. Voelker<br>
OpenStack Architect<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><br>
On Feb 2, 2015, at 10:39 AM, Kingshott, Daniel (Helion Professional Services.) <<a href="mailto:daniel.kingshott@hp.com">daniel.kingshott@hp.com</a>> wrote:<br>
<br>
> I agree with Das, those folks who truly need AWS compatible API's either use Eucalyptus or a 3rd party tool to which manages their AWS and Openstack deployments.<br>
><br>
> Thanks,<br>
><br>
> Dan<br>
><br>
><br>
> -----Original Message-----<br>
> From: Kamhout, Das [mailto:<a href="mailto:das.kamhout@intel.com">das.kamhout@intel.com</a>]<br>
> Sent: Friday, January 30, 2015 4:26 PM<br>
> To: Esker, Robert; Barrett, Carol L; <a href="mailto:enterprise-wg@lists.openstack.org">
enterprise-wg@lists.openstack.org</a><br>
> Cc: Cooklin, Joel R<br>
> Subject: Re: [Win The Enterprise-wg] [OpenStack] [Win the Enterprise] EC2 API feedback<br>
><br>
> From our experience, people using AWS utilize a large assortment of APIs (ELB, CloudFormation, S3, EBS, EC2, Route53), and many have chosen to use higher level tools to handle their cloud app deployments either through an abstraction layer, or through a PaaS
(RightScale, Enstratius, Cloud Forms, CloudFoundry, and now Docker, Kubernetes, MesoSphere).<br>
><br>
> Being that OpenStack doesn¹t really have full API compatibility to AWS, generally we have stuck with the native commandsŠ simple enough for the types of scripts to have variables that do get instance calls to have EC2 or Nova semantics depending on the endpoint
type.<br>
><br>
> Personally I would rather see more focus on getting OpenStack APIs consistent, backwards compatible, and working across different OpenStack deployments as a higher priority.<br>
><br>
> -Das<br>
> Intel (formerly Intel IT)<br>
><br>
> On 1/30/15, 3:42 PM, "Esker, Robert" <<a href="mailto:Rob.Esker@netapp.com">Rob.Esker@netapp.com</a>> wrote:<br>
><br>
>> Carol et al,<br>
>><br>
>> A number of our customers employ OpenStack motivated in large part for<br>
>> it¹s ability to function as an on-prem AWS of sorts (something they can<br>
>> burst from or repatriate to w/ out altering app deployment logic, or<br>
>> simply used as a target for dev tools that expect an AWS endpoint).<br>
>><br>
>> Cheers,<br>
>><br>
>> Rob Esker<br>
>> NetApp, Inc.<br>
>><br>
>><br>
>><br>
>><br>
>> On 1/30/15, 6:01 PM, "Barrett, Carol L" <<a href="mailto:carol.l.barrett@intel.com">carol.l.barrett@intel.com</a>> wrote:<br>
>><br>
>>> Hi All - I wanted to run this by you to get your input on importance<br>
>>> for our Enterprise Customers?<br>
>>> Thanks<br>
>>> Carol<br>
>>><br>
>>> -----Original Message-----<br>
>>> From: Michael Still [mailto:<a href="mailto:mikal@stillhq.com">mikal@stillhq.com</a>]<br>
>>> Sent: Thursday, January 29, 2015 4:01 PM<br>
>>> To: <a href="mailto:foundation@lists.openstack.org">foundation@lists.openstack.org</a>; OpenStack Development Mailing List<br>
>>> Subject: [OpenStack Foundation] Finding people to work on the EC2 API<br>
>>> in Nova<br>
>>><br>
>>> 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 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<br>
>>> -- 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 problem.<br>
>>><br>
>>> Thoughts welcome.<br>
>>><br>
>>> Michael<br>
>>><br>
>>> --<br>
>>> Rackspace Australia<br>
>>><br>
>>> _______________________________________________<br>
>>> Foundation mailing list<br>
>>> <a href="mailto:Foundation@lists.openstack.org">Foundation@lists.openstack.org</a><br>
>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation</a><br>
>>><br>
>>> _______________________________________________<br>
>>> Enterprise-wg mailing list<br>
>>> <a href="mailto:Enterprise-wg@lists.openstack.org">Enterprise-wg@lists.openstack.org</a><br>
>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/enterprise-wg" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/enterprise-wg</a><br>
>> _______________________________________________<br>
>> Enterprise-wg mailing list<br>
>> <a href="mailto:Enterprise-wg@lists.openstack.org">Enterprise-wg@lists.openstack.org</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/enterprise-wg" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/enterprise-wg</a><br>
><br>
><br>
> _______________________________________________<br>
> Enterprise-wg mailing list<br>
> <a href="mailto:Enterprise-wg@lists.openstack.org">Enterprise-wg@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/enterprise-wg" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/enterprise-wg</a><br>
><br>
> _______________________________________________<br>
> Enterprise-wg mailing list<br>
> <a href="mailto:Enterprise-wg@lists.openstack.org">Enterprise-wg@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/enterprise-wg" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/enterprise-wg</a><br>
<br>
<br>
_______________________________________________<br>
Enterprise-wg mailing list<br>
<a href="mailto:Enterprise-wg@lists.openstack.org">Enterprise-wg@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/enterprise-wg" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/enterprise-wg</a><o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <o:p></o:p></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Anthony Hobbs<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">SRE Operations Architect<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Mirantis Inc<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>