On 7 August 2013 18:08, Uri Simchoni <[email protected]> wrote: > Hi, > > As far as I can tell (from testing and looking at the code, at least for > libvirt driver), the config drive is not rebuilt after initial spawning > (except for some migration scenarios), which means the guest cannot see > updates to its metadata. > > Is this a valid statement, and would it make sense to have the disk rebuilt > on events such as suspend/resume or stop/start?
Thats certainly my understanding and one of the reasons I dislike it :). Being able to update it when the guest is restarted would be an improvement IMO - but note that the EC2 metadata service is largely static too; thats something I'd like to see us change (e.g. making ssh keys more dynamic)... but thats a different story. I suggest putting a blueprint together, as the exact places where it's safe to update an instance-mounted image will need careful identification. -Rob -- Robert Collins <[email protected]> Distinguished Technologist HP Converged Cloud _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
