On 02/17/2017 07:05 PM, Clint Byrum wrote:
Excerpts from Michael Still's message of 2017-02-18 09:41:03 +1100:
We have had this discussion several times in the past for other reasons.
The reality is that some people will never deploy the metadata API, so I
feel like we need a better solution than what we have now.
However, I would consider it probably unsafe for the hypervisor to read the
current config drive to get values, and persisting things like the instance
root password in the Nova DB sounds like a bad idea too.
Agreed. What if we simply have a second config drive that is for "things
that change" and only rebuild that one on reboot?
Or not.
Why are we trying to reinvent configuration management systems in Nova?
-jay
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
