Hello pkg'ers,
I'm working on snap upgrade
http://www.opensolaris.org/os/project/caiman/Snap_Upgrade specifically the CLI
and have in the design that the CLI will support upgrade:
beadm upgrade [-d] [-Z] [-u] [-z zoneName[,zoneName ...]]
[-n beName[,beName...]] pathToSolarisImage
-d - dryrun. Verify the BE configuration and Solaris image.
-u - Don't display a message asking to download beadm software.
-Z - Do not upgrade any Zones. Mutually exclusive with
the -z option.
-z zoneName - Upgrade one or more non-global Zones.
Not specifying the -z option defaults to upgrading
beName
plus all the Zones that are part of that BE. zoneName
is a comma separated list of Zone names. A Zone
can only be upgraded if it's parent BE is being
upgraded.
-n beName - Optional beName to upgrade. Default is to upgrade
the
active BE. The keyword all means to upgrade all known
BE's
on the system.
After talking with a few interested parties it has become clear that we don't
want to have two ways of doing the same thing, pkg image-update and beadm
upgrade. Not sure they would be considered the same operation since beadm
upgrade could be seen as upgrading the Boot Environment and making
modifications to that BE so it can be a bootable instance of opensolaris. Where
image-update, in its current form, seems to be more in line with updating the
opensolaris image with the latest packages and not support modifying the Boot
Environment. Now pkg image-update could be enhanced/modified to do what beadm
upgrade was designed for and we could scrap beadm upgrade altogether however I
would like to seek input as to why that would be the best way to go.
Thanks for any comments.
Tim
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
