Re: [zones-discuss] New zone, sysidtool:net isn't starting
Blastwave is fine for installing in the global zone. However, this implies that packages added or updated in the global zone would get applied to ALL non-global zones as well. The only issue comes when say you want to install just mysql in one zone and apache2 in another zone. For this you would be better off installing them independently in two separate zones. To take this one step further, one of the really cool differentiators of blastwave from sunfreeware is that you can update all the blastwave packages via pkg-get upgrade. This single action applies all updates. If you ran this in the global zone, it would only update the blastwave packages known about in the global zone. If you install additional packages in a non-global zone, those packages wouldn't get updated. In addition, if the packages in a non-global zone that are unique to that zone break as a result of the pkg-get upgrade in the global zone, the non-global zone wouldn't have a way to reconcile or know that reconciliation was necessary. All that to say, I personally prefer to manage blastwave package sets independently in each non-global zone. Its really just a preference to keep it simple. Brad On Wed, 2007-01-31 at 18:08 -0700, Jerry Jelinek wrote: > Tim Cook wrote: > > So essentially at this time blastwave is just a *bad idea* for global > > zones. Is something like sunfreeware ok then? I assume the -G option > > should work with those packages? > > I don't know a lot of the details of blastwave and how > many different options it gives you. > > However, in some cases the behavior you are seeing is a > "good thing". It is nice sometimes to be able to manage > all of your software across your virtual environments > from a single point (the global zone). In other cases > you want to manage things independently. Generally, you have > the ability to do both with zones (modulo the shared the shared > OS). However, I am not sure if blastwave is zone aware or > not. But, it sounds like zonemgr does a nice job of integrating > with blastwave to solve some of these issues. > > Jerry > ___ > zones-discuss mailing list > zones-discuss@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
RE: [zones-discuss] New zone, sysidtool:net isn't starting
That is correct. With the parms you specified, zonemgr will ask you if you are sure . To automatically answer yes, add a -F. Brad On Wed, 2007-01-31 at 17:04 -0600, Tim Cook wrote: > Nice. So to clarify, after a zone is already added, from the global > zone I can do: > > zonemgr -a modify -n zone1 -G blastwavepkg? > > Also, am I to assume zonemgr defaults to sparse zone as I don't see a -t > s in their. And that if I were to do a -t w, it would be a whole root > zone vs. the sparse? > > > Tim Cook > > > > > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Wednesday, January 31, 2007 4:46 PM > To: Jerry Jelinek > Cc: Tim Cook; [EMAIL PROTECTED]; John Clingan; > zones-discuss@opensolaris.org > Subject: Re: [zones-discuss] New zone, sysidtool:net isn't starting > > I recommend that you restrict blastwave bits to the non-global zone. > That way you cannot end up with package conflicts between the global > zone and non-global zones or between non-global zones. > > I have made installing Blastwave packages really easy for you via > the zonemgr with the "-G " option. Note that this > works for sparse and whole root zones. > > For example the following invocation of zonemgr will >1. Create a sparse (standard inheritied directories) zone >2. named mysql >3. in /zones/mysql >4. with IP address 192.168.0.10 >5. on nic hme0 >6. with CIDR netmask of /24 >7. and add host record for host name mysql >8. Inherit the resolution config from the global zone >9. and Install pkg-get, mysql5, apache2, and all > requisite bits from blastwave. > >zonemgr -a add -n mysql -z /zones -P abc123 \ > -C /etc/resolv.conf -C /etc/nsswitch.conf \ > -I "192.168.0.10|hme0|24|mysql" -G mysql5 -G apache2 > > Note that copying resolv.conf and nsswitch.conf may not > be necessary depending on your global and non-global > configs. This is just what I do on my test system. > > More info available at the Zone Manager site: > http://opensolaris.org/os/project/zonemgr/ > > Hope that helps! > > Brad > > On Wed, 2007-01-31 at 10:32 -0700, Jerry Jelinek wrote: > > Tim Cook wrote: > > > So what about /opt/csw, is there anyway to prevent the zones from > > > linking to it? I know you can't remove it from the inherit-pkg-dir > > > because it says it's invalid. It's been somewhat a pain to use > pkg-get > > > (blastwave) with zones because of it. > > > > I don't think I understand what your configuration is. > > Do you have the 4 standard inherited directories (which doesn't > > include /opt)? Or are you saying you inherit /opt but want > > a private /opt/csw? > > > > If it is the first one, then /opt is not inherited by > > default which is why you get an error when you try to remove it. > > > > If it is the second one, then there are various ways you can > > inherit directories from the global zone but still have private > > subdirectories. The easiest is described in the FAQ here: > > > > http://opensolaris.org/os/community/zones/faq/#cfg_io_usrlocal > > > > for /usr/local but it works just as well for other paths. > > > > If I misunderstood what your question is, please let us know. > > > > Thanks, > > Jerry > > > > > > ___ > > zones-discuss mailing list > > zones-discuss@opensolaris.org > ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] New zone, sysidtool:net isn't starting
Tim Cook wrote: So essentially at this time blastwave is just a *bad idea* for global zones. Is something like sunfreeware ok then? I assume the -G option should work with those packages? I don't know a lot of the details of blastwave and how many different options it gives you. However, in some cases the behavior you are seeing is a "good thing". It is nice sometimes to be able to manage all of your software across your virtual environments from a single point (the global zone). In other cases you want to manage things independently. Generally, you have the ability to do both with zones (modulo the shared the shared OS). However, I am not sure if blastwave is zone aware or not. But, it sounds like zonemgr does a nice job of integrating with blastwave to solve some of these issues. Jerry ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] New zone, sysidtool:net isn't starting
Tim Cook wrote: Hi Gerald, When I run : zonemgr -a modify -n global -G nano I get the following error(s): zlogin: 'zlogin' not applicable to the global zone zlogin: 'zlogin' not applicable to the global zone Error: The wget command is required to download and install the Blastwave pkg-get.pkg package. Any input? zonemgr is version 1.8 Sorry for the confusion. When I was referring to the -G option, I meant for pkgadd. Jerry ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] New zone, sysidtool:net isn't starting
Tim Cook wrote: I'm confused then if /opt is not inherited by default. This was my scenario: Install snv_b55. Then installed the pkg-get tool from blastwave and installed screen, openssh, and a few other utils (all of which go into /opt/csw/whatever. I then created my zpool tank, and then put two zones on that tank /tank/zone1 /tank/zone2. Both of these zones have the /opt/csw/whatever directories that were created by pkg-get, as well as those packages. If I try to remove the packages from the global zone, it also removes it from zone1/2. To me this looks like inheritance??? If I am missing something/doing something wrong, please let me know. To elaborate a little on the suggestion Brad had about using zonemgr, what is really happening here is that you are installing the pkgs from the global zone. The way pkgs get installed depends upon three pkg attributes in the pkg; SUNW_PKG_ALLZONES, SUNW_PKG_HOLLOW, and SUNW_PKG_THISZONE. The attributes are described fully in the "Solaris Containers-Resource Management and Solaris Zones" book but when none of these are set to 'true' then the default behavior, when installing a pkg from within the global zone, is to also install the pkg into each non-global zone. All three of these attributes have a default value of 'false' so most non-core solaris pkgs do not even have these attributes visible in the pgkinfo file. The zones book chapter 23, "About Packages and Patches on a Solaris System with Zones Installed" describes all of this in detail. As Brad pointed out, the way to work around this is to run the pkgadds from within each non-global zone. In this way you can set up completely different /opt configurations on a zone by zone basis. When installing pkgs like this in the global zone, you can use the -G option to prevent their installation in the non-global zones. Jerry ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] New zone, sysidtool:net isn't starting
I recommend that you restrict blastwave bits to the non-global zone. That way you cannot end up with package conflicts between the global zone and non-global zones or between non-global zones. I have made installing Blastwave packages really easy for you via the zonemgr with the "-G " option. Note that this works for sparse and whole root zones. For example the following invocation of zonemgr will 1. Create a sparse (standard inheritied directories) zone 2. named mysql 3. in /zones/mysql 4. with IP address 192.168.0.10 5. on nic hme0 6. with CIDR netmask of /24 7. and add host record for host name mysql 8. Inherit the resolution config from the global zone 9. and Install pkg-get, mysql5, apache2, and all requisite bits from blastwave. zonemgr -a add -n mysql -z /zones -P abc123 \ -C /etc/resolv.conf -C /etc/nsswitch.conf \ -I "192.168.0.10|hme0|24|mysql" -G mysql5 -G apache2 Note that copying resolv.conf and nsswitch.conf may not be necessary depending on your global and non-global configs. This is just what I do on my test system. More info available at the Zone Manager site: http://opensolaris.org/os/project/zonemgr/ Hope that helps! Brad On Wed, 2007-01-31 at 10:32 -0700, Jerry Jelinek wrote: > Tim Cook wrote: > > So what about /opt/csw, is there anyway to prevent the zones from > > linking to it? I know you can't remove it from the inherit-pkg-dir > > because it says it's invalid. It's been somewhat a pain to use pkg-get > > (blastwave) with zones because of it. > > I don't think I understand what your configuration is. > Do you have the 4 standard inherited directories (which doesn't > include /opt)? Or are you saying you inherit /opt but want > a private /opt/csw? > > If it is the first one, then /opt is not inherited by > default which is why you get an error when you try to remove it. > > If it is the second one, then there are various ways you can > inherit directories from the global zone but still have private > subdirectories. The easiest is described in the FAQ here: > > http://opensolaris.org/os/community/zones/faq/#cfg_io_usrlocal > > for /usr/local but it works just as well for other paths. > > If I misunderstood what your question is, please let us know. > > Thanks, > Jerry > > > ___ > zones-discuss mailing list > zones-discuss@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] New zone, sysidtool:net isn't starting
Tim Cook wrote: So what about /opt/csw, is there anyway to prevent the zones from linking to it? I know you can't remove it from the inherit-pkg-dir because it says it's invalid. It's been somewhat a pain to use pkg-get (blastwave) with zones because of it. I don't think I understand what your configuration is. Do you have the 4 standard inherited directories (which doesn't include /opt)? Or are you saying you inherit /opt but want a private /opt/csw? If it is the first one, then /opt is not inherited by default which is why you get an error when you try to remove it. If it is the second one, then there are various ways you can inherit directories from the global zone but still have private subdirectories. The easiest is described in the FAQ here: http://opensolaris.org/os/community/zones/faq/#cfg_io_usrlocal for /usr/local but it works just as well for other paths. If I misunderstood what your question is, please let us know. Thanks, Jerry ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] New zone, sysidtool:net isn't starting
[EMAIL PROTECTED] wrote: FYI, you can also use "create -b" (blank) so you don't have to run remove-pkg-dir 4 times. Actually, the documented way to create a whole-root zone *is* to remove the default inherit-pkg-dir resources. The reason for this is "create -b" says to use a blank template - namely, no properties set and no resources defined. It doesn't mean "create a whole-root zone" and in the future, an empty template might not be the same as a whole-root zone. During the development of the project I suggested we introduce something like "create -w" or "create -t SUNWwhole" ;-) and perhaps it's time to consider that again. Also, with the new duckhorn changes in b56 you no longer have to qualify the resources, so you could remove the inherit-pkg-dir resources with a single command. This will make it a bit easier to create a whole root zone. Jerry ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] New zone, sysidtool:net isn't starting
When using the zone manager you just tack on a "-t w" to zonemgr to create a whole root zone. The default is a sparse zone or if you want to specify it from the command line its "-t s". http://opensolaris.org/os/project/zonemgr/ Brad On Mon, 2007-01-29 at 16:50 -0800, [EMAIL PROTECTED] wrote: > > FYI, you can also use "create -b" (blank) so you don't have to run > > remove-pkg-dir 4 times. > > Actually, the documented way to create a whole-root zone *is* to remove > the default inherit-pkg-dir resources. The reason for this is "create > -b" says to use a blank template - namely, no properties set and no > resources defined. It doesn't mean "create a whole-root zone" and in > the future, an empty template might not be the same as a whole-root > zone. > > During the development of the project I suggested we introduce > something like "create -w" or "create -t SUNWwhole" ;-) and perhaps > it's time to consider that again. > > dsc > ___ > zones-discuss mailing list > zones-discuss@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] New zone, sysidtool:net isn't starting
Learn something new every day. I didn't know that and thanks for the clarification. Your suggestion of introducing a "whole root zone" makes should be revisited. Not because of lazy typists but because of incorrect assumptions folks (like me) might make. [EMAIL PROTECTED] wrote: FYI, you can also use "create -b" (blank) so you don't have to run remove-pkg-dir 4 times. Actually, the documented way to create a whole-root zone *is* to remove the default inherit-pkg-dir resources. The reason for this is "create -b" says to use a blank template - namely, no properties set and no resources defined. It doesn't mean "create a whole-root zone" and in the future, an empty template might not be the same as a whole-root zone. During the development of the project I suggested we introduce something like "create -w" or "create -t SUNWwhole" ;-) and perhaps it's time to consider that again. dsc ___ zones-discuss mailing list zones-discuss@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] New zone, sysidtool:net isn't starting
FYI, you can also use "create -b" (blank) so you don't have to run remove-pkg-dir 4 times. Actually, the documented way to create a whole-root zone *is* to remove the default inherit-pkg-dir resources. The reason for this is "create -b" says to use a blank template - namely, no properties set and no resources defined. It doesn't mean "create a whole-root zone" and in the future, an empty template might not be the same as a whole-root zone. During the development of the project I suggested we introduce something like "create -w" or "create -t SUNWwhole" ;-) and perhaps it's time to consider that again. dsc ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] New zone, sysidtool:net isn't starting
FYI, you can also use "create -b" (blank) so you don't have to run remove-pkg-dir 4 times. John Clingan Sun Microsystems Sent from mobile phone. -Original Message- From: Tim Cook <[EMAIL PROTECTED]> Subj: [zones-discuss] New zone, sysidtool:net isn't starting Date: Mon Jan 29, 2007 4:07 pm Size: 2K To: zones-discuss@opensolaris.org So I started by doing the following to create a zone. The zone resides on a zfs pool. This is the first zone on this system: # zonecfg -z z1 z1: No such zone configured Use 'create' to begin configuring a new zone. zonecfg:z1> create zonecfg:z1> remove inherit-pkg-dir dir=/sbin zonecfg:z1> remove inherit-pkg-dir dir=/usr zonecfg:z1> remove inherit-pkg-dir dir=/platform zonecfg:z1> remove inherit-pkg-dir dir=/lib zonecfg:z1> set autoboot=true zonecfg:z1> set zonepath=/tank/z1 zonecfg:z1> add net zonecfg:z1:net> set address=192.168.2.201 zonecfg:z1:net> set physical=hme0 zonecfg:z1:net> end zonecfg:z1> verify zonecfg:z1> commit zonecfg:z1> exit # zoneadm -z z1 verify # zoneadm -z z1 install # zoneadm -z z1 boot So, I've got the following output from svcs -xv, and the logs themselves show absolutely nothing as far as errors are concerned: # svcs -xv svc:/system/sysidtool:net (sysidtool) State: offline since Mon Jan 29 14:57:58 2007 Reason: Start method is running. See: http://sun.com/msg/SMF-8000-C4 See: man -M /usr/man -s 1M sysidtool See: /var/svc/log/system-sysidtool:net.log Impact: 18 dependent services are not running: svc:/system/sysidtool:system svc:/milestone/sysconfig:default svc:/milestone/multi-user:default svc:/system/webconsole:console svc:/application/graphical-login/cde-login:default svc:/milestone/multi-user-server:default svc:/application/cde-printinfo:default svc:/system/system-log:default svc:/network/smtp:sendmail svc:/system/utmp:default svc:/system/console-login:default svc:/network/ssh:default svc:/network/inetd:default svc:/application/management/wbem:default svc:/system/sac:default svc:/system/postrun:default svc:/network/rpc/bind:default svc:/system/filesystem/autofs:default svc:/network/rpc/smserver:default (removable media management) State: uninitialized since Mon Jan 29 14:55:04 2007 Reason: Restarter svc:/network/inetd:default is not running. See: http://sun.com/msg/SMF-8000-5H See: man -M /usr/share/man -s 1M rpc.smserverd Impact: 1 dependent service is not running: svc:/milestone/multi-user-server:default svc:/system/dbus:default (D-BUS message bus) State: maintenance since Mon Jan 29 14:57:59 2007 Reason: Start method exited with $SMF_EXIT_ERR_FATAL. See: http://sun.com/msg/SMF-8000-KS See: man -M /usr/man -s 1M dbus See: /var/svc/log/system-dbus:default.log Impact: This service is not running. # exit Help??? What did I do wrong here? This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] New zone, sysidtool:net isn't starting
On Mon 29 Jan 2007 at 04:07PM, Tim Cook wrote: > Help??? What did I do wrong here? Tim, Thanks for giving it a spin-- the usability feedback is good. You are doing well so far-- now log into the zone on console (zlogin -C z1) and answer the system identification questions so the zone knows its hostname, name service, etc. (this can also be automated, but for now, do it manually). Sorry this isn't more obvious. Maybe we should add something to the output at the end of installation. -dp -- Daniel Price - Solaris Kernel Engineering - [EMAIL PROTECTED] - blogs.sun.com/dp ___ zones-discuss mailing list zones-discuss@opensolaris.org
[zones-discuss] New zone, sysidtool:net isn't starting
So I started by doing the following to create a zone. The zone resides on a zfs pool. This is the first zone on this system: # zonecfg -z z1 z1: No such zone configured Use 'create' to begin configuring a new zone. zonecfg:z1> create zonecfg:z1> remove inherit-pkg-dir dir=/sbin zonecfg:z1> remove inherit-pkg-dir dir=/usr zonecfg:z1> remove inherit-pkg-dir dir=/platform zonecfg:z1> remove inherit-pkg-dir dir=/lib zonecfg:z1> set autoboot=true zonecfg:z1> set zonepath=/tank/z1 zonecfg:z1> add net zonecfg:z1:net> set address=192.168.2.201 zonecfg:z1:net> set physical=hme0 zonecfg:z1:net> end zonecfg:z1> verify zonecfg:z1> commit zonecfg:z1> exit # zoneadm -z z1 verify # zoneadm -z z1 install # zoneadm -z z1 boot So, I've got the following output from svcs -xv, and the logs themselves show absolutely nothing as far as errors are concerned: # svcs -xv svc:/system/sysidtool:net (sysidtool) State: offline since Mon Jan 29 14:57:58 2007 Reason: Start method is running. See: http://sun.com/msg/SMF-8000-C4 See: man -M /usr/man -s 1M sysidtool See: /var/svc/log/system-sysidtool:net.log Impact: 18 dependent services are not running: svc:/system/sysidtool:system svc:/milestone/sysconfig:default svc:/milestone/multi-user:default svc:/system/webconsole:console svc:/application/graphical-login/cde-login:default svc:/milestone/multi-user-server:default svc:/application/cde-printinfo:default svc:/system/system-log:default svc:/network/smtp:sendmail svc:/system/utmp:default svc:/system/console-login:default svc:/network/ssh:default svc:/network/inetd:default svc:/application/management/wbem:default svc:/system/sac:default svc:/system/postrun:default svc:/network/rpc/bind:default svc:/system/filesystem/autofs:default svc:/network/rpc/smserver:default (removable media management) State: uninitialized since Mon Jan 29 14:55:04 2007 Reason: Restarter svc:/network/inetd:default is not running. See: http://sun.com/msg/SMF-8000-5H See: man -M /usr/share/man -s 1M rpc.smserverd Impact: 1 dependent service is not running: svc:/milestone/multi-user-server:default svc:/system/dbus:default (D-BUS message bus) State: maintenance since Mon Jan 29 14:57:59 2007 Reason: Start method exited with $SMF_EXIT_ERR_FATAL. See: http://sun.com/msg/SMF-8000-KS See: man -M /usr/man -s 1M dbus See: /var/svc/log/system-dbus:default.log Impact: This service is not running. # exit Help??? What did I do wrong here? This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
