Peter Memishian wrote: > I agree this is compelling, and very much philosophically in-line with the > Clearview vanity naming model. However, I am not sure how to make it > administratively "approachable", unless we're comfortable saying that > links in local zones are not visible from the global zone. My > recollection is that restriction *would* be consistent with the > administrative model for stack instances (e.g., that one must log into the > zone to administer its networking stack) -- if so, this might not be > conceptually problematic.
The detailed usage would have to be looked at in details, but it seems that there is a way to make this work while keeping these links visible from the global zone as well. For instance, the specification of the zone to which a name applies could be implicit, e.g. during the creation of a zone from zonecfg(1M), or explicit when invoking dladm(1M). > However, it does seem a bit at-odds with things like ps(1), which allows > processes from all zones to be manipulated. But that approach is also not > without its problems (e.g., if different zones are running different name > services, a ps(1) in the global zone may return some misleading results). > Perhaps we should touch base with the Zones team. I'm thinking of an approach where "dladm show-link" could simply take additional -z and -Z arguments, akin to the same options currently provided by ps(1). -- Nicolas Droux, Solaris Kernel Networking Sun Microsystems, Inc. http://blogs.sun.com/droux
