On 03/ 8/11 04:16 PM, Mike Gerdts wrote:
[snip]
Could you elaborate on why they'd need to modify publishers to allow
the attach to succeed? In the situation you described, you'd end up
with a publisher with two origins, one functional, one not. Our
transport should be resilient to that situation. I haven't thought
of any situation yet where a user would have to be able to modify
the zone prior to attaching it, but it may be that I just haven't
thought of it yet.
If the zone that's being attached includes one or more publishers that
is not also defined in the global zone, I don't think the system repo
will help. Let's take the hypothetical situation in which a company was
acquired and the sweep from the acquiring company's IT department upset
the IP/DNS config a fair amount. Pre-cutover images that include
application-specific repos are much more usable if the admin has control
over how the origins are altered without having to configure
inappropriate repos in the GZ.
Why wouldn't the zone be allowed to have publishers that are not defined
in the global zone? I agree that providing the admin a way to modify
publishers is useful, it's less clear to me why that would need to
happen on attach, as opposed to prior to attaching or after the zone has
been attached and booted.
In any case, I agree that, unless the repos in questions were configured
via the system publisher prior to the network cutover, the system
publisher doesn't help you here.
Brock
I think it's a separate question whether a user wants to modify the
zone prior to attaching it and whether we want to support that.
Currently we allow people to extract then "install -d" or "attach -d".
Providing a more automated extraction mechanism may be helpful with
upcoming enhancements.
[snip]
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
