Skip to main content

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

System requirements and sizing

There are hardware, networking, and operating system requirements for running an HCP for cloud scale system with one or more instances.

Hardware requirements

To install HCP for cloud scale on on-premises hardware for production use, you must provision at least four instances (nodes) with sufficient CPU, RAM, disk space, and networking capabilities. This table shows the minimum and recommended hardware requirements for each instance in an HCP for cloud scale system.

Resource

Minimum

Recommended

RAM

32 GB

128 GB

CPU

8-core

24-core

Available disk space

500 GB 10k SAS RAID

2000 GB 15k SAS RAID

Network interface controller (NIC)(1) 10 Gb Ethernet(2) 10 Gb Ethernet
IP addresses(1) static(2) static
Firewall Port Access Port 443 for S3 API Port 8000 for Admin App GUI Port 9084 for MAPI and Storage Management App GUI Same
Internal IP Ports See NetworkingSame
Network Time IP address of time service (NTP)Same
ImportantEach instance uses all available RAM and CPU resources on the server or virtual machine on which it's installed.

Operating system and Docker minimum requirements

Each server or virtual machine you provide must meet these requirements:

  • 64-bit Linux distribution
  • Docker version 1.13.1 or later installed
  • IP and DNS addresses configured
Additionally, you should install all relevant patches on the operating system and perform appropriate security hardening tasks.
ImportantInstall the current Docker version suggested by your operating system, unless that version is earlier than 1.13.1. The system cannot run with Docker versions prior to 1.13.1.

Operating system and Docker qualified versions

This table shows the operating systems, Docker and SELinux configurations with which the HCP for cloud scale system has been qualified.

Operating systemDocker versionDocker storage configurationSELinux setting
Fedora 27Docker 18.03.0-cedirect-lvmEnforcing
Red Hat Enterprise Linux 7.4Docker 18.03.0-cedirect-lvmEnforcing
Ubuntu 16.04-LTSDocker 17.03.0-ceaufsN/A
CentOS 7.4Docker 18.03.1-ceoverlay2Enforcing

Docker considerations

  • The Docker installation directory on each instance must have at least 20 GB available for storing the HCP for cloud scale Docker images.
  • Make sure that the Docker storage driver is configured correctly on each instance before installing HCP for cloud scale.

    After installing HCP for cloud scale, changing the Docker storage driver requires a reinstallation of HCP for cloud scale.

    To view the current Docker storage driver on an instance, run:

    docker info

  • If you want to enable SELinux on the system instances, you need to use a Docker storage driver that supports it. The storage drivers that SELinux supports differ depending on the Linux distribution you're using. For more information, see the Docker documentation.
  • If you are using the Docker devicemapper storage driver:
    • Make sure that there's at least 40 GB of Docker metadata storage space available on each instance. HCP for cloud scale requires 20 GB to install successfully and an additional 20 GB to successfully update to a later version.

      To view Docker metadata storage usage on an instance, run:

      docker info

    • On a production system, do not run devicemapper in loop-lvm mode. This can cause slow performance or, on certain Linux distributions, HCP for cloud scale may not have enough space to run.

SELinux considerations

  • You should decide whether you want to run SELinux on system instances and enable or disable it before installing HCP for cloud scale.

    Enabling or disabling SELinux on an instance requires you to reboot the instance.

    To view whether SELinux is enabled on an instance, run: sestatus

  • If you want to enable SELinux on the system instances, you need to use a Docker storage driver that supports it.

    The storage drivers that SELinux supports differ depending on the Linux distribution you're using. For more information, see the Docker documentation.

Virtual machine host requirements

You can deploy HCP for cloud scale on virtual machines from a .tgz file. Instances deploying HCP for cloud scale cannot run other software, and multiple HCP for cloud scale nodes cannot be deployed on a single instance. If you want to deploy multiple instance on the same hardware, you need to use a hypervisor and guest VMs and deploy each HCP for cloud scale instance on a separate guest.

The HCP for cloud scale software has been qualified on these virtual machine host platforms:

  • Hitachi Unified Compute Platform (UCP) 4.1.0

Networking

This topic describes the network usage and requirements for both system instances and services.

NoteYou can configure the network settings for each service when you install the system. You cannot change these settings after the system is up and running.
Site hostname

The HCP for cloud scale site hostname is configured during installation. This hostname is very important because it is required for access to:

  • The HCP for cloud scale user interface
  • The S3 API
Instance IP address requirements

All instance IP addresses must be static. This includes both internal and external network IP addresses, if applicable to your system.

ImportantIf the IP address of any instance changes, you must reinstall the system.

For more information, see Handling network changes.

Network types

Each of the HCP for cloud scale services can bind to one type of network, either internal or external, for receiving incoming traffic. If your network infrastructure supports having two networks, you may want to isolate the traffic for most system services to a secured internal network that has limited access. You would then leave the following services on your external network for user access:

  • Admin-App
  • Metadata-Cache
  • Metadata-Coordination
  • Metadata-Gateway
  • Metadata-Policy-Engine
  • Metrics
  • S3-Gateway
  • Tracing-Agent
  • Tracing-Collector
  • Tracing-Query
  • MAPI-Gateway

You can use either a single network type for all services or a mix of both types. If you want to use both types, every instance in your system must be addressable by two IP addresses; one on your internal network, and one on your external network. If you use only one network type, each instance needs only one IP address.

Allowing access to external resources

Regardless of whether you're using a single network type or a mix of types, you need to configure your network environment to ensure that all instances have outgoing access to the external resources you want to use, such as:

  • The storage components where your object data is stored
  • Identity providers for user authentication
  • Email servers that you want to use for sending email notifications
Ports

Each service binds to a number of ports for receiving incoming traffic.

Before installing HCP for cloud scale, you can configure the services to use different ports, or use the default values shown in the tables below.

For information, see (Optional) Reconfigure network.config on each server or virtual machine.

External ports

The following table contains information about the service ports that users use to interact with the system.

On every instance in the system, each of these ports:

  • Must be accessible from any network that requires administrative or data access to the system
  • Must be accessible from every other instance in the system
NoteDebugging ports are accessible only when debug is set to true in install_path/hcpcs/config/cluster.config
Default Port ValueUsed by ServicePurpose
80 (S3 HTTP port, if enabled)S3 GatewayObject persistence and access

443 (S3 HTTPS port)

S3 Gateway

Object persistence and access

8000Admin AppSystem Management application GUI

9099

MAPI Gateway

Object Storage Management application GUI

Internal ports

This table lists the ports used for intrasystem communication by the services. On every instance in the system, each of these ports:

  • Must be accessible from every other instance in the system
  • Should not be accessible from outside the system

You can find more information about how these ports are used in the documentation for the third-party software underlying each service

See also Services.

Default Port ValueUsed ByPurpose
2181SynchronizationPrimary port used to communicate with the service
2888 SynchronizationServer-server communication
3888SynchronizationLeader elections
5000SynchronizationDebugging
5001Admin AppDebugging
5004WatchdogDebugging
5007SentinelDebugging
5050Cluster CoordinationPrimary port used to communicate with the master service
5051Cluster WorkerPrimary port used to communicate with the worker service
5555WatchdogPrimary port used for JMX inter-service communication
5778Tracing AgentAgent HTTP port
6831Tracing Agent UDP port
7000CassandraTCP port for database commands and data
7199CassandraUsed for database JMX connections
7203KafkaUsed for message queue JMX connections
8005Admin AppTomcat shutdown port
8007 Sentinel Tomcat shutdown port
8022 Watchdog SSH
8080Service DeploymentPrimary port used to communicate with the service
8081ChronosPrimary port used to communicate with the scheduling service
8889 Sentinel Primary port used to communicate with the service
9042CassandraPrimary port used to communicate with the database service
9091Network ProxyPrimary port used to communicate with the HA proxy service
9092KafkaPrimary port used to communicate with the message queue service
9190OAuthOAuth port
9191MetricsPrimary port used to communicate with the service
9200ElasticsearchUsed to communicate with Elasticsearch cluster
9201ElasticsearchUsed to communicate with Elasticsearch nodes
9301ElasticsearchElasticsearch intercluster communication
9600LogstashPrimary port used to communicate with the logging service
9601LogstashPort used to listen for syslog connections
9750S3 GatewaySupport
9751Metadata GatewaySupport
9752MAPI GatewaySupport
9753Metadata CacheSupport
9758Metadata Policy EngineSupport
9760Metadata CoordinationSupport
9990S3 GatewayRemote monitoring
9991Metadata GatewayMonitoring
9992MAPI GatewayMonitoring
9993Metadata CacheMonitoring
9998Metadata Policy EngineMonitoring
10000Metadata CoordinationMonitoring
12000S3 GatewayDebugging
12001Metadata GatewayDebugging
12002MAPI GatewayDebugging
12003Metadata CacheDebugging
12004MetricsDebugging
12005Tracing CollectorDebugging
12006Tracing QueryDebugging
12007Tracing AgentDebugging
12008Metadata Policy EngineDebugging
12010Metadata CoordinationDebugging
12500Metadata GatewayRaft RPC Communication
12501Metadata GatewayMetadata RPC Communication
12510Metadata CoordinationRPC communication
12520Metadata Policy EngineRPC communication
13300Metadata CacheCache TCP discovery
13370S3 GatewayCache TCP communication
13371Metadata GatewayCache TCP communication
13372MAPI GatewayCache TCP communication
13373Metadata CacheCache TCP communication
13378Metadata Policy EngineCache TCP communication
13380Metadata CoordinationCache TCP communication
13453Metadata CacheCache TCP communication
13500S3 GatewayCache client connector
13501Metadata GatewayCache client connector
13502MAPI GatewayCache client connector
13503Metadata CacheCache client connector
13508Metadata Policy EngineCache client connector
13510Metadata CoordinationCache client connector
14267Tracing Collector Collecting thrift spans from tracing agents
14268Tracing Collector HTTP port
15050Cluster CoordinationLocal port to which the service directly binds
16686Tracing QueryHTTP port (APIs and user interface)
18000Admin AppLocal port to which the service directly binds
18080Service DeploymentLocal port to which the service directly binds
18889SentinelLocal port to which the service directly binds
31000 to 34000Service DeploymentPort range used by both Service Deployment and Docker for running containers
47000CacheTCP cache communication
47008Metadata Policy EngineTCP cache communication
47500CacheTCP cache discovery
48000CacheTCP connector
48500CacheClient connector
48508Metadata Policy EngineClient connector

Time source requirements

If you are installing a multi-instance system, each instance should run NTP (network time protocol) and use the same external time source. For information, see support.ntp.org.

Supported browsers

The HCP for cloud scale web applications support these web browsers:

  • Google Chrome latest
  • Mozilla Firefox latest