I have received signatures for both contracts, which are archived in the case directory. The timer has expired with no comments on this case, so I am marking this case closed approved.
-Charles Charles Debardeleben wrote: > As it turns out, the time constraint for this project requires that > this contract > be approved by Tuesday 5/29/07. I believe that this contract qualifies > for > self review, so I am moving the fasttrack timer to 5/28/2007. > > -Charles > > -------- Original Message -------- > Subject: [Fwd: "Cluster" Brand Zone [PSARC/2007/304 FastTrack > timeout 05/31/2007]] > Date: Thu, 24 May 2007 16:46:38 -0700 > From: Charles Debardeleben <Charles.Debardeleben at Sun.COM> > To: PSARC-EXT at sun.com > > > > I am sponsoring this fast-track for Ellard Roush, with a timeout of > 05/31/2007. > The point of this fast-track are 2 contracts for install behavior if > the brand type > is cluster. The 2 contracts are in the case directory. One is between > the Solaris Cluster > team and the Zones team, the other is between the Solaris Cluster and > the install > team. > > -Charles > > -------- Original Message -------- > Subject: "Cluster" Brand Zone [PSARC/2007/304 FastTrack timeout > 05/31/2007] > Date: Thu, 24 May 2007 16:27:48 -0700 (PDT) > From: Charles Debardeleben <cfd at alta.sfbay.sun.com> > To: PSARC at sac.sfbay.sun.com > > > > Template Version: @(#)sac_nextcase 1.58 05/23/07 SMI > This information is Copyright 2007 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > "Cluster" Brand Zone > 1.2. Name of Document Author/Supplier: > Author: Ellard Roush > 1.3 Date of This Document: > 24 May, 2007 > 4. Technical Description > Subject: PSARC FastTrack [05/22/2007]: "Cluster" Brand Zone > > 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 > 1.2. Name of Document Author/Supplier: > Author: Ellard Roush > 1.3 Date of This Document: > 22 May 2007 > > 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 reserves a new brand type, "cluster", which will be used > to implement a zone aware Solaris Cluster product. 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 4. > 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 and still executes the "native" > "zone halt" callback function. > > The first non-native brand was the "lx" brand, which implements a > Linux user-space environment. Since lx-branded zones contain only > Linux software, the Solaris tools used for installing, patching, and > upgrading zones were modified to bypass lx-branded zones. This bypass > was implemented in a heavy-handed way, and it actually causes the > tools to bypass all non-native zones. > > Cluster-branded zones contain native Solaris software, and must be > subject to all the same installation, patching, and upgrade processes > as a native zone. > > The support for other zone brands, such as "lx", will continue to be > as defined in "PSARC/2003/460 - Admin/Install Zones Support". > > This approach is considered an interim solution, and is being taken > due to the tight time constraints to get into Solaris 10 update 4. A > more generic solution will be implemented as a follow-on to this > project. That solution will add new interfaces to the BrandZ > infrastructure, which will allow us to remove any special knowledge of > the "cluster" brand from the zones utilities. The specification of > these interfaces will be submitted as a separate PSARC case. > > Without the change proposed in this fast track case, Solaris Cluster > could not support Oracle RAC in Zones with Solaris 10 update 4. > That is very important for the cluster product and would be a STOPPER > issue for that product. Thus we chose to follow the path of > an interim solution for S10u4 followed by the long term solution. > > 5. Reference Documents > PSARC/2003/460 - Admin/Install Zones Support > PSARC/2005/471 - BrandZ: Support for non-native zones > PSARC/2006/440 - BrandZ -aware Installer > > 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 > >
