Sun Microsystems
Products & Services
 
Support & Training
 
 

Previous Previous     Contents     Index     Next Next
Chapter 4

Planning Your Deployment

This chapter describes what you need to plan before starting the configuration stages and deploying the software load to a cluster. This chapter includes the following sections:

Defining Your Cluster

When choosing your hardware and software configuration, you must decide the following:

  • The services you want to run on each node group

  • Whether you want to deploy user applications or third party software on the cluster

Planning Your Cluster

You must define your cluster hardware configuration before you start to configure your deployment environment. If you use an example hardware configuration, you can use the template files for configuring the cluster that are provided for that hardware configuration. For information about the example hardware configurations, see the Netra High Availability Suite Foundation Services 2.1 6/03 Hardware Guide.

Planning Node Groups

Nodes belonging to a node group share the following properties:

  • Node type. For example, master-eligible nodes, diskless nodes, or dataless nodes.

  • Operating system. For example, Solaris 9 operating system.

  • Architecture. For example, SPARC.

  • Class. For example, sun4u.

  • Foundation Services configuration. For example:

    • NHAS_MASTER_ELIGIBLE

      • RBS

      • NSM

      • WDT_MASTER_ELIGIBLE

    • NHAS_DATALESS

      • WDT_DATALESS

    • NHAS_DISKLESS

      • MAC_ADDR_POLICY or STATIC_CLIENT_ID_POLICY

      • WDT_DISKLESS

  • Software. For example, the same user applications.

  • Peripheral capabilities. For example, the same disk and I/O card capabilities.

The node groups are defined so that groups of hardware can be configured to run particular services and applications. For example, you can define a node group for two master-eligible nodes called master_el, that can be configured to run a selection of Foundation Services.

For information on how to configure node groups, see Defining Nodes and Node Groups.

Planning Services for Your Cluster

Each node group must be assigned core services that are defined by core services lists. The core service list that you assign to a node group depends on the role of the node group. The following table summarizes the core service lists.

Table 4-1 Predefined Core Service Lists

Node Group

Core Service List

Description

Master-eligible

NHAS_MASTER_ELIGIBLE

Full range of services, including:

  • CGTP

  • CMM

  • SNDR

  • Reliable NFS

  • Daemon Monitor

  • Node Management Agent

Diskless

NHAS_DISKLESS

  • CGTP

  • CMM

  • Daemon Monitor

  • Node Management Agent

Dataless

NHAS_DATALESS

  • CGTP

  • CMM

  • Daemon Monitor

  • Node Management Agent

When the core services have been defined, optional services can be added. The following table describes the optional service lists.

Table 4-2 Optional Service Lists

Node Group

Service List

Description

Master-eligible node group

NSM

Node State Manager

 

WDT_MASTER_ELIGIBLE

Watchdog timer for master-eligible nodes

Master-eligible node group that contains diskless nodes

RBS

Reliable Boot Service. To enable a diskless node to boot, you must assign the RBS option.

Diskless node group

WDT_DISKLESS

Watchdog timer for diskless nodes

Dataless node group

WDT_DATALESS

Watchdog timer for dataless nodes

Previous Previous     Contents     Index     Next Next