<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 11/20/2013 03:54 PM, Clint Byrum
wrote:<br>
</div>
<blockquote cite="mid:1384915934-sup-3222@clint-HP" type="cite">
<pre wrap="">Excerpts from Robert Collins's message of 2013-11-19 16:22:41 -0800:
</pre>
<blockquote type="cite">
<pre wrap="">On 20 November 2013 13:00, Sean Dague <a class="moz-txt-link-rfc2396E" href="mailto:sean@dague.net"><sean@dague.net></a> wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">As long as the metadataservice doesn't move out :) - that one I think
is pretty core and we have no native replacement [configdrive is not a
replacement :P].
</pre>
</blockquote>
<pre wrap="">
Slightly off tangent thread.
So we recently moved devstack gate to do con fig drive instead of metadata
service, and life was good (no one really noticed). In what ways is
configdrive insufficient compared to metadata service? And is that something
that we should be tackling?
</pre>
</blockquote>
<pre wrap="">
* The metadata service can be trivially updated live - and Heat wants
to use this to get rid of it's own metadata service... whereas config
drive requires unplugging the device, updating the data and replugging
- and thats a bit more invasive.
</pre>
</blockquote>
<pre wrap="">
This one is key. Both Trove and Savanna have run into the same
limitation as Heat: networks that cannot reach the API endpoints don't
get to have their API specific Metadata that updates over time. By
putting it in the EC2 metadata service, we can access it via the Neutron
proxy and then Heat/Trove/Savanna can update it later to provide a
control bus for in-instance tools.
</pre>
</blockquote>
I've got some nova changes which I will resurrect when I get the
chance.<br>
<br>
They allow nova instance userdata to be updated via the nova API:<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="https://review.openstack.org/#/c/53732/">https://review.openstack.org/#/c/53732/</a><br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="https://review.openstack.org/#/c/49971/">https://review.openstack.org/#/c/49971/</a><br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="https://review.openstack.org/#/c/49973/">https://review.openstack.org/#/c/49973/</a><br>
<br>
<br>
</body>
</html>