If you don't use Automated Installer, you can safely delete this message.
With the integration of
Author: Jan Damborsky<[email protected]>
Repository: /hg/caiman/slim_source
Latest revision: 70dd9e819f257783d7f7aecf291f215da963ebe7
Total changesets: 1
Log message:
15723 - Teach AI to use new SMF based System Configuration framework for
configuring user and root accounts
15410 - The installer delivered SMF manifests should be relocated to
/lib/svc/manifest
13737 - Automated Installer needs support for setting terminal type from AI
manifest
user has been provided with better control over configuration of system
installed by Automated Installer. There are two aspects of integrated
changes:
* System Configuration manifest is now in form of SMF profile which
gets applied on first boot of installed system during process
of Early Manifest Import [1]. That provides for mechanism to configure
any SMF service on installed system via System Configuration Manifest.
* New SMF service svc:/system/install/config:default is delivered
to the installed system. This SMF service is responsible for
configuring user and root accounts during first boot of installed
system.
In particular, following parameters can be customized:
* user account
- login name
- password
- description
- user's shell
- uid
- gid
- profiles - see prof_attr(4) for details
- roles
- account type - see user_attr(4) for details
- expire - expiration date for login. If set to '0' (zero),
user will be forced to change password at next login.
- home directory ZFS dataset
- home directory mountpoint
* root account
- password
- account type
- expire
Please see design specification [2] and System Configuration
project pages [3] for more details.
SC portion of default AI manifest was modified to reflect
those changes. Since it is now possible to configure profiles
assigned to user, user account is no longer created with
'Primary Administrator' profile assigned by default.
IMPACT
======
As a result, format of System Configuration manifest changed - please see
design specification [2] and new default AI manifest for details [5].
In order to mitigate impact of this change and ease the process of
transition,
following steps were taken:
* new AI images accept System Configuration (SC) manifest in old format.
New AI images can recognize that provided SC manifest is in old format.
In that case, SC manifest is converted to the new format during the
installation.
Then further handled as new SC manifest.
However, new features (e.g. enhanced configuration of user/root accounts)
are not supported in such scenario.
This support will work only for limited number of builds and will be
removed
along with integration of AI/DC manifest rework at the latest.
Thus, it is strongly recommended to switch to the new format of SC
manifest
as soon as feasible.
* current version of installadm(1M) tool will accept new SC manifests.
In order to take advantage of new format of SC manifest,
upgrade of installadm(1M) tool is not necessary. However, it is recommended.
* tool for converting old SC manifest to the new format is provided.
In order to ease the transition in cases when people maintain bunch
of SC manifests, simple conversion tool has been provided to convert
old SC manifests into new format.
Latest version of this tool is available for download from System
Configuration
project pages [4].
It can handle following forms of SC manifest:
- SC manifest embedded in combined AI manifest as XML comment
enclosed within
<sc_embedded_manifest> XML tag
- standalone SC manifest included in combined manifest by means of
<sc_manifest_file>
XML tag
Usage:
$ ./scconv.ksh <old_sc_manifest.xml> <new_sc_manifest.xml>
Since it is single-purpose tool, it takes into account format
of SC manifest and it does not contain full-featured XML parser.
Please be aware of following limitations:
* whole System Configuration XML element has to fit one line. Element
split between several lines is ignored and thus not populated
in new manifest.
* XML attributes has to be specified in following order (the same order
which is used by default SC manifest): name, type, value
CONTACT
=======
In case you need help or encounter any issues, please send email
describing the issue to [email protected] mailing list.
REFERENCES
==========
[1]
http://hub.opensolaris.org/bin/download/Community+Group+smf/smf_design_docs/emidesignmar09.html
[2]
http://hub.opensolaris.org/bin/download/Project+caiman/System+Configuration+Project/scsmfdesignlatest.pdf
[3]
http://hub.opensolaris.org/bin/view/Project+caiman/System+Configuration+Project
[4]
http://hub.opensolaris.org/bin/download/Project+caiman/System+Configuration+Project/scconv.ksh
[5]
http://src.opensolaris.org/source/xref/caiman/slim_source/usr/src/cmd/auto-install/default.xml
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
