If the horizon team would like neutron features to live outside, I wonder if it would make more sense to create a new 'neutron-ui' repo instead of it being trunk specific. That way we don't have to come up with a new repo for every new feature that needs a horizon UI. On Feb 3, 2017 09:26, "Bence Romsics" <bence.romsics at gmail.com> wrote: > Hi All, > > I'd like to add support for Neutron Trunks [1][2] into Horizon > together with a few colleagues in the Pike cycle. We thought of > writing a new Horizon plugin [3] for that purpose. That way I hope to > keep it optional for deployment and minimize the maintenance cost for > the Horizon core team. Of course we'd welcome all review feedback, > especially from the Horizon and Neutron teams. > > To host the work I'd like create a new project: openstack/neutron-trunk-ui > > Following the Project Creator's Guide, here's a proposed new project > config: > > https://review.openstack.org/428730 > > And the corresponding governance change: > > https://review.openstack.org/428796 > > Please review them and if you agree approve. Or guide me to a better > change. > > Thanks in advance, > Bence Romsics > > [1] https://github.com/openstack/openstack-manuals/blob/master/ > doc/networking-guide/source/config-trunking.rst > [2] https://wiki.openstack.org/wiki/Neutron/TrunkPort > [3] http://docs.openstack.org/developer/horizon/tutorials/plugin.html > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170205/db3e20dc/attachment.html>