Hi,
I'd like to get opinions on several issues regarding autopush after vanity
naming.
As you might know, as part of the Clearview vanity naming component, one can
configure autopush based on per-link using dladm set-linkprop (whereas
before, one can only configure it per-driver).
We also provided a dladm subcommand to migrate the old autopush
configuration to the new form using:
dladm migrate-autopush -f <filename> [<link>]
To make the migration automatically, I an thinking of implicitly running
"dladm migrate-autopush -f /etc/iu.ap" during each reconfiguration boot and
whenever a new link is created (for example, when an aggregation or a VLAN
is created).
And my questions are:
1. One restriction of the implicated behavior is that it will only the
autopush configuration stored in /etc/iu.ap. But I don't see any good way to
solve this.
2. Also, a link can be assigned to an exclusive local zone, and the
autopush(1M) setting is stored in its zone-local file system. Is it possible
that I can know the relative path of that local zone and do the autopush
migration using the information stored in /local-zone-path/root/etc/iu.ap?
Is this a good idea at all?
3. Another problem is that when both forms of autopush configuration exist,
if we apply both autopush settings, it might leads to incorrect behavior. So
that I'd like only apply the per-link autopush setting in that case. Is this
acceptable?
Thanks
- Cathy
