Hi All,
If you don't use the Solaris Automated Installer(AI) you can safely
ignore this message. Otherwise please read on...or read the pre-flag
day message at:
http://hub.opensolaris.org/bin/view/Project+caiman/Pre-Flag+Day+for+bug+16423
Starting in build 147 there will be changes in AI which will result
in a flag day. Specifically the changes are:
-AI schema and manifest changes
-AI server:'installadm' cli changes in support of the new
AI schema
The changes to the AI schema and the resulting AI manifests are not
backward
compatible. If you wish to deploy Solaris Nevada build 147 or higher you
must use the newer AI manifest. This means you must update your AI
server to
build 147 as well. The changes to 'installadm' will allow for backwards
compatibility for managing builds earlier than b147. This backwards
compatibility will be maintained until b157.
***AI schema and manifest changes***
The changes to the AI schema and the resulting AI manifest were made
to provide a user interface that is more intuitive and easy to use. The new
AI interface provides the same functionality as AI does today. The new
interface will allow for expansion of AI functionality. The New AI manifest
format for build 147 will provide the same functionality as is currently
provided with AI. The AI schema changes are being made to allow
for enhancement of AI functionality while trying to maintain compatibility
moving forward.
The AI schema has been changed to utilize DTD as the schema language
and to add new element and attribute definitions. The AI manifest will no
longer be an embedded manifest with the AI criteria manifest. The AI
criteria manifest will be a separate entity. This is detailed
below in the installadm(1m) changes section.
Documents that will help you get started on making this transition are:
New AI default.xml manifest:
===========================
http://hub.opensolaris.org/bin/download/Project+caiman/Flag+Days/default.xml
New AI ai_manifest.xml manifest:
===============================
http://hub.opensolaris.org/bin/download/Project+caiman/Flag+Days/aimanifest.xml
Use case transition guide:
=========================
http://hub.opensolaris.org/bin/download/Project+caiman/Flag+Days/usecases.txt
XSLT file for manifest transformation from old->new:
===================================================
http://hub.opensolaris.org/bin/download/Project+caiman/Flag+Days/old%2Dto%2Dnew.xslt
To transform the old manifests using the XSLT document run the following
command:
xsltproc -o <output file> <stylesheet> <file>
If /usr/bin/xsltproc is not available on your system, you can install
it with:
pfexec pkg install pkg:/library/libxslt
Please verify the output from running this transform to ensure that
everything is correct in the new manifest.
Details:
------------
1. <ai/ai_instance> are the top level tags for the new AI manifest.
2. Top level target specification for AI:
<target/target_device>
These are the top level elements to specify a target for use in the root
pool for installation. It is not required. If not specified, the AI client
will choose the disk. The algorithm used for choosing the disk remains
unchanged. Specifically the rules are:
1. The installer gets the recommended size for installing the
OpenSolaris OS from the AI libraries. Currently, the recommended
size is 13 GB.
2. The installer searches for available disks on the client. To
determine the default target, the automated installer looks for an
available disk with at least recommended size. The disks are found
in the order they are reported by the libdiskmgt library.
3. When the first disk is found, the installer checks the size of that
disk.
-If the size is greater than or equal to the recommended size,
the installer selects the disk and returns to the
installation procedure.
-If the size is less than the recommended size, the installer
goes to the next disk to check the size.
4. If there is no match, the automated installation fails.
A target_device can be one of the following types:
disk, swap or dump device
3. At the top level a target disk must be specified using this path:
target/target_device/disk
4. A disk can be specified by a name, a set of properties to describe the
disk, a keyword or an iscsi device. A disk can also contain partitions
and/or slices.
5. Disk criteria are divided into the following mutually exclusive groups:
G1: Deterministic disk criteria
===========================
target/target_device/disk/iscsi parameters
target/target_device/disk_name, with name_type attribute:
one of ctd, volid, devpath or devid
G2: non-deterministic disk criteria
===============================
target/target_device/disk/disk_prop: Any of dev_type,
dev_vendor or dev_size
G3: Keyword disk criteria
=====================
target/target_device/disk_keyword: boot_disk
6. Partitions can be specified on x86 architecture, and are specified with
a name and optionally a partition type. Partitions have an action
attribute associated with them, one of: create, delete or use_existing.
Specifying size is optional. The meaning of these attributes is the
same as the meaning of the similarly named tags in the old AI manifest.
If the use_existing action is specified for a partition, the AI client
will install on the first disk found by libdiskmgt containing an
existing Solaris (type 191) partition. This is equivalent to the
meaning of a value of "true" for the
<target_device_use_solaris_partition>
element in the old AI manifest. Only one use_existing partition
can be specified per manifest.
7. Slices are similar to partitions. The differences are:
-You can specify a specific slice to be used as the root slice
-You can force overwriting of a slice
-There is no use_existing action for a slice
-Slices have an action, 'preserve', that allows for specification
of slices where data is to be preserved during install.
8. Packages and IPS image data are similar to the old specification
but use current IPS nomenclature such as publisher and origin.
The first publisher specified under a <source> element is taken
to be the primary publisher and subsequent publishers are taken
to be secondary.
***Installadm changes***
For reference, the updated man page is here:
http://hub.opensolaris.org/bin/download/Project+caiman/Flag+Days/installadm.1m.txt
Changes have been made to installadm(1m) in support of the schema and
manifest changes noted above. However, there will be backward support
for older install images with installadm(1m).
Details of Compatibility with older AI services
-----------------------------------------------
The updated installadm(1m) tool in build 147 will continue
to support older install images, and hence older Criteria
manifests for those install images. That is, you can still
use 'installadm add' to add a Criteria manifest with referenced
or embedded AI and SC manifests files to older install services.
This support is planned to be be removed at build 157.
installadm add-manifest
================
In build 147, the "installadm add" command, which is used
to add a manifest into an install service, has changed. The
usage no longer takes a Criteria manifest, but rather, an AI
manifest; criteria is specified separately on the command line.
installadm add-manifest -m <manifest> -n <svcname>
[-c <criteria=value|range> ... | -C <criteria.xml>]
Note: These usage changes are required when adding manifests to build 147
and later install services. When adding manifests to previous build
install services, the use of the separate criteria specification is
supported, but is not required. Any criteria specified separately with
-c or
-C will override criteria specified in the Criteria manifest given with -m.
Details:
------------
1. The "add" subcommand is renamed to "add-manifest".
The "add" subcommand will continue to work for backwards
compatibility, but will be removed in build 157. Proper
notice will be given prior to removal.
2. The "remove" subcommand is renamed to "delete-manifest".
The "remove" subcommand will continue to work for backwards
compatibility, but will be removed in build 157. Proper
notice will be given prior to removal.
3. The format of the manifest file given via the -m argument
has changed. The file to provide is no longer a Criteria
manifest with an AI and SC manifest referenced or embedded,
but is now the AI manifest instead. The AI manifest will contain
an SC profile as a referenced file, or an embedded file using the
same tag names as was used to reference or embed an SC profile
in the old Criteria manifest. See default.xml here:
http://hub.opensolaris.org/bin/download/Project+caiman/Flag+Days/default.xml
3. Criteria is specified separately on the command line via
criteria options, or a separate criteria manifest file containing
only criteria. For example,
$ installadm add-manifest -n service1 -m manifest.xml \
-c arch=i86pc -c ipv4=10.20.5.1-10.20.5.100
~or~
$ installadm add-manifest -n service1 -m manifest.xml \
-C criteria.xml
The criteria specifiable as criteria options on the command line
are the same ones supported in a criteria manifest file from
previous builds. See the installadm(1m) manpage for examples and
information.
installadm set-criteria
=======================
In addition, build 147 also introduces a new subcommand,
"installadm set-criteria", which allows a user to modify the
criteria for an already published manifest. This subcommand
can be used for new (build 147 and later) install services
as well as older install services. See the updated installadm(1m) manpage
for more details.
installadm set-criteria -m <manifest> -n <svcname>
-a|-c <criteria=value|range> ... | -C <criteria.xml>
***Where to ask questions***
email: caiman-disc...@opensolaris.org for questions and help
Bugs found should be filed as follows:
For internal users, use bugster
Product: Solaris
Category: install
Subcategory: autoinstall
For External users, use defect.opensolaris.org
development/installer/autoinstall
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
