<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 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:宋体;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@font-face
{font-family:"\@宋体";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* 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.25in 1.0in 1.25in;}
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-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Sergey and Michael, thanks for explaining these.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">-Ken<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></a></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Sergey Lukjanov [mailto:slukjanov@mirantis.com]
<br>
<b>Sent:</b> Tuesday, March 31, 2015 12:00 AM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [Sahara] Question about Sahara API v2<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Agree with Mike, thx for the link.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Mon, Mar 30, 2015 at 4:55 PM, michael mccune <<a href="mailto:msm@redhat.com" target="_blank">msm@redhat.com</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">On 03/30/2015 07:02 AM, Sergey Lukjanov wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">My personal opinion for API 2.0 - we should discuss design of all object<br>
and endpoint, review how they are used from Horizon or<br>
python-saharaclient and improve them as much as possible. For example,<br>
it includes:<br>
<br>
* get rid of tons of extra optional fields<br>
* rename Job -> Job Template, Job Execution -> Job<br>
* better support for Horizon needs<br>
* hrefs<br>
<br>
If you have any ideas ideas about 2.0 - please write them up, there is a<br>
99% chance that we'll discuss an API 2.0 a lot on Vancouver summit.<o:p></o:p></p>
</blockquote>
<p class="MsoNormal"><br>
+1<br>
<br>
i've started a pad that we can use to collect ideas for the discussion: <a href="https://etherpad.openstack.org/p/sahara-liberty-api-v2" target="_blank">
https://etherpad.openstack.org/p/sahara-liberty-api-v2</a><br>
<br>
things that i'd like to see from the v2 discussion<br>
<br>
* a full endpoint review, some of the endpoints might need to be deprecated or adjusted slightly (for example, job-binary-internals)<br>
<br>
* a technology review, should we consider Pecan or stay with Flask?<br>
<br>
* proposals for more radical changes to the api; use of micro-versions akin to nova's plan, migrating the project id into the headers, possible use of swagger to aid in auto-generation of api definitions.<br>
<br>
i think we will have a good amount to discuss and i will be migrating some of my local notes into the pad over this week and the next. i invite everyone to add their thoughts to the pad for ideas.<br>
<br>
mike<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><o:p></o:p></p>
</div>
</div>
</blockquote>
</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>
<p class="MsoNormal">Sincerely yours,<br>
Sergey Lukjanov<br>
Sahara Technical Lead<br>
(OpenStack Data Processing)<br>
Principal Software Engineer<br>
Mirantis Inc.<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>