[openstack-dev] [TripleO] *ExtraConfig, backwards compatibility & deprecation

Giulio Fidente gfidente at redhat.com
Wed Sep 14 16:32:07 UTC 2016


On 09/14/2016 05:59 PM, Giulio Fidente wrote:
> On 09/14/2016 02:31 PM, Steven Hardy wrote:
>> Related to this is the future of all of the per-role customization
>> interfaces.  I'm thinking these don't really make sense to maintain
>> long-term now we have the new composable services architecture, and it
>> would be better if we can deprecate them and move folks towards the
>> composable services templates instead?
>
> my experience is that the ExtraConfig interfaces have been useful to
> provide arbitrary hiera and class includes
>
> I wonder if we could ship by default some roles parsing those parameters?

thinking more about it, the *ExtraConfig interfaces also offer a simple 
mechanism to *override* any hiera setting we push via the templates ... 
which isn't easy to achieve with roles

a simple short-term solution could be to merge ExtraConfig in the $role 
mapped_data, thoughts?

while to move in a more container-aware condition we could probably have 
some $serviceExtraConfig param mapped into each service?
-- 
Giulio Fidente
GPG KEY: 08D733BA | IRC: gfidente



More information about the OpenStack-dev mailing list