adding pkgs to non-global zones

adding pkgs to non-global zones

Post by Frank Cusac » Sun, 21 May 2006 10:43:21



Can I safely run pkgadd and pkgrm to add/remove pkgs from non-global
zones?  I want to create non-sparse zones but some of them need
packages I don't wish to add to all zones.  If I add a package from
the global zone, the only options are global-zone-only or all-zones.

Assuming that works, how do I keep the non-global zone patched?  Running
smpatch from the global zone patches all zones.  Can I just run smpatch
from the non-global zone?

Yes, I will be "upgrading" to pca eventually.

-frank

 
 
 

adding pkgs to non-global zones

Post by Ian Collin » Sun, 21 May 2006 11:37:25



> Can I safely run pkgadd and pkgrm to add/remove pkgs from non-global
> zones?  I want to create non-sparse zones but some of them need
> packages I don't wish to add to all zones.  If I add a package from
> the global zone, the only options are global-zone-only or all-zones.

Yes, I have several zones with different combinations of Blastwave packages.

Quote:> Assuming that works, how do I keep the non-global zone patched?  Running
> smpatch from the global zone patches all zones.  Can I just run smpatch
> from the non-global zone?

Pass, I share all the core OS stuff between zones.

--
Ian Collins.

 
 
 

adding pkgs to non-global zones

Post by Michael Wei » Sun, 21 May 2006 17:52:24


hi Frank,

if a package must be installed in all zones identically or not is defined in
3 new parameters in the pkginfo file within the package.

The parameter SUNW_PKG_ALLZONES is the moste relevant for your question. If
the value is "true" the package _must_ be installed and identical in all
zones and it _must_ be installed by the global zone admin.

If the value is "false", the package can be installed in a local zone only.
For installing in the global zone only you have to use the "-G" option then.

Look at #man -s5 pkginfo

Michael Weis


> Can I safely run pkgadd and pkgrm to add/remove pkgs from non-global
> zones?  I want to create non-sparse zones but some of them need
> packages I don't wish to add to all zones.  If I add a package from
> the global zone, the only options are global-zone-only or all-zones.

> Assuming that works, how do I keep the non-global zone patched?
> Running smpatch from the global zone patches all zones.  Can I just
> run smpatch from the non-global zone?

> Yes, I will be "upgrading" to pca eventually.

> -frank

 
 
 

adding pkgs to non-global zones

Post by Frank Cusac » Mon, 22 May 2006 05:17:06



Quote:> hi Frank,

> if a package must be installed in all zones identically or not is defined in
> 3 new parameters in the pkginfo file within the package.

> The parameter SUNW_PKG_ALLZONES is the moste relevant for your question. If
> the value is "true" the package _must_ be installed and identical in all
> zones and it _must_ be installed by the global zone admin.

> If the value is "false", the package can be installed in a local zone only.
> For installing in the global zone only you have to use the "-G" option then.

OK, that's good.

But how do I manage patches for packages installed only in non-global zones?

-frank

 
 
 

adding pkgs to non-global zones

Post by Lion- » Tue, 23 May 2006 07:21:35


Quote:> Can I safely run pkgadd and pkgrm to add/remove pkgs from non-global zones?

That depends on the way those zones are setup and the packages you're trying to
install/remove. If your non-global zone is build up from directory dependencies
then I think its pretty obvious that you won't succeed in running the removal
of a package since it may /look/ as if its installed but its actually on the
global zone and 'shared' across the other zones.  And vica versa.

But if you install a complete non-global zone (with a minimum of dependencies)
then yes; it will behave like any other zone.

Quote:> Assuming that works, how do I keep the non-global zone patched?  Running
> smpatch from the global zone patches all zones.  Can I just run smpatch from
> the non-global zone?

Why not just giving it a try before asking ?  That would have cleared it up for
you pretty well.

--
Groetjes, Peter

.\\ PGP/GPG key: http://www.catslair.org/pubkey.asc

 
 
 

adding pkgs to non-global zones

Post by Frank Cusac » Tue, 23 May 2006 08:48:48



Quote:>> Can I safely run pkgadd and pkgrm to add/remove pkgs from non-global zones?

> That depends on the way those zones are setup and the packages
> you're trying to install/remove. If your non-global zone is build up
> from directory dependencies

As I said originally, I am creating non-sparse zones.  (That's the
awkward Sun terminology.)

Quote:>> Assuming that works, how do I keep the non-global zone patched?  Running
>> smpatch from the global zone patches all zones.  Can I just run smpatch from
>> the non-global zone?

> Why not just giving it a try before asking ?  That would have
> cleared it up for you pretty well.

Whether it actually works is different from if it is expected to work.
I don't want to get into a habit that happens to work, but then breaks
because something was "fixed".

-frank

 
 
 

adding pkgs to non-global zones

Post by Dave Mine » Fri, 26 May 2006 03:54:13




>>> Can I safely run pkgadd and pkgrm to add/remove pkgs from non-global zones?
>> That depends on the way those zones are setup and the packages
>> you're trying to install/remove. If your non-global zone is build up
>> from directory dependencies

> As I said originally, I am creating non-sparse zones.  (That's the
> awkward Sun terminology.)

>>> Assuming that works, how do I keep the non-global zone patched?  Running
>>> smpatch from the global zone patches all zones.  Can I just run smpatch from
>>> the non-global zone?
>> Why not just giving it a try before asking ?  That would have
>> cleared it up for you pretty well.

> Whether it actually works is different from if it is expected to work.
> I don't want to get into a habit that happens to work, but then breaks
> because something was "fixed".

Yes, it's expected and supported to run pkgadd/pkgrm within a non-global
zone to manage packages meant to be installed only in that zone.

Dave

 
 
 

adding pkgs to non-global zones

Post by Frank Cusac » Fri, 26 May 2006 05:17:57





[attribution lost]:
>>>> Assuming that works, how do I keep the non-global zone patched?  Running
>>>> smpatch from the global zone patches all zones.  Can I just run smpatch from
>>>> the non-global zone?
>>> Why not just giving it a try before asking ?  That would have
>>> cleared it up for you pretty well.
>> Whether it actually works is different from if it is expected to
>> work.
>> I don't want to get into a habit that happens to work, but then breaks
>> because something was "fixed".

> Yes, it's expected and supported to run pkgadd/pkgrm within a
> non-global zone to manage packages meant to be installed only in that
> zone.

That wasn't the question (that you're answering).  That pkgadd/pkgrm is
expected to work in non-global zones seems to have already been answered.

The part that Lion-O asked that I should just try, and that I said I wanted
to know what is expected, is how to manage patches for packages installed
in non-global zones.

thanks
-frank

 
 
 

1. Advice sought: global zone pkgs vs. local zone pkgs

i'm running into a situation where some of our packages don't
install onto a local zone as a result of inheritance from
the global zone.  (some have request scripts, for example.)

the question--before i go any further:
does it make sense to install a small cluster, like SUNWCuser
on the global zone, and bigger clusters on the local zones?
(assuming that's what you need.)  or do you install
the biggest cluster of all the local zones onto the global zone?
or is it basically assumed that all the zones will have the
same cluster/pkgs?

assuming that having different clusters is possible, here's
the tradeoffs i see:
if the global zone has everything then, if the patches work
right, patching the global should do the right thing
for everybody (assuming that's what you want).
disadvantage:  you have to go to the trouble of
deleting packages from the local zones by hand.
and that can be a real chore.

if the global zone is small, i don't know whether a patch
that's not needed in the global but is needed in a local
will know how to patch just the local zone.
and you have to add packages by hand to the local zones.
also a real chore.

and, furthermore, this all assumes that it's possible to
get different clusters installed one the zones.  and it
further assumes that getting all those zones set up is
a feasible thing.   it appears to me that these assumptions
have a good chance of being wrong, and that renders the
questions above moot.

j.
--

Head of Sun Support, Sr. Operating Systems Specialist
Applied Research Labs, Computer Science Div.                   S224
University of Texas at Austin

2. tracking a "potential hacker"

3. Viewing non-global routes from global zone

4. EZ-2000+ series help

5. patchadd fails on non-global non-sparse non-running zones

6. Installing Linux on a Quantum Bigfoot HD

7. Problems with remove packages in non-global zone

8. strange goings on...

9. solaris 10 pkgadd in non-global zone cpio error

10. ISC dhcpd in a Solaris 10 non-global zone - working!

11. Fwd: cvs commit: ports/java Makefile ports/java/jboss2 Makefile distinfo pkg-comment pkg-deinstall pkg-descr pkg-install pkg-plist

12. Global zone and resource pool

13. Solaris 10 Global on Intranet, and Zone in Extranet