<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=us-ascii">
<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-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi Robert,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I see you have enough volunteers. You can put me on the backup list in case somebody drops out or you need additional bodies.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Regards<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">…Juerg<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<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""> Boris Pavlovic [mailto:bpavlovic@mirantis.com]
<br>
<b>Sent:</b> Sunday, November 24, 2013 8:09 PM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [Nova][Schduler] Volunteers wanted for a modest proposal for an external scheduler in our lifetime<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Robert, <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Btw, I would like to be a volunteer too=)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Boris Pavlovic <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Sun, Nov 24, 2013 at 10:43 PM, Robert Collins <<a href="mailto:robertc@robertcollins.net" target="_blank">robertc@robertcollins.net</a>> wrote:<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">On 22 November 2013 23:55, Gary Kotton <<a href="mailto:gkotton@vmware.com">gkotton@vmware.com</a>> wrote:<br>
><br>
><br>
<br>
>>> I'm looking for 4-5 folk who have:<br>
>>> - modest Nova skills<br>
>>> - time to follow a fairly mechanical (but careful and detailed work<br>
>>> needed) plan to break the status quo around scheduler extraction<br>
><br>
> I would be happy to take part. But prior I think that we need to iron out<br>
> a number of issues:<o:p></o:p></p>
</div>
<p class="MsoNormal">Cool! Added your name to the list of volunteers, which brings us to 4,<br>
the minimum I wanted before starting things happening.<o:p></o:p></p>
<div>
<p class="MsoNormal"><br>
> 1. Will this be a new service that has an API, for example will Nova be<o:p></o:p></p>
</div>
<p class="MsoNormal">> able to register a host and provide the host statistics.<br>
<br>
This will be an RPC api initially, because we know the performance<br>
characteristics of the current RPC API, and doing anything different<br>
to that is unnecessary risk. Once the new structure is:<br>
* stable<br>
* gated with unit and tempest tests<br>
* with a straightforward and well documented migration path for deployers<br>
<br>
Then adding a RESTful API could take place.<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
> 2. How will the various components interact with the scheduler - same as<br>
> today - that is RPC? Or a REST API? The latter is a real concern due to<br>
> problems we have seen with the interactions of nova and other services<o:p></o:p></p>
</div>
<p class="MsoNormal">RPC initially. REST *only* once we've avoided second system syndrome.<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
> 3. How will current developments fit into this model?<o:p></o:p></p>
</div>
<p class="MsoNormal">Code sync - take a forklift copy of the code, and apply patches to<br>
both for the one cycle.<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
> All in all I think that it is a very good and healthy idea. I have a<br>
> number of reservations - these are mainly regarding the implementation and<br>
> the service definition.<br>
><br>
> Basically I like the approach of just getting heads down and doing it, but<br>
> prior to that I think that we just need to understand the scope and mainly<br>
> define the interfaces and how they can used/abused and consumed. It may be<br>
> a very good topic to discuss at the up and coming scheduler meeting - this<br>
> may be in the middle of the night for Robert. If so then maybe we can<br>
> schedule another time.<o:p></o:p></p>
</div>
<p class="MsoNormal">Tuesdays at 1500 UTC - I'm in UTC+13 at the moment, so thats 0400<br>
local. A leeeetle early for me :) I'll ping you on IRC about resolving<br>
the concerns you raise, and you can proxy my answers to the sub group<br>
meeting?<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
> Please note that this is scheduling and not orchestration. That is also<br>
> something that we need to resolve.<o:p></o:p></p>
</div>
<p class="MsoNormal">Yup, sure is.<br>
<br>
-Rob<o:p></o:p></p>
<div>
<p class="MsoNormal"><br>
--<br>
Robert Collins <<a href="mailto:rbtcollins@hp.com">rbtcollins@hp.com</a>><br>
Distinguished Technologist<br>
HP Converged Cloud<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><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>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>