Apcera Platform Installation Workflow

Installation workflow

  1. Review and complete the installation prerequisites that are applicable.
  2. Install Apcera on your chosen platform.
  3. Perform the post installation tasks.

The resulting cluster architecture looks similar as follow:

screenshot
The number of instance managers (IMs) is defined by the user during the cluster configuration. The storage nodes and Splunk are optional components, and not required. For more details, refer to Apcera Architecture and Components.

Refer to Required Ports for Deployment for the lists of ports used by the Apcera platform.

Redeploy is required if you change hardware (disk, attached storage, RAM, etc.) on any cluster machine host, physical or virtual.

Installation prerequisites

Before you install Apcera Platform, review and complete the following prerequisites that are applicable.

Prerequisite Description
Generate SSL certificate chain and key If you want to provide your own certificate instead of using the Apcera generated self-signed certificate, complete this task.
Configuring SSH If you want to provide your own SSH public key to connect to the cluster hosts, complete this task. .
Using Google Auth as the Identity Provider If Google OAuth 2.0 is your chosen identity provider, you will need to create a Google Auth project and generate the keys for client_id, client_secret, web_client_id for cluster access via APC and the web console.
Using Active Directory as the Identity Provider If Active Directory is your chosen identity provider, be sure to gather necessary information about the Active Directory server.
Using LDAP as the Identity Provider If LDAP is your chosen identity provider, be sure to gather necessary information about the LDAP server.
Using Keycloak as the Identity Provider If Keycloak is your chosen identity provider, be sure to gather necessary information about the Keycloak server.
Splunk license Apcera integrates with Splunk to index and search system logs. It is recommended to leverage Splunk to help manage your production cluster; however, it is optional.

Platform support matrix

A minimum installation on any supported provider requires 14 virtual machines (VMs), and each VM requires its own public IP address. Ensure that your account has enough quota to provision cloud infrastructure to fulfill these requirements.

Provider Prerequisites Multi-Cloud Deployment Documentation Notes
AWS AWS Installation Prerequisites Installer Installing Apcera on AWS Installer supports creating additional IM pool on GCE
Azure Azure Installation Prerequisites Manual Installing Apcera on Azure  
GCE GCE Installation Prerequisites Installer Installing Apcera on GCE  
OpenStack OpenStack Installation Prerequisites Manual Installing Apcera on OpenStack  
vSphere vSphere Installation Prerequisites Manual Installing Apcera on vSphere vCloud support is deprecated in 2.4.