What can I do with the Apcera Platform?

Apcera Platform is an excellent platform for building and running microservices or small-scale apps in production. The platform can scale horizontally with unlimited worker nodes you can also do larger jobs (if you have access to a larger platform) that are not time sensitive and not customer / user facing. It is also a wonderful sandbox and QA environment that comes with many built-in hooks to popular developer frameworks, databases, and external services.

Where can I download the Apcera Platform?

The Apcera Platform is provided at no charge for evaluation purposes. Contact Apcera at https://www.apcera.com/setup for the next steps.

What infrastructure does the Apcera Platform run on?

The Apcera Platform 2.0 release supports setting up and running clusters using the following virtualization providers:

  • Amazon Web Services (AWS)
  • Google Compute Engine
  • Microsoft Azure
  • OpenStack
  • vSphere

How do I get support or report an issue?

For a quick start, join the discussions on the community forum at https://community.apcera.com, where you can get assistance from the the growing user community and Apcera team members.

What common developer tools does Apcera support?

The platform supports most of the popular languages, tools, databases, and applications out of the box. We support services such as S3 and NFS as well as databases such as MySQL, Postgres, MongoDB, Memcached and Redis. Check out Apcera package scriptsand sample apps on Github to get an idea of the sorts of things that people are doing with Apcera.

What is Apcera Policy Engine and how does it work?

The Apcera Policy Engine is a is a system of pervasive policy controls to help you create a trusted compute environment. The Policy Engine allows you to set controls for services (which services can bind to which applications), resource consumption (storage, disk, etc), geolocation of workload, package and software versions (i.e. applications running in production must use JDK 1.8), and compute environment (local, public, private,hybrid). You use policy to govern the behavior of workloads and resources in your cluster. To implement policy, you encode your business rules using the policy language and syntax. Apcera provides you with various tools for working with policy, including a policy editor for authoring policy, and managing policy documents.

Why would I use Apcera’s over Docker?

Apcera is a full-featured distributed application environment with support Docker images in addition many other useful tools and features including our policy engine, semantic pipelines, stagers for common frameworks, and package management.

What job sizes can I run on the Apcera Platform?

You can actually run unlimited job sizes subject to available system resources. Apcera Platform allows you to spin up as many worker compute nodes as you want within the configuration of your cluster.

Do workloads and cluster environments I set up in Apcera persist?

Yes. You can choose to make workload data and environments persistent by using Apcera’s NFS provider.

Why do I get a 'REMOTE HOST IDENTIFICATION HAS CHANGED' error when I try to SSH to my cluster?

When attempting to ssh into Orchestrator or other cluster node the connection fails with the following error:


ssh ubuntu@192.168.2.130
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

This is a standard SSH error that occurs when IPs get reused for different hosts. It is meant to catch potential “man-in-the-middle” attacks. To fix this issue run the following command, replacing with the IP of the node to which you want to connect:


ssh-keygen -R <Cluster-Node-IP>

This deletes the invalid key from the known_hosts file. You should now be able to SSH into your cluster.