Hi Mike,

On Tue, 2011-03-08 at 12:34 -0800, Mike Gerdts wrote:
> Is there any ongoing work that will do any of the following during zone
> attach?

>  - Change origins of publishers so that they align with those found in
>    the global zone

Yes, the goal of the sysrepo work is to selectively proxy publishers
configured in global zones to non-global zones automatically.  During
attach, I'd expect the non-global zone to talk to the system publisher
to find out which publishers it should now have configured.

I think the RFE here is 
https://defect.opensolaris.org/bz/show_bug.cgi?id=17538

which would merge publishers that are provided by the system publisher
vs. those configured locally.  It will be tricky to determine a policy
here though (eg. how do we know that previously locally-configured
publishers in the zone are no longer accessible or valid?)

The sysrepo work is described more in the following bugs:
https://defect.opensolaris.org/bz/buglist.cgi?&status_whiteboard=sysrepo

>  - Change origins based on some other mapping mechanism

I think that's part of the above - if a publisher configured in the zone
was previously marked as one that would proxy through the system
publisher, then it would be updated automatically I think.

>  - Delete, disable, or make publishers non-sticky

Again, if those publishers were previously sysrepo-proxied, then I'd
expect that the publishers would disappear if deleted or disabled - I'm
not sure of the policy involved there, Brock or Ed may have a better
idea of how to merge publishers.

> I ask because in doing some work with p2v, I went to attach an archive
> of a Solaris 11 Express global zone.  The "local" publisher in that
> archive was set to a host in .sun.com that no longer exists.  The
> "local" publisher in the global zone points to the .oracle.com
> replacement for the missing .sun.com host.
> 
> If this problem just goes away with system repo, linked images, or other
> related work I won't spend a lot of time addressing it.

It's not a problem that will go away, but it may become someone else's
problem to solve :-)

        cheers,
                        tim


_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to