As a workaround you can use tarball in requirements.txt (or test-requirements.txt). Each versions of Horizon/openstack_dashboard is available at http://tarballs.openstack.org/horizon/. Each tarball is generated every time corresponding branch or tag is updated. If you would like to use horizon I-3 as a requirement, please add the following line to your requirements.txt:
http://tarballs.openstack.org/horizon/horizon-2014.1.b3.tar.gz Thanks, Akihiro On Fri, Mar 21, 2014 at 2:22 AM, Paul Belanger <paul.belan...@polybeacon.com> wrote: > On Mon, Mar 17, 2014 at 5:22 AM, Timur Sufiev <tsuf...@mirantis.com> wrote: >> It depends on openstack_dashboard, namely on >> openstack_dashboard.settings. So it is fine from Murano's point of >> view to have openstack_dashboard published on PyPi. Many thanks for >> considering my request :). >> > We are having this issue too, for now we have worked around it with > pip switches allowing to download from an external source, but > hopefully we'll get horizon and openstack_dashboard split out in the > near future. > > Like you, we've built a dashboard atop of horizon, mostly because of > the existing keystone integration. Everything else we do is external > to OpenStack. > > -- > Paul Belanger | PolyBeacon, Inc. > Jabber: paul.belan...@polybeacon.com | IRC: pabelanger (Freenode) > Github: https://github.com/pabelanger | Twitter: > https://twitter.com/pabelanger > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
