Cloud Foundry and OpenStack are the biggest Open Source projects in their domain. As IaaS and PaaS walk hand in hand the idea of combining both worlds is close. anynines is running their public Cloud Foundry offering on top of OpenStack for more than three years with two years running on a self-hosted OpenStack setup. As head of public Paas operations Julian Weber has gained a lot of knowledge to share about setting up and operating Cloud Foundry installations. This presentation leads the audience through the journey of adopting the Cloud Foundry Open Source version and breeding it to a highly available and production ready Cloud Foundry setup. The listener is guided through the analysis of potential single points of failure in standard CF Open Source setups up to required changes in the Cloud Foundry OS release to reach our goal. As this talk is about Cloud Foundry operations we also need to talk about experiences with BOSH as a general purpose tool for software lifecycle management of big distributed systems and possible improvements to the BOSH tool set and workflows. The talk will enable advanced DevOps to dive deeper into the technical details of setting up production ready Cloud Foundry installations based on Cloud Foundry Open Source.

1. Experience Report
Cloud Foundry Open Source Operations

2. Introduction

3. Lucas Pinto Steffen Zuber
@medk_ @SteffenZuber
lpinto@anynines.com szuber@anynines.com
DevOps
anynines Service Framework Team
Who we are

4. Agenda
1. Requirements
2. CF System Analysis
3. Solutions
4. Question Round

5. 1. Requirements

6. Requirements
• High-Availability
• Resilience
• Self-Healing
• Monitoring

7. Requirements
• High-Availability
• Resilience
• Self-Healing
• Monitoring

8. Requirements
• High-Availability
• Resilience
• Self-Healing
• Monitoring

9. Requirements
• High-Availability
• Resilience
• Self-Healing
• Monitoring

10. 2. CF System Analysis

11. CF System Analysis
UAA-DB
UAA HM DEA
Router
HAProxy
Nats
CC
CC-DB
CC-Blobstore
(Debian NFS)

12. CF SPOFs
UAA-DB
UAA HM DEA
Router
HAProxy
Nats
CC
CC-DB
CC-Blobstore
(Debian NFS)

13. CC-DB & UAA-DB
UAA-DB
UAA HM DEA
Router
HAProxy
Nats
CC
CC-DB
CC-Blobstore
(Debian NFS)

14. CC-Blobstore
UAA-DB
UAA HM DEA
Router
HAProxy
Nats
CC
CC-DB
CC-Blobstore
(Debian NFS)

15. HAProxy
UAA-DB
UAA HM DEA
Router
HAProxy
Nats
CC
CC-DB
CC-Blobstore
(Debian NFS)

16. Static IPs
• cf-release templates are based on static IPs
(Nats, Consul, etcd, router)
• —> BOSH VM healing problems on
OpenStack
• —> Destroys value proposition of BOSH
• Not really the Cloud way
• Goal: Service Discovery via DNS

17. 3. Solutions

18. CC-DB & UAA-DB
CC-DB UAA-DB
UAA HM DEA
Router
HAProxy
Nats
CC
CC-Blobstore
(Debian NFS)
PostgreSQL Cluster
(CC-DB + UAA-DB)

19. CC-Blobstore
CC-Blobstore
(Debian NFS)
UAA HM DEA
Router
HAProxy
Nats
CC
PostgreSQL Cluster
(CC-DB + UAA-DB)
CC-Blobstore
(S3 / Swift)

20. HAProxy
HAProxy
UAA HM DEA
Router
Nats
CC
PostgreSQL Cluster
(CC-DB + UAA-DB)
CC-Blobstore
(S3 / Swift)
SSL-
Gateways

21. Static IPs
Consul
Cluster
UAA HM DEA
Router
Nats
CC
PostgreSQL Cluster
(CC-DB + UAA-DB)
CC-Blobstore
(S3 / Swift)
SSL-
Gateways

22. 4. Question Round