Sponsored Content
Operating Systems Solaris Available design options for a cluster hosting many different virtualized Solaris versions Post 302902374 by Peasant on Tuesday 20th of May 2014 08:52:39 AM
Old 05-20-2014
LDOM (Oracle VM server for SPARC), with HA LDOM solaris cluster between physical nodes, it will cost you since SC is 'per core'.

Trouble is : If a node fails for some reason, cluster will only boot the LDOM on the next host (couple of minutes of downtime, but downtime).

You can migrate old machines to future LDOMs using flar archive or similar method.

Option is using LDOMs and running Solaris cluster between virtual machines. Depending on your resource (application) you will be able to configure active / active or active / passive.

If a node dies, other node and its ldom with SC will takeover, while you can just import the rest of the machines (ldoms) to working node (what SC HA LDOM does, but automatically, in above example).

Be sure to have auto-boot?=false for all ldom's which are on shared storage.
You don't want to boot root zpool on two nodes at once Smilie

You might also use bare metal with branded zones (doubtful solaris 8 will work that way) and Solaris cluster with HA ZONE or Solaris cluster zone cluster for high availability.
Or just importing the zone manually if the node dies, since zone rpool will not import on another node if configured properly (it will give error that it is active on another node).

Hope that helps
Regards
Peasant.
This User Gave Thanks to Peasant For This Post:
 

6 More Discussions You Might Find Interesting

1. Solaris

Solaris versions

Hi, Does anyone know if the various releases of Solaris are archived anywhere? I work for a DR company and it would be useful to have different releases of a Solaris version number i.e. Solaris 10 6/06 (3 Replies)
Discussion started by: callmebob
3 Replies

2. UNIX for Dummies Questions & Answers

Design Options for Property Files

Dear all, Hello and Good Morning. I have a properties file in a specific directory in UNIX that can be accessed by certain users. This properties file is being used by a number of backend programs. The properties file contain the username and the password of the database as well. How do I design... (1 Reply)
Discussion started by: jackal28
1 Replies

3. High Performance Computing

Building a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris

Provides a description of how to set up a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris. More... (0 Replies)
Discussion started by: Linux Bot
0 Replies

4. Solaris

How to know which versions we are using c, c++ in Solaris.

How to know which versions we are using c, c++ in Solaris. Thanks & Regards Durgaprasad (1 Reply)
Discussion started by: durgaprasadr13
1 Replies

5. Solaris

Solaris 10 - Zones - Design thoughts

Good morning to one and all :-) About to set up a M5000 server, then create a few zones to port over a few apps. So, anyone had experience of zones ? and what things I need to consider / design / workout before hand ?? I need to work out whats going to be ported over, what the ip... (6 Replies)
Discussion started by: sbk1972
6 Replies

6. UNIX for Dummies Questions & Answers

MilesWeb.com shared hosting or unlimited hosting plans?

I want to host a website in India, after all my research I have found MilesWeb.com, I am planning to go for their shared plan http://www.milesweb.com/cpanel-hosting.php I have test their contact options and response time, they are really available 24/7. I have checked few other providers, they... (1 Reply)
Discussion started by: Guruguy
1 Replies
cmdeleteconf(1m)														  cmdeleteconf(1m)

NAME
cmdeleteconf - Delete either the cluster or the package configuration SYNOPSIS
cmdeleteconf [-f] [-v] [-c cluster_name] [[-p package_name]...] DESCRIPTION
cmdeleteconf deletes either the entire cluster configuration, including all its packages, or only the specified package configuration. If neither cluster_name nor package_name is specified, cmdeleteconf will delete the local cluster's configuration and all its packages. If the local node's cluster configuration is outdated, cmdeleteconf without any argument will only delete the local node's configuration. If only the package_name is specified, the configuration of package_name in the local cluster is deleted. If both cluster_name and pack- age_name are specified, the package must be configured in the cluster_name, and only the package package_name will be deleted. cmdelete- conf with only cluster_name specified will delete the entire cluster configuration on all the nodes in the cluster, regardless of the con- figuration version. The local cluster is the cluster that the node running the cmdeleteconf command belongs to. Only a superuser, whose effective user ID is zero (see id(1) and su(1)), can delete the configuration. To delete the cluster configuration, halt the cluster first. To delete a package configuration you must halt the package first, but you do not need to halt the cluster (it may remain up or be brought down). To delete the package VxVM-CVM-pkg (HP-UX only), you must first delete all packages with STORAGE_GROUP defined. While deleting the cluster, if any of the cluster nodes are powered down, the user can choose to continue deleting the configuration. In this case, the cluster configuration on the down node will remain in place and, therefore, be out of sync with the rest of the cluster. If the powered-down node ever comes up, the user should execute the cmdeleteconf command with no argument on that node to clean up the config- uration before doing any other Serviceguard command. Options cmdeleteconf supports the following options: -f Force the deletion of either the cluster configuration or the package configuration. -v Verbose output will be displayed. -c cluster_name Name of the cluster to delete. The cluster must be halted already, if intending to delete the cluster. -p package_name Name of an existing package to delete from the cluster. The package must be halted already. There should not be any packages in the cluster with STORAGE_GROUP defined before having a package_name of VxVM-CVM-pkg (HP-UX only). RETURN VALUE
Upon completion, cmdeleteconf returns one of the following values: 0 Successful completion. 1 Command failed. EXAMPLES
The high availability environment contains the cluster, clusterA , and a package, pkg1. To delete package pkg1 in clusterA, do the following: cmdeleteconf -f -c clusterA -p pkg1 To delete the cluster clusterA and all its packages, do the following: cmdeleteconf -f -c clusterA AUTHOR
cmdeleteconf was developed by HP. SEE ALSO
cmcheckconf(1m), cmapplyconf(1m), cmgetconf(1m), cmmakepkg(1m), cmquerycl(1m). Requires Optional Serviceguard Software cmdeleteconf(1m)
All times are GMT -4. The time now is 10:48 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy