Download as PDF, PPTX
Uploaded byVMware Tanzu
Cloud Foundry Summit 2015: Managing Multiple Cloud with a Single BOSH Deployment
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.
More Related Content
Similar to Cloud Foundry Summit 2015: Managing Multiple Cloud with a Single BOSH Deployment
Cloud Foundry Summit 2015: Managing Multiple Cloud with a Single BOSH Deployment
- 1. Alexander Lomov Cloud FoundryEngineer github: @allomov twitter: @code1n Alan Moran Cloud Foundry Architect github: @bonzofenix twitter: @bonzofenix
- 2.
- 3. * Buenos Aires Oslo London Zurich Sunnyvale, CA Copenhagen Minsk SantaFe 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 storybegun...
- 5. How this storybegun...
- 6.
- 7. Be close toyour clients
- 8. Redundancy brings faulttolerance
- 9. What about Cloud Foundry onMulti Cloud?
- 10. There are variouslimitation...
- 11. UAA and CCneeds consistent datastore
- 12. NATS is notdesigned for multi-cluster work NATS cluster at work
- 13.
- 14. ● Replicate thesame Cloud Foundry installation. The solution ● Distribute load though GeoDNS. ● Deploy apps on All CF Clusters.
- 15. One bosh torule them all
- 16.
- 17.
- 18. BOSH supporting multipleclouds
- 19. BOSH Cloud SpecificInputs
- 20.
- 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 # savescloud config to the Director $ bosh update cloud-config ./iaas.yml # outputs saved config to stdout $ bosh cloud-config
- 23.
- 24.
- 25.
- 26.
- 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.
- 29. ● Binding Deployment ●Creating a Plan ● Package Compilation ● Creating Jobs/VMs
- 30.
- 31. Build-in multiple cloud deploymentto a binding process Problem
- 32.
- 33. ● Binding Deployment ●Creating a Plan ● Package Compilation ● Creating Jobs/VMs
- 34.
- 35.
- 36. Provide an accessto a blobstore to all bosh-agents Problem
- 37. Use separate blobstorefor each cloud and sync them Solution Use separate blobstore and compile packages on each cloud
- 38. Use external blobstorewhich 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.
- 41.
- 42.
- 43.
- 44.
- 45. Provide an accessto a NATS cluster to all bosh-agents Problem
- 46. Make some NATSservers public or share them using VPN Solution Use “https messaging bus” mode
- 47.
- 48. One bosh torule them all
- 49. Alexander Lomov Cloud FoundryEngineer github: @allomov twitter: @code1n Alan Moran Cloud Foundry Architect github: @bonzofenix twitter: @bonzofenix
- 51. Alexander Lomov Cloud FoundryEngineer github: @allomov twitter: @code1n Alan Moran Cloud Foundry Architect github: @bonzofenix twitter: @bonzofenix