Open Stack

Hi team,

Last week on the Horizon meeting we discussed [1] possible options for
Horizon release model to address current issues for plugins maintainers.
Some background could be found here [2].

The main issue is that we should have some stable API for plugins and be
able to release it as needed. We're trying to cover several use cases with
this effort. E.g:
- do not break plugins with Horizon changes (cross-project CI would help
with some issues here too)
- provide an easy way to develop plugins which require specific Horizon
version and features

For now, most of the plugins use 'horizon' package to implement
dashboard extensions. Some plugins use parts of 'openstack_dashboard'
package. In such case, it becomes complicated to develop plugins based on
current master and have CI up and running.

The idea is to introduce something like 'horizonlib' or 'horizon-sdk' with
a stable API for plugin development. We're going to collect everything
needed for this library, so plugins developers could consume only it and do
not relate on any internal Horizon things.

We'd got horizonlib in the past. Unfortunately, we missed information about
what was good or bad but we'll do our best to succeed in this.


If you have any comments or questions, please do not hesitate to drop few
words into this conversation or ping me in IRC. We're going to collect as
much feedback as we can before we'll discuss it in details during the next
PTG.


[1]
http://eavesdrop.openstack.org/meetings/horizon/2018/horizon.2018-06-06-15.01.log.html#l-29
[2]
http://lists.openstack.org/pipermail/openstack-dev/2018-March/128310.html

Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180613/3003bceb/attachment.html>