[mailto:amot...@gmail.com]
Sent: Monday, February 6, 2017 5:18 AM
To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [horizon] [neutron] Horizon support for Neutron
Trunks - PTL approval needed
I have the same o
> If this is inside the Neutron tree, then support should live in the Horizon
> repo
This sounds like a conclusion. So I have abandoned the requests on
gerrit for the new repo.
Instead I just uploaded a Horizon blueprint draft for Pike:
I have the same opinion as Kevin,
UI support for a feature in the neutron repo should be in the main horizon
repo.
I believe this improves usability too.
If I have a neutron deployment (it is a typical deployment now),
I would like to use neutron feature support only after installing the main
Just caught up with Kevin on IRC. If this is inside the Neutron tree, then
support should live in the Horizon repo; similar to routers, floating ips etc.
My initial, incorrect understanding was that it was more akin to lbaas or
vpnaas.
Rob
On 6 February 2017 at 10:50, Kevin Benton
Well the UIs for the extensions inside the main Neutron repo are in the
main horizon repo so far (e.g. routers, floating IPs, security groups,
etc). LBaaS is a separate repo with separate devs so it makes sense to me
that it would have its own UI repo.
Trunks would be the the first extension that
Core Neutron features should be within Horizon, with extensions outside. This
is a little hazy since even the default behaviour in Neutron is still a plugin,
but thats the general idea. There are already some features outside, like the
lbaas dashboard. Personally, I’d keep them in their own
That idea has merit, though I don't know what the scope for such a
'neutron-ui' might be. I'm definitely supportive of the Neutron Trunks
UI efforts, but it'd be good to get an answer on this scope question
before rolling along and creating the project.
Richard
On 6 February 2017 at 12:14,
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
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.
