Out of Sync: Maddy's Blog

Compellent Technologies has partnered with Sun to offer Solaris Cluster certification on their Storage Center arrays. The interoperability matrix for Compellent is now listed at: 

http://www.sun.com/software/cluster/osp/compellent_interop.xml

The answer:

http://www.sun.com/software/solaris/pdf/cluster_ldoms_final_hi_res.pdf

3PAR storage is Solaris Cluster's newest enterprise class storage partner and is now officially listed on the Solaris Cluster 3rd party storage matrix:

http://www.sun.com/software/cluster/osp/3par_inserv.xml

3PAR is a leading provider of utility storage a category of highly virtualized and dynamically tiered storage arrays. The inclusion of 3PAR support on Solaris Cluster adds another dynamic storage option for Solaris Cluster customers to deploy.

One of the common issues I face is having many pools with the same name. This happens many times I reinstall the OS for a new build of Sun Cluster software is out to test.  I use standard naming conventions and hence when I create a new pool without checking if there is already one with the same name, then I get an error on import:

bash-3.00# zpool import app
cannot import 'app': more than one matching pool
import by numeric ID instead

So how to find out which pools are available?  There are 2 way.  You can either use the ZFS manager GUI if you aren't too comfortable using the CLI or you can execute zpool import command which will list all the potential pools that can be imported:

bash-3.00# zpool import
  pool: app
    id: 17303573419851088164
 state: ONLINE
status: The pool was last accessed by another system.
action: The pool can be imported using its name or numeric identifier and
    the '-f' flag.
   see: http://www.sun.com/msg/ZFS-8000-EY
config:

    app         ONLINE
      raidz1    ONLINE
        c2t1d3  ONLINE
        c2t1d2  ONLINE

  pool: app
    id: 13179891989473835286
 state: ONLINE
status: The pool is formatted using an older on-disk version.
action: The pool can be imported using its name or numeric identifier, though
    some features will not be available without an explicit 'zpool upgrade'.
config:

    app         ONLINE
      c2t1d1    ONLINE

  pool: mysql
    id: 6396206132307901430
 state: ONLINE
status: The pool is formatted using an older on-disk version.
action: The pool can be imported using its name or numeric identifier, though
    some features will not be available without an explicit 'zpool upgrade'.
config:

    mysql       ONLINE
      c2t1d0    ONLINE

  pool: post
    id: 11620670201616239827
 state: ONLINE
status: The pool is formatted using an older on-disk version.
action: The pool can be imported using its name or numeric identifier, though
    some features will not be available without an explicit 'zpool upgrade'.
config:

    post        ONLINE
      c2t0d2    ONLINE

Now that I know the pools and their IDs,

bash-3.00# zpool import 13179891989473835286
bash-3.00# zpool destroy app

Voila!

Zones as the choice of virtualization offers many benefits in Solaris Cluster by virtue of the many options available to suit every need.  But for some new users, it would be a tad confusing with all the options and which one to use for which situation.  I have tried to summarize my views in this blog on the best fit.

To start with, we'll list the options:

1. Failover Zone/ HA Zone

2. Zone node

3. Zone Cluster

How did we end up with so many solutions? The concept of zones is fairly new in Solaris, i.e, starting with Solaris 10.  As the feature matures, more features are added and accordingly the Sun Cluster product starts taking advantage of it.

Now, let us dive into the details!

FAILOVER ZONE/HA ZONE:

The first supported solution for zones on Solaris 10 with Sun Cluster was introduced with the Sun Cluster 3.1u4 release. It is a GDS agent that makes the zone failover from one cluster node to the other. Of course, it requires that the zone configuration on the nodes be identical and the zone be installed on the shared storage for enabling failover.  This solution also has an option of monitoring the applications running inside the zone using SMF. 

It also supports branded zones apart from native zone.  Solaris8, Solaris9 and lx branded zones can also be made HA. The SMF based monitoring is particularly useful for legacy applications that don't have a Sun Cluster agent but still requires HA. This solution has been used in the now famous "Flying Containers" presentations at various events!  GUUG-Frühjahrsfachgespräch 2008 Tutorium Teil 2: Flying Container (German). For over view on the technical implementation, refer to Sun Cluster and Solaris 10 Containers.

ZONE NODE:

The Sun Cluster 3.2 release, enabled zones to be treated like physical nodes to be part of RGs. On 3.2, cluster services are automatically started on any native zone installed and configured on a Sun Cluster node. For those applications that were supported on Solaris Containers, it provided HA out of the box! Hence it is best for those applications which are supported with containers and have a Sun Cluster agent but don't have the requirement of the zone itself failing over in case of a failure.

It is very helpful if you have the application running in a combination of physical nodes and zones. Also those applications which are scalable and have to hosted exclusively in zones.

ZONE CLUSTER:

The feature released in the latest Sun Cluster release SC 3.2u2, introduces a new brand of zone called "cluster".  It enables the administrator to create a set of identical "cluster" zones on various physical cluster nodes that form a virtual cluster.  The administrator can delegate devices and other resources to the Zone Cluster.

This solution is very useful in hosted environments.  A single physical cluster can be partitioned and many virtual clusters can  be created for hosting different applications/isolate the application and data. Refer to the blue print on Deploying Oracle RAC in Zone Clusters.

In summary, there are many options available in Sun Cluster for taking care of your application deployment in Solaris zones.  You can choose which is the best fit once you can understand the benefits of each and hopefully this article was helpful introduction!