Migrating a running Cloud Foundry

from VMWare to OpenStack

•What is Cloud Foundry?

•IaaS and PaaS

•VMware vs. OpenStack

•The migration

•Conclusion

Cloud Foundry

•= application platform = PaaS software

•Open source software (apache 2)

Service(e.g. MySQL)

Services(e.g. MySQL)

Services(e.g. MySQL)

Services(e.g. MySQL)

RouterRouter

DEA

RouterHealth Manager

RouterCloud Controller

Cloud ControllerDatabase

Get desired states

Request droplet start/stop

DEADEADEADEA

Droplet / Service metadata

API request Droplet request

Droplet changenotifications

Droplet heartbeat & exit messages

Consume a service

IaaS and PaaS

•Building against infrastructure requires ops knowledge

•Building against a PaaS doesn’t

It’s all about the Apps!

VMware vs. OpenStack

•VMware is a fine piece of technology

•If you have invested into it, no immediate need to move away from it.

•OpenStack is an upcoming candidate and might become the industry standard for infrastructure

•Open source and enterprise versions available (Piston, Canonical, HP, …)

Our requirements

•We already had OpenStack knowledge

•For a public PaaS buying costs is everything —> Saving license costs was key!

•Moving from a hosted VMWare to a self-hosted Openstack…

… doubled monthly costs

quadrupled RAM and CPU cores!

The Migration

> 1 week to prepare

< 1 hour to execute

< 30 min downtime

•Setup the OpenStack environment

•Deploy Cloud Foundry on OpenStack

•Migrate configuration, data and apps

•Switch DNS entries

•Official migration announcement in the anynines bloghttp://rh.gd/a9vmw2sos

•A blog post about technical details will follow on blog.cloudfoundry.com

Conclusion

Building against a PaaS protects investments made into software

development.

An infrastructure must be present.

!

Which one doesn’t matter.

Thank you!