Re: [zones-discuss] E20K VCS in non-global Zone
Hi, Please read this white paper for understanding how VCS clustering is done with zones. http://www.computerworld.com/action/whitepapers.do?command=viewWhitePape rDetailcontentId=9005992intsrc=wp_li_spons White paper is titled Implementing Solaris(tm) Zones with Veritas(tm) Cluster Server by Symantec Essentially, In the Service Group, DiskGroup, Mount type resources come first and then on top of them there is a resource of type Zone and then on top of it is an IP type resource for configuring VIP inside the zone. Mounting of lofs is handled still by zone (based on zonecfg config done earlier) while zone is booted from VCS as it is a resource now. So, zone should have auto_boot? Set to false. Hope you are using VCS 5.0 as that is the best recommended with zones eventhough 4.1 has some support I understand. Thanks, Sampath Message: 1 Date: Sat, 28 Jul 2007 00:54:48 PDT From: Chew Tian Hai [EMAIL PROTECTED] Subject: [zones-discuss] E20K VCS in non-global Zone To: zones-discuss@opensolaris.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=UTF-8 Currently, The E20K have been partitioned into 2 domains.Domain A and B have been installed with 3 Zones each. VCS ver 5.0 will be installed and configured to provide Failover of the local-zone on each of the Domain A and B The non-global Zone?s application will be DB2. All the Local-Zone and Data mount-point are configured in a shared storage.I have configure as show bleow: Domain A Configure the file system and mount as shown below: ZONEA /dev/rdsk/c2t30d0s0 /zone/systemA---zonepath /dev/rdsk/c2t30d1s0 /systemA/appsw--Store DB binary and application sw Where /dbdata,dblog and dbarchlog will be configured under Volume Manager to provide failover to Zone B Domain B ZONE B Configure the file system and mount as shown below: /dev/rdsk/c2t30d2s0 /zone/systemA---zonepath /dev/rdsk/c2t30d3s1 /systemA/appsw--Store DB binary and application sw The local-Zone have been installed and setup and set the zonepath as normal file system for DomainA and Domain B as show above Can I put the zonepath as /zone/systemA and Application as lofs file system instead of Volume Manager Control when under VCS control in non-global zone? This message posted from opensolaris.org -- ___ zones-discuss mailing list zones-discuss@opensolaris.org End of zones-discuss Digest, Vol 27, Issue 28 * ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] E20K VCS in non-global Zone
Thank you Mike. Please let me know which services (via rc or SMF) got affected by this. Mainly if they belong to OS or Infrastructure software or applications? This e-mail and its attachments are confidential and solely for the intended addressee(s). Do not share or use them without Fannie Mae's approval. If received in error, contact the sender and delete them. -Original Message- From: Mike Gerdts [mailto:[EMAIL PROTECTED] Sent: Monday, July 30, 2007 11:38 AM To: Kari, Sampath K Cc: zones-discuss@opensolaris.org Subject: Re: [zones-discuss] E20K VCS in non-global Zone On 7/30/07, Kari, Sampath K [EMAIL PROTECTED] wrote: Essentially, In the Service Group, DiskGroup, Mount type resources come first and then on top of them there is a resource of type Zone and then on top of it is an IP type resource for configuring VIP inside the zone. If SMF or rc scripts will start services that require non-loopback addresses are up, you will have race conditions between the normal zone boot process and VCS adding the IP address. The way that I have worked around this is to have the zone boot into single-user mode by default (svcadm milestone -d svc:/milestone/single-user:default), then add an application resource that runs init 3 after the IP address is up. The monitor script for this resource can check to be sure that svcs -o state -H svc:/milestone/multi-user-server:default returns online. I have requested that Symantec improve things in this area. In particular, I have requested: - zones should be able to specify boot arguments - there should be a zone run-level resource type Mike -- Mike Gerdts http://mgerdts.blogspot.com/ ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] E20K VCS in non-global Zone
On 7/30/07, Kari, Sampath K [EMAIL PROTECTED] wrote: Thank you Mike. Please let me know which services (via rc or SMF) got affected by this. Mainly if they belong to OS or Infrastructure software or applications? * NFS If you have NFS mounts via /etc/vfstab or the automounter, the mounts may fail during zone boot because of DNS, NIS, LDAP lookups and/or actual mount requests getting no such route errors. During zone shutdown the IP address will get taken away before the zone shutdown begins, making it impossible for apps running in the zone to shutdown cleanly. There are other problems (bugs) in this area that may or may not be fixed in the version of Solaris you are running that will cause the zone shutdown to fail. This failure may require a reboot of the global zone to recover. * NIS, LDAP, etc. Name service lookups that may be required for applications to start may fail or behave differently. For example, if you are using NIS or LDAP for a name service for passwd, the equivalents of passwd, shadow, user_attr, prof_attr, etc. in the name service will be searched. Depending on the configuration of nsswitch.conf, initial startup may say I can't get to the network name service, so let's assume that files is sufficient. If you restart the app at some other time via svcadm restart (or access the account via su - user, login, etc.) you will likely be able to get to the shared name services and entries in there may make it so that various account attributes are different. * Application-specific There are likely many variants of this... Suppose you have an application server that connects to a database at startup. Further suppose various apps in the server may not be written well, the application server needs to be restarted whenever the database connection is lost (e.g. database bounced). When this app server starts up, it will likely (sometimes) fail to connect to the database. As such, you will have to restart the app server after VCS brings up the IP address. This is not a comprehensive list. It is just a sampling of the types of things that I ran into or could see as likely failure modes when trying to get VCS (and similar service groups in VAD) to work with zones. Mike -- Mike Gerdts http://mgerdts.blogspot.com/ ___ zones-discuss mailing list zones-discuss@opensolaris.org
