Skip to end of metadata
Go to start of metadata
AWS ONLY

Platforms-as-a-Service, a.k.a PaaS, have been all the rage in 2011. Our friends at VMware developed Cloud Foundry which has also grown in popularity very quickly. Now with Scalr you can easily run and operate your own Cloud Foundry cluster. 


Differences Between The Roles

Scalr ships several roles for running a CloudFoundry stack:

  • cf-all-in-one - Ubuntu 10.04 x64 with all CloudFoundry components and services and Nginx frontend. This role is ideal to start with CloudFoundry to test runs, trials, and evaluations. What’s more, it’s cheap way to run on a public cloud since it runs on a single server. This role does not scale.
  • cf-dea - Ubuntu 10.04 x64 configured to be a DEA. Your application will run on this role. Recommended instance type: m1.large. This role does scale.
  • cf-router - Ubuntu 10.04 x64 configured to be Router. It's a tiny component which simply proxies requests to DEA or to Cloud Controller. Recommended instance type: t1.micro. This role does scale.
  • cf-cchm - Ubuntu 10.04 x64 configured to run Cloud controller and Health manager. It also use EBS volumes for CloudFoundry's own database. Recommended instance type: m1.large. This role does not scale.

How To Add This Role

CloudFoundry Images are available under the Farm Designer (Main Menu > Farms > Add Button (plus))

Roles Combinations

We suggest 3 different role combinations depending on different stages of your project:

Development

  • cf-all-in-one (1 instance)

Staging

  • cf-all-in-one (1 instance)
  • cf-dea (1..n instances)
  • cf-router(1..n instances)

Production

  • nginx (1..n instances)
  • cf-router (1..n instances)
  • cf-cchm (1 instance)
  • cf-dea (1..n instances)

Why Should I Use Scalr To Setup Cloud Foundry?

There are many reasons for you to use Cloud Foundry with Scalr:

  1. Everything is auto-installed and configured. Get a full stack deployed in a few clicks.
  2. Auto scaling for DEA and Routers. You can configure scaling based on LA or RAM usage or any other metrics include custom ones.
  3. CloudFoundry database stored on EBS volumes for persistence.

Future Development

We are working on deep integration (bindings) into Scalr-managed MySQL, PostgreSQL, Redis, Mongo. Cloud Foundry has not been integrated into Chef yet but the Cloud Foundry team is working hard to prepare cookbooks for it. 
 

How Can I Access My Cloud Foundry Role?

To access to your role, you can install the command line interface named vmc on your laptop.

http://docs.cloudfoundry.com/tools/vmc/installing-vmc.html

To create a new account:

  • You can ssh into you Cloud Foundry Role and use the command: vmc add-user
  • You will have to enter an email/password.
  • Then on your laptop you have to add to your hosts file: <IP of your instance> api.vcap.me
  • Execute the following command on your laptop to define your target: vmc target api.vcap.me
  • Then you can login into your Cloud Foundry role with: vmc login
  • If you want to deploy use simply: vmc push
Labels
  • None