<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:"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:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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]--></head><body lang=EN-GB link="#0563C1" vlink="#954F72"><div class=WordSection1><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><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'>Mike,<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><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'>Is this something that will be added into OpenStack or made available as open source through something like stackforge ?<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><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 lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> Mike Spreitzer [mailto:mspreitz@us.ibm.com] <br><b>Sent:</b> 20 September 2013 03:27<br><b>To:</b> OpenStack Development Mailing List<br><b>Subject:</b> Re: [openstack-dev] Medium Availability VMs<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><tt><span style='font-size:10.0pt'>> From: Tim Bell <<a href="mailto:Tim.Bell@cern.ch">Tim.Bell@cern.ch</a>></span></tt> <br><tt><span style='font-size:10.0pt'>> ...</span></tt> <br><tt><span style='font-size:10.0pt'>> Discussing with various people in the community, there seems to be </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> interest in a way to</tt></span> <br><tt><span style='font-size:10.0pt'>> </span></tt> <br><tt><span style='font-size:10.0pt'>> - Identify when a hypervisor is being drained or is down </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> and inventory its VMs</tt></span> <br><tt><span style='font-size:10.0pt'>> - Find the best practise way of restarting that VM for </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> hypervisors still available</tt></span> <br><tt><span style='font-size:10.0pt'>> o Live migration</span></tt> <br><tt><span style='font-size:10.0pt'>> o Cold migration</span></tt> <br><tt><span style='font-size:10.0pt'>> - Defining policies for the remaining cases</span></tt> <br><tt><span style='font-size:10.0pt'>> o Restart from base image</span></tt> <br><tt><span style='font-size:10.0pt'>> o Suspend</span></tt> <br><tt><span style='font-size:10.0pt'>> o Delete</span></tt> <br><tt><span style='font-size:10.0pt'>> </span></tt> <br><tt><span style='font-size:10.0pt'>> This touches multiple components from Nova/Cinder/Quantum (at minimum).</span></tt> <br><tt><span style='font-size:10.0pt'>> </span></tt> <br><tt><span style='font-size:10.0pt'>> It also touches some cloud architecture questions if OpenStack can </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> start to move into the low hanging fruit parts of service consolidation.</tt></span> <br><tt><span style='font-size:10.0pt'>> </span></tt> <br><tt><span style='font-size:10.0pt'>> I’d like to have some form of summit discussion in Hong Kong around </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> these topics but it is not clear where it fits.</tt></span> <br><tt><span style='font-size:10.0pt'>> </span></tt> <br><tt><span style='font-size:10.0pt'>> Are there others who feel similarly ? How can we fit it in ?</span></tt> <br><br><tt><span style='font-size:10.0pt'>When there are multiple viable choices, I think direction should be taken from higher layers. The operation of draining a hypervisor can be parameterized, the VMs themselves can be tagged, by an indication of which to do.</span></tt> <br><br><tt><span style='font-size:10.0pt'>I myself am working primarily on holistic infrastructure scheduling, which includes quiescing and draining hypervisors among the things it can do. Holistic scheduling works under the direction of a template/pattern/topology that describes a set of interacting resources and their relationships, and so is able to make a good decision about where VMs should move to.</span></tt> <br><br><tt><span style='font-size:10.0pt'>Re-starting a VM can require software coordination.</span></tt> <br><br><tt><span style='font-size:10.0pt'>I think holistic infrastructure scheduling is logically downstream from software coordination and upstream from infrastructure orchestration. I think the ambitions for Heat are expanding to include the latter two, and so must also have something to do with holistic infrastructure scheduling.</span></tt> <br><br><tt><span style='font-size:10.0pt'>Regards,</span></tt> <br><tt><span style='font-size:10.0pt'>Mike</span></tt> <o:p></o:p></p></div></div></body></html>