Implementation Worksheet: Data Center Edition, Premium Edition
This worksheet is designed to help you gather the values and information you'll need to implement a Cassatt Active Response environment for utility computing. I listed each document you might use, and each value you'll need as you follow the document. Next to each value I noted the planning document that will help you determine the right value for your implementation.
Although I put the tasks in roughly the order you'll do them, you may do them in a slightly different order, and you might not need all of the documents I listed.
You can print this document if you want to record your values and make notes as you work through the installation.
Control node and switch setup
Use this document if you are installing Premium Edition (which uses a single control node), regardless of vendor:
Control Node Setup: Single Server (All)
Use one of these documents if you are installing Data Center Edition with two control nodes:
Control Node Setup: Dual Servers (Dell/HP)
Control Node Setup: Dual Servers (IBM)
* Dual control nodes only
Installing Red Hat ELAS on the control node(s)
The Red Hat ELAS installation calls for the values in the following table. A few values used in setting up control node hardware are used again when installing Red Hat ELAS; those values are not repeated in this section.
Control Node: Installing Red Hat ELAS
Configuring storage
Use the following table to record shared storage information.
Control Node: Configuring Storage Access
Installing Cassatt Active Response
Several values used in setting up control node hardware are used again when installing Cassatt Active Response; those values become the defaults during installation and are not repeated in this section.
Control Node: Installing Cassatt Active Response
* Dual control nodes only
top
Adding networks and switches to Cassatt Active Response (Data Center Edition only)
Adding networks and switches to Cassatt Active Response allows you to take advantage of the Network Manager for applications that have networking requirements beyond a single, flat network. For more information, read Understanding Cassatt Active Response Network Manager.
Adding networks and switches to Cassatt Active Response is a simple process in the Cassatt Active Response Controller; you will need the information in the following tables for each network and switch Cassatt Active Response will manage.
Networks
Switches
Item |
Your Value(s) |
Background or planning document |
Switch type |
|
N/A |
Connection type |
|
Connection information:
Hostname or IP Address
Port Number
Login
Password
Device Prompt (if needed for the connection type) |
|
Adding application nodes
Several values used in setting up control node hardware and installing Cassatt Active Response are used again when in this section; those values are not repeated in this section.
Application Node Setup: Dell
Application Node Setup: HP
Application Node Setup: IBM
Application
Node Setup: Nodes That Use External Power Controllers
External Power Controllers: Configuration and Setup
Application
Node Setup: Virtual Power Controllers
IBM BladeCenters only:
External power controllers only:
top
Adding applications
Understanding Blueprints for Deploying Applications
For each image you are deploying, you'll need most of the values from the following three tables. The actual values you'll need depend on your image type: Cassatt Active Response collects slightly different information, and in a slightly different order, based on the operating system and whether the application is a Virtual Machine Monitor (VMM).
Image capture
Item |
Your Value(s) |
Background or planning document |
Image name |
|
N/A |
Image version |
|
Image type (linux, vmhost, windows, solaris) |
|
IP address of the image host |
|
Root password for the image host |
|
Description of image |
|
Requires personalization |
|
Understanding Image Creation and Capture |
Instance-specific directories |
|
Custom attributes |
|
Hardware architecture (ia32, sparc) |
|
Hardware requirements:
Min/max CPU speed
Min/max CPUs/node
Min/max RAM
Min/max NICs
HBA/HBA key
Local disk (y/n)
Min/max local disk size
Swap space
Temp space (y/n) |
|
Local installation |
|
Alternative to NFS: Image on Local Disk |
System timeout |
|
Understanding Image Creation and Capture |
OS name |
|
N/A |
OS version |
|
OS monitoring:
SNMP (y/n)
SNMP port
Read community
SNMP timeout
SNMP collection interval
SNMP retry count
Ping (y/n)
Ping timeout
Ping collection interval
Ping retry count
Script (y/n)
Script pathname
Script timeout
Script collection interval
Script retry count
|
|
Understanding Monitoring Collectors |
Use a copy of the next table for each application that you want to monitor.
Item |
Your Value(s) |
Background or planning document |
Application name |
|
N/A |
Application version |
|
Application description |
|
Application monitoring:
SNMP (y/n)
SNMP port
Read community
SNMP timeout
SNMP collection interval
SNMP retry count
HTTP (y/n)
HTTPS (y/n)
HTTP port
HTTP path
HTTP timeout
HTTP collection interval
HTTP retry count
Script (y/n)
Script pathname
Script timeout
Script collection interval
Script retry count
JMX (y/n)
JMX user name
JMX password
JMX listen port
JMX classpath
JMX timeout
JMX collection interval
JMX retry count |
|
Understanding Monitoring Collectors |
Tier creation
Several values are prepopulated from those you entered during image capture. You can change the values during tier creation when the tier requirements differ from those captured for the image, so those items are repeated in this table.
Item |
Your Value(s) |
Background or planning document |
Name |
|
N/A |
Description |
|
Image |
|
Email alerts on/off
Email address
Email on tier critical
Email on tier warning |
|
Understanding Tier Configuration and Personalization |
Reboot on failure (y/n) |
|
Auto move to maintenance pool |
|
Priority |
|
Node harvesting on/off |
|
Operational target |
|
Minimum nodes |
|
Maximum nodes |
|
Hardware requirements:
Architecture
Min/max CPU speed
Min/max CPUs
Min/max RAM
Min/max NICs
IP multipathing
Min local disk size
HBA/HBA key |
|
Custom attributes |
|
Tier depends on another tier |
|
Use a copy of the next table for each network the tier requires (Data Center Edition only).
top
Was this article useful? Tell us what you think.
Email infocentral@cassatt.com.
|