David Edmondson wrote: > On Fri, Mar 09, 2007 at 03:41:47PM +0800, Cathy Zhou wrote: >> So today, one can do: >> >> # dladm set-linkprop -t zoneid=foo bge1 >> # dladm reset-linkprop -t zoneid bge1 >> >> in a global zone to change or reset zoneid for a given link, even >> this link has been assigned to a exclusive zone. Do you suggest that >> we remove this support? > > It's necessary to have a way to move links between zones (i.e. perform > the assignment, manipulate the namespace). If this is the way to do > that then it would be wrong to remove it. If there is a different way > to manipulate the namespace then perhaps this would be redundant. >
As I understand it, another way is using zonecfg. But as zoneid is also an attribute of a link, so that a lot of people feel strongly that it should also be able to be configured by dladm. The problem of using dladm set-linkprop in the proposed new world will be the object under configuration will keep changing its representation while its zoneid changes: foo/bge1 -> bar/bge1 ... and I am not sure whether this is a good idea. I agree this needs some thought but I think the problem needs to be solved with a big virtualization picture and I am not sure this has to be solved now. I'd prefer defering this kind of complicated decisions to a later project, and we will only support per-zone iptun names (created by ifconfig ip.tun0 plumb). The only difference user will see from today is that one can create an iptun in a global zone and assign it to an exclusive zone. Thanks - Cathy
