I'm thinking an Apache caching server front end with redirects to local repositories that get updated on some regulated release schedule. That way, we deliver a friendly URL for the pkg publisher, and clients don't have to proxy out for updates. We're also looking at what Ops Center will be able to do, since that's now free.
- Chuck Floyd AT&T On Feb 21, 2012, at 9:20 AM, "King, Jeff (GE Aviation, US)" <jeff.k...@ge.com> wrote: > Re: pca-proxy.cgi questions > > My team has simultaneously patched as many as 1000 Solaris servers a night > through the pca proxy without incident. > As long as your infrastructure (i.e, network, pca webserver proxy) can handle > the load pca should function without incident. > > My current struggle is locating something that will work for Solaris 11 as > fantastically as what Martin has put together for pre-Solaris 11 > > Jeff ☺ > > > -----Original Message----- > From: pca-boun...@lists.univie.ac.at [mailto:pca-boun...@lists.univie.ac.at] > On Behalf Of pca-requ...@lists.univie.ac.at > Sent: Tuesday, February 21, 2012 6:00 AM > To: pca@lists.univie.ac.at > Subject: pca Digest, Vol 49, Issue 17 > > Send pca mailing list submissions to > pca@lists.univie.ac.at > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.univie.ac.at/mailman/listinfo/pca > or, via email, send a message with subject or body 'help' to > pca-requ...@lists.univie.ac.at > > You can reach the person managing the list at > pca-ow...@lists.univie.ac.at > > When replying, please edit your Subject line so it is more specific than "Re: > Contents of pca digest..." > > > Today's Topics: > > 1. Re: what is my release number (Glenn Satchell) > 2. Re: what is my release number (Lee, Jarrett) > 3. Re: pca-proxy.cgi questions (Martin Paul) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 21 Feb 2012 13:03:47 +1100 > From: "Glenn Satchell" <glenn.satch...@uniq.com.au> > To: "PCA \(Patch Check Advanced\) Discussion" <pca@lists.univie.ac.at> > Subject: Re: [pca] what is my release number > Message-ID: > <73dc4ea7530ca92345061bcc94e4de35.squir...@mail.uniq.com.au> > Content-Type: text/plain;charset=iso-8859-1 > > Patching only updates existing packages already on your system. It does not > add any new features or packages. There is a patch bundle (you'll have to > look for this on MOS) that gets to the release, it even includes a special > patch that updates the release file when done, but the limitation mentioned > above still applies. > > Usual procedure is to burn a DVD or network boot and then run the install. > It will detect your existing system and offer to do an upgrade or a fresh > install. The upgrade removes patches and installs new packages, while > retaining the system's configuration. > > regards, > -glenn > >> You can patch your way to the kernel/package equivalent of a release, >> but if you want to upgrade to a specific release you need to look more >> at a prcedure involving live upgrade. >> >> Fred >> >> On 2/20/12, Wickline, Bob (N-STERLING COMPUTERS CORPORATION) >> <bob.wickl...@lmco.com> wrote: >>> Unfortunately, patching does not update the release: >>> >>> https://blogs.oracle.com/patch/entry/solaris_patches >>> >>> >>> -----Original Message----- >>> From: pca-boun...@lists.univie.ac.at >>> [mailto:pca-boun...@lists.univie.ac.at] >>> On Behalf Of McGraw, Robert P >>> Sent: Monday, February 20, 2012 2:23 PM >>> To: 'pca@lists.univie.ac.at' >>> Subject: EXTERNAL: [pca] what is my release number >>> >>> I was under the impression that installing the latest patches, was >>> the same as installing the latest release. >>> >>> Over the weekend I installed all the latest patches for my host and I >>> still get the following release information. >>> >>> # cat /etc/release >>> Solaris 10 5/09 s10x_u7wos_08 X86 >>> Copyright 2009 Sun Microsystems, Inc. All Rights Reserved. >>> Use is subject to license terms. >>> Assembled 30 March 2009 >>> >>> I would like to upgrade to Solaris 10 10/09. How do I do this. >>> >>> Robert >>> >>> _____________________________________________________________________ >>> Robert P. McGraw, Jr. >>> Manager, Computer System EMAIL: rmcg...@purdue.edu >>> Purdue University ROOM: MATH-807 >>> Department of Mathematics PHONE: (765) 494-6055 >>> 150 N. University Street >>> West Lafayette, IN 47907-2067 >>> >>> >>> >>> >>> >> >> -- >> Sent from my mobile device >> >> Fred Chagnon >> fchag...@gmail.com >> >> > > > > > > ------------------------------ > > Message: 2 > Date: Tue, 21 Feb 2012 02:37:17 +0000 > From: "Lee, Jarrett" <jarrett....@cedarcrestone.com> > To: "PCA (Patch Check Advanced) Discussion" <pca@lists.univie.ac.at> > Subject: Re: [pca] what is my release number > Message-ID: > <4ff0fcd1f3b385479105e854d1367d5e11269...@ccimbxp01.cedarcrestone.com> > Content-Type: text/plain; charset="us-ascii" > > One can still use LiveUpgrade to get to the desired update level, or release, > so that the system only requires a reboot. > > Basic steps: > - Mount media (NFS from a Jumpstart or DVD or even ISO using lofiadm) on the > system to be upgraded > - Uninstall the LiveUpgrade packages (SUNWlucfg and related packages) from > the current system > - Install the LiveUpgrade packages from the new release's media > - Use LiveUpgrade to create an Alternate Boot Environment > - Run the LiveUpgrade tools against the ABE but use the new release's media > as the source > - luactivate the ABE > - reboot > - profit! > > You can even LiveUpgrade from UFS to ZFS root if you desire, but I would not > recommend going to a new release and ZFS simultaneously. Instead, do it as > separate LiveUpgrade activities to limit the scope of your changes in case > there is an issue. > > Also, another plus for LiveUpgrade: If things go South, remember that you can > always boot from alternate media and use "luactivate" to roll back your > changes and boot the previous BE. > > Thanks, > Jarrett > > > Jarrett Lee > CedarCrestone, Inc. > UNIX Administrator, Server Technologies > Managed Services > ____________________________________________________________ > Email: jarrett....@cedarcrestone.com > ____________________________________________________________ > If you are not the intended recipient of this message please treat > confidentially, notify the sender and delete it. > > -----Original Message----- > From: pca-boun...@lists.univie.ac.at [mailto:pca-boun...@lists.univie.ac.at] > On Behalf Of Glenn Satchell > Sent: Monday, February 20, 2012 9:04 PM > To: PCA (Patch Check Advanced) Discussion > Subject: Re: [pca] what is my release number > > Patching only updates existing packages already on your system. It does not > add any new features or packages. There is a patch bundle (you'll have to > look for this on MOS) that gets to the release, it even includes a special > patch that updates the release file when done, but the limitation mentioned > above still applies. > > Usual procedure is to burn a DVD or network boot and then run the install. > It will detect your existing system and offer to do an upgrade or a fresh > install. The upgrade removes patches and installs new packages, while > retaining the system's configuration. > > regards, > -glenn > >> You can patch your way to the kernel/package equivalent of a release, >> but if you want to upgrade to a specific release you need to look more >> at a prcedure involving live upgrade. >> >> Fred >> >> On 2/20/12, Wickline, Bob (N-STERLING COMPUTERS CORPORATION) >> <bob.wickl...@lmco.com> wrote: >>> Unfortunately, patching does not update the release: >>> >>> https://blogs.oracle.com/patch/entry/solaris_patches >>> >>> >>> -----Original Message----- >>> From: pca-boun...@lists.univie.ac.at >>> [mailto:pca-boun...@lists.univie.ac.at] >>> On Behalf Of McGraw, Robert P >>> Sent: Monday, February 20, 2012 2:23 PM >>> To: 'pca@lists.univie.ac.at' >>> Subject: EXTERNAL: [pca] what is my release number >>> >>> I was under the impression that installing the latest patches, was >>> the same as installing the latest release. >>> >>> Over the weekend I installed all the latest patches for my host and I >>> still get the following release information. >>> >>> # cat /etc/release >>> Solaris 10 5/09 s10x_u7wos_08 X86 >>> Copyright 2009 Sun Microsystems, Inc. All Rights Reserved. >>> Use is subject to license terms. >>> Assembled 30 March 2009 >>> >>> I would like to upgrade to Solaris 10 10/09. How do I do this. >>> >>> Robert >>> >>> _____________________________________________________________________ >>> Robert P. McGraw, Jr. >>> Manager, Computer System EMAIL: rmcg...@purdue.edu >>> Purdue University ROOM: MATH-807 >>> Department of Mathematics PHONE: (765) 494-6055 >>> 150 N. University Street >>> West Lafayette, IN 47907-2067 >>> >>> >>> >>> >>> >> >> -- >> Sent from my mobile device >> >> Fred Chagnon >> fchag...@gmail.com >> >> > > > > > > > ------------------------------ > > Message: 3 > Date: Tue, 21 Feb 2012 10:47:57 +0100 > From: Martin Paul <martin.p...@univie.ac.at> > To: "PCA (Patch Check Advanced) Discussion" <pca@lists.univie.ac.at> > Subject: Re: [pca] pca-proxy.cgi questions > Message-ID: <4f43684d....@univie.ac.at> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Lee, Jarrett wrote: >> How does PCA handle multiple clients checking in with the local patch >> server simultaneously? What if two servers ask for the same patch >> before the patch downloads completely? Does it have a mechanism that >> knows the original request to download the patch has not yet completed? > > That's no problem, PCA takes care of that. When a client asks for a patch > which is currently being downloaded due to some other request, PCA will > complete the download and then deliver the patch to both clients. This seems > to be pretty robust, I can't remember any recent problem reports about such > issues. > >> We plan to have a few hundred servers downloading patches at one time. >> Will this be fine? Anybody else already doing this? > > I don't have hundreds of clients, but I've heard from others that have. So > this should be fine. If you do experience any trouble, let me know. Even > more, tell us when you have your setup running and working - success stories > are always welcome :) > > If you want to spread the load to multiple servers, you might be interested > to hear that you can even build a cascade of pca proxies - just point one > proxy at another by setting xrefurl/patchurl on a secondary proxy to the > primary proxy. > > hth, > Martin. > > > > ------------------------------ > > _______________________________________________ > pca mailing list > pca@lists.univie.ac.at > https://lists.univie.ac.at/mailman/listinfo/pca > > > End of pca Digest, Vol 49, Issue 17 > ***********************************
