2.5 Cloud Manager Application Server Requirements

Use the requirements in this section to plan your deployment of the Cloud Manager Application Server.

2.5.1 Requirements for the Application Server

The network machine where you install Cloud Manager Application Server software must meet the requirements in Table 2-5:

Table 2-5 Application Server Requirements

Item

Requirement

Operating System

SUSE Linux Enterprise Server 11 Service Pack 4 (SLES 11 SP 4) on the 64-bit (x86-64) architecture (Intel processor or AMD Opteron processor)

Hardware

  • Processor:

    • Minimum: 2.5 GHz 64-bit (or equivalent) Intel processor or AMD Opteron processor

    • Recommended: Dual-Core, 2.5 GHz (or greater) 64-bit, Intel processor or AMD Opteron processor

  • RAM:

    • Minimum: 4 GB

    • Recommended: 6 GB (or greater)

  • Disk Space: 40 GB

If the Cloud Manager Application Server and Cloud Manager Orchestration Server are on the same server, the following are minimum requirements:

  • 4 Pentium-class CPU cores

  • 40 GB disk space

  • 4 GB RAM

Database

PostgreSQL 9.2 (included with SLES 11 SP 4)

You can use a local or external PostgreSQL database for use with the Orchestration Server. We recommend that you install and run PostgreSQL on a different server than where you install Orchestration Server.

Authentication Source

Cloud Manager supports the following authentication methods:

  • NetIQ eDirectory (LDAP)

  • Microsoft Active Directory (LDAP)

  • NetIQ Access Manager

2.5.2 Port Requirements for the Application Server

Table 2-6 identifies the ports and protocols required by the Cloud Manager Application Server. The ports (or their substitutes if you are not using the defaults) must be open for both inbound and outbound communication.

Table 2-6 Port Requirements for the Cloud Manager Application Server

Port Number

Protocol

Function

8061

TCP

Used by ESB HTTP.

8102

TCP

(secure) Used by Karaf SSH.

8181

TCP

Used by the Karaf Management console.

8182

TCP

(not secure) Used by Jetty HTTP (default).

8183

TCP

(secure) Used by Jetty HTTPS (default).

10990

TCP

Used by the RMI Registry.

61613

TCP

Used by the active MQ Stomp.

61616

TCP

Used by the active MQ Openwire.

VNC ports

(1000–1xxx)

TCP

Used by connections to VM consoles through a VNC client.

By default, a VNC proxy port is chosen at random, however the port can be set by the Cloud Administrator in the Configuration page of the Cloud Manager Web Console. There is also an option for an external proxy to offload the traffic from the Cloud Manager Application Server.

Typically, this means TCP port 1000 for the first VM on a VM host, 1001 for the second, and so on. These connections go to the VM host, exposing the console on behalf of the VM.

For more information, see Configuring Remote Console Access to Workloads in the Cloud Manager Procedures Guide.