Sun Management Center Change Manager 1.0.1 Administration Guide

- Previous: Managed Hosts
- Next: Change Manager Overview (Task Map)

## Deployment Operations

Change Manager supports three automated software deployment operations. Each of the following operations deploy software in the form of a Solaris Flash archive to managed hosts:

- Initial installation

- Reinstallation

- Live update

### Initial Installation

After the managed host is added, you must create custom JumpStart data prior to performing the initial installation. The custom JumpStart data is based on the host properties for each specified managed host.

For initial installation, the Change Manager server acts as an installation server to deploy a Solaris Flash archive to managed hosts. The Solaris boot image and the custom JumpStart data are used to install the Solaris Flash archive on the managed host.

An initial installation must be initiated directly on the managed host by typing the following command at the OpenBootTM prompt:

    ok> boot net - install

This `boot` command cannot be initiated by Change Manager because the Sun Management Center agent and the Change Manager agent module are not yet available on the managed host.

The first time you use Change Manager to install a Solaris Flash archive on a managed host, you must use the initial installation operation. The Solaris Flash archive must include the Sun Management Center agent and the Change Manager agent module, which enable the managed host and the Change Manager server to communicate.

### Reinstallation

A reinstallation is equivalent to an initial installation except that the operation is initiated by Change Manager rather than by you typing `boot net - install` at the OpenBoot prompt. A reinstallation can be initiated by Change Manager because the Sun Management Center agent and the Change Manager agent module are now available on the managed host. The system software on the managed host is overwritten by the software in the Solaris Flash archive.

### Live Update

To perform a live update operation (also called update), the managed host must be running the Sun Management Center agent and the Change Manager agent module. The update uses the Solaris Live Upgrade feature to install the Solaris Flash archive on the inactive boot environment of a running managed host. When the installation completes, the inactive boot environment is marked as active and the system reboots to run the new software stack. The other boot environment is unchanged.

Note –

You can fall back to the previous boot environment to ``undo'' the update operation. This fallback operation marks the previously running boot environment as the active boot environment, then reboots the system to run the previous software stack.

You can monitor the setup for installation, update, and reinstallation operations by viewing the Change Manager job queue. See Chapter 7, Monitoring Jobs (Tasks).

### Example—Getting Started With Change Manager

The following example outlines the process you might follow to use Change Manager to deploy software to managed hosts.

1. Install and configure the Change Manager server.

   The Change Manager server is used as a repository for installation files and audit files and to manage hosts.

   See Chapter 2, Hardware and Software Requirements (Planning) for server requirements. See Chapter 3, Installing, Configuring, and Accessing the Change Manager Server (Tasks) for the server installation procedures.

2. Create a Solaris Flash archive on a master system that you can deploy to the hosts you manage with Change Manager.

   Note that the Sun Management Center agent and the Change Manager agent module must be installed on the master system before you create the Solaris Flash archive.

   See Chapter 4, Creating a Deployable Solaris Flash Archive (Tasks) for information about creating the Solaris Flash archive.

3. Log in to the Change Manager browser interface at the following URL:

       https://cm01:6789

   In this example, `cm01` is the host name of the Change Manager server.

   At the login page, provide the user name and password of a valid Sun Management Center user.

   See Authorizing Users to Access Change Manager for information about creating Sun Management Center users for Change Manager.

4. Import a Solaris boot image to the Change Manager repository.

   This boot image is required to perform the initial installation of managed hosts. The boot image must also match the version of the Solaris Flash archive that you want to install.

   The boot image must be completely imported to the repository before you can use it to deploy an archive to managed hosts. You can determine the status of the import job by monitoring the job queue.

   - See Solaris Boot Image for information about Solaris boot images.

   - See How to Import Solaris Boot Images to the Change Manager Repository (Web Browser) or How to Import Solaris Boot Images to the Change Manager Repository (Command Line) for the procedure that shows how to import the boot images to the Change Manager repository.

   - See Chapter 7, Monitoring Jobs (Tasks) for information about monitoring jobs.

5. Import the Solaris Flash archive you created to the repository.

   The archive and the matching boot image must be stored in the repository for you to perform deployments of the archive to managed hosts.

   The archive must be completely imported to the repository before you can use it to deploy managed hosts. You can determine the status of the import job by monitoring the job queue.

   - See Solaris Flash Archive for information about Solaris Flash archives.

   - See How to Import Solaris Flash Archives to the Change Manager Repository (Web Browser) or How to Import Solaris Flash Archives to the Change Manager Repository (Command Line) for the procedure that shows how to import the archives to the Change Manager repository.

   - See Chapter 7, Monitoring Jobs (Tasks) for information about monitoring jobs.

6. Create a shared profile to describe the configuration of your managed hosts.

   When specifying the disk layout in this shared profile, you might want to specify a second boot environment to enable subsequent update operations.

   See Chapter 5, Installing Solaris Flash Archives on Managed Hosts (Tasks) for procedures that show how to create shared profiles. See Chapter 10, Parameters for Shared Profiles and Host Properties (Reference) for information about the host properties.

7. Add managed hosts to the Sun Management Center topology.

   These managed hosts are the target systems that are to be installed with the Solaris Flash archive you create. You must specify the shared profile you want to use to configure the managed hosts.

   You can organize the topology by creating a hierarchy of host groups. You can add managed hosts to the host groups.

   - See How to Add a Managed Host (Web Browser) or How to Add Managed Hosts (Command Line) for the procedure that shows how to add managed hosts.

   - See Chapter 9, Maintaining the Sun Management Center Topology (Tasks) for procedures that show how to organize and maintain the Sun Management Center topology.

8. Set up hosts for initial installation.

   Set up the custom JumpStart installation files by running the setup operation.

   The setup operation must complete before you can deploy managed hosts. You can determine the status of the setup job by monitoring the job queue.

   - See How to Perform an Initial Installation (Web Browser) or How to Perform an Initial Installation (Command Line) for information about the setup operation.

   - See Chapter 7, Monitoring Jobs (Tasks) for information about monitoring jobs.

9. Perform initial installations of the managed hosts that you added.

   Manually start the initial installation operation on each managed host that you want to install by typing the following on each host's console:

       ok> boot net - install

   - See How to Perform an Initial Installation (Web Browser) or How to Perform an Initial Installation (Command Line) for the procedure that shows how to install managed hosts.

   - See Chapter 7, Monitoring Jobs (Tasks) for procedures that show how to monitor jobs in the job queue.

10. After the managed hosts are successfully installed, you can issue other Change Manager commands to the managed hosts.

    By issuing these commands, you can verify whether the Change Manager server can successfully communicate with the managed hosts. For example, you can submit a get software status request to your managed hosts.

    When this operation succeeds, you can perform further deployment tasks and audit tasks on your managed hosts.

- Previous: Managed Hosts
- Next: Change Manager Overview (Task Map)

- © 2010, Oracle Corporation and/or its affiliates