OpenAperture

OpenAperture is a free, open-source hybrid cloud management platform that delivers software quickly and consistently regardless of location or workload. This future-ready platform from Lexmark Enterprise Software provides a comprehensive management system to handle the six pillars of cloud management – provisioning, deployment, monitoring, maintenance, security and metering.

Creating an CoreOS Cluster

OpenAperture designed to run on top of a set of CoreOS clusters via the Fleet daemon (HTTP and fleetctl tools). If you're spinning up clusters in Amazon, There are up-to-date AMIs available in each region (make sure to review the cloud-init settings before hand). OpenAperture can run in other Cloud providers or in private data centers, as long as the CoreOS clusters are available.

OpenAperture components are recommended to on a 3-node cluster at a minimum. Depending on your usage, you may want to tweak the sizes and configurations of the node. For example, all of the OpenAperture System Components are written in Elixir and have a much higher startup cost than, say, Ruby on Rails apps.

It's important to realize that the CoreOS clusters, based on the release channel selected, will automatically upgrade themselves to the latest version of CoreOS. The OpenAperture components must be keep up-to-date with CoreOS to ensure compatibility.

Networking Between Clusters

The following considerations should be made when configuring CoreOS clusters for use with OpenAperture:

• Clusters running a Management Assembly will need to:
  • expose a port for HTTP traffic (HTTPS will need to be terminated at a Load Balancer)
  • expose port 5432 to a Postgres instance
  • expose ports for incoming and outgoing AMQP messages (this port is configurable in the MessagingBrokerConnectionOptions); by default these ports are 5672 and 15672
• Clusters running a Build Assembly will need to:
  • expose port 2375 between the Builder Assembly cluster and the docker build cluster
• Clusters running a Deployment Assembly will need to:
  • expose ports 4001 and 7002 between the Deployment Assembly cluster and any application clusters
  • expose port 22 between the Deployment Assembly cluster and any application clusters