On Sat, Mar 03, 2007 at 12:30:30AM +0800, Cathy Zhou wrote: > Maybe my question wasn't clear. But I mean if a physical link is > already assigned to an exclusive zone, whether the global zone can > assign a VLAN over this physical link to another zone.
That wouldn't work. > I think this is completely a valid operation today. But in the > future, if we allows the local zone administrators to create its own > VLANs, aggregations, it will cause problem. Agreed. Perhaps Meem's filesystem analogy needs to be taken further - we could view the links as a graph. Assigning a link to a zone would assign all derivative links to the zone. If any of the derivative links were already assigned to a non-global zone then the assignment of the ancestor would fail. Unfortunately it seems that the graph is complicated significantly by nodes that generate links via composition. Figuring that out requires some more thought. (Is it similar to "lofs" mounts? Hmm, probably not.) > >The first case is the global zone attempting to create a derivative of > >a link that is outside its' namespace. The second case is the global > >zone creating a derivative of a link that is inside its' namespace. > >It can then assign the derivative link to another zone (at which point > >the derivative link would be removed from the namespace of the global > >zone and added to that of the non-global zone). > > > Assuming the global zone assigns bge1001 to zone a, so that bge1001 should > be deleted from the global zone link namespace, but bge1 should still exist > in the global zone link namespace, and bge1 cannot be assigned to any other > local zones. Is that right? Yes. > What I want to understand is that what information the global zone > care about a local-zone created link, and how the global zone use > that information. At a trivial level, the global zone administrator may wish to know that a non-global zone administrator is using VLAN id N over a particular physical link, hence the suggestion that "observability" is of interest. dme.
