yahoo-eng-team team mailing list archive

[Oleksandr Kozachenko <2049067@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

In network topology page, interfaces table in RouterDetailView includes both interfaces in the current project's networks and also interfaces in the shared networks in other projects. But all information except the id_or_name of the interfaces in the shared networks are missing, more specifically, the status field is shown as red and other fields are `none`.
The typical case is when you create a router against the provider network which is shared for all tenants.

I think it is because of the limitation of shared networks. i.e. users
cannot inspect ports and ip address information of the shared network
because of the perm lack. But the status field as red is worse than
rather missing values because users worry about that red color which
normally means dead/down.

Is there any possibility to allow access to the ports in the shared network from the tenant network which is connected?
If that is much work in rbac side, i think it is better to remove those interfaces of shared network from interface list or set the status field as None.

** Affects: horizon
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/2049067

Title:
  Information about interfaces of shared network are missing in network
  topology

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  In network topology page, interfaces table in RouterDetailView includes both interfaces in the current project's networks and also interfaces in the shared networks in other projects. But all information except the id_or_name of the interfaces in the shared networks are missing, more specifically, the status field is shown as red and other fields are `none`.
  The typical case is when you create a router against the provider network which is shared for all tenants.

  I think it is because of the limitation of shared networks. i.e. users
  cannot inspect ports and ip address information of the shared network
  because of the perm lack. But the status field as red is worse than
  rather missing values because users worry about that red color which
  normally means dead/down.

  Is there any possibility to allow access to the ports in the shared network from the tenant network which is connected?
  If that is much work in rbac side, i think it is better to remove those interfaces of shared network from interface list or set the status field as None.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/2049067/+subscriptions