Installing and Configuring Zones

Installing and configuring Solaris Zones involves the following tasks:

Enabling a zone to run in your chosen data service configuration, as explained in the following sections:
- How to Enable a Zone to Run in a Failover Configuration
- How to Enable a Zone to Run in a Multiple-Masters Configuration
Installing and configuring a zone, as explained in:
- How to Install a Zone and Perform the Initial Internal Zone Configuration

Perform this task for each zone that you are installing and configuring. This section explains only the special requirements for installing Solaris Zones for use with HA for Solaris Zones. For complete information about installing and configuring Solaris Zones, see Oracle Solaris Administration: Oracle Solaris Zones, Oracle Solaris 10 Zones, and Resource Management.

How to Enable a Zone to Run in a Failover Configuration

Register the SUNW.HAStoragePlus resource type.

# clresourcetype register SUNW.HAStoragePlus

Create a failover resource group.

# clresourcegroup create solaris-zone-resource-group

Create a resource for the zone`s disk storage.

This HAStoragePlus resource is for the zonepath. The file system must be a failover file system.

# clresource create \
-g solaris-zone-resource-group \
-t SUNW.HAStoragePlus \
-p Zpools=solaris-zone-instance-zpool \
solaris-zone-has-resource-name

(Optional) Create a resource for the zone's logical hostname.

# clreslogicalhostname create \
-g solaris-zone-resource-group \
-h solaris-zone-logical-hostname \
solaris-zone-logical-hostname-resource-name

Enable the failover resource group.

# clresourcegroup online -M solaris-zone-resource-group

How to Enable a Zone to Run in a Multiple-Masters Configuration

Create a scalable resource group.

# clresourcegroup create \
-p Maximum_primaries=max-number \
-p Desired_primaries=desired-number \
solaris-zone-resource-group

Enable the scalable resource group.

# clresourcegroup online -M solaris-zone-resource-group

How to Install a Zone and Perform the Initial Internal Zone Configuration

Perform this task on each node that is to host the zone.

Note - For complete information about installing a zone, see Oracle Solaris Administration: Oracle Solaris Zones, Oracle Solaris 10 Zones, and Resource Management.

Before You Begin

Consult Configuration Restrictions and then determine the following requirements for the deployment of the zone with Oracle Solaris Cluster:

The number of Solaris Zone instances that are to be deployed.
The zpool containing the file system that is to be used by each Solaris Zone instance.

Ensure that the zone is configured.

If the zone that you are installing is to run in a failover configuration, configure the zone's zone path to specify a file system on a zpool. The zpool must be managed by the SUNW.HAStoragePlus resource that you created in How to Enable a Zone to Run in a Failover Configuration.

For detailed information about configuring a zone before installation of the zone, see the following documentation:

Note - This procedure assumes you are performing it on a two-node cluster. If you perform this procedure on a cluster with more than two nodes, perform on all nodes any steps that say to perform them on both nodes.

Become superuser on one node of the cluster.
Alternatively, if your user account is assigned the System Administrator profile, issue commands as non-root through a profile shell, or prefix the command with the pfexec command.
If you will use a solaris10 brand zone, set up the system image.
Follow procedures in Creating the Image for Directly Migrating Oracle Solaris 10 Systems Into Zones in Oracle Solaris Administration: Oracle Solaris Zones, Oracle Solaris 10 Zones, and Resource Management.

Create an HAStoragePlus resource.

Specify the ZFS storage pool and the resource group that you created.

phys-schost-1# clresource create -t SUNW.HAStoragePlus \
-g resourcegroup -p Zpools=pool hasp-resource

Bring the resource group online.

phys-schost-1# clresourcegroup online -eM resourcegroup

Create a ZFS file-system dataset on the ZFS storage pool that you created.
You will use this file system as the zone root path for the solaris brand zone that you create later in this procedure.
```
phys-schost-1# zfs create pool/filesystem
```
For a solaris brand zone, ensure that the universally unique ID (UUID) of each node's boot-environment (BE) root dataset is the same value.
1. Determine the UUID of the node where you initially created the zone.
  Output is similar to the following.
```
phys-schost-1# beadm list -H
…
b101b-SC;8fe53702-16c3-eb21-ed85-d19af92c6bbd;NR;/;756…
```
  In this example output, the UUID is 8fe53702-16c3-eb21-ed85-d19af92c6bbd and the BE is b101b-SC.
2. Set the same UUID on the second node.
```
phys-schost-2# zfs set org.opensolaris.libbe:uuid=uuid rpool/ROOT/BE
```
  Note - If you use a multimaster configuration, you do not need to set the UUID as described in this step.

On both nodes, configure the solaris or solaris10 brand non-global zone.

Set the zone root path to the file system that you created on the ZFS storage pool.

Configure the zone.

Note - You must define the osc-ha-zone attribute in the zone configuration, setting type to boolean and value to true.

For a solaris brand zone, use the following command.

phys-schost# zonecfg -z zonename \
'create ; add attr; set name=osc-ha-zone; set type=boolean; set value=true; end;
set zonepath=/pool/filesystem/zonename ; set autoboot=false'

For a solaris10 brand zone, use the following command.

phys-schost# zonecfg -z zonename \
'create ; set brand=solaris10; set zonepath=/pool/filesystem/zonename ;
add attr; set name=osc-ha-zone; set type=boolean;
set value=true; end; set autoboot=false'

Verify the zone configuration.

phys-schost# zoneadm list -cv
  ID NAME          STATUS        PATH                           BRAND    IP    
   0 global        running       /                              solaris  shared
   - zonename      configured   /pool/filesystem/zonename         brand    shared

From the node that masters the HAStoragePlus resource, install the solaris or solaris10 brand non-global zone.

Note - For a multi-master configuration, you do not need an HAStoragePlus resource as described in Step a and you do not need to perform the switchover described in Step 9.

Output is similar to the following:

Determine which node masters the HAStoragePlus resource.

phys-schost# clresource status
=== Cluster Resources ===

Resource Name             Node Name       Status        Message
--------------            ----------      -------       -------
 hasp-resource              phys-schost-1   Online        Online
                          phys-schost-2    Offline       Offline

Perform the remaining tasks in this step from the node that masters the HAStoragePlus resource.

Install the zone on the node that masters the HAStoragePlus resource for the ZFS storage pool.
- For a solaris brand zone, use the following command.
```
phys-schost-1# zoneadm -z zonename install
```
- For a solaris10 brand zone, use the following command.
```
phys-schost-2# zoneadm -z zonename install -a flarimage -u
```

Verify that the zone is installed.

phys-schost-1# zoneadm list -cv
  ID NAME           STATUS       PATH                           BRAND    IP    
   0 global         running      /                              solaris  shared
   - zonename       installed    /pool/filesystem/zonename        brand    shared

Boot the zone that you created and verify that the zone is running.

phys-schost-1# zoneadm -z zonename boot
phys-schost-1# zoneadm list -cv
  ID NAME           STATUS       PATH                           BRAND    IP    
   0 global         running      /                              solaris  shared
   - zonename       running      /pool/filesystem/zonename        brand    shared

Open a new terminal window and log in to the zone console.
Follow the interactive steps to finish the zone configuration.
Halt the zone.
The zone's status should return to installed.
```
phys-schost-1# zoneadm -z zonename halt
```
Forcibly detach the zone.
```
phys-schost-1# zoneadm -z zonename detach -F
```
The zone state changes from installed to configured.

Switch the resource group to the other node and forcibly attach the zone.
1. Switch over the resource group.
  Input is similar to the following, where phys-schost-1 is the node that currently masters the resource group and phys-schost-2 is the node to which you switch the resource group.
```
phys-schost-1# clresourcegroup switch -n phys-schost-2 resourcegroup
```
  Perform the remaining tasks in this step from the node to which you switch the resource group.
2. Forcibly attach the zone to the node to which you switched the resource group.
```
phys-schost-2# zoneadm -z zonename attach -F
```
3. Verify that the zone is installed on the node.
  Output is similar to the following:
```
phys-schost-2# zoneadm list -cv
  ID NAME           STATUS       PATH                           BRAND    IP    
   0 global         running      /                              solaris  shared
   - zonename       installed    /pool/filesystem/zonename        brand    shared
```
4. Boot the zone.
```
phys-schost-2# zoneadm -z zonename boot
```
5. Open a new terminal window and log in to the zone.
  Perform this step to verify that the zone is functional.
```
phys-schost-2# zlogin -C zonename
```
6. Halt the zone.
```
phys-schost-2# zoneadm -z zonename halt
```
7. Forcibly detach the zone.
```
phys-schost-1# zoneadm -z zonename detach -F
```
  The zone state changes from installed to configured.

Skip Navigation Links
Exit Print View
	Oracle Solaris Cluster Data Service for Oracle Solaris Zones Guide Oracle Solaris Cluster 4.0