<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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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";}
@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">Gosha – this is wonderful news. Complements Intel interest.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I am in the Glance area .. stopped by a couple of times, the room was available 2 pm onwards.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Contact made and can continue via email and IRC.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Malini<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:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Georgy Okrokvertskhov [mailto:gokrokvertskhov@mirantis.com]
<br>
<b>Sent:</b> Friday, November 07, 2014 8:20 AM<br>
<b>To:</b> Bhandaru, Malini K<br>
<b>Cc:</b> OpenStack Development Mailing List<br>
<b>Subject:</b> Re: OVF/OVA support<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p>Hi Malini,<o:p></o:p></p>
<p>I am interested in OVa support for applications. Specifically Ova to Heat as this is whay we usually do in Murano project.<o:p></o:p></p>
<p>When is free format session for Glance? Should we add this to session etherpad?<o:p></o:p></p>
<p>Thanks,<br>
Gosha<o:p></o:p></p>
<div>
<p class="MsoNormal">On Nov 5, 2014 6:06 PM, "Bhandaru, Malini K" <<a href="mailto:malini.k.bhandaru@intel.com">malini.k.bhandaru@intel.com</a>> wrote:<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Please join us on Friday in the Glance track – free format session, to discuss supporting OVF/OVA in OpenStack.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Poll:<o:p></o:p></p>
<p>1)<span style="font-size:7.0pt"> </span>How interested are you in this feature? 0 – 10<o:p></o:p></p>
<p>2)<span style="font-size:7.0pt"> </span>Interested enough to help develop the feature?
<o:p></o:p></p>
<p> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Artifacts are ready for use.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">We are considering defining an artifact for OVF/OVA.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">What should the scope of this work be? Who are our fellow travelers?<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Intel is interested in parsing OVF meta data associated with images – to ensure that a VM image lands on the most appropriate hardware in the cloud instance, to ensure optimal performance.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">The goal is to remove the need to manually specify image meta data, allow the appliance provider to specify HW requirements, and in so doing reduce human error.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Are any partners interested in writing an OVF/OVA artifact => stack deployment? Along the lines of heat?<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">As a first pass, Intel we could at least<o:p></o:p></p>
<p>1)<span style="font-size:7.0pt"> </span>Defining artifact for OVA, parsing the OVF in it, pulling out the images therein and storing them in the glance image database and attaching meta data to the same.<o:p></o:p></p>
<p>2)<span style="font-size:7.0pt"> </span>Do not want to imply that OpenStack supports OVA/OVF -- need to be clear on this.<o:p></o:p></p>
<p>3)<span style="font-size:7.0pt"> </span>An OpenStack user could create a heat template using the images registered in step -1
<o:p></o:p></p>
<p>4)<span style="font-size:7.0pt"> </span>OVA to Heat – there may be a loss in translation! Should we attempt this?<o:p></o:p></p>
<p>5)<span style="font-size:7.0pt"> </span>What should we do with multiple volume artifacts?<o:p></o:p></p>
<p>6)<span style="font-size:7.0pt"> </span>Are volumes read-only? Or on cloning, make copies of them?
<o:p></o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>