Jordan Vaughan skrev:
On 12/ 4/09 02:28 PM, Anil wrote:
Once a the global zone is upgraded (and rebooted with the new BE),
what is the best way to update the zones?
It seems like all I would need to do is:
pkg -R <zone path>/root image-update
reboot zone
This seems like a hack, how would "post package" processing happen if
this is not done from the zone itself?
Should I instead *from the zone* take a clone, update parentbe zfs
option, set it to active. Then, imate-update the snapshot/clone? This
seems like a hack too!
Try detaching and attaching the zones that need to be upgraded:
# zoneadm -z <zone> detach
[image-update the global zone]
[reboot the machine to the new BE]
# zoneadm -z <zone> attach -U
You might be able to perform the detach/attach operations while in the
updated global zone BE. Please see the Zones FAQ
(http://hub.opensolaris.org/bin/view/Community+Group+zones/faq) for
details.
Hope that helps,
Jordan
What is the reason for the detach/attach?
I have just switched to OS, and when I upgraded from 127 to 128a, with
one zone (named swan), I ran (in the global zone):
---
pkg image-update --be-name os-snv_128a
beadm mount os-snv_128a /a
pkg -R /a/zones/swan/root image-update
beadm umount os-snv_128a
beadm activate os-snv_128a
init 6
---
This allows me to update everything without having to stop anything,
A speed optimization might be:
---
beadm create os-snv_128a
beadm mount os-snv_128a /a
pkg -R /a image-update
pkg -R /a/zones/swan/root image-update
beadm umount os-snv_128a
beadm activate os-snv_128a
init 6
---
Here the image-updates:s can be run in parallel.
As I'm a newcomer to opensolaris updates I might be way off.
Thomas
_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org
