Skip Navigation Links | |
Exit Print View | |
Installing Oracle Solaris 11.1 Systems Oracle Solaris 11.1 Information Library |
Part I Oracle Solaris 11.1 Installation Options
1. Overview of Installation Options
Part II Installing Using Installation Media
2. Preparing for the Installation
5. Automated Installations That Boot From Media
6. Unconfiguring or Reconfiguring an Oracle Solaris instance
Part III Installing Using an Install Server
7. Automated Installation of Multiple Clients
8. Setting Up an Install Server
Matching Clients With Installation and Configuration Instructions
Selecting System Configuration Profiles
10. Provisioning the Client System
11. Configuring the Client System
12. Installing and Configuring Zones
13. Running a Custom Script During First Boot
15. Troubleshooting Automated Installations
Part IV Performing Related Tasks
A. Working With Oracle Configuration Manager
When you create a new install service, install-service-image-path/auto_install/manifest/default.xml is the initial default AI manifest for that install service.
This default AI manifest is shown in the below example. This default manifest might be slightly different in different install images.
The target section in the default manifest defines ZFS file systems, or datasets, to be created. The default manifest does not define a target disk for the installation. Refer to the ai_manifest(4) man page for a description of how the default target location for the installation is determined when no target disk is specified in the manifest.
The destination section can be used to specify which locales to install. Facet specifications can be used in the manifest to limit the locales that are installed, which can save time and space if you do not need all locales. If no facets are specified, then facets for all locales default to true. Refer to the ai_manifest(4) man page for more information about setting image facets and attributes.
The software installation instructions specify the default IPS package repository and install the following two packages:
The entire package is required. This incorporation package constrains system packages being installed to compatible versions. Proper system update and correct package selection depend on the presence of this incorporation. Do not remove the installation of this package from your AI manifest, and do not uninstall this package after installation.
The solaris-large-server package is a group package of tools and device drivers that you might want in most environments that you install. This package installs many network and storage drivers, Python libraries, Perl, and much more. For a complete list of packages that are included in the solaris-large-server group package, use the pkg contents command as described in Listing All Installable Packages in a Group Package in Adding and Updating Oracle Solaris 11.1 Software Packages.
For information about how to find the names of other packages that you might want to install, see Adding and Updating Oracle Solaris 11.1 Software Packages.
<?xml version="1.0" encoding="UTF-8"?> <!-- Copyright (c) 2008, 2012, Oracle and/or its affiliates. All rights reserved. --> <!DOCTYPE auto_install SYSTEM "file:///usr/share/install/ai.dtd.1"> <auto_install> <ai_instance name="default"> <target> <logical> <zpool name="rpool" is_root="true"> <!-- Subsequent <filesystem> entries instruct an installer to create following ZFS datasets: <root_pool>/export (mounted on /export) <root_pool>/export/home (mounted on /export/home) Those datasets are part of standard environment and should be always created. In rare cases, if there is a need to deploy an installed system without these datasets, either comment out or remove <filesystem> entries. In such scenario, it has to be also assured that in case of non-interactive post-install configuration, creation of initial user account is disabled in related system configuration profile. Otherwise the installed system would fail to boot. --> <filesystem name="export" mountpoint="/export"/> <filesystem name="export/home"/> <be name="solaris"/> </zpool> </logical> </target> <software type="IPS"> <destination> <image> <!-- Specify locales to install --> <facet set="false">facet.locale.*</facet> <facet set="true">facet.locale.de</facet> <facet set="true">facet.locale.de_DE</facet> <facet set="true">facet.locale.en</facet> <facet set="true">facet.locale.en_US</facet> <facet set="true">facet.locale.es</facet> <facet set="true">facet.locale.es_ES</facet> <facet set="true">facet.locale.fr</facet> <facet set="true">facet.locale.fr_FR</facet> <facet set="true">facet.locale.it</facet> <facet set="true">facet.locale.it_IT</facet> <facet set="true">facet.locale.ja</facet> <facet set="true">facet.locale.ja_*</facet> <facet set="true">facet.locale.ko</facet> <facet set="true">facet.locale.ko_*</facet> <facet set="true">facet.locale.pt</facet> <facet set="true">facet.locale.pt_BR</facet> <facet set="true">facet.locale.zh</facet> <facet set="true">facet.locale.zh_CN</facet> <facet set="true">facet.locale.zh_TW</facet> </image> </destination> <source> <publisher name="solaris"> <origin name="http://pkg.oracle.com/solaris/release"/> </publisher> </source> <!-- The version specified by the "entire" package below, is installed from the specified IPS repository. If another build is required, the build number should be appended to the 'entire' package in the following form: <name>pkg:/entire@0.5.11-0.build#</name> --> <software_data action="install"> <name>pkg:/entire@0.5.11-0.175.1</name> <name>pkg:/group/system/solaris-large-server</name> </software_data> </software> </ai_instance> </auto_install>