experience report: cloud foundry open source operations
TRANSCRIPT
Experience ReportCloud Foundry Open Source
Operations
Introduction
Lucas Pinto Steffen Zuber
@medk_ @[email protected] [email protected]
DevOpsanynines Service Framework Team
Who we are
Agenda
1. Requirements2. CF System Analysis3. Solutions4. Question Round
1. Requirements
Requirements
• High-Availability • Resilience• Self-Healing• Monitoring
Requirements
• High-Availability • Resilience• Self-Healing• Monitoring
Requirements
• High-Availability • Resilience• Self-Healing• Monitoring
Requirements
• High-Availability • Resilience• Self-Healing• Monitoring
2. CF System Analysis
CF System Analysis
UAA-DB
UAA HM DEA
Router
HAProxy
Nats
CC
CC-DBCC-Blobstore (Debian NFS)
CF SPOFs
UAA-DB
UAA HM DEA
Router
HAProxy
Nats
CC
CC-DBCC-Blobstore (Debian NFS)
CC-DB & UAA-DB
UAA-DB
UAA HM DEA
Router
HAProxy
Nats
CC
CC-DBCC-Blobstore (Debian NFS)
CC-Blobstore
UAA-DB
UAA HM DEA
Router
HAProxy
Nats
CC
CC-DBCC-Blobstore (Debian NFS)
HAProxy
UAA-DB
UAA HM DEA
Router
HAProxy
Nats
CC
CC-DBCC-Blobstore (Debian NFS)
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
3. Solutions
CC-DB & UAA-DB
CC-DB UAA-DB
UAA HM DEA
Router
HAProxy
Nats
CCCC-Blobstore (Debian NFS)
PostgreSQL Cluster (CC-DB + UAA-DB)
CC-Blobstore
CC-Blobstore (Debian NFS)
UAA HM DEA
Router
HAProxy
Nats
CCPostgreSQL Cluster (CC-DB + UAA-DB)
CC-Blobstore (S3 / Swift)
HAProxyHAProxy
UAA HM DEA
Router
Nats
CCPostgreSQL Cluster (CC-DB + UAA-DB)
CC-Blobstore (S3 / Swift)
SSL-Gateways
Static IPsConsul Cluster
UAA HM DEA
Router
Nats
CCPostgreSQL Cluster (CC-DB + UAA-DB)
CC-Blobstore (S3 / Swift)
SSL-Gateways
4. Question Round