|
|
Flag Day: PSARC/2005/487 sysidtool(1m) Integrated NFSv4 Prompts
Date: Tue, 4 Apr 2006 10:45:31 -0500
From: Rick Mesta <Ricardo dot Mesta at sun dot com>
To: onnv-gate at onnv dot eng dot sun dot com, on-all at sun dot com
Subject: Flag Day: PSARC/2005/487 sysidtool(1m) Integrated NFSv4 Prompts
PSARC/2005/487 sysidtool(1m) Integrated NFSv4 Prompts
5110062 NFSv4 domain prompting should be done by sysidtool framework
6231897 ON changes in support of 5110062: nuke sysidnfs4(1m)
... represents a flag day for people who:
. Install Solaris systems (other than bfu or cap-eye Install)
. Configure/maintain JumpStart servers
. Incrementally build their own ON 'nightly' archives
. Build their own net install images
. Use NFSv4
If none of the above describes you, you can stop reading now =:)
Otherwise, please read on...
Administrative Impact
=====================
This putback introduces several enhancements to the handling of
the NFSv4 domain setting.
1) In an effort to remove customer dissatisfiers, the s10fcs NFSv4
domain text prompt after 1st reboot has been removed. This prompt
has been fully integrated into the Install framework. As such,
you will experience a new curses/Java prompt at installation
time.
2) We continue to urge you to use the SWAN configured NFSv4 domain.
If you choose DNS as your name service during install, then you
simply select continue/F2_OK and you're done.
If you chose another naming service (other than DNS) _or_ you
know you _won't_ be using DNS for hostname resolution, you can
do either of the following:
a) select the default domain at the curses/Java prompts
b) _and_ configure DNS after system install
<< OR >>
a) choose to specify a domain at the curses/Java prompts
b) and specify "sun.com" as usual
3) A new sysidcfg keyword ('nfs4_domain') has been introduced for
use in JumpStart installs. You no longer need to use the s10fcs
set_nfs4_domain jumpstart_sample script. Just add the following
to your existing sysidcfg to configure your system and suppress
any prompting.
nfs4_domain=sun.com
Again, taking the SWAN configured NFSv4 domain is preferred, so
to do that via JumpStart, use the following setting in conjunction
to setting up the system's DNS resolver.
nfs4_domain=dynamic
Using the 'nfs4_domain' keyword to install an earlier WOS build
will result in the parser not recognizing the sysidcfg file and
prompting you for all values.
Developer Impact
================
Building incremental nightlies
------------------------------
This putback introduces a flag day for those who perform incremental
nightlies (i.e., nightly -i and/or "i" in NIGHTLY_OPTIONS). Once you
sync up w/the changes introduced by this putback, you'll notice a
warning saying usr/sbin/sysidnfs4 no longer belongs to a package. This
causes the cpio archives build to fail. In order to fix this, you can
either
a) make a clobber build
<< OR >>
b) do 'rm -f ${ROOT}/usr/sbin/sysidnfs4' to blow the offending
binary from your proto area _and_ remove the following line
from ${SRC}/runtime.out
./usr/sbin/sysidnfs4: NEEDED=libc.so.1
Rolling your own Netinstall images
----------------------------------
This putback also introduces a flag day for those of you who build
your own net install images. The delivery of this feature impacts
the ON and Install consolidations. As such, if you _do_ build your
own net install images, you'll need to include the following pkgs
ON Install Java Install
--------- ---------------- ------------
SUNWhea SUNWadmr SUNWicdw
SUNWnfscu SUNWsibi
SUNWcdrom
SUNWadmap
SUNWadmlib-sysid
SUNWicda
If you use ON images with N-1 WOS pkgs for creating your own net
install images (we're currently only aware of ON PIT doing this
at the moment), you can use your existing work arounds to continue
to configure the NFSv4 domain in /etc/default/nfs NFSMAPID_DOMAIN.
If you do _not_ pick up the corresponding Install pkgs, your new
net install images won't set the NFSMAPID_DOMAIN, and you will see
your files be owned by 'nobody'.
Finally, this putback makes no changes to the existing system, so
bfu, cap-eye Install, or hand-installing binaries out of your own
ON workspace will just work.
Please file any bugs to the following cat/subcat as appropriate:
ON: kernel/nfsv4
Install: sysadmin/sysidtool (curses)
solaris_install/wizard_sysid (java)
Questions relating to this putback can be sent to nfs-eng at sun dot com
and csi-iteam at sun dot com, respectively.
thx,
rick
|