On 03/ 8/11 12:34 PM, 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
- Change origins based on some other mapping mechanism
- Delete, disable, or make publishers non-sticky
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. On the other
hand, if it is something that those efforts won't take care of, I'll
probably add this to my {p,v}2v todo list.
The system repo work introduces a distinction between user configured
publishers and publishers which the system provided for the zone.
In the specific case of p2v, the following will happen. On attach, the
(now) zone, will be told to use the system repo to get its publisher
configuration. The publishers it finds there will be (as a group) higher
ranked than the publishers previously configured for the image. The
system publishers will also be in the same ranked order as the global
zone is. The user configured publishers (ie, those that were configured
in the physical image prior to the p2v) will remain, but will be ranked
behind all system publishers. If any publisher is in both the system
publishers and the user publishers, the origins will be merged and the
publisher will be at the system publisher rank.
So, in your example, zone would end up with a "local" publisher with two
origins, one .sun.com and one .oracle.com.
The sysrepo will not disable publishers except in the case where a
publisher was previous a system publisher has disappeared from the GZ,
but packages were installed from that publisher.
The sysrepo will delete system publishers when they're removed from the
GZ, unless packages are installed from them.
The sysrepo will make enforce that publishers match on stickiness
between the GZ and NGZ.
The sysrepo will not change or remap origins of any user publishers as I
can't imagine how this could be done safely and regularly without user
intervention. The sysrepo will change, remove, and add origins to any
system publishers in order to make them match the GZ's configuration.
I think that covers everything asked about, but please let me know what
I missed or needs clarification.
Thanks,
Brock
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
