How to Deploy Virtual Clusters Using Solaris Zones, and Why
This Sun BluePrints paper introduces the zone cluster, a virtual cluster in which a Solaris Zone is configured as a virtual node. The zone cluster supports the consolidation of multiple cluster applications on a single cluster.
Hi All
Kindly let me know how can I move Solaris 10 OS running update 10 on physical machine to another machine solaris zone running Solaris 10 update 11 (2 Replies)
Trying to set or modify the randomly set hostID of a Solaris 10 virtual/guest machine that I installed on a Windows-XP host machine (using Virtual Box 4.1.12).
I was able to set/modify the hostname of the Solaris 10 virtual/guest machine during installation as well as via the Virtual Box... (4 Replies)
Guys,
I have an old program which has pretty specific instructions that it requires solaris10u4 and the recommended patch cluster releases in april 2008.
I have installed solari10u4, and my questions are :-
1. If i upgrade to the latest patch release would have an impact on the... (0 Replies)
I am learning Solaris Zones and I have the following doubts:
1.Sun has developed both Zones concept as well as Virtual Box concept. To work in Solaris if zones method is there, what is the need for virtual box?
From my little knowledge, I feel virtual box and the whole root zone are same... (4 Replies)
Hi Guys,
I haven't worked on solaris zones earlier. I have a query regarding the zones.
We have MQ software installed on a solaris container. I am not sure on which zone this s/w is intalled.
I have logged into this container via putty.
When I search for the package, I got the package... (7 Replies)
Hi,
for Solaris Patch Clusters version 10_x86_Recommended.zip (Jul 15 2009 / 817 MB - SunSolve)
MD5: be40488b0fb1d081deda69dbca415be3 is correct?
(the problem is that I don't have an account. ...therefore I can't login on Sunsolve for view MD5 page)
yes, is a terrible thread!
... (3 Replies)
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)