<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">I wrote the app-catalog-ui plugin. I was going to bring this up but hadn't gotten to it yet. Thanks for bringing it up.<br>
<br>
We do package it up in an rpm, so if its installed with the rest of the packages it should just work. The horizon compress/collect rpm hook does the right thing already. It does cause it to be enabled though, so I was thinking, maybe we make a docker environment
variable ENABLED_PLUGINS that contains a list of plugins to be enabled?<br>
<br>
The value of ENABLED_PLUGINS could be written into /etc/openstack-dashboard/local-settings.d and the plugins could enable themselves based on it?<br>
<br>
I'd rather have the horizon container be bigger then needed and have all the plugins test/ready to go as needed instead of trying to slide the plugins in myself. Its kind of a pain.<br>
<br>
Thanks,<br>
Kevin<br>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div style="direction: ltr;" id="divRpF187118"><font face="Tahoma" color="#000000" size="2"><b>From:</b> Dave Walker [email@daviey.com]<br>
<b>Sent:</b> Sunday, July 03, 2016 1:15 PM<br>
<b>To:</b> OpenStack Development Mailing List<br>
<b>Subject:</b> [openstack-dev] [kolla][horizon] Out of branch horizon plugins?<br>
</font><br>
</div>
<div></div>
<div>
<div dir="ltr">Hi,
<div><br>
</div>
<div>Whilst writing a Kolla plugin, I noticed some issues with the way Horizon is configured in Kolla.</div>
<div><br>
</div>
<div>Horizon is increasingly embracing a plugin architecture with UI's and Dashboards being maintained outside of Horizon's tree.</div>
<div><br>
</div>
<div>These can be found with the type:horizon-plugin tag in openstack/governance [0], with 16 projects at current.</div>
<div><br>
</div>
<div>This isn't really addressed in Kolla, and is a little awkward to integrate as the horizon docker image is pure horizon.</div>
<div><br>
</div>
<div>Some projects have a tools/register_plugin.sh which performs the grunt work, where as others require a workflow similar to: </div>
<div><br>
</div>
<div>
<div>cp /path/to/projects/new/panel openstack_dashboard/local/enabled/</div>
<div>cp /path/to/local/defualt/settings openstack_dashboard/local/local_settings.d/</div>
<div>cp /path/to/*policy.json openstack_dashboard/conf/</div>
<div># compress if environment wants it</div>
<div>./manage.py collectstatic</div>
<div>./manage.py compress</div>
</div>
<div><br>
</div>
<div>(Separately, it would be nice if this was standardised.. but not the topic of this thread)</div>
<div><br>
</div>
<div>It would seem logical to pack all of these into the horizon docker image, and add a symlink into dashboard/local/enabled via ansible, policy.json and default settings with some conditionals if enabled_$service... but this will make the horizon docker image
larger and more complicated.</div>
<div><br>
</div>
<div>What are your thoughts?</div>
<div><br>
</div>
<div>[0] <a href="http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml" target="_blank">
http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml</a><br>
</div>
<div><br>
</div>
<div>--</div>
<div>Kind Regards,</div>
<div>Dave Walker</div>
</div>
</div>
</div>
</div>
</body>
</html>