Declarative Infrastructure with Cloud Foundry BOSH
•Download as PPTX, PDF•
7 likes•4,283 views
Initially built to deploy and manage the Cloud Foundry “Elastic Runtime”, the platform that allows application developers and operators to easily deploy and manage applications and services through the entire app lifecycle (including production!), Cloud Foundry BOSH is a system that manages any virtual machine clusters of arbitrarily complex, distributed systems. You define your release through packages (what gets installed on the VMs), jobs (what is run on the VMs) and a deployment manifest (declaration of the cluster) and BOSH will first deploy and then continue to maintain your cluster to match that desired state. The result is a self-healing, eventually consistent system that markedly reduces the operational burdens and supports a great number of other Devops functions such as canary, zero-downtime upgrades, autoscaling, built in high availability and more. In this session we’ll show you how to create, deploy and manage a BOSH release, and we’ll watch what BOSH does when bad things happen.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (6)
Similar to Declarative Infrastructure with Cloud Foundry BOSH
Similar to Declarative Infrastructure with Cloud Foundry BOSH (20)
More from cornelia davis
More from cornelia davis (20)
Recently uploaded
Recently uploaded (20)
Declarative Infrastructure with Cloud Foundry BOSH
- 2. 2© 2015 Pivotal Software, Inc. All rights reserved. 2© 2015 Pivotal Software, Inc. All rights reserved. Declarative Infrastructure with Cloud Foundry BOSH Gluecon 2015 Cornelia Davis, Director, Platform Engineering, Cloud Foundry @cdavisafc May 20, 2015
- 3. 3© 2015 Pivotal Software, Inc. All rights reserved. 3© 2015 Pivotal Software, Inc. All rights reserved. Demo
- 4. 4© Copyright 2015 Pivotal. All rights reserved. All that is in the Elastic Runtime The ERS is deployed and managed as a cluster of VMs Pivotal CF Elastic Runtime Dynamic Router OAuth 2.0 Server (UAA) Health Manager Application Execution (DEA) Warden Build Packs Login Server Cloud Controller Blob Store Message Bus(NATS) Sys Log ServicesandBrokers Collector Loggregator ROUTING AUTHENTICATION APP LIFECYCLE APP STORAGE & EXECUTION MESSAGING METRICS & LOGGING Pivotal CF OpsManager/BOSH
- 5. 5© Copyright 2015 Pivotal. All rights reserved. BOSH Manages VM Clusters Pivotal CF Elastic Runtime Dynamic Router OAuth 2.0 Server (UAA) Health Manager Application Execution (DEA) Warden Build Packs Login Server Cloud Controller Blob Store Message Bus(NATS) Sys Log MySQL Collector Loggregator ROUTING AUTHENTICATION APP LIFECYCLE APP STORAGE & EXECUTION MESSAGING METRICS & LOGGING Pivotal CF OpsManager/BOSH RabbitMQ Riak Redis Cassandra CloudbeesJenkins
- 6. 6© Copyright 2015 Pivotal. All rights reserved.
- 7. 7© Copyright 2015 Pivotal. All rights reserved. Provision services, not machines Enables continuous delivery Cloud-agnostic view of Platform Ops Holistic Toolchain for “rule them all" Eliminate bespoke automation on top of config management Why BOSH
- 8. 8© Copyright 2015 Pivotal. All rights reserved. The BOSH Architecture Very similar to ERS architecture itself Director as analogy to Cloud Controller Different CPIs exist per IaaS implementation Workers responsible for executing tasks as dictated by Director
- 9. 9© Copyright 2015 Pivotal. All rights reserved. Let’s talk Eventual Consistency…
- 10. 10© Copyright 2013 Pivotal. All rights reserved. In the Elastic Runtime Router Blobstore Cloud Controller etcd Cell Cell Cell Pivotal Cloud Foundry Elastic Runtime Access App DB Service credentialscreds Converger & Auctioneer Desired State credscreds Actual State
- 11. 11© Copyright 2013 Pivotal. All rights reserved. In BOSH IaaSPivotal CF Operations Manager PaaS Ops Health Manager AGENT DEA AGENT Cloud Controller AGENT Message Bus Health Monitor Responses: pager email monitoring ressurector … BOSH Director Desired State Actual State
- 12. 12© Copyright 2013 Pivotal. All rights reserved. VMs are Monitored IaaSPivotal CF Operations Manager PaaS Ops Health Manager AGENT DEA AGENT Cloud Controller AGENT Message Bus Health Monitor Responses: pager email monitoring ressurector … BOSH Director Desired State Actual State
- 13. 13© Copyright 2013 Pivotal. All rights reserved. VMs are Monitored IaaSPivotal CF Operations Manager PaaS Ops Health Manager AGENT DEA AGENT Cloud Controller AGENT Message Bus Health Monitor Responses: pager email monitoring ressurector … BOSH Director Desired State Actual State CPI
- 14. 14© 2015 Pivotal Software, Inc. All rights reserved. Platform Services (stateful): Run in virtual machines Applications (stateless): Run in containers Cloud Foundry manages transformations between existing and desired system states, using immutable infrastructure. Amend (Re)deploy (Re)configure (Re)connect Monitor Current State Desired State
- 15. 15© Copyright 2013 Pivotal. All rights reserved. 15© Copyright 2013 Pivotal. All rights reserved. BOSH Details
- 16. 16© 2015 Pivotal Software, Inc. All rights reserved. Cloud-native Application Platform (3rd Platform) Elastic Runtime Agile Microservices Elastic Hadoop Jenkins Service (CI) Google Redis Pivotal Cloud Foundry Operations Manager (BOSH) KV Store VMware EC2Openstack Mediates to the infrastructure, drawing from pools of resources Rabbit MQ Produces and manages the specified topologies
- 17. 17© 2015 Pivotal Software, Inc. All rights reserved. BOSH to Infrastructure resource_pools: - name: infrastructure network: default size: 6 stemcell: name: bosh-stemcell version: 0.4.6 cloud_properties: cpu: 1 disk: 8192 ram: 4096 Specify: – Pools of VMs – Pools of networks Nodes declared in the topology will draw from the resources networks: - name: default subnets: - reserved: - 172.31.220.2 - 172.31.220.10 static: - 172.31.220.11 - 172.31.220.100 range: 172.31.220.0/22 gateway: 172.31.220.1 ...
- 18. 18© 2015 Pivotal Software, Inc. All rights reserved. Cluster Topology Specify: Jobs (VMs) – Attributes – i.e. how many – Resource pool consumption Properties – i.e. Wordpress needs the ip address of MySQL
- 19. 19© 2015 Pivotal Software, Inc. All rights reserved. BOSH Deployment Manifest jobs: - name: mysql template: mysql instances: 1 resource_pool: common-resource-pool persistent_disk: 10240 networks: - name: wordpress-network static_ips: - 10.244.0.2 - name: wordpress template: wordpress instances: 1 ... properties: mysql: address: 10.244.0.2 password: rootpass wordpress: admin: foo@bar.com servers: - 10.244.0.6 servername: 10.244.0.10 db: name: wp user: wordpress pass: w0rdpr3ss ...
- 20. 20© 2015 Pivotal Software, Inc. All rights reserved. BOSH Release Packages: Bits installed onto VMs – Reference source and blobs – List dependencies – Installation scripts Jobs: Processes started on VMs – Templates: parameters instantiated at deployment time – Start scripts Release = collection of packages and jobs Release
- 21. 21© 2015 Pivotal Software, Inc. All rights reserved. Message Bus Deploying the CF Runtime with Cloud Foundry BOSH IaaS Cloud Foundry Operations Manager/BOSH DB BOSH Director Blobs Health Monitor Deployment • Packages • Blobs • Source • Jobs • Manifest Deploy my CF Worker VMs Messaging Target VMHealth Manager Target VMCloud Controller Target VM Operator
- 22. 22© 2015 Pivotal Software, Inc. All rights reserved. 22© 2015 Pivotal Software, Inc. All rights reserved. Demo
- 23. 23© 2015 Pivotal Software, Inc. All rights reserved. Cluster Topology
- 24. 24© 2015 Pivotal Software, Inc. All rights reserved. 24© 2015 Pivotal Software, Inc. All rights reserved. Demo
- 25. 25© 2015 Pivotal Software, Inc. All rights reserved. Canary Deployments Manifest
- 26. 26© 2015 Pivotal Software, Inc. All rights reserved. How do canary deployments work Manifest
- 27. 27© 2015 Pivotal Software, Inc. All rights reserved. How do canary deployments work Manifest No downtime, atomic rolling update
- 28. 28© 2015 Pivotal Software, Inc. All rights reserved. Different Flavors of BOSH Microbosh – all BOSH components on a single VM Full BOSH – Deployed with Microbosh – Each component is a job, hence separate VM bosh-lite – You can run this on your laptop. Warden (linux container) CPI – http://github.com/cloudfoundry/bosh-lite
- 29. 29© 2015 Pivotal Software, Inc. All rights reserved. Summary Cloud Foundry is – OSS – Both the Elastic Runtime and BOSH – Eventual consistency is core tenet – Governed by the Cloud Foundry Foundation – a Linux Foundation Numerous vendors commercial distributions Declarative, Immutable, Repeatable Infrastructure!
- 30. 30© 2015 Pivotal Software, Inc. All rights reserved. 30© Copyright 2015 Pivotal. All rights reserved. Thank You
Editor's Notes
- Cloud Foundry PaaS
- Of course, the BOSH agent on a VM can only communicate back to the Operations Manager if the VM is there, so let’s talk about what happens when a VM disappears. First thing to understand is that by “disappear” I mean that the BOSH agent is not functional; the VM could be there, but Ops Manager no longer knows what it is up to so for all intents and purposes it’s “gone”. How does Ops Manager know? One of the things that a BOSH agent is responsible for is sending out heartbeat messages and by default it does so every 60 seconds. The OMHM is constantly listening for those heartbeats and when it finds that one is missing it will itself produce and alert and pass that through the list of responders. Just as described above, this could result in emails, pages and operations dashboard alerts, but in this case there is one more responder that kicks in – the “resurector”. The resurector will communicate with the IaaS over which PCF is running and will ask that the failed VM be replaced. Of course it will be replaced with a VM running the appropriate part of the elastic runtime – i.e. a health manager or DEA, etc. That’s right, Operations Manager will restart failed cluster components.
- Of course, the BOSH agent on a VM can only communicate back to the Operations Manager if the VM is there, so let’s talk about what happens when a VM disappears. First thing to understand is that by “disappear” I mean that the BOSH agent is not functional; the VM could be there, but Ops Manager no longer knows what it is up to so for all intents and purposes it’s “gone”. How does Ops Manager know? One of the things that a BOSH agent is responsible for is sending out heartbeat messages and by default it does so every 60 seconds. The OMHM is constantly listening for those heartbeats and when it finds that one is missing it will itself produce and alert and pass that through the list of responders. Just as described above, this could result in emails, pages and operations dashboard alerts, but in this case there is one more responder that kicks in – the “resurector”. The resurector will communicate with the IaaS over which PCF is running and will ask that the failed VM be replaced. Of course it will be replaced with a VM running the appropriate part of the elastic runtime – i.e. a health manager or DEA, etc. That’s right, Operations Manager will restart failed cluster components.
- Of course, the BOSH agent on a VM can only communicate back to the Operations Manager if the VM is there, so let’s talk about what happens when a VM disappears. First thing to understand is that by “disappear” I mean that the BOSH agent is not functional; the VM could be there, but Ops Manager no longer knows what it is up to so for all intents and purposes it’s “gone”. How does Ops Manager know? One of the things that a BOSH agent is responsible for is sending out heartbeat messages and by default it does so every 60 seconds. The OMHM is constantly listening for those heartbeats and when it finds that one is missing it will itself produce and alert and pass that through the list of responders. Just as described above, this could result in emails, pages and operations dashboard alerts, but in this case there is one more responder that kicks in – the “resurector”. The resurector will communicate with the IaaS over which PCF is running and will ask that the failed VM be replaced. Of course it will be replaced with a VM running the appropriate part of the elastic runtime – i.e. a health manager or DEA, etc. That’s right, Operations Manager will restart failed cluster components.