Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 

Hardware, Software, and Virtual Machine Requirements for Contrail Service Orchestration

Minimum Hardware Requirements for Contrail Service Orchestration

Table 2 lists the makes and models of node servers and servers that you can use in CSO. When you obtain node servers and servers for CSO, we recommend that you:

  • Select hardware that was manufactured within the last year.
  • Ensure that you have active support contracts for servers so that you can upgrade to the latest firmware and BIOS versions.

The number of node servers and servers that you require depends on whether you are installing a trial or a production environment.

Table 8 shows the required hardware specifications for node servers and servers in a trial environment.

Table 8: Trial Environment or Trial HA Environment

Function

Trial Environment

Trial HA Environment

Node or Server Specification

Storage

Greater than 1 TB of one of the following types:

  • Serial Advanced Technology Attachment (SATA)
  • Serial Attached SCSI (SAS)
  • Solid-state drive (SSD)

Greater than 1 TB of one of the following types:

  • SATA
  • SAS
  • SSD

CPU

One 64-bit dual processor, type Intel Sandybridge, such as Intel Xeon E5-2670v3 @ 2.5 GHz or higher specification

One 64-bit dual processor, type Intel Sandybridge, such as Intel Xeon E5-2670v3 @ 2.5 GHz or higher specification

Network interface

One Gigabit Ethernet (GE) or 10 Gigabit Ethernet interface

One Gigabit Ethernet or 10 Gigabit Ethernet interface

CSO Servers (includes Contrail Analytics in a VM )

Number of nodes or servers

1

3

vCPUs per node or server

48

48

RAM per node or server

256 GB

256 GB

Contrail Cloud Platform for a Centralized Deployment

Number of nodes or servers

1

4–8

  • 3 nodes for Contrail controller, and analytics
  • 1–4 Contrail compute nodes

vCPUs per node or server

48

48

RAM per node or server

256 GB

256 GB

Table 9 shows the required hardware specifications for node servers and servers in a production environment.

Table 9: Production Environment (HA and non-HA)

Server Function

Values

Node or Server Specification

Storage

Greater than 1 TB of one of the following types:

  • SATA
  • SAS
  • SSD

CPU

One 64-bit dual processor, type Intel Sandybridge, such as Intel Xeon E5-2670v3 @ 2.5 GHz or higher specification

Network interface

One Gigabit Ethernet (GE) or 10 Gigabit Ethernet interface

CSO Servers

Number of nodes or servers for a non-HA environment

3

  • 1 central server
  • 1 regional server
  • 1 Contrail Analytics server

Number of nodes or servers for an HA environment

9

  • 3 central server
  • 3 regional server
  • 3 Contrail Analytics servers

vCPUs per node or server

48

RAM per node or server

256 GB

Contrail Analytics Server for a Distributed Deployment

Number of nodes or servers

1

vCPUs per node or server

48

RAM per node or server

256 GB

Contrail Cloud Platform for a Centralized Deployment

Number of nodes or servers

4–28

  • 3 nodes for Contrail controller, and analytics
  • 1–25 Contrail compute nodes

vCPUs per node or server

48

RAM per node or server

256 GB

Software and Virtual Machine Requirements

You must use the software versions that were tested in CSO. This section shows the VMs required for each type of environment.

Table 10 shows complete details about the VMs required for a non-HA trial environment.

Table 10: Details of VMs for a Non-HA Trial Environment

Name of VM

Components That Installer Places in VM

Resources Required

Ports to Open

csp-installer-vm

  • 4 vCPUs
  • 24 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-central-infravm

Third-party applications used as infrastructure services

  • 8 vCPUs
  • 48 GB RAM
  • 200 GB hard disk storage

See Table 14.

csp-central-msvm

All microservices, including GUI applications

  • 8 vCPUs
  • 48 GB RAM
  • 200 GB hard disk storage

See Table 14.

csp-regional-infravm

Third-party applications used as infrastructure services

  • 4 vCPUs
  • 24 GB RAM
  • 200 GB hard disk storage

See Table 14.

csp-regional-msvm

All microservices, including GUI applications

  • 4 vCPUs
  • 24 GB RAM
  • 200 GB hard disk storage

See Table 14.

csp-regional-sblb

Load balancer for device to Fault Management Performance Management (FMPM) microservice connectivity

  • 4 vCPUs
  • 8 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-space-vm

Junos Space Virtual Appliance and database—required only if you deploy virtualized network functions (VNFs) that use this EMS

  • 4 vCPUs
  • 16 GB RAM
  • 200 GB hard disk storage

See Table 14.

csp-contrailanalytics-1

Contrail Analytics for a distributed deployment

For a centralized or combined deployment, you use Contrail Analytics in the Contrail Cloud Platform.

  • 8 vCPUs
  • 48 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-vrr-vm

Virtual route reflector (VRR)

  • 4 vCPUs
  • 8 GB RAM
  • 200 GB hard disk storage

See Table 14.

csp-central-k8mastervm

Central K8 Master VM

  • 4 vCPUs
  • 8 GB RAM
  • 200 GB hard disk storage

-

csp-regional-k8mastervm

Regional K8 Master VM

  • 4 vCPUs
  • 8 GB RAM
  • 200 GB hard disk storage

-

Table 11 shows complete details about VMs and microservice collections required for a production environment without HA.

Table 11: Details of VMs for a Production Environment Without HA

Name of VM or Microservice Collection

Components That Installer Places in VM

Resources Required

Ports to Open

csp-installer-vm

  • 4 vCPUs
  • 64 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-central-infravm

Third -party applications used as infrastructure services

  • 16 vCPUs
  • 64 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-central-msvm

All microservices, including GUI applications

  • 16 vCPUs
  • 64 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-regional-infravm

Third -party applications used as infrastructure services

  • 16 vCPUs
  • 64 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-regional-msvm

All microservices, including GUI applications

  • 16 vCPUs
  • 64 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-regional-sblb

Load balancer for device to microservice connectivity

  • 4 vCPUs
  • 32 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-space-vm

Junos Space Virtual Appliance and database—required only if you deploy VNFs that use this EMS

  • 4 vCPUs
  • 32 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-central-elkvm

Logging applications

  • 4 vCPUs
  • 32 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-regional-elkvm

Logging applications

  • 4 vCPUs
  • 32 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-vrr-vm

VRR

  • 4 vCPUs
  • 8 GB RAM
  • 200 GB hard disk storage

See Table 14.

csp-central-k8mastervm

Central K8 Master VM

  • 4 vCPUs
  • 8 GB RAM
  • 200 GB hard disk storage

-

csp-regional-k8mastervm

Regional K8 Master VM

  • 4 vCPUs
  • 8 GB RAM
  • 200 GB hard disk storage

-

csp-contrailanalytics-1

Contrail Analytics for a distributed deployment

For a centralized or combined deployment, you use Contrail Analytics in the Contrail Cloud Platform.

  • 48 vCPUs
  • 256 GB RAM
  • 300 GB hard disk storage

See Table 14.

Table 12 shows complete details about the VMs for a trial HA environment.

Table 12: Details of VMs for a trial HA Environment

Name of VM or Microservice Collection

Components That Installer Places in VM

Resources Required

Ports to Open

csp-installer-vm

  • 4 vCPUs
  • 48 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-central-infravm1

Third-party applications used as infrastructure services

  • 4 vCPUs
  • 32 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-central-infravm2

Third-party applications used as infrastructure services

  • 4 vCPUs
  • 32 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-central-infravm3

Third-party applications used as infrastructure services

  • 4 vCPUs
  • 32 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-central-lbvm1

Load-balancing applications

  • 4 vCPUs
  • 16 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-central-lbvm2

Load-balancing applications

  • 4 vCPUs
  • 16 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-central-lbvm3

Load-balancing applications

  • 4 vCPUs
  • 16 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-central-msvm1

All microservices, including GUI applications

  • 8 CPUs
  • 64 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-central-msvm2

All microservices, including GUI applications

  • 8 vCPUs
  • 64 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-central-msvm3

All microservices, including GUI applications

  • 8 vCPUs
  • 64 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-regional-infravm1

Third-party applications used as infrastructure services

  • 4 vCPUs
  • 32 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-regional-infravm2

Third-party applications used as infrastructure services

  • 4 vCPUs
  • 32 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-regional-infravm3

Third-party applications used as infrastructure services

  • 4 vCPUs
  • 32 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-regional-msvm1

All microservices, including GUI applications

  • 8 CPUs
  • 32 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-regional-msvm2

All microservices, including GUI applications

  • 8 CPUs
  • 32 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-regional-msvm3

All microservices, including GUI applications

  • 8 CPUs
  • 32 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-regional-lbvm1

Load-balancing applications

  • 4 vCPUs
  • 16 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-regional-lbvm2

Load-balancing applications

  • 4 vCPUs
  • 16 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-regional-lbvm3

Load-balancing applications

  • 4 vCPUs
  • 16 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-space-vm

Junos Space Virtual Appliance and database—required only if you deploy VNFs that use this EMS

  • 4 vCPUs
  • 16 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-contrailanalytics-1

Contrail Analytics for a distributed deployment

For a centralized or combined deployment, you use Contrail Analytics in the Contrail Cloud Platform.

  • 16 vCPUs
  • 48 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-regional-sblb1

Load balancer for device to FMPM microservice connectivity

  • 4 vCPUs
  • 24 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-regional-sblb2

Load balancer for device to FMPM microservice connectivity

  • 4 vCPUs
  • 24 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-vrr-vm1

Virtual route reflector (VRR)

  • 4 vCPUs
  • 8 GB RAM
  • 200 GB hard disk storage

See Table 14.

csp-vrr-vm2

Virtual route reflector (VRR)

  • 4 vCPUs
  • 8 GB RAM
  • 200 GB hard disk storage

See Table 14.

Table 13 shows complete details about VMs and microservice collections required for a production environment with HA.

Table 13: Details of VMs for a Production Environment with HA

Name of VM or Microservice Collection

Components That Installer Places in VM

Resources Required

Ports to Open

csp-installer-vm

  • 4 vCPUs
  • 32 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-central-infravm1

Third-party applications used as infrastructure services

  • 16 vCPUs
  • 64 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-central-infravm2

Third-party applications used as infrastructure services

  • 16 vCPUs
  • 64 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-central-infravm3

Third-party applications used as infrastructure services

  • 16 vCPUs
  • 64 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-central-lbvm1

Load-balancing applications

  • 4 vCPUs
  • 32 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-central-lbvm2

Load-balancing applications

  • 4 vCPUs
  • 32 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-central-lbvm3

Load-balancing applications

  • 4 vCPUs
  • 32 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-central-msvm1

All microservices, including GUI applications

  • 16 vCPUs
  • 64 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-central-msvm2

All microservices, including GUI applications

  • 16 vCPUs
  • 64 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-central-msvm3

All microservices, including GUI applications

  • 16 vCPUs
  • 64 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-regional-infravm1

Third-party applications used as infrastructure services

  • 16 vCPUs
  • 64 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-regional-infravm2

Third-party applications used as infrastructure services

  • 16 vCPUs
  • 64 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-regional-infravm3

Third-party applications used as infrastructure services

  • 16 vCPUs
  • 64 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-regional-msvm1

All microservices, including GUI applications

  • 16 vCPUs
  • 64 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-regional-msvm2

All microservices, including GUI applications

  • 16 vCPUs
  • 64 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-regional-msvm3

All microservices, including GUI applications

  • 16 vCPUs
  • 64 GB RAM
  • 500 GB hard disk storage

See Table 14.

csp-regional-lbvm1

Load-balancing applications

  • 4 vCPUs
  • 32 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-regional-lbvm2

Load-balancing applications

  • 4 vCPUs
  • 32 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-regional-lbvm3

Load-balancing applications

  • 4 vCPUs
  • 32 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-space-vm

Junos Space Virtual Appliance and database—required only if you deploy VNFs that use this EMS

  • 4 vCPUs
  • 32 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-central-elkvm1

Logging applications

  • 4 vCPUs
  • 32 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-central-elkvm2

Logging applications

  • 4 vCPUs
  • 32 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-central-elkvm3

Logging applications

  • 4 vCPUs
  • 32 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-regional-elkvm1

Logging applications

  • 4 vCPUs
  • 32 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-regional-elkvm2

Logging applications

  • 4 vCPUs
  • 32 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-regional-elkvm3

Logging applications

  • 4 vCPUs
  • 32 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-regional-sblb1

Load balancer for device to FMPM microservice connectivity

  • 4 vCPUs
  • 32 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-regional-sblb2

Load balancer for device to FMPM microservice connectivity

  • 4 vCPUs
  • 32 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-regional-sblb3

Load balancer for device to FMPM microservice connectivity

  • 4 vCPUs
  • 32 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-vrr-vm1

Virtual route reflector (VRR)

  • 4 vCPUs
  • 32 GB RAM
  • 300 GB hard disk storage

See Table 14.

csp-vrr-vm2

Virtual route reflector (VRR)

  • 4 vCPUs
  • 32 GB RAM
  • 300 GB hard disk storage

See Table 14.

Contrail Analytics | 32 | Contrail Analytics server | csp-contrailanalytics-1 | 48/256G | 33

| Contrail Analytics server | csp-contrailanalytics-2 | 48/256G | 34

| Contrail Analytics server | csp-contrailanalytics-3 | 48/256G

Table 14 shows the ports that must be open on all VMs in CSO to enable the following types of CSO communications:

  • External—CSO user interface (UI) and CPE connectivity
  • Internal—Connectivity between CSO components

The provisioning tool opens these ports on each VM; however, if you provision the VMs manually, you must manually open the ports on each VM.

Table 14: Ports to Open on CSO VMs

Port Number

CSO Communication Type

Port Function

22

External and internal

SSH

80

Internal

HAProxy

83

External

Network Service Designer

179

External

BGP for VRR

443

External and internal

HTTPS, including Administration Portal and Customer Portal

514

Internal

Syslog receiving port

1414

Internal

Cassandra Java Virtual Machine (JVM)

1936

External

HAProxy status page

1947

External

Icinga service

2181

Internal

ZooKeeper client

2216

External

CSO telemetry converter

2379

Internal

etcd client communication

2380

Internal

etcd peer

2888

Internal

ZooKeeper follower

3000

External

Grafana

3306

Internal

MySQL

3514

External

Contrail Analytics Syslog receiving port

3888

Internal

ZooKeeper leader

4001

Internal

SkyDNS etcd discover

4443

Internal

HAProxy

4505, 4506

Internal

Salt communications

5000, 5001

Internal

Keystone public

5044

Internal

Beats

5543

Internal

Logstash UDP

5601

External

Kibana UI

5665

Internal

Icinga API

5666

Internal

icinga nrpe

5671

Internal

RabbitMQ SSL listener

5672

Internal

RabbitMQ client

6000

Internal

Swift Object Server

6001

Internal

Swift Container Server

6002

Internal

Swift Account Server

6379

Internal

Redis

6543

Internal

Virtualized Network Function manager (VNFM)

7000

Internal

Kubernetes API server

7804

External

Device connectivity

8006

Internal

Network Service Orchestrator

8016

Internal

Notification engine

8080

Internal

cAdvisor

8081

Internal

Contrail Analytics

8082

Internal

Device Management Service (DMS) central

8083

Internal

Activation Service (AS) central

8085

Internal

DMS Schema

8086

Internal

Contrail Analytics

8090, 8091

Internal

Generic container

8528

Internal

Arango Cluster

8529

Internal

Arango DB

8530

Internal

Arango Cluster

8531

Internal

Arango Cluster

9042

Internal

Cassandra native transport

9090

Internal

Swift Proxy Server

9091

Internal

xmltec-xmlmail tcp

9101

External and internal

HA proxy exporter

9102

Internal

jetdirect

9160

Internal

Cassandra

9200

Internal

Elasticsearch

10000

Internal

Docker repository from CSP installer

10248

Internal

kubelet healthz

10255

Internal

kubelet

15100

Internal

Logstash TCP

15672

Internal

RabbitMQ management

30000-32767

Internal

Kubernetes service node range

30900

External

Prometheus

30901

Internal

Kubernetes

35357

Internal

Keystone private

Modified: 2018-03-31