<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:Cambria;
        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:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:"Comic Sans MS";
        panose-1:3 15 7 2 3 3 2 2 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:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0cm;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
span.apple-style-span
        {mso-style-name:apple-style-span;}
span.EmailStyle18
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle19
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I don’t have any objections to this being exposed – but the question was should we expose it, and I don’t see any benefit to the user for this particular key. 
  Of course, as you say, a provider may want to expose many specific metadata keys.  Perhaps we should look at how to do this generically rather than special-casing the disk-config key?<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 suspect it would not be desirable to expose _<i>all</i>_ metadata keys to the guest?  I’m not sure what metadata we have at the moment, but I can certainly
 imagine adding some metadata that would be best to stay private in the future.<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">Bob<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>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Richard Goodwin [mailto:richard.goodwin@RACKSPACE.COM]
<br>
<b>Sent:</b> 18 June 2013 15:25<br>
<b>To:</b> OpenStack Development Mailing List<br>
<b>Subject:</b> Re: [openstack-dev] Discussion around blueprint https://blueprints.launchpad.net/nova/+spec/add-disk-config-to-xenstore<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Bob,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">They could do extra deduction/guessing work to infer that, but it's a valid piece of metadata from the base image, so I'm concerned why there's so much discussion
 about exposing it? Seems like a provider could have a reason for exposing any number of metadata bits in the Store for their implementation needs.  In addition, it assumes that any scenario where there is some unpartitioned space, the intent is to partition
 it; but the real desire is to determine that based on the image metadata (or API parameter).<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Pardon me not having a lot of history on this process in the past.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span class="apple-style-span"><b><span style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">Richard Goodwin </span></b></span><b><span style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black"><br>
</span></b><span style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">Product Manager </span><span style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:#DA0000">–</span><span style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black"> Cloud
 Servers & Cloud Images</span><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#DA0000"><br>
</span><span class="apple-style-span"><span style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:gray">Ideation | Intellection | Activator | Relator | Responsibility</span></span><span style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:gray"><br>
</span><span class="apple-style-span"><span style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:#414141">Phone: (512) 788 5403 – Cell: (512) 736-7897 </span></span><span class="apple-style-span"><span style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:#4C4B4D">(Austin)</span></span><span style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:#4C4B4D"><br>
</span><span class="apple-style-span"><span style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:#414141">Skype:</span></span><span class="apple-style-span"><span style="font-size:9.0pt;font-family:"Cambria","serif";color:black"><a href="file:///\\callto\::rtgoodwin"><span style="font-family:"Calibri","sans-serif";text-decoration:none"> rtgoodwin</span></a></span></span><span class="apple-style-span"><span style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:#414141"> -
 Yahoo: </span></span><span class="apple-style-span"><span style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:blue"><a href="file:///\\ymsgr\sendim%3Frichardtgoodwin"><span style="color:#414141">richardtgoodwin</span></a> </span></span><span style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:blue"><br>
</span><span class="apple-style-span"><span style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:#414141">AIM: dellovision - IRC: goody / rgoodwin</span></span><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">From:
</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Bob Ball <<a href="mailto:bob.ball@citrix.com">bob.ball@citrix.com</a>><br>
<b>Reply-To: </b>OpenStack Development Mailing List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<b>Date: </b>Tuesday, June 18, 2013 4:31 AM<br>
<b>To: </b>OpenStack Development Mailing List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<b>Subject: </b>Re: [openstack-dev] Discussion around blueprint <a href="https://blueprints.launchpad.net/nova/+spec/add-disk-config-to-xenstore">
https://blueprints.launchpad.net/nova/+spec/add-disk-config-to-xenstore</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I’m not sure I understand why the user might want to access the disk_config value from within the guest?</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">This seems to be something they could infer from the partition structure – i.e. if the whole drive is partitioned then disk_config was AUTO when the instance
 was created.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Bob</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> Navneet Kumar [<a href="mailto:navneetk@thoughtworks.com">mailto:navneetk@thoughtworks.com</a>]
<br>
<b>Sent:</b> 18 June 2013 04:52<br>
<b>To:</b> <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
<b>Subject:</b> [openstack-dev] Discussion around blueprint <a href="https://blueprints.launchpad.net/nova/+spec/add-disk-config-to-xenstore">
https://blueprints.launchpad.net/nova/+spec/add-disk-config-to-xenstore</a></span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Hi,</span><span style="color:black"><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#333333">disk_config has been introduced by the extension 'DiskConfig'( [[</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><a href="http://docs.rackspace.com/openstack-extensions/compute/rax-dcf/content/rax-dcf.pdf" target="_blank"><span style="font-size:9.0pt;color:#0033AA;text-decoration:none">http://docs.rackspace.com/openstack-extensions/compute/rax-dcf/content/rax-dcf.pdf</span></a></span><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#333333">]]
 ) .This extension exposes api to set and retrieve the disk_config values ( either 'MANUAL" or "AUTO' ) .As a user one wants to access the value of disk_config from inside of instance but currently there is no way to get the value of disk_config from inside
 of instance.<br>
To get any metadata/userdata of the instance a config drive ( [[</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><a href="http://docs.openstack.org/trunk/openstack-compute/admin/content/config-drive.html" target="_blank"><span style="font-size:9.0pt;color:#0033AA;text-decoration:none">http://docs.openstack.org/trunk/openstack-compute/admin/content/config-drive.html</span></a></span><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#333333">]]
 ) can be attached to the instance during boot-up.So disk_drive information can also be included in the config drive.</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#333333">Should we include this value in the config drive and xen store as well ?</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="color:black">-- <br>
-----------------------------<br>
</span><b><i><span style="font-family:"Comic Sans MS";color:#666666">Navneet Kumar</span></i></b><span style="color:black"><br>
</span><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:silver">Application Developer<br>
Thoughtworks India<br>
Mob: +91 9686577076</span><span style="font-family:"Arial","sans-serif";color:#666666"><br>
<br>
<br>
</span><span style="color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>