openstack team mailing list archive

[Tim Bell <Tim.Bell@xxxxxxx>]

Puppet is great for this sort of thing. There are various ways of querying
parameters and making choices about them. A typical example would be where
you want to adjust a configuration parameter due to memory configuration or
network.

Writing the puppet configuration is not difficult... Puppetlabs have an
excellent and actively maintained configuration suite on the puppetforge for
OpenStack along with tutorial videos.

Chef support is also there so there is choice. The DevOps panel gives some
discussion around this
(http://www.openstack.org/summit/san-diego-2012/openstack-summit-sessions/pr
esentation/devops-panel)

I think building an openstack specific database for configuration would be
hard work to include all of the flexibility that Puppet offers.  It is worth
having a good look at puppet or chef before starting this.

Tim

> 
> @Jon - I am happy that these ideas resonate with you. My moot point is
that
> the metadata should be within the openstack implementation and not
outside.
> I am not very familiar with Puppet - is there a way to query the
parameters set
> in the conf file. I would think that Puppet would be given a conf file to
deploy.
> The values within the conf file would still remain abstracted and not be
readily
> available. Please correct me if I'm wrong in my presumption. Having the
> parameters with their default values in the data store would allow a
better
> understanding of the different configuration parameters. Also if its in a
> database then dependency and relationship rules or even constraints
> (permissible values) could be defined.
>

Attachment: smime.p7s
Description: S/MIME cryptographic signature