Re: [openstack-dev] [puppet][horizon] - Add extra plugins config to puppet-horizon

[Denis Egorenko]

>
> 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@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@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-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Best Regards,
Egorenko Denis,
Senior Deployment Engineer
Mirantis
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [puppet][horizon] - Add extra plugins config to puppet-horizon

[Emilien Macchi]

On Thu, Apr 14, 2016 at 10:59 AM, Fox, Kevin M <kevin@pnnl.gov> wrote:
> Depends on horizon version I think. Mitaka gained a local_settings.d magic
> dir that plugins can drop things into.

That's a very good news, indeed. I think we target Newton and beyond.

So it seems like we can either continue to manage templates and put
them in local_settings.d directory or write a ruby provider that will
take care of one single local_settings.py.

> Thanks,
> Kevin
>
> 
> From: Marcos Fermin Lobo
> Sent: Thursday, April 14, 2016 5:52:31 AM
> To: openstack-dev@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-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Emilien Macchi

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [puppet][horizon] - Add extra plugins config to puppet-horizon

[Fox, Kevin M]

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@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [puppet][horizon] - Add extra plugins config to puppet-horizon

[Jason Guiditta]

On 14/04/16 10:16 -0400, Emilien Macchi wrote:

On Thu, Apr 14, 2016 at 9:21 AM, Denis Egorenko  wrote:

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}?



Well, not exactly puppet-{ui-plugin}. For example, we already have murano
module and it has manifests for UI plugin installation.

On a one side, in such way we are keeping all module related configuration
in one place.
On another side, all UI configuration probably should be placed in horizon
module. But in this case, we need to support in horizon module full
configuration for each UI plugin.

So, i think we can keep UI configuration in-place (in separate module) if we
have this module at all. For cases, when we need only support some UI
settings/plugins - we can keep it in puppet-horizon.

Thoughts?


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

What do you think?


I like the sound of this, keeps the file managements central like all
the _config providers, while allowing each module to specify the
parts that only it knows or cares about.

-j

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [puppet][horizon] - Add extra plugins config to puppet-horizon

[Emilien Macchi]

On Thu, Apr 14, 2016 at 9:21 AM, Denis Egorenko  wrote:
>> 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}?
>
>
> Well, not exactly puppet-{ui-plugin}. For example, we already have murano
> module and it has manifests for UI plugin installation.
>
> On a one side, in such way we are keeping all module related configuration
> in one place.
> On another side, all UI configuration probably should be placed in horizon
> module. But in this case, we need to support in horizon module full
> configuration for each UI plugin.
>
> So, i think we can keep UI configuration in-place (in separate module) if we
> have this module at all. For cases, when we need only support some UI
> settings/plugins - we can keep it in puppet-horizon.
>
> Thoughts?

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

What do you think?

> 2016-04-14 16:00 GMT+03:00 Emilien Macchi :
>>
>> On Thu, Apr 14, 2016 at 8:52 AM, Marcos Fermin Lobo
>>  wrote:
>> > 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}?
>> >
>> I don't think having a separated Puppet module for each plugin will
>> help us, maintaining a module is a lot of work.
>> One thing we could do is to have classes:
>> horizon::plugin::murano
>> horizon::plugin::foobar etc
>>
>> What do you think?
>> --
>> Emilien Macchi
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
> --
> Best Regards,
> Egorenko Denis,
> Senior Deployment Engineer
> Mirantis
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Emilien Macchi

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [puppet][horizon] - Add extra plugins config to puppet-horizon

[Denis Egorenko]

>
> 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}?


Well, not exactly puppet-{ui-plugin}. For example, we already have murano
module and it has manifests for UI plugin installation.

On a one side, in such way we are keeping all module related configuration
in one place.
On another side, all UI configuration probably should be placed in horizon
module. But in this case, we need to support in horizon module full
configuration for each UI plugin.

So, i think we can keep UI configuration in-place (in separate module) if
we have this module at all. For cases, when we need only support some UI
settings/plugins - we can keep it in puppet-horizon.

Thoughts?

2016-04-14 16:00 GMT+03:00 Emilien Macchi :

> On Thu, Apr 14, 2016 at 8:52 AM, Marcos Fermin Lobo
>  wrote:
> > 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}?
> >
> I don't think having a separated Puppet module for each plugin will
> help us, maintaining a module is a lot of work.
> One thing we could do is to have classes:
> horizon::plugin::murano
> horizon::plugin::foobar etc
>
> What do you think?
> --
> Emilien Macchi
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Best Regards,
Egorenko Denis,
Senior Deployment Engineer
Mirantis
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [puppet][horizon] - Add extra plugins config to puppet-horizon

[Emilien Macchi]

On Thu, Apr 14, 2016 at 8:52 AM, Marcos Fermin Lobo
 wrote:
> 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}?
>
I don't think having a separated Puppet module for each plugin will
help us, maintaining a module is a lot of work.
One thing we could do is to have classes:
horizon::plugin::murano
horizon::plugin::foobar etc

What do you think?
-- 
Emilien Macchi

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [puppet][horizon] - Add extra plugins config to puppet-horizon

[Marcos Fermin Lobo]

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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev