Re: [zones-discuss] Re: zone migration
Ihsan Zaghmouth wrote: What is the official release date of solaris10 for customers that will support Detach and Attach operations on a Zone ? Ihsan, Attach and detach is planned to be part of S10u3. The schedule for that release is currently showing November but that could change. Jerry ___ zones-discuss mailing list zones-discuss@opensolaris.org
[zones-discuss] Re: zone migration
What is the official release date of solaris10 for customers that will support Detach and Attach operations on a Zone ? cheers Ihsan This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] zones, upgrades, and vxvm
[EMAIL PROTECTED] wrote: Actually, that's not quite right. Standard upgrade is supported in upgrading from 3/05 to 1/06. Heh, I will have to eat crow then, a customer told me that he upgrade a box with zones from 3/05 to 1/06 and I said I don't know how you managed to do that, according to this document that's not possible. A little outdated information is a dangerous thing, filter timely or taste not from BigAdmin. :) CT ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] zones, upgrades, and vxvm
S10 1/06: Will not update a zoned system. You must remove the zones before updating. Actually, that's not quite right. Standard upgrade is supported in upgrading from 3/05 to 1/06. S10 6/06: Will not use LiveUpgrade to update a zoned system. If you want to update a zoned system, you must use Standard Upgrade. The situation with 6/06 is the same as with 1/06 - standard upgrade only is supported for systems with zones. The only release where there is currently no upgrade solution is in Nevada. dsc ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] zones, upgrades, and vxvm
To summarize: S10 1/06: Will not update a zoned system. You must remove the zones before updating. S10 6/06: Will not use LiveUpgrade to update a zoned system. If you want to update a zoned system, you must use Standard Upgrade. S10 ?/??: Can update a zoned system with Standard Upgrade of Live Upgrade. Jason Schroeder wrote: Outdated - there wasn't anything to upgrade s10 + zones *to* till 1/06... http://docs.sun.com/app/docs/doc/817-0552/6mgbi4fgb?a=view /jason Christine Tran wrote: Hi David, Umm ... sorry, perhaps this is outdated, my notes have a section cut&pasted from a BigAdmin article "Understanding The Basics About Solaris Containers in the Solaris 10 OS" dated 8/05. It says that for 3/05, standard upgrade and LU don't know about non-global zones. Specifically: "To prevent a Solaris instance with non-global zones installed from being damaged by an upgrade attempt, code has been added to both standard upgrade and Live Upgrade to detect the presence of non-global zones and to refuse to upgrade if non-global zones are installed in Solaris 10 GA (3/05)." Is this not correct or did I misunderstand? CT [EMAIL PROTECTED] wrote: Just to clarify that upgrade from 3/05 when zones are present is supported for "standard" upgrade. It's the LU piece that is under development. ___ zones-discuss mailing list zones-discuss@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org -- -- Jeff VICTOR Sun Microsystemsjeff.victor @ sun.com OS AmbassadorSr. Technical Specialist Solaris 10 Zones FAQ:http://www.opensolaris.org/os/community/zones/faq -- ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] zones, upgrades, and vxvm
Outdated - there wasn't anything to upgrade s10 + zones *to* till 1/06... http://docs.sun.com/app/docs/doc/817-0552/6mgbi4fgb?a=view /jason Christine Tran wrote: Hi David, Umm ... sorry, perhaps this is outdated, my notes have a section cut&pasted from a BigAdmin article "Understanding The Basics About Solaris Containers in the Solaris 10 OS" dated 8/05. It says that for 3/05, standard upgrade and LU don't know about non-global zones. Specifically: "To prevent a Solaris instance with non-global zones installed from being damaged by an upgrade attempt, code has been added to both standard upgrade and Live Upgrade to detect the presence of non-global zones and to refuse to upgrade if non-global zones are installed in Solaris 10 GA (3/05)." Is this not correct or did I misunderstand? CT [EMAIL PROTECTED] wrote: Just to clarify that upgrade from 3/05 when zones are present is supported for "standard" upgrade. It's the LU piece that is under development. ___ zones-discuss mailing list zones-discuss@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] zones, upgrades, and vxvm
Hi David, Umm ... sorry, perhaps this is outdated, my notes have a section cut&pasted from a BigAdmin article "Understanding The Basics About Solaris Containers in the Solaris 10 OS" dated 8/05. It says that for 3/05, standard upgrade and LU don't know about non-global zones. Specifically: "To prevent a Solaris instance with non-global zones installed from being damaged by an upgrade attempt, code has been added to both standard upgrade and Live Upgrade to detect the presence of non-global zones and to refuse to upgrade if non-global zones are installed in Solaris 10 GA (3/05)." Is this not correct or did I misunderstand? CT [EMAIL PROTECTED] wrote: Just to clarify that upgrade from 3/05 when zones are present is supported for "standard" upgrade. It's the LU piece that is under development. ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] zones, upgrades, and vxvm
Christine, LU doesn't work for boxes with zones yet, afaik. zonepath on vxvm volumes won't work for upgrade from 3/05 (granted, upgrade from 3/05 with zones isn't supported anyway). I have no reason to think this would work with 1/06 Just to clarify that upgrade from 3/05 when zones are present is supported for "standard" upgrade. It's the LU piece that is under development. For VxVM and other file systems whose metadata isn't known from within the miniroot, upgrading a system with zones on such file systems will be an issue until that support is made available. dsc ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] zones, upgrades, and vxvm
LU doesn't work for boxes with zones yet, afaik. zonepath on vxvm volumes won't work for upgrade from 3/05 (granted, upgrade from 3/05 with zones isn't supported anyway). I have no reason to think this would work with 1/06 either, vxconfigd has to run in order to present the volumes to the OS, and I don't think it can run while you're doing an upgrade. I seem to remember removing VxVM mountpoints from vfstab before initiating upgrade for S8. Incidentally I just asked this question regarding SVM volumes being present during upgrade, and the answer from our engineer is that yes, it should work. Haven't tried it yet though. CT William D. Hathaway wrote: Hi, A co-worker recently posted this question: "Does anyone know if you can put the zone root's on a Veritas Volume Manager volume and then have the ability to upgrade in the future? " My gut feeling is that if you using Live Upgrade this might work, but it would definitely not work using the old-school standard upgrade method. Anyone care to comment on the current or future supportability of this? Thanks! William Hathaway This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] patching zones sparse package files (pspool)
Hi Paul There is currently no available supported way of doing this. So . the patch would literally have to copy a postinstall into the directory /var/sadm/pkg/SUNWcsr/save/pspool/SUNWcsr/install and also edit the pkgmap in /var/sadm/pkg/SUNWcsr/save/pspool/SUNWcsr to reflect the new file this could be done via prepatch script and some shell scripting. So not pretty, but it's the only way I know that this can be accomplished. Enda Paul Roberts wrote: Hi, I'm looking at a problem that occurs when installing a non-global zone due to some code that is executed in the postinstall script of the SUNWcsr package (the error occurs because this code is not zone aware and should not be executed within a non-global zone). As I understand it (and this is still a little new to me so please correct me if I'm wrong) the script is being run from a copy that was saved at package install time in /var/sadm/pkg/SUNWcsr/save/pspool/SUNWcsr/install One proposed solution to this problem is to modify SUNWcsr's postinstall script so that checks are made to ensure this code is only run under the correct circumstances. This solution works fine, but the question is, how can the updated postinstall script be delivered as a patch such that it is available upon zone creation in the above directory? As I understand things, the data stored in the pspool directory is saved from the metadata associated with a package when that package is installed, as as such those files themselves do not belong to a package (e.g., the do not appear in .../install/contents) and are not patch-able deliverables in their own right. Is there an existing recommended method for updating these files in patches? One possibility might be to include a script with the patch that would manually edit the pspool copy of the postinstall file to include the updated code. Would that be a viable solution? Are there any glaring disadvantages associated with that method? Many thanks for your help, - Paul ___ zones-discuss mailing list zones-discuss@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
[zones-discuss] patching zones sparse package files (pspool)
Hi, I'm looking at a problem that occurs when installing a non-global zone due to some code that is executed in the postinstall script of the SUNWcsr package (the error occurs because this code is not zone aware and should not be executed within a non-global zone). As I understand it (and this is still a little new to me so please correct me if I'm wrong) the script is being run from a copy that was saved at package install time in /var/sadm/pkg/SUNWcsr/save/pspool/SUNWcsr/install One proposed solution to this problem is to modify SUNWcsr's postinstall script so that checks are made to ensure this code is only run under the correct circumstances. This solution works fine, but the question is, how can the updated postinstall script be delivered as a patch such that it is available upon zone creation in the above directory? As I understand things, the data stored in the pspool directory is saved from the metadata associated with a package when that package is installed, as as such those files themselves do not belong to a package (e.g., the do not appear in .../install/contents) and are not patch-able deliverables in their own right. Is there an existing recommended method for updating these files in patches? One possibility might be to include a script with the patch that would manually edit the pspool copy of the postinstall file to include the updated code. Would that be a viable solution? Are there any glaring disadvantages associated with that method? Many thanks for your help, - Paul ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] zones, upgrades, and vxvm
Unfortunately, at this time LU will not work on a system that has zones. Sun is working on a plan to remove this restriction. William D. Hathaway wrote: Hi, A co-worker recently posted this question: "Does anyone know if you can put the zone root's on a Veritas Volume Manager volume and then have the ability to upgrade in the future? " My gut feeling is that if you using Live Upgrade this might work, but it would definitely not work using the old-school standard upgrade method. Anyone care to comment on the current or future supportability of this? Thanks! William Hathaway -- -- Jeff VICTOR Sun Microsystemsjeff.victor @ sun.com OS AmbassadorSr. Technical Specialist Solaris 10 Zones FAQ:http://www.opensolaris.org/os/community/zones/faq -- ___ zones-discuss mailing list zones-discuss@opensolaris.org
[zones-discuss] zones, upgrades, and vxvm
Hi, A co-worker recently posted this question: "Does anyone know if you can put the zone root's on a Veritas Volume Manager volume and then have the ability to upgrade in the future? " My gut feeling is that if you using Live Upgrade this might work, but it would definitely not work using the old-school standard upgrade method. Anyone care to comment on the current or future supportability of this? Thanks! William Hathaway This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
