[Openstack-operators] YAML config

John Dewey john at dewey.ws
Mon Feb 1 17:08:04 UTC 2016

IMO config files should generally be managed as a template. If the files were YAML, I would still be managing them as a template. I went down the path of managing ini files with Ansible’s ini_file module, and it’s just not worth it.

On February 1, 2016 at 8:59:10 AM, Alexis Lee (lxsli at hpe.com) wrote:

Hi operators,  

I have a spec up to allow config files to be specified as YAML instead  
of INI: https://review.openstack.org/273468  

The main benefit from my perspective is being able to use YAML tooling  
to transform config (EG as part of an Ansible run). Crudini doesn't work  
well with MultiStrOpts.  

There's also a patch to allow logging config to be specified as YAML:  

The main benefit here is not having to declare your handlers, loggers  
and formatters before defining them. This has caught my team a couple of  
times when making logging changes.  

Are these features you are interested in or should I let them die?  

Alexis (lxsli)  
Nova developer, Hewlett-Packard Limited.  
Registered Office: Cain Road, Bracknell, Berkshire RG12 1HN.  
Registered Number: 00690597 England  
VAT number: GB 314 1496 79  

OpenStack-operators mailing list  
OpenStack-operators at lists.openstack.org  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160201/75436bc9/attachment.html>

More information about the OpenStack-operators mailing list