[openstack-dev] [oslo.config] Centralized config management
clint at fewbar.com
Sat Jan 11 02:38:48 UTC 2014
Excerpts from Nachi Ueno's message of 2014-01-10 13:42:30 -0700:
> Hi Flavio, Clint
> I agree with you guys.
> sorry, may be, I wasn't clear. My opinion is to remove every
> configuration in the node,
> and every configuration should be done by API from central resource
> manager. (nova-api or neturon server etc).
> This is how to add new hosts, in cloudstack, vcenter, and openstack.
> Cloudstack: "Go to web UI, add Host/ID/PW".
> vCenter: "Go to vsphere client, Host/ID/PW".
> - Manual
> - setup mysql connection config, rabbitmq/qpid connection config,
> keystone config,, neturon config, xxxx
> We have some deployment system including chef / puppet / packstack, TripleO
> - Chef/Puppet
> Setup chef node
> Add node/ apply role
> - Packstack
> - Generate answer file
> - packstack --install-hosts=192.168.1.0,192.168.1.1,192.168.1.2
> - TripleO
> - UnderCloud
> nova baremetal node add
> - OverCloud
> modify heat template
> For residence in this mailing list, Chef/Puppet or third party tool is
> easy to use.
> However, I believe they are magical tools to use for many operators.
> Furthermore, these development system tend to take time to support
> newest release.
> so most of users, OpenStack release didn't means it can be usable for them.
> IMO, current way to manage configuration is the cause of this issue.
> If we manage everything via API, we can manage cluster by horizon.
> Then user can do "go to horizon, just add host".
> It may take time to migrate config to API, so one easy step is to convert
> existing config for API resources. This is the purpose of this proposal.
Hi Nachi. What you've described is the vision for TripleO and Tuskar. We
do not lag the release. We run CD and will be in the gate "real soon
now" so that TripleO should be able to fully deploy Icehouse on Icehouse
More information about the OpenStack-dev