Recommended
Recommended
More Related Content
Viewers also liked
Viewers also liked (20)
Similar to MultiCloud Bursting from Openstack to Windows Azure and Amazon AWS with Rightscale - 5th OpenStack Birthday at Bitnami - SEVILLE
Similar to MultiCloud Bursting from Openstack to Windows Azure and Amazon AWS with Rightscale - 5th OpenStack Birthday at Bitnami - SEVILLE (20)
Recently uploaded
Recently uploaded (20)
MultiCloud Bursting from Openstack to Windows Azure and Amazon AWS with Rightscale - 5th OpenStack Birthday at Bitnami - SEVILLE
- 1. Hybrid Cloud, Cloud Bursting, Multicloud based on OPENSTACK, Rightscale, Amazon AWS and Windows Azure Happy Birthday Openstack! SEVILLE
- 2. nicolas.bertet@bn-cloud.com CEO of BN-CLOUD Http://www.bn-cloud.com BN-CLOUD, an international network of experts in Cloud Computing and Cloud Bursting based on Seville.
- 3. SENSORS: clothes, devices, environment: Temperature Humidity Luminosity Acoustic Pollution Location Body Temperature, cardiac signal, skin conductance + MOBILE, SOCIAL MEDIA => posts, tweets ... Data continuous emission in real time
- 4. 4.4 ZetaB => 44 ZetaB COLLECT
- 7. DECISIONS
- 8. BIG DATA Risks: Natural, Commercial, Industrial Phenomenon: Politics, Religious, Social Environment, Energy Banking and trading Transactions Big scientific installations
- 9. And …- Augmented and virtual Reality Blogs Apps Social Media eCommerce SaaS Product Social Gaming Video Streaming
- 12. Cloud Strategy: Select the Best Cloud for Each Application Application Portfolio App 1 App 2 App 3 … App N Requirements Filter Performance Cost Security Compliance Geo-Location Providers Existing Data Center Application Portfolio App 1 App 2 App 3 … App N Ressource Pools Public Cloud 1 Public Cloud 2 Hosted Private Internal Private
- 13. Orgs Know They Need Multi-Cloud RIGHTSCALE SURVEY - 2015 13
- 14. 1.Operate anywhere 2.Leverage existing investments 3.Optimize costs 4.Access unique capabilities 5.Create resilient architectures 6.Maintain vendor leverage 7.Prepare their strategy to anticipate the future IT trends What are the Reasons To Go Multi- Cloud?
- 16. What are the MULTI-CLOUD PAIN POINTS? APIs differ: sets of resources, formats and encoding, several versions for a single cloud ABSTRACTIONS differ: VLANs, security groups, NAT, ACLs … local/attachable disks, backup, snapshots HYPERVISORS and MACHINE IMAGES differ FEATURES differ COST MODELS, BILLING, REPORTING differ SEMANTICS differ
- 17. HOW TO THINK MULTI-CLOUD and OVERCOME these PAIN POINTS? GENERIC CONCEPTS : “durable storage” instead of “EBS volumes” TOOLS turning the GENERIC CONCEPTS into CLOUD- SPECIFIC : Scripts, Recipes GEOGRAPHIC DISPERSITY : improve the availability and reliability but increase as well the latency and costs associated Think about how to share the DATA : live replication, periodic backups, global storage… Think HA and Portability
- 20. ARCHITECTURE EVOLUTION ACCORDING TO THE WORKLOAD ON A BLOG - BEST PRACTICES
- 21. Hybrid Cloud Private Cloud Public Cloud
- 22. APPLICATION LAYER DATABASE LAYER CINDER DNS 1. SIMPLE DEPLOYMENT of a WEB APPLICATION
- 25. APPLICATION LAYER DATABASE LAYER CINDER LB SWIFT 3. HIGH AVAILABILITY SINGLE POINT OF FAILURE DNS
- 26. APPLICATION LAYER DATABASE LAYER CINDER LB SWIFT ROUND ROBIN DNS SINGLE POINT OF FAILURE 3. HIGH AVAILABILITY
- 27. APPLICATION LAYER DATABASE LAYER CINDER LB SWIFT EBS S3 ROUND ROBIN DNS 4. GEO-REPLICATED = MORE AVAILABLE + MORE RELIABLE HIGH AVAILABILITY REPLICATION VPN MASTER SLAVE
- 29. APPLICATION LAYER DATABASE LAYER CINDER LB SWIFT EBS S3 DRIVE BLOB ... ... ROUND ROBIN DNS VPN 6. MULTICLOUD STRATEGY REPLICATION
- 30. APPLICATION LAYER DATABASE LAYER CINDER LB SWIFT EBS S3 DRIVE BLOB ... ... WEB CACHING ROUND ROBIN DNS DB CACHING VPN VPN 7. LATENCY OPTIMIZATION CDN CLOUDFRONT AZURE CDN
- 31. BUT, TAKE INTO ACCOUNT THE COSTS
- 32. APPLICATION LAYER DATABASE LAYER CINDER LB SWIFT EBS S3 ... ROUND ROBIN DNS VPN 9. MULTICLOUD HA Costs: €€€€ NO DOWNTIME
- 33. APPLICATION LAYER DATABASE LAYER CINDER LB SWIFT EBS S3 ... ROUND ROBIN DNS VPN 10. HOT DR Costs = €€€ Rapid Recovery > 5 minutes But similar to WARM DR
- 34. APPLICATION LAYER DATABASE LAYER CINDER LB SWIFT EBS S3 ... ROUND ROBIN DNS VPN 10. WARM DR Minimal Additional costs: €€ Fairly rapid recovery > 1 hour RECOMMENDED DR
- 35. APPLICATION LAYER DATABASE LAYER CINDER LB SWIFT EBS S3 ... ROUND ROBIN DNS VPN 10. COLD DR Low Costs: € Slow recovery > few hours Slow to recuperate data, Slow to bring the database to a operational state.
- 36. Proof Of Concept: HYBRID CLOUD, MULTI- CLOUD, CLOUD BURSTING Openstack, Rightscale, AWS, Azure
- 38. Instances listing All the openstack servers are operational
- 40. The LB can see 2 running application servers
- 42. CPU consumption We increase the load on Openstack1 Server
- 43. Alerts The threshold (CPU usage >60%) is reached and triggers the first vote to prepare the burst on AWS and Azure
- 44. Instances listing The first application server is operational on AWS Array
- 45. LB console The application server on AWS is registered by the LB
- 47. Instances listing We load openstack 1 and 2 application server to trigger the cloud bursting in Azure
- 48. The alert of openstack1 (and openstack2) is started because the CPU consumption is greater than 60% Alerts
- 49. AWS Array Two application servers on AWS are operational
- 50. Azure Web Array The application server on Azure array is operational
- 51. LB Console All the servers are activated