Sebastien Roy wrote:
> An issue that came up during my testing and that needs resolution is how
> to handle displaying information on the underlying topology of links
> assigned to exclusive stack non-global zones. For example, if a VNIC,
> VLAN, or aggregation is assigned to a non-global zone, the links that
> would be listed in the "OVER" column belong to the global zone, and the
> question is, should non-global zones have visibility at that level? For
> example, should a zone be aware that its assigned VNIC is over bge1, a
> link that doesn't even show up in show-link and that it otherwise has no
> visibility into?
>
> I'd suggest that non-global zones should not be allowed to view such
> topology information. If that's the case, then what does show-link
> display in the "OVER" column for such links? It could leave the column
> empty (a default string of "--"), or it could display something
> indicative that the information is not accessible and otherwise unknown
> (e.g. "?").
>
> Along the same lines, it would mean that while show-link from an
> exclusive stack non-global zone would display a list of links assigned
> to that zone, show-aggr, show-vnic, show-vlan would be off limits and
> show nothing.
You can provide a self-consistent view if the ngz will show
- the tunnels created in the zone
- the links assigned to the zone
which I think is what you are proposing. That means that other parts are
hidden. Then over being '--' would make sense.
It isn't clear to me that the class should be for the links that are
assigned to the ngz, but I don't think it should care whether it is
assigned a vlan, a vnic, an aggr, or a physical. Would it make sense to
show all of them as vnics??
Erik
