1.1 PlateSpin Orchestrate Requirements

This section includes the hardware and software requirements for the following PlateSpin Orchestrate components:

1.1.1 Orchestrate Server

The network machine where you install the Orchestrate Server software must meet the following requirements:

Table 1-1 Orchestrate Server Requirements

Item

Requirement

Server Usage

  • PlateSpin Orchestrate Server: Your server might be capable of handling tasks in addition to the tasks an Orchestrate Server performs for PlateSpin Orchestrate. However, we strongly recommend that you install the Orchestrate Server software on a dedicated server to ensure optimal performance. For example, you might not want the server to host Novell eDirectory™.

    NOTE:Although you can install the PlateSpin Orchestrate Server on a Virtual Machine, do not try to manage that server using PlateSpin Orchestrate. In addition, installing the server on a VM slows down the performance of the product.

  • PlateSpin Orchestrate Monitoring Server: This pattern is an Apache* Web server that is installed alongside the Orchestrate Server.

Refer to the information in Section A.0, PlateSpin Orchestrate Components: Install Patterns for more detail about these patterns.

Operating System

  • SUSE® Linux Enterprise Server 10 (SLES 10) Service Pack 2 (SP2), on the 32-bit (x86) and 64-bit (x86-64) architectures (Intel* and AMD* Opteron* processors)

Hardware

  • Processor: Xeon* 2.8 GHz 32-bit, or equivalent AMD or Intel processor (minimum); Dual-Core Xeon 4 GHz 32-bit or 64-bit (recommended)

  • RAM: 2 GB minimum; 4 GB recommended

  • Disk Space: 350 MB minimum for installing; 1 GB recommended for managing fewer than 100 resources.

Hostname Resolution

The server must resolve device hostnames by using a method such as DNS (recommended).

IP Address

The server must have a static IP address or a permanently leased DHCP address.

NOTE:For more information about the requirements for virtual machine management, see Section 1.1.5, Orchestrate VM Client.

1.1.2 Required Network Resources

The Orchestrate Server must allow traffic on TCP ports 80, 8001, 8100, 8101 (these four ports are configurable), and UDP and TCP port 1099 (mandatory). The following list summarizes the network resources required in a PlateSpin Orchestrate setup:

  • Port 80 is used for the Server Portal when monitoring is not installed. When monitoring is installed, the monitoring related Apache server takes port 80 and the Server Portal is moved to port 8080. The Monitoring Server transparently routes communication for the PlateSpin Orchestrate Server Portal to port 8080.

  • Port 8001 is used for communication with the Administrator Information page.

  • Port 8100 is used with a custom protocol for communication with the Orchestrate Agent and for invoking the zos command line interface or opening the Java* Developer’s toolkit.

  • Port 8101 is also used for invoking the zos command line interface or opening the Java Developer’s toolkit by using TLS.

  • Port 1099 is used with RMI for invoking the zosadmin command line interface and/or for running the Orchestrate Development Client.

Monitored systems (physical and virtual) send metrics to the Monitoring Server on UDP port 8649. The Monitoring Server is installed on the same system as the PlateSpin Orchestrate Server.

Connections to VM consoles are accommodated through a VNC client. Typically, this means TCP port 5900 for the first VM on a VM host, 5901 for the second, and so on. Note that these connections go to the VM host, exposing the console on behalf of the VM.

Datagrid multicast file transfers use UDP ports 4011-4014 are used. UDP port 4000 is used as a datagrid multicast request port and a control channel port. Multicast groups for datagrid multicast-based file transfers are 239.192.10.10-14.

The following illustration shows these relationships.

Figure 1-1 PlateSpin Orchestrate Network Resources

1.1.3 Orchestrate Agent

PlateSpin Orchestrate manages jobs on and gathers data about data center computing resources running the PlateSpin Orchestrate Agent and meet the following minimum requirements:

Table 1-2 Orchestrate Agent Requirements

Item

Requirement

Operating System

Linux machines:

  • SUSE Linux Enterprise Server 9 SP3 (32-bit or 64-bit)

  • SUSE Linux Enterprise Server 10 SP1 (32-bit or 64-bit)

  • SUSE Linux Enterprise Server 10 SP2 (32-bit or 64-bit)

  • SUSE Linux Enterprise Server 11 (32-bit or 64-bit)

  • Red Hat* Enterprise Linux* 4 (32-bit or 64-bit)

  • Red Hat Enterprise Linux 5 (32-bit or 64-bit)

Windows* machines:

  • Windows Server* 2003 (32-bit or 64-bit)

  • Windows Server 2008 (32-bit or 64-bit)

VMware* console operating systems:

ESX machine:

  • ESX 3.0.x /3.5.x

Hardware

The Orchestrate Agent does not require a minimum hardware configuration other than a minimum recommended disk space of 100 MB.

TCP Ports

The computing node communicates with the Orchestrate Server over a custom protocol. The server listens for the agent on port 8100 and 8101 (port 8101 is for secure agent connections). Network firewalls need to allow outgoing agent connections to these ports on the server.

1.1.4 VM Hosts

We recommend that computers designated as VM hosts in your data center be able to host the VM and run it according to designated parameters of the specific VM. The processor architecture must match the designated VM’s processor in architecture, although not in version number. In order for a machine to serve as a host machine, it must also have a hypervisor installed along with the operating system. For a detailed list of the supported hypervisors, see Table 2-2.

Table 1-3 Minimum and Recommended Hardware Requirements for VM Host Machines

Host Operating System

Minimum Requirements

Recommended Hardware

SLES 11

  • x86 or x86_64

  • 2 GB RAM

  • 30 GB Hard Drive Space

  • x86 or x86_64

  • 4+ GB RAM

  • 100+ GB Hard Drive Space

SLES 10 SP2

  • x86 or x86_64

  • 2 GB RAM

  • 30 GB Hard Drive Space

  • x86 or x86_64

  • 4+ GB RAM

  • 100+ GB Hard Drive Space

Windows Server 2008 enabled with Hyper-V

  • 1GHz (x86 processor) or 1.4GHz (x64 processor)

  • 512MB RAM

  • 10 GB Hard Drive Space

  • 2+ GHz

  • 2+ GB RAM

  • 40+ GB Hard Drive Space

ESX 3.0.x/3.5.x

*Subject to the VMWare support matrix

*Subject to the VMWare support matrix

VMware Virtual Center

*Subject to the VMWare support matrix

*Subject to the VMWare support matrix

VMware Server

*Subject to the VMWare support matrix

*Subject to the VMWare support matrix

1.1.5 Orchestrate VM Client

The VM Client allows you to manage VMs in your enterprise. You can install the VM Client interface on the following platforms:

Table 1-4 VM Client Supported Operating Systems and Installation Files

Operating System

Installation File

  • SLES 10 SP2 (32-bit)

  • SLES 10 SP2 (64-bit)

/i386/SLE10/nvmminst

/x86_64/SLE10/nvmminst

  • SLES 11 or SLED 11 (32-bit)

  • SLES 11 or SLED 11 (64-bit)

sles11/i386/SLE11/nvmminst

sles11/x86_64/SLE11/nvmminst

Windows XP or Vista (32-bit or 64-bit)

\Windows\nvmminst.exe

1.1.6 Other Orchestrate Clients

You can monitor and run jobs, run the command line interfaces, and create and modify jobs by using the tools and monitors included with the PlateSpin Orchestrate Clients. PlateSpin Orchestrate manages jobs on and gathers data about data center computing resources that meet the following minimum requirements:

Table 1-5 Orchestrate Client Requirements

Item

Requirement

Operating System

Linux machines:

  • SUSE Linux Enterprise Server 10 SP2 (32-bit or 64-bit)

  • SUSE Linux Enterprise Server 11 (32-bit or 64-bit)

  • SUSE Linux Enterprise Desktop 11 (32-bit or 64 bit)

Windows machines:

  • Windows XP (32-bit or 64-bit)

  • Windows Vista* (32-bit or 64-bit)

Hardware

The Orchestrate Development Client installation does not require a minimum hardware configuration other than a minimum recommended disk space of 100 MB and an SVGA-grade monitor.

TCP Ports

The Orchestrate Clients consist of various components that communicate with the Orchestrate Server:

  • Port 8100 is used with a custom protocol for invoking the zos command line interface or for opening the SDK (Java Developer’s toolkit).

  • Port 8101 is also used for invoking the zos command line interface or opening the Java Developer’s toolkit by using TLS.

  • Port 1099 is used with RMI for invoking the zosadmin command line interface or for running the Orchestrate Development Client.

IMPORTANT:The platforms listed here have been tested for the 2.0 release, and are the only platforms supported at this time.

Some of the install programs for other operating systems that are embedded with the Administrator Information page have not been tested for this release.