[openstack-dev] MultiStrOpt opts can be problematic...
Dan Prince
dprince at redhat.com
Wed Aug 28 17:51:06 UTC 2013
So I recently ran into a fun config issue in trying to configure Nova to work w/ Ceilometer using Puppet:
https://bugs.launchpad.net/puppet-ceilometer/+bug/1217867
Today, what you need to do to make Nova work with ceilometer is add this to your nova.conf file:
notification_driver=nova.openstack.common.notifier.rpc_notifier
notification_driver=ceilometer.compute.nova_notifier
As it turns out Multi-line config entries aren't very fun to deal with in the config management world. The puppet nova_config provider doesn't (yet) have a good way to support them. The core of the issue is they pose all sorts of problems in knowing whether a given tool should modify the existing config values.
In the short term we can look into doing one of these Puppet land:
-Using a conf.d directory for config (would require a change to the nova-compute init script to use --config-dir)
-String together various resources in puppet to "make it work", etc. (file_line, augeus, etc)
Long term though I'm thinking what if MultiStrOpt's were to go away? They seem to be more trouble than they are worth...
Dan
More information about the OpenStack-dev
mailing list