Open Stack

Hi,

Whilst writing a Kolla plugin, I noticed some issues with the way Horizon
is configured in Kolla.

Horizon is increasingly embracing a plugin architecture with UI's and
Dashboards being maintained outside of Horizon's tree.

These can be found with the type:horizon-plugin tag in openstack/governance
[0], with 16 projects at current.

This isn't really addressed in Kolla, and is a little awkward to integrate
as the horizon docker image is pure horizon.

Some projects have a tools/register_plugin.sh which performs the grunt
work, where as others require a workflow similar to:

cp /path/to/projects/new/panel openstack_dashboard/local/enabled/
cp /path/to/local/defualt/settings
openstack_dashboard/local/local_settings.d/
cp /path/to/*policy.json openstack_dashboard/conf/
# compress if environment wants it
./manage.py collectstatic
./manage.py compress

(Separately, it would be nice if this was standardised.. but not the topic
of this thread)

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.

What are your thoughts?

[0]
http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml

--
Kind Regards,
Dave Walker
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160703/dd00980b/attachment.html>