Hi Jerry,

May I request that a possible impact on the "cluster" brand be 
evaluated? As you know, the "cluster" brand has the same packaging 
characteristics as that of the native brand. I would just like to make 
sure that your changes do not cause update on attach to fail for zone 
clusters.

Thanks,
Zoram

On 03/08/10 19:36, Gerald Jelinek wrote:
> I'm sponsoring this for myself.  I've filed this as closed approved
> automatic but if anyone thinks this needs review I can change it to
> a fast-track.
>
> Thanks,
> Jerry
>
> Template Version: @(#)sac_nextcase 1.69 02/15/10 SMI
> This information is Copyright 2010 Sun Microsystems
> 1. Introduction
>     1.1. Project/Component Working Name:
>        zone update on attach all
>     1.2. Name of Document Author/Supplier:
>        Author:  Gerald Jelinek
>     1.3  Date of This Document:
>       08 March, 2010
> 4. Technical Description
> The current behavior of zones "update on attach" [1] with the "native"
> brand using SVr4 packaging is to update the minimal set of packages
> needed to make the zone usable.  This is specified with the -u option.
> We have heard from many users that this is not meeting their needs
> or expectations.  Instead, what they want is to update the maximal
> set of SVr4 packages.  That is, they want to update the same set of
> packages as would be installed in a newly created zone so that they
> can compare an updated zone to a new zone and see that they are
> the same [2].  This case adds a new attach option, -U, to the "native"
> SVr4 branded zone so that users can use "update on attach" to update
> all of the packages as would be installed into a new zone.
>
> EXPORTED INTERFACES
>
>       zoneadm attach option
>               [-U]                    Committed for the "native" brand
>
> REFERENCES
>
> 1. PSARC 2007/621 zone update on attach
> 2. zoneadm attach option to make zone match newly installed zone
>    Bugid 6886977 http://bugs.opensolaris.org/view_bug.do?bug_id=6886977
>
> 6. Resources and Schedule
>     6.4. Steering Committee requested information
>       6.4.1. Consolidation C-team Name:
>               ON
>     6.5. ARC review type: Automatic
>     6.6. ARC Exposure: open
>
>   

Reply via email to