On Tue, 3 Jul 2012, Vishvananda Ishaya wrote: > > The config drive was a later addition because we thought it might be useful. > The plan was to add it to the metadata server once we had a /openstack > available. > > > >> The main difference between user-data and metadata is that metadata is > >> available to the api, whereas user-data is only available in the guest. > > > > So to avoid confusion, if the intent was tags, I think we should disable > > the 'meta.js' file injection, and get over the screams now. > > > > half and half is just confusing. > > > > Thoughts? > > Seems much more useful in metadata server than in config drive, but we should > probably keep the same semantics we have been discussing > > i.e. the same values are in both places. Config drive is information as it > was during > launch and metadata is current information.
That does make sense. The only thing that is confusing is its similarity to user-data. putting it in the MD then leads us to the other thread/request ([Openstack] Setting VM passwords when not running on Xen) of having it be writable from the instance. _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
