|
|
Sponsored Content
Operating Systems
Solaris
Clustering Solaris Zones/Containers
Post 302187523 by trouphaz on Monday 21st of April 2008 10:24:55 AM
04-21-2008
Clustering Solaris Zones/Containers
Hello everyone. I'm working on a fairly large project at my company and have been looking for some guidance. I just happened to stumble on this forum when looking for help with Solaris, so I'm hoping that you all won't mind me bothering you with my questions. 
Anyway, here goes. Is it possible to cluster an application within Solaris 10 Zones/Containers so that we could fail an application and all of its filesystems from one container to another? We are currently using VCS (though would consider other clustering technologies) and their recommendation is to have 2 separate, but identical zones configured on the hosts. This allows you to patch the offline one while the other one runs production. But, I can't seem to find a way to migrate the app from one zone to another for failover. Is this possible or in this scenario is it necessary to also maintain 2 distinct copies of your app, configuration and log files?
Anyway, here goes. Is it possible to cluster an application within Solaris 10 Zones/Containers so that we could fail an application and all of its filesystems from one container to another? We are currently using VCS (though would consider other clustering technologies) and their recommendation is to have 2 separate, but identical zones configured on the hosts. This allows you to patch the offline one while the other one runs production. But, I can't seem to find a way to migrate the app from one zone to another for failover. Is this possible or in this scenario is it necessary to also maintain 2 distinct copies of your app, configuration and log files?
|
|
5 More Discussions You Might Find Interesting
1. Solaris
Hi,
I'm running containers/zones on Solaris 10:
SunOS be2900 5.10 Generic_118833-33 sun4u sparc SUNW,Netra-T12
zoneadm list -vc gives:
ID NAME STATUS PATH
0 global running /
1 bvsmapp01 running /zones/bvsmapp01
2... (3 Replies)
Discussion started by: jabberwocky
3 Replies
2. Solaris
Hello,
I have been using sparc workstations :SUNW,Ultra-5_10
Total 4 such machines. Users use it for mpich programming and all run solaris 8
but I always have hard time maintaining these machines. Authentication for these machines work from solaris 10 using NIS and there are nfs mounts on... (14 Replies)
Discussion started by: upengan78
14 Replies
3. Solaris
While installing a Solaris 8 zone to a Solaris container I received this message. Anyone have this problem?
Patchadd is terminating.
Postprocess: Applying p2v module S31_fix_net
Postprocess: Applying p2v module S32_fix_nfs
Postprocess: Applying p2v module S33_fix_vfstab
... (1 Reply)
Discussion started by: cornsnap
1 Replies
4. Solaris
Hi Expects,
Can broadly explain difference between Zones and containers. (4 Replies)
Discussion started by: Rajesh_Apple
4 Replies
5. Red Hat
Hi, I come from a legacy Solaris background with lots of experience with Solaris Containers/zones that we use for network and process isolation from each other.
Currently we have a RHEL7 Linux VM running on VMWare, but we would like to segment that VM with some form of containers and achieve... (1 Reply)
Discussion started by: ckmehta
1 Replies
LEARN ABOUT DEBIAN
lldptool-app
lldptool(8) Linux lldptool(8) NAME
APP - Show / manipulate APP TLV configuration SYNOPSIS
lldptool -t -i ethx -V APP [-c app] lldptool -T -i ethx -V APP [-d] app=prio,sel,pid DESCRIPTION
The APP TLV is an informational TLV and will advertise the current configured application table. If the peer APP TLV and a local APP TLV match the same selector and protocol field the local parameter is used. ARGUMENTS
app Configures a local application data field using the three parameters priority (prio), selector (sel), and protocol (pid). The -d option can be provided to remove an entry which matches the three parameters. Theory of Operations The APP TLV is an informational TLV for most end stations it is not expected that setting APP data should be required. Peer data will be processed and added to the application data table by default assuming there does not already exist a local entry with matching selector and priority fields. By adding APP data to the application table it is available for applications, eg iscsid, to query. Applications query for a specific proto- col and selector and may use this data to map traffic to the corresponding traffic class. EXAMPLE &; USAGE Configure ISCSI application for priority 4 on eth2 lldptool -T -i eth2 -V APP app=4,2,3260 Configure FCoE application for priority 3 on eth2 lldptool -T -i eth2 -V APP app=3,1,35078 Remove FCoE application for priority 3 on eth2 lldptool -T -i eth2 -V APP -d app=3,1,35078 Display locally configured application table on eth2 lldptool -t -i eth2 -V APP -c app Display last transmitted APP TLV on eth2 lldptool -t -i eth2 -V APP SOURCE
o IEEE 802.1Qaz (http://www.ieee802.org/1/pages/dcbridges.html) NOTES
Currently changing the default priority is not supported by default it is set to zero. SEE ALSO
lldptool(8), lldpad(8) AUTHOR
John Fastabend open-lldp February 2010 lldptool(8)