Apcera Platform

Community Edition


Apcera Community Edition is the first cloud platform that lets developers and ITOps build a working compute cluster in as little as 15 minutes on numerous public and private cloud providers.

Thank You For Downloading CE!

Visit our developer portal for resources, tutorials, and join our community for more insights on what you can accomplish.

Share Apcera Community Edition:

  • youtube
  • facebook
  • twitter
  • facebook
Watch Video

Getting Started with
Apcera Community Edition

Requirements for Setup

This section provides requirements for installing the Apcera Platform Community Edition (CE) using the apcera-setup tool. To run the apcera-setup tool and deploy the Apcera Platform, we require the following:

  • Linux (x86_64), Mac OS 10.7 to 10.12, or Windows 64-bit, 16 GB System RAM recommended.
  • 12 GB free disk space
  • Internet connection
  • IPv4 addressing (IPv6 is not supported at this time)
Supported infrastructure providers

You install the Apcera Platform Community Edition on top of an infrastructure provider. Apcera supports the following infrastructure providers for installing the community edition:

  • Oracle VirtualBox (default provider)
  • VMware Fusion or Workstation
  • Amazon Web Services (AWS)
  • Microsoft Azure
  • Google Compute Engine (GCE)
  • OpenStack
  • VMware vSphere

View More +

Local installation requirements

To install the Apcera Platform locally on VirtualBox, VMware Fusion or Workstation, we require the following resources:

  • Oracle VirtualBox 5, VMware Fusion 8, or VMware Workstation 12 installed on Mac OS X or Windows 64-bit, or vSphere 5.5 or 6
  • Approximately 8 GB of RAM to deploy the platform with 1 IM (total of 3 VMs)
  • Approximately 6 GB of RAM for the minimum runtime environment with 1 IM (total of 2 VMs)
  • Approximately 3 GB of RAM for each additional Instance Manager (1 VM per IM)

View More +

AWS installation requirements

To install the Apcera Platform hosted on Amazon Web Services (AWS), we require the following resources:

  • An AWS account with configured VPC, Subnet, and Security Group rules for hosting the Apcera Platform
  • One t2.small instance for the Orchestrator VM (not required at runtime)
  • One t2.medium instance for all Management Plane components
  • One m4.large instance for each Instance Manager (1 IM per runtime host)

See also Apcera Platform Deployment Requirements for AWS.

View More +

OpenStack installation requirements

To install the Apcera Platform on OpenStack, all the apcera-setup instances use “m1.medium” instance type (flavor).

In addition, you must provide the following information during apcera-setup:

  • Identity Endpoint
  • Username and Password
  • Tenant Name
  • Region
  • Network ID (internal network)
  • Floating IP pool (external network)
  • Security Group Name

View More +

vSphere installation requirement

To install the Apcera Platform on vSphere, we require the following resources:

  • vSphere 5.5 or 6
  • Approximately 8 GB of RAM to deploy the platform with 1 IM (total of 3 VMs)
  • Approximately 6 GB of RAM for the minimum runtime environment with 1 IM (total of 2 VMs)
  • Approximately 3 GB of RAM for each additional Instance Manager (1 VM per IM)

View More +

Microsoft Azure installation requirements

To use the Azure provider, you will need to provide your Azure subscription ID and credentials, including your Azure tenant ID, client ID and client secret.

View More +

Google Compute Engine installation requirements

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. The JSON file contains the project key you will need to install Apcera.

If you do not have a Google Cloud Platform project, see the documentation for creating a project.

GCE resource requirements:

  • The Apcera Platform provisions virtual machines hosted on a minimum of three GCE instances.

View More +

Data we collect

When you deploy the Apcera Platform using the apcera-setup tool and opt-in to data collection, the following non-identifying telemetry data is sent to Apcera to help us improve the user experience:

  • Deployment date
  • Provisioner type (aws, virtualbox, vmware)
  • Number of IMs (1 or more)
  • Deployment status (success, error, other)

View More +

What's New in Version 2.2.3

New features in this release include:

  • Installs
    • Apcera Platform Community Edition version 2.4.2
    • APC version 2.4.2 command line tool
    • Apcera Web Console version 6.0.12
  • Added support for AWS us-east-2 region
  • Support for running apcera-setup on macOS Sierra
  • Configure Zabbix for cluster monitoring

New features & capabilities in Apcera Platform version 2.4.2

  • Addresses CVE-2016-8655 vulnerability
  • KeyCloak authentication
  • RabbitMQ, gnatsd, and Minio services can now be created from the console
  • Orchestrator reboot command to facilitate cluster rolling restart
  • Amazon ECR registry support
  • Upgraded all machine images to kernel 3.13.0-83.127.apcera6
  • Virtual Network supported on Google Cloud Engine and Azure
  • Audit logging enhancements
  • Improved metrics
  • Enhanced Docker image support in the multi-resource manifest
  • New NFS providers will default to NFSv4

Developer

Visit developer.apcera.com for more Community Edition resources including tutorials, FAQs and the peer support forum. Installation is as simple as the following steps:

  • 1 Create SSH Key
  • 2 Prepare installation environment
  • 3 Accept Terms and Conditions
  • 4 Domain name configuration
  • 5 Configure HTTPS
  • 6 Choose an infrastructure provider
  • 7 Enter DNS servers
  • 8 Create the platform!

You can also watch the installation video, and check out Apcera’s comprehensive Features list