Clustering Solaris Zones/Containers Post: 302187543

Sponsored Content

Operating Systems Solaris Clustering Solaris Zones/Containers Post 302187543 by trouphaz on Monday 21st of April 2008 11:51:47 AM

04-21-2008

Registered User

Quote:

Originally Posted by DukeNuke2

yes, you can do that. with the new version of cluster 3.2 you can also cluster linux zones Smilie

also you don't have to cluster the app... you can cluster the whole zone! but the best practice depends on what exactly you want to do!

hth,
DN2

one of the issues that we're trying to address with clustering the zone vs clustering the app has to do with patching. with app level clustering as it is now, you can patch the OS on the offline node and then fail the service groups over after your are complete. if there are any issues you can go back to the previous system and recover the offline node or if not you can proceed with patching the other system that is now the offline node.

with zones, at some point you need to patch the zone itself since even with a sparse root you have files that need to be updated. during that time, you either just have the app down or hope that nothing happens while you patch.

i'm looking for maximum uptime including system maintenance (and management likes the option for application isolation).

trouphaz

View Public Profile for trouphaz

Find all posts by trouphaz

5 More Discussions You Might Find Interesting

1. Solaris

solaris containers/zones reboot order

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...

2. Solaris

need help on containers/zones

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...

3. Solaris

Solaris 8 Containers

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 ...

4. Solaris

difference between zones and containers

Hi Expects, Can broadly explain difference between Zones and containers.

5. Red Hat

Looking for equivalent of Solaris containers/zones in RHEL7 Linux

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...

LEARN ABOUT CENTOS

crm_node

PACEMAKER(8)						  System Administration Utilities					      PACEMAKER(8)

NAME

       Pacemaker - Part of the Pacemaker cluster resource manager

SYNOPSIS

       crm_node command [options]

DESCRIPTION

       crm_node - Tool for displaying low-level node information

OPTIONS

       -?, --help
	      This text

       -$, --version
	      Version information

       -V, --verbose
	      Increase debug output

       -Q, --quiet
	      Essential output only

   Stack:
       -A, --openais
	      Only try connecting to an OpenAIS-based cluster

       -H, --heartbeat
	      Only try connecting to a Heartbeat-based cluster

   Commands:
       -n, --name
	      Display the name used by the cluster for this node

       -N, --name-for-id=value
	      Display the name used by the cluster for the node with the specified id

       -e, --epoch
	      Display the epoch during which this node joined the cluster

       -q, --quorum
	      Display a 1 if our partition has quorum, 0 if not

       -l, --list
	      Display all known members (past and present) of this cluster (Not available for heartbeat clusters)

       -p, --partition
	      Display the members of this partition

       -i, --cluster-id
	      Display this node's cluster id

       -R, --remove=value
	      (Advanced) Remove the (stopped) node with the specified name from Pacemaker's configuration and caches

       In the case of Heartbeat, CMAN and Corosync 2.0, requires that the node has already been removed from the underlying cluster

   Additional Options:
       -f, --force

AUTHOR

       Written by Andrew Beekhof

REPORTING BUGS

       Report bugs to pacemaker@oss.clusterlabs.org

Pacemaker 1.1.10-29.el7 					     June 2014							      PACEMAKER(8)