Table of contents
No headersScalr ships several roles for running CloudFoundry stack
- cf-all-in-one - Ubuntu 10.04 x64 with all CloudFoundry components and services and Nginx frontend. This role is good to start with CloudFoundry.
- cf-dea - Ubuntu 10.04 x64 configured to be a
DEA. Your application will run on this role. Recommended instance type: m1.large. - 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. - 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.
We suggest 3 different role combinations for 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 CloudFoundry on Scalr? Why not consider a do-it-yourself setup?
- Everything auto-installed and configured. Get a full stack deployed in a few clicks.
- Auto scaling for DEA and Routers. You can configure scaling based on LA or RAM usage or any other metrics include custom ones.
- CloudFoundry database stored on EBS volumes for persistence.
- We're working on deep integration (bindings) into Scalr-managed MySQL, PostgreSQL, Redis, Mongo, and any other service in the works.
