JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Installing Oracle Solaris 11 Systems     Oracle Solaris 11 Information Library
search filter icon
search icon

Document Information

Preface

Part I Oracle Solaris 11 Installation Options

1.  Overview of Installation Options

Part II Installing Using Installation Media

2.  Preparing for the Installation

3.  Using the LiveCD

4.  Using the Text Installer

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

9.  Customizing Installations

10.  Provisioning the Client System

Customizing an XML AI Manifest File

Creating an AI Manifest at Client Installation Time

Create a Derived Manifests Script

Retrieve Client Attributes

Customize the AI Manifest

Example Derived Manifests Scripts

Testing Derived Manifests Scripts

Add a Derived Manifests Script To an Install Service

11.  Configuring the Client System

12.  Installing and Configuring Zones

13.  Running a Custom Script During First Boot

14.  Setting Up Oracle Configuration Manager For Use By AI Client Systems

15.  Installing Client Systems

16.  Troubleshooting Automated Installations

Chapter 10

Provisioning the Client System

When you create an AI install service, you get a default AI manifest that specifies how to provision the clients. The AI manifest is an XML file that specifies where to install the operating system and what software packages to install. You can also specify disk configuration such as striping, mirroring, and partitioning. See the ai_manifest(4) man page and the install_service_image_path/auto_install/manifest/ai_manifest.xml sample AI manifest for information about the XML elements in an AI manifest.

This chapter explains how you can create custom AI manifests for particular clients.

Any particular install service can include both XML manifest files and scripts for generating manifest files. Any particular client uses only one AI manifest, either static or generated by a script. Which manifest or script a particular client uses depends on the criteria specified when the manifest or script is added to the install service. If the client does not match any criteria to use a custom manifest or script, the default manifest is used. Any manifest or script in a service can be designated to be the default for that service.