Cloud Foundry Summit 2015: Managing Multiple Cloud with a Single BOSH Deployment
4 likes•4,260 views
The document outlines the roles of Alexander Lomov and Alan Moran as Cloud Foundry engineers and architects, respectively, discussing multi-cloud deployment strategies and challenges. It highlights the need for redundancy, load distribution via geodns, and the significance of consistent data storage across clouds. Additionally, it provides technical solutions for binding deployments, accessing blobstores, and setting up messaging infrastructure in multi-cloud environments.
Cloud Foundry Summit 2015: Managing Multiple Cloud with a Single BOSH Deployment
- 1. Alexander Lomov Cloud Foundry Engineer github: @allomov twitter: @code1n Alan Moran Cloud Foundry Architect github: @bonzofenix twitter: @bonzofenix
- 3. * Buenos Aires Oslo London Zurich Sunnyvale, CA Copenhagen Minsk Santa Fe Boston 30%Female 70%Male +5Join us on an average month FACTS ON ALTOROS Altoros offices Altoros’s delivery partner in APAC Singapore SingaporTokyo 256+Full Time Enablers DevOps Software Engineers
- 4. How this story begun...
- 5. How this story begun...
- 7. Be close to your clients
- 8. Redundancy brings fault tolerance
- 9. What about Cloud Foundry on Multi Cloud?
- 10. There are various limitation...
- 11. UAA and CC needs consistent datastore
- 12. NATS is not designed for multi-cluster work NATS cluster at work
- 13. Timeouts
- 14. ● Replicate the same Cloud Foundry installation. The solution ● Distribute load though GeoDNS. ● Deploy apps on All CF Clusters.
- 15. One bosh to rule them all
- 16. HOW?
- 17. Bosh supporting single cloud
- 18. BOSH supporting multiple clouds
- 19. BOSH Cloud Specific Inputs
- 20. Cloud Configs
- 21. Cloud Config Example networks: - name: my-net type: vip resource_pools: - name: my-vms network: my-net compilation: workers: 5 network: my-net iaas.yml
- 22. Cloud Configs # saves cloud config to the Director $ bosh update cloud-config ./iaas.yml # outputs saved config to stdout $ bosh cloud-config
- 23. Multiple Cloud Deployment Inputs
- 24. Stemcell Upload
- 25. Stemcell Upload
- 26. Stemcell Upload
- 27. bosh upload stemcell --cloud dc-0 openstack-stemcell.tgz bosh upload stemcell --cloud dc-1 vsphere-stemcell.tgz Stemcell Upload bosh update cloud-config openstack.yml bosh upload stemcell openstack-stemcell.tgz bosh update cloud-config vsphere.yml bosh upload stemcell vsphere-stemcell.tgz or
- 28. Ready to deploy
- 29. ● Binding Deployment ● Creating a Plan ● Package Compilation ● Creating Jobs/VMs
- 30. Binding Process
- 31. Build-in multiple cloud deployment to a binding process Problem
- 33. ● Binding Deployment ● Creating a Plan ● Package Compilation ● Creating Jobs/VMs
- 36. Provide an access to a blobstore to all bosh-agents Problem
- 37. Use separate blobstore for each cloud and sync them Solution Use separate blobstore and compile packages on each cloud
- 38. Use external blobstore which is accessible to all clouds Solution Use DAV blobstore and share it using VPN
- 39. ● Binding Deployment ● Creating a Plan ● Package Compilation ● Creating Jobs/VMs
- 40. Creating Jobs
- 41. Creating Jobs
- 42. Creating Jobs
- 43. Creating Jobs
- 44. Creating Jobs
- 45. Provide an access to a NATS cluster to all bosh-agents Problem
- 46. Make some NATS servers public or share them using VPN Solution Use “https messaging bus” mode
- 47. Solution
- 48. One bosh to rule them all
- 49. Alexander Lomov Cloud Foundry Engineer github: @allomov twitter: @code1n Alan Moran Cloud Foundry Architect github: @bonzofenix twitter: @bonzofenix
- 51. Alexander Lomov Cloud Foundry Engineer github: @allomov twitter: @code1n Alan Moran Cloud Foundry Architect github: @bonzofenix twitter: @bonzofenix