1. Migrating a running
Cloud Foundry
from VMWare to OpenStack

2. • What is Cloud Foundry?
• IaaS and PaaS
• VMware vs. OpenStack
• The migration
• Conclusion

3. Cloud Foundry

4. • = application platform = PaaS software
• Open source software (apache 2)

5. API request
Router
Router
Droplet request
DEA
DEA
DEA
DEA
DEA
Router
Cloud Controller
Droplet change
notifications
Request droplet
start/stop
Droplet heartbeat &
exit messages
Router
Health Manager
Get desired states
Droplet / Service metadata
Cloud
Controller
Database
Consume a service
Service
Services
Services
(e.g. MySQL)
Services
(e.g. MySQL)
(e.g. MySQL)
(e.g. MySQL)

6. IaaS and PaaS

7. • Building against infrastructure requires
ops knowledge
• Building against a PaaS doesn’t

8. It’s all about the Apps!

9. VMware vs.
OpenStack

10. • 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, …)

11. Our requirements

12. • 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 selfhosted Openstack…

13. … doubled monthly costs
quadrupled RAM and CPU cores!

14. The Migration

15. > 1 week to prepare

16. < 1 hour to execute

17. < 30 min downtime

18. • Setup the OpenStack environment
• Deploy Cloud Foundry on OpenStack
• Migrate configuration, data and apps
• Switch DNS entries

19. • Official migration announcement in the
anynines blog
http://rh.gd/a9vmw2sos
• A blog post about technical details will
follow on blog.cloudfoundry.com

20. Conclusion

21. Building against a PaaS
protects investments
made into software
development.

22. An infrastructure must
be present.
!
Which one doesn’t
matter.

23. Thank you!