GCE Installation Requirements for Apcera
This document describes the requirements for installing the Apcera Platform on GCE using Terraform.
- Set up Terraform
- Apcera Cluster Images
- GCE Project
- GCE Resources
- Static IP
Set up Terraform
Install the supported version of Terraform.
Download the Terraform files for GCE.
Setup your Terraform working directory.
The file unzips to a directory named
Copy this directory to a known location, such as
Review the Terraform files.
gcefolder you should have the following:
gce-modulesubdirectory contains the module for GCE. These files define the GCE machines and networking. For default deployments you do not need to modify these files. See GCE requirements for details on these files.
You will edit the
cluster.conf.erbfiles to deploy the Apcera Platform to GCE.
Apcera Cluster Images
You will need the Apcera-provided VM image for GCE for the Orchestrator host and the Base image for all other cluster hosts.
To obtain these VMs, provide Apcera Support with the following information:
- GCE project name, for example:
- GCE credentials JSON file, for example:
Once you provide this information, Apcera will upload a GCE base Apcera image for creating the cluster hosts to your GCE project.
Once you have the images, go to Compute Engine > Images and select the image. Note that the image name starts with
continuum-base- which you will enter in the
terraform.tfvars file later in the GCE configuration process.
To install Apcera Platform hosted on Google Compute Engine (GCE), a Google Cloud Platform project is required.
If you already have a Google Cloud Platform project, download the JSON file for your account. The JSON file contains the project key you will need to install Apcera.
If you do not have a Google Cloud Platform project, see creating a GCE project.
During the installation the following GCE resources will be created:
Is not tied to any geographical region. Can contain 0 or more "subnets."
Has a CIDR range (like "10.2.3.0/24"). Is tied to a region "region" (like "us-west1", "us-central1", etc). Hosts in a "subnet" can be spread amoung the "zones" for the "subnet"'s "region"
Is a specific geographical location. Named this like "us-west1", "us-central1", etc.
An isolated location within a "region"
- named things like ("us-west1-a", "us-west1-b")
- See: https://cloud.google.com/compute/docs/regions-zones/regions-zones
You need a static IP on on the GCE side which will be used by AWS to connect to the IMs on GCE. The static IP is added to the main.tf file.