From Charles.Debardeleben@sun.com Thu May 24 16:50:07 2007 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4ONo6Xq015627 for ; Thu, 24 May 2007 16:50:07 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l4ONmntY011329 for <@sunmail3mpk.sfbay.sun.com:PSARC-EXT@sun.com>; Fri, 25 May 2007 00:48:51 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JIK00F01KTDQF00@nwk-avmta-2.sfbay.sun.com> for PSARC-EXT@sun.com (ORCPT PSARC-EXT@sun.com); Thu, 24 May 2007 16:48:49 -0700 (PDT) Received: from nwk-ea-fw-1.sun.com ([10.4.134.5]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JIK00CKRKTDGC40@nwk-avmta-2.sfbay.sun.com> for PSARC-EXT@sun.com (ORCPT PSARC-EXT@sun.com); Thu, 24 May 2007 16:48:49 -0700 (PDT) Received: from d1-sfbay-09.sun.com ([192.18.39.119]) by nwk-ea-fw-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l4ONmmGS014041 for ; Thu, 24 May 2007 16:48:48 -0700 (PDT) Received: from conversion-daemon.d1-sfbay-09.sun.com by d1-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0JIK00001KPW6W00@d1-sfbay-09.sun.com> (original mail from Charles.Debardeleben@Sun.COM) for PSARC-EXT@sun.com (ORCPT PSARC-EXT@sun.com); Thu, 24 May 2007 16:48:48 -0700 (PDT) Received: from [129.146.104.69] by d1-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JIK002LRKTCDIPH@d1-sfbay-09.sun.com> for PSARC-EXT@sun.com (ORCPT PSARC-EXT@sun.com); Thu, 24 May 2007 16:48:48 -0700 (PDT) Date: Thu, 24 May 2007 16:46:38 -0700 From: Charles Debardeleben Subject: [Fwd: "Cluster" Brand Zone [PSARC/2007/304 FastTrack timeout 05/31/2007]] Sender: Charles.Debardeleben@sun.com To: PSARC-EXT@sun.com Message-id: <465623DE.90206@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 User-Agent: Thunderbird 1.5.0.5 (X11/20060814) Status: RO Content-Length: 4539 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 To: PSARC@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 Copyright 2007 Sun Microsystems, Inc. 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 From Charles.Debardeleben@sun.com Thu May 24 17:56:32 2007 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4P0uWha017221 for ; Thu, 24 May 2007 17:56:32 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l4P0tFwV028674 for <@sunmail2sca.sfbay.sun.com:PSARC-EXT@sun.com>; Thu, 24 May 2007 17:55:17 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JIK00419NW4NT00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-EXT@sun.com (ORCPT PSARC-EXT@sun.com); Thu, 24 May 2007 17:55:16 -0700 (PDT) Received: from nwk-ea-fw-1.sun.com ([10.4.134.6]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JIK007DJNW38SB0@nwk-avmta-1.sfbay.Sun.COM> for PSARC-EXT@sun.com (ORCPT PSARC-EXT@sun.com); Thu, 24 May 2007 17:55:15 -0700 (PDT) Received: from d1-sfbay-09.sun.com ([192.18.39.119]) by nwk-ea-fw-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l4P0tFkt006235 for ; Thu, 24 May 2007 17:55:15 -0700 (PDT) Received: from conversion-daemon.d1-sfbay-09.sun.com by d1-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0JIK00501NTOND00@d1-sfbay-09.sun.com> (original mail from Charles.Debardeleben@Sun.COM) for PSARC-EXT@sun.com (ORCPT PSARC-EXT@sun.com); Thu, 24 May 2007 17:55:15 -0700 (PDT) Received: from [129.146.104.69] by d1-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JIK002CSNW2DI1I@d1-sfbay-09.sun.com> for PSARC-EXT@sun.com (ORCPT PSARC-EXT@sun.com); Thu, 24 May 2007 17:55:15 -0700 (PDT) Date: Thu, 24 May 2007 17:53:05 -0700 From: Charles Debardeleben Subject: [Fwd: [Fwd: "Cluster" Brand Zone [PSARC/2007/304 FastTrack timeout 05/27/2007]]] Sender: Charles.Debardeleben@sun.com To: PSARC-EXT@sun.com Message-id: <46563371.9060203@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 User-Agent: Thunderbird 1.5.0.5 (X11/20060814) Status: RO Content-Length: 4963 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 To: PSARC-EXT@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 To: PSARC@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 Copyright 2007 Sun Microsystems, Inc. 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 From Charles.Debardeleben@sun.com Tue May 29 15:16:35 2007 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l4TMGZdb014322 for ; Tue, 29 May 2007 15:16:35 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l4TMFATW015307; Tue, 29 May 2007 15:15:16 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JIT0012VPTFN600@nwk-avmta-1.sfbay.Sun.COM>; Tue, 29 May 2007 15:15:15 -0700 (PDT) Received: from nwk-ea-fw-1.sun.com ([10.4.134.6]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JIT000YAPTEIMC0@nwk-avmta-1.sfbay.Sun.COM>; Tue, 29 May 2007 15:15:14 -0700 (PDT) Received: from d1-sfbay-10.sun.com ([192.18.39.120]) by nwk-ea-fw-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l4TMFEDH006994; Tue, 29 May 2007 15:15:14 -0700 (PDT) Received: from conversion-daemon.d1-sfbay-10.sun.com by d1-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0JIT00101PP4PU00@d1-sfbay-10.sun.com> (original mail from Charles.Debardeleben@Sun.COM); Tue, 29 May 2007 15:15:14 -0700 (PDT) Received: from [129.146.104.69] by d1-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JIT006RCPTEHCG5@d1-sfbay-10.sun.com>; Tue, 29 May 2007 15:15:14 -0700 (PDT) Date: Tue, 29 May 2007 15:13:01 -0700 From: Charles Debardeleben Subject: Re: [Fwd: [Fwd: "Cluster" Brand Zone [PSARC/2007/304 FastTrack timeout 05/27/2007]]] In-reply-to: <46563371.9060203@sun.com> Sender: Charles.Debardeleben@sun.com To: PSARC-EXT@sun.com Cc: brahma-dev@sun.com, sicr@sun.com, zones-core@sun.com Message-id: <465CA56D.1070208@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <46563371.9060203@sun.com> User-Agent: Thunderbird 1.5.0.5 (X11/20060814) Status: RO Content-Length: 5469 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 > To: PSARC-EXT@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 > To: PSARC@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 Copyright 2007 Sun Microsystems, Inc. > 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 > >