> Here's my first cut at the UV whitepaper for BigAdmin. I'd appreciate
> some critical eyes and comments.
>
> http://www.opensolaris.org/os/project/clearview/uv/howto/
Seb,
This is great, thanks for writing this up. A few ideas and comments
that occurred to me along the way:
* In the "main benefits" bullet list, a related case is using
vanity naming to insulate the system from non-hardware changes
too -- e.g. deployments of aggregations and VLANs can be done
seamlessly.
* Second paragraph of Example 1: s/isn't't/isn't/
* After the "dladm create-aggr" in Example 1: "Any name can be
chosen" isn't quite true. We should mention the namespace
format requirements and also s/name/unused name/.
* General comment: persistence isn't covered in the whitepaper.
We should probably mention that (like other dladm subcommands)
dladm rename-link will persist unless -t is used. Also, at
least for example 1, we should mention that any files with the
old names (such as the list mentioned in Example 2) would need
to be located and updated.
* Regarding Example 2: if the rename-link is done after the
"cfgadm -c configure", will IP get properly reconfigured with
public0's configuration? In other words, will the dladm
rename-link cause the IP RCM module to get run again and thus
make use of /etc/hostname.public0? (IIRC, another way to do
Example 2 is to do the dladm rename-link before the cfgadm
configure).
* Regarding Example 3: Is migration impossible, or just difficult
and error-prone? Or, phrased differently, if this is
impossible, then the lab router configuration in Example 1
(where we renamed links and then hunted down any affected files)
also seems impossible. Or am I missing your point?
--
meem
