Hi Thorsten,<div><br></div><div>pvo and I have put together some rough answers to your questions at: <a href="http://etherpad.openstack.org/clouddrive">http://etherpad.openstack.org/clouddrive</a></div><div><br></div><div>
To answer your questions in short though; the rough idea for the clouddrive is a small ~64MB ISO formatted volume that would be attached and mounted read-only by the guest instance on boot. All injected-files (re: xs-inject-files), base metadata (IP addresses, passwords, etc), and custom metadata would be written into that volume on instance creation. Updates would be possible in the same manner that injected files can be updated, but would basically require the whole drive be detached and rewritten.</div>
<div><br></div><div>Thanks,</div><div>Christopher</div><div><br><div class="gmail_quote">On Sun, Jun 19, 2011 at 1:14 PM, Paul Voccio <span dir="ltr"><<a href="mailto:paul.voccio@rackspace.com">paul.voccio@rackspace.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Thorsten,<br>
<br>
I'll take a run at these since I wrote the blueprint. It was initially<br>
more of a placeholder that was going to get filled out later but Vish<br>
bumped the priority before we (Ozone) was ready to move forward. I haven't<br>
talked to Chris in regards to his implementation and I haven't seen the<br>
code yet. I'll take a look at the code and update the blueprint later<br>
tonight/tomorrow.<br>
<br>
pvo<br>
<div><div></div><div class="h5"><br>
On 6/17/11 7:03 PM, "Thorsten von Eicken" <<a href="mailto:tve@rightscale.com">tve@rightscale.com</a>> wrote:<br>
<br>
>We're very much looking forward to the new "portable configuration<br>
>drive" functionality and would like to provide feedback. If this is not<br>
>the best forum, please point me to it.<br>
><br>
>The blueprint<br>
>is: <a href="https://blueprints.launchpad.net/nova/+spec/configuration-drive" target="_blank">https://blueprints.launchpad.net/nova/+spec/configuration-drive</a><br>
>We reviewed the initial work<br>
>in:<br>
><a href="https://github.com/ChristopherMacGown/nova/commit/47c041a642ff32085b314047" target="_blank">https://github.com/ChristopherMacGown/nova/commit/47c041a642ff32085b314047</a><br>
>5d7a2a62dcb62c1a<br>
><br>
>Feedback:<br>
><br>
>1. It is not always obvious how to enumerate attached devices and the<br>
>document doesn't explicitly cover how we'd determine which attached<br>
>device represents the configuration volume. Specifically consider<br>
>Windows as well.<br>
><br>
>2. Will the configuration drive be available at boot time on a new<br>
>instance? Or does it appear "later" (that would be bad)?<br>
<br>
><br>
>3. How does one send the configuration drive content? What is the API<br>
>call where we provide the configuration information and what is the<br>
>expected format?<br>
<br>
<br>
<br>
><br>
>4. It looks like the configuration content is placed into a config.json<br>
>file, is this correct? Is that a blob passed through the API? Does it<br>
>have to be json or is that just a convention? What is the max size?<br>
><br>
>5. What are the permissions required to access the configuration drive?<br>
>Would be ideal for the content to be root/administrator accessible only<br>
>(because it may contain credentials). Can this be influenced via the API?<br>
><br>
>6. Is this device going to be read-only?<br>
><br>
>7. We need to be able to change the configuration content when<br>
>stopping&starting instances, will this be possible?<br>
><br>
>8. There is a related spec: 'instance-transport'. Is that still<br>
>relevant? Or superseded by the configuration drive?<br>
><br>
>9. Will the configuration drive contain any metadata? E.g. IP addresses,<br>
>names of available volumes, instance ID, etc.<br>
><br>
>Thanks much!<br>
>Thorsten - CTO RightScale<br>
><br>
><br>
><br>
>_______________________________________________<br>
>Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
>Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
>Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
>More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
<br>
<br>
<br>
</div></div>Confidentiality Notice: This e-mail message (including any attached or<br>
embedded documents) is intended for the exclusive and confidential use of the<br>
individual or entity to which this message is addressed, and unless otherwise<br>
expressly indicated, is confidential and privileged information of Rackspace.<br>
Any dissemination, distribution or copying of the enclosed material is prohibited.<br>
If you receive this transmission in error, please notify us immediately by e-mail<br>
at <a href="mailto:abuse@rackspace.com">abuse@rackspace.com</a>, and delete the original message.<br>
Your cooperation is appreciated.<br>
<div><div></div><div class="h5"><br>
<br>
_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div><span style="border-collapse:collapse;color:rgb(68, 68, 68);font-family:arial, sans-serif;font-size:13px">Christopher MacGown<br>Piston Cloud Computing, Inc.<br>
<a style="color:rgb(34, 34, 34)">(415) 300-0944</a><br>chris@piston.cc</span></div><br>
</div>