Open Stack

>
> Does Murano uses the same local_settings.py file as Horizon? If yes,
> we might stop using puppet-murano to manage this file.


Yes, it uses same file.

And maybe find a mechanism in puppet-horizon with a provider, so we
> can have a plugin architecture like:
> horizon::plugins::murano
> horizon::plugins::foobar
> that would use this provider to configure a common local_settings.py
> and notify service on change, like we do for .conf files.


That's idea for researching, sounds good. We can implement something like
*_config providers for conf files.

Also, another question. If we will move all UI stuff to puppet-horizon, do
we need
add some dependency for changed modules on horizon module?
Right now, modules with UI configuration don't have dependency on horizon.
May be we need to add it?

Depends on horizon version I think. Mitaka gained a local_settings.d magic
> dir that plugins can drop things into.


That's a really good. We can use a separate file for each plugin then and
pass it to provider.

2016-04-14 17:59 GMT+03:00 Fox, Kevin M <Kevin.Fox at pnnl.gov>:

> Depends on horizon version I think. Mitaka gained a local_settings.d magic
> dir that plugins can drop things into.
>
> Thanks,
> Kevin
>
> ------------------------------
> *From:* Marcos Fermin Lobo
> *Sent:* Thursday, April 14, 2016 5:52:31 AM
> *To:* openstack-dev at lists.openstack.org
> *Subject:* [openstack-dev] [puppet][horizon] - Add extra plugins config
> to puppet-horizon
>
> Hi all,
>
> I have a question about puppet-horizon module and UI plugins for Horizon.
>
> Some of UI plugins, like murano-dashboard, needs to add extra parameters
> https://github.com/openstack/murano-dashboard/blob/master/muranodashboard/local/local_settings.py.example
> to local_settings file (which comes from Horizon).
>
> My question is: Should puppet-horizon module provide those extra
> parameters coming from each official UI plugins? or this kind of things
> should come from specific a puppet-{ui-plugin}?
>
> Thanks.
>
> Cheers,
> Marcos
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Best Regards,
Egorenko Denis,
Senior Deployment Engineer
Mirantis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160414/d4c55d55/attachment-0001.html>