Open Stack

I agree that having options in how you specify your configuration would be nice.
I see that your change is to add yaml support, not replace INI, so that's a plus.
Specifically with regards to ansible, you're correct that the ini_file module is sub-optimal, we've recently changed our playbooks away from ini_file to template, because we found that we couldn't properly enforce the contents of the config files with ini only.

That said, I can understand why people are hesitant to allow this, as shown in the review, some of the questions about documentation and tooling are good points.

> On Feb 1, 2016, at 8:54 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:
> https://review.openstack.org/259000
> 
> 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
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160201/5eb9b3b4/attachment.pgp>