|
|
Flag-day: Clearview Nemo unification and vanity naming
Date: Thu, 24 Jan 2008 10:09:35 +0800
From: Cathy Zhou <Cathy.Zhou at sun dot com>
To: onnv-gate at onnv dot eng dot sun dot com, on-all at sun dot com
Subject: Flag-day: Clearview Nemo unification and vanity naming
The integration of:
PSARC 2006/499 Clearview Nemo unification and vanity naming
PSARC 2007/527 Addendum for Clearview Vanity Naming and Nemo
Unification
PSARC 2008/002 Clearview UV Updates
is a flag-day for bfu users, Cap-eye Install users, and incremental
nightly builds as described below.
BFU:
An updated version of bfu is delivered with this project. Users of
bfu must use this updated bfu script in order for network interfaces
to come up properly at first boot after upgrade. Use of an old bfu
script with these new bits will results in link aggregations not being
created at first boot, and may also result in new features not working
properly. This can be rectified by rebooting a second time.
The bfu script was changed to merge the /etc/dladm/aggregation.conf
and /etc/dladm/linkprop.conf files into a single
/etc/dladm/datalink.conf file with a new format. Once the upgrade is
done, bfu renames the old aggregation.conf and linkprop.conf files out
of the way by appending a ".bak" suffix to each file. A backwards bfu
across the UV changes will not result in the old aggregation.conf and
linkprop.conf being restored by default. Instead, the administrator
will need to manually rename both files back to their original names.
Cap-Eye Install:
This is also a flag day for users of "Cap-eye Install". This project
introduces a kernel door up-call mechanism between the dls module and
the new dlmgmtd daemon which is critical to network configuration. As
such, do not mix kernel and user-space from before and after this
putback using Install, as doing so will likely result in network
configuration failures.
Nightly Builds:
This is a flag-day for incremental builds, meaning that a full clobber
nightly build is needed in a workspace which has brought over these
changes for the first time. An incremental nightly build in such a
workspace will fail as follows:
==== cpio archives build errors (DEBUG) ====
Failed to create generic root archive: 10460 blocks
Failed to create generic usr archive: 422350 blocks
cpiotranslate: etc/dladm/aggregation.conf: no packaging info
cpiotranslate: etc/dladm/linkprop.conf: no packaging info
cpiotranslate: usr/lib/amd64/llib-lrcm.ln: no packaging info
cpiotranslate: usr/lib/llib-lrcm.ln: no packaging info
cpiotranslate: usr/lib/llib-lrcm: no packaging info
Additional Information:
This project introduces two significant changes to network datalink
interface administration in Solaris. The first ("Nemo Unification")
allows all datalink interfaces to be administered using the dladm(1M)
command and provides Nemo functionality for all network interfaces
regardless of whether a driver is a Nemo driver. Some significant
benefits of this functionality are:
* Ability to create dladm(1M) link aggregations using any set
of Ethernet links, including non-Nemo devices such as
Cassini (ce).
* Ability to create VLAN interfaces over any Ethernet link.
* Use zones with exclusive IP Instances with any interface.
The second ("Vanity Naming") allows administrators to choose
meaningful names for their network interfaces. This allows network
configuration to be decoupled from the underlying hardware of the
system, allowing seamless replacement of network hardware of differing
chipsets, migration of networking-related configuration from one
system or zone to another, etc. For examples and documentation,
please feel free to browse the documents at the following URL under
the "Network Link Names" section:
http://www.opensolaris.org/os/project/clearview/docs/
A draft dladm(1M) man page is also available for those wishing to use
the new features in dladm before the man page is integrated into the
WOS (note that the man page is for both the Clearview UV and upcoming
Brussels project):
http://www.opensolaris.org/os/project/clearview/dladm-uv-brussels.1m.txt
Please file any bugs or RFEs related to this feature using the
following bugster categories under the solaris product:
* kernel/gld for Nemo framework issues including the softmac
kernel module
* network/dladm for issues with configuration using the
dladm command
Feel free to use our project discussion mailing list for any
communication related to this project:
clearview-discuss at opensolaris dot org
Visit out project home page for additional information at:
http://www.opensolaris.org/os/project/clearview/
|