I am sponsoring this fast-track (which only records a
contract) for Ellard Roush. A copy of the contract
is in the case directory and both managers will approve
the contract before the timeout.
Thanks,
Jerry
Template Version: @(#)sac_nextcase %I% %G% SMI
This information is Copyright 2008 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
"Cluster" Brand Zone Interfaces
1.2. Name of Document Author/Supplier:
Author: Ellard Roush
1.3 Date of This Document:
03 December, 2008
4. Technical Description
Subject: PSARC FastTrack [08/??/2008]: "Cluster" Brand Zone Interfaces
Template Version: @(#)sac_nextcase 1.56 10/26/05 SMI
This information is Sun Proprietary: Need-to-Know
1. Introduction
1.1. Project/Component Working Name:
"Cluster" Brand Zone Interfaces
1.2. Name of Document Author/Supplier:
Author: Ellard Roush
1.3 Date of This Document:
30 July 2008
4. Technical Description
The BrandZ feature set provides a way to tailor the behavior
of a zone via a set of callbacks for specific purposes, such
as zone boot, zone halt, zone install, etc.
This case establishes a contract for zone interfaces used to support
a new brand type, "cluster", which will be used
to implement a zone aware Solaris Cluster product.
The brand type "cluster" was approved in PSARC 2007/304.
This case is just for the contract for zone related interfaces
to be used by the already approved "cluster" brand zone.
This product supports the ability to run Oracle RAC in Zones,
as well as other cluster applications. The "cluster" brand will be released
as part of a Sun Cluster product release that will run on
Solaris 10 update 5.
The "cluster" brand type is closely related to the "native"
brand type. Essentially, the "cluster" zone uses the callback
mechanism in order to do things in addition to what the "native"
brand type does. For example, the cluster code learns about zone
halt with the "zone halt" callback. This enables Sun Cluster to
perform zone shutdown actions and the callback still executes the "native"
"zone halt" function.
Sun Cluster uses the libzonecfg library to determine information
about the configured zone. The "cluster" brand zone supports
the full set of Solaris zone features. Sun Cluster intentionally
does not duplicate what is done by Solaris zones, instead we
use the Solaris zone functionality. Sun Cluster adds support
for cluster resources: cluster file systems, failover file systems,
logical host addresses (failover IP addresses), and shared IP address
(IP address support for scalable applications). Sun Cluster ensures
that zone configuration information relevant to cluster applications
is consistent on the zones on the different machines.
5. Reference Documents
PSARC/2002/174 - Virtualization and Namespace Isolation in Solaris
PSARC/2005/471 - BrandZ: Support for non-native zones
PSARC/2007/350 - Etude: Migration Technology
PSARC/2008/125 - Etude Part Deux: Solaris 9 to
Solaris 10 Migration Technology
PSARC/2007/304 - "Cluster" Brand Zone
PSARC/2006/651 - Brand specific handlers for zoneadm(1M) commands
CLARC/2004/1405 - RAC on Zones (see requirement specification
in /shared/SC/dev-process/features/2004/1405)
6. Resources and Schedule
6.4. Steering Committee requested information
6.4.1. Consolidation C-team Name:
ON
6.5. ARC review type: FastTrack
6. Resources and Schedule
6.4. Steering Committee requested information
6.4.1. Consolidation C-team Name:
ON
6.5. ARC review type: FastTrack
6. Resources and Schedule
6.4. Steering Committee requested information
6.4.1. Consolidation C-team Name:
Solaris Cluster
6.5. ARC review type: FastTrack
6. Resources and Schedule
6.4. Steering Committee requested information
6.4.1. Consolidation C-team Name:
ON
6.5. ARC review type: FastTrack
6.6. ARC Exposure: open
