tl;dr: how to progreed in separating horizon and openstack_dashboard

About a year ago now we agreed, it makes sense to separate horizon and

Thanks to Radomirs work in unbundling JavaScript libraries, we're
finally there.

It was decided to rename horizon to horizon_lib[1], and to rename
openstack_dashboard to horizon.

Now following[2]:

The split:
code freeze -- no patches merged, except for the ones mentioned here,
- rename "horizon" to "horizon_lib", fix all corresponding imports,
- rename "openstack_dashboard" to "horizon", fix all corresponding
- clone the "horizon" repository using git-filter to skip the
  dashboard files, create an external repository on github for that,
- add new project to openstack-infra/config called horizon_lib, with
  the new repo as the upstream, setup CI for the new project,
- verify that the new repository works correctly,
- remove the horizon_lib files from the old repository in one big

end of code freeze

I tried that in [3], [4]. I renamed openstack_dashboard to
openstack_horizon, rather than horizon to be sure, I really catched all
imports etc., and to make sure, it's clear, what component is meant.
During this process, the name horizon is a bit ambiguous.

It was a somehow larger rework, just search and replace didn't do the
job here, and I'm quite confident to have left one or the other thing
There were quite a few additional code changes necessary, mostly due
flake8 tests (renamed names are longer, breaking line length,
horizon_lib and horizon are now separate, imports must be

So, how do we proceed from here?
- how do we block the gate
- how to create a new repo
- how to set up ci for the new project?
- how to integrate new horizon_lib and horizon (or openstack-horizon) to


[1] http://lists.openstack.org/pipermail/openstack-dev/2014-June/037996.html
[2] https://etherpad.openstack.org/p/horizon-split-plan
[3] https://github.com/mrunge/openstack_horizon
[4] https://github.com/mrunge/horizon_lib

OpenStack-dev mailing list

Reply via email to