How far is too far? The Hybrid Cloud Distance Factor
•Download as PPTX, PDF•
0 likes•755 views
Trey Tyler, Sr. Solution Strategist for OVH US, presented "How far is too far? The Hybrid Cloud Distance Factor" at VMworld 2017.
Recommended
Recommended
More Related Content
What's hot
What's hot (19)
Similar to How far is too far? The Hybrid Cloud Distance Factor
Similar to How far is too far? The Hybrid Cloud Distance Factor (20)
Recently uploaded
Recently uploaded (20)
How far is too far? The Hybrid Cloud Distance Factor
- 1. OVH: How Far Is Too Far? The Hybrid Cloud Distance Factor. ––– Trey Tyler | Sr. Solution Strategist
- 2. ©2017 OVH US | Proprietary & Confidential ––– VMworld disclaimer This presentation may contain product features that are currently under development. This overview of new technology represents no commitment from VMware or OVH to deliver these features in any generally available product. Features are subject to change, and must not be included in contracts, purchase orders, or sales agreements of any kind. Technical feasibility and market demand will affect final delivery. Pricing and packaging for any new technologies or features discussed or presented have not been determined. 2
- 3. ©2017 OVH US | Proprietary & Confidential ––– AGENDA 1. Introduction - 5 Minutes 2. Challenges of Owning a Hybrid Cloud – 15 Minutes 3. How OVH Can Help – 30 minutes 4. Q&A 3
- 4. 2017 Proprietary and Confidential WHO IS OVH? 4
- 5. 2017 Proprietary and Confidential©2017 OVH US | Proprietary & Confidential ––– Over 1.2 Million Business Clients in 138 Countries Own 11+ Tbps Network with 32 Points of Presence 2017 27 data centers in 11 countries 2020 50 data centers Data center capacity: 1.3 million physical servers; 260,000 already deployed 19 years experience building & managing servers + data centers INTRODUCING OVH – GLOBAL HYPER-SCALE CLOUD PROVIDER * https://www.netcraft.com/internet-data-mining/hosting-analysis/ 5th Largest Cloud Provider in the world* 2016 20 data centers in 5 countries
- 6. 2017 Proprietary and Confidential©2017 OVH US | Proprietary & Confidential ––– OVH BUILDS ITS OWN DATA CENTERS 6
- 7. 2017 Proprietary and Confidential©2017 OVH US | Proprietary & Confidential ––– 30% natural air cooling + 70% water cooling = 0% air conditioning OVH MANUFACTURES SERVERS & USES GREEN TECHNOLOGY 7
- 8. 2017 Proprietary and Confidential©2017 OVH US | Proprietary & Confidential ––– Hosted Private Cloud Dedicated Servers Bare Metal Global Hyper-Scale Reach OVH’s Fiber Optic Network (11+ Tbps) + Anti-DDoS + Private LAN Public Cloud SOLUTIONS TO SUIT YOUR NEEDS High Touch Customer Support & Services + Dedicated Cloud + Virtual Private Cloud + Disaster Recovery + VMware SDDC + Open API + Automation Compatibility + Scalability + Bring you own License + Non-Virtual Workloads + Proprietary Software 8
- 9. 2017 Proprietary and Confidential2017 Proprietary and Confidential CHALLENGES OF HYBRID CLOUD 9
- 11. ©2017 OVH US | Proprietary & Confidential ©2017 OVH US | Proprietary & Confidential Cloud and Hybrid Cloud Considerations Latency Initial Setup Technical Experience Bandwidth Hardware Maintenance Troubleshooting Security Replacement Hardware Project Timelines Network Availability Time to Respond to Failure People Design Production & Shipping Times Travel & Telecommuting Connectivity Loss of Control Flexibility Visibility HYBRID CLOUD CHALLENGES 11
- 12. 2017 Proprietary and Confidential HOW OVH CAN HELP 1 2
- 13. ©2017 OVH US | Proprietary & Confidential ©2017 OVH US | Proprietary & Confidential HYBRID CLOUD CHALLENGES Cloud and Hybrid Cloud Considerations Latency Initial Setup Technical Experience Bandwidth Hardware Maintenance Troubleshooting Security Replacement Hardware Project Timelines Network Availability Time to Respond to Failure People Design Production & Shipping Times Travel & Telecommuting Connectivity Loss of Control Flexibility Visibility 13
- 14. ©2017 OVH US | Proprietary & Confidential ©2017 OVH US | Proprietary & Confidential OWN THE BACKBONE 14
- 15. ©2017 OVH US | Proprietary & Confidential ©2017 OVH US | Proprietary & Confidential OWN THE BACKBONE 15
- 16. ©2017 OVH US | Proprietary & Confidential ©2017 OVH US | Proprietary & Confidential OWN THE BACKBONE 16
- 17. ©2017 OVH US | Proprietary & Confidential ©2017 OVH US | Proprietary & Confidential HYBRID CLOUD CHALLENGES Cloud and Hybrid Cloud Considerations Latency Initial Setup Technical Experience Bandwidth Hardware Maintenance Troubleshooting Security Replacement Hardware Project Timelines Network Availability Time to Respond to Failure People Design Production & Shipping Times Travel & Telecommuting Connectivity Loss of Control Flexibility Visibility 17
- 18. ©2017 OVH US | Proprietary & Confidential ©2017 OVH US | Proprietary & Confidential 18 • Pre-Firewall • OVH Managed Firewall • Firewall Network • Customer Configurable per IP address • Shield • UDP reflexion/amplification attacks filtering • Armor • Profiles based mitigation • Does the grunt of the work : SYN Authentication, Zombie detection, payload patterns, … • Only enabled when we detect an attack VAC Pre-Firewall Firewall Shield Armor VAC Architecture DDoS MITIGATION
- 19. ©2017 OVH US | Proprietary & Confidential ©2017 OVH US | Proprietary & Confidential VAC VAC VAC VAC SBG RBX GRA BHS Reference Article: https://www.ovh.com/us/news/articles/a2367.the-ddos-that-didnt-break-the-camels-vac LEVERAGING A GLOBAL NETWORK 19
- 20. ©2017 OVH US | Proprietary & Confidential ©2017 OVH US | Proprietary & Confidential Cloud and Hybrid Cloud Considerations Latency Initial Setup Technical Experience Bandwidth Hardware Maintenance Troubleshooting Security Replacement Hardware Project Timelines Network Availability Time to Respond to Failure People Design Production & Shipping Times Travel & Telecommuting Connectivity Loss of Control Flexibility Visibility HYBRID CLOUD CHALLENGES 20
- 21. ©2017 OVH US | Proprietary & Confidential ©2017 OVH US | Proprietary & Confidential Customer Managed Networks & vRACK OVH POP Open Stack vSphere-as- a-Service Dedicated Server Roubaix Hillsboro Vint Hill Customer DC vSphere-as- a-Service CONNECTIVITY SIMPLIFIED 21
- 22. ©2017 OVH US | Proprietary & Confidential ©2017 OVH US | Proprietary & Confidential Top of Rack Host Switches Hosts / Storage Q-in-Q VLAN Super Spine Exchanger Q-in-Q Backbone VXLAN DC 1 DC 2 VXLANSpine VRACK ARCHITECTURE 22
- 23. ©2017 OVH US | Proprietary & Confidential ©2017 OVH US | Proprietary & Confidential VRACK SIMPLIFIES CONNECTIVITY 23
- 24. ©2017 OVH US | Proprietary & Confidential ©2017 OVH US | Proprietary & Confidential VRACK SIMPLIFIES CONNECTIVITY 24
- 25. ©2017 OVH US | Proprietary & Confidential ©2017 OVH US | Proprietary & Confidential Cloud and Hybrid Cloud Considerations Latency Initial Setup Technical Experience Bandwidth Hardware Maintenance Troubleshooting Security Replacement Hardware Project Timelines Network Availability Time to Respond to Failure People Design Production & Shipping Times Travel & Telecommuting Connectivity Loss of Control Flexibility Visibility HYBRID CLOUD CHALLENGES 25
- 26. ©2017 OVH US | Proprietary & Confidential ©2017 OVH US | Proprietary & Confidential • 8 Minutes for physical host provisioning • 30 minutes for entire new vSphere as a service provisioning • Just a moments time for PCI provisioning • Automated host replacement AUTOMATION AT THE CORE 26
- 27. ©2017 OVH US | Proprietary & Confidential ©2017 OVH US | Proprietary & Confidential HYBRID CLOUD CHALLENGES Cloud and Hybrid Cloud Considerations Latency Initial Setup Technical Experience Bandwidth Hardware Maintenance Troubleshooting Security Replacement Hardware Project Timelines Network Availability Time to Respond to Failure People Design Production & Shipping Times Travel & Telecommuting Connectivity Loss of Control Flexibility Visibility 27
- 28. ©2017 OVH US | Proprietary & Confidential ©2017 OVH US | Proprietary & Confidential vCenter • vMotion • svMotion • Fault Tolerance • DRS • HA • vDS NSX • Logical Switches (VXLAN) • Distributed Logical Router (DLR) • Edge Services Gateways (ESG) • Distributed Firewall (DFW) • SpoofGuard • Guest Introspection vROPS • Operations Platform • Policy Management • Performance Monitoring & Analytics • Capacity Management • Change, Config, & Compliance Management vCenter NSX vROPS SAME TOOLS, SAME INTERFACE 28
- 29. ©2017 OVH US | Proprietary & Confidential ©2017 OVH US | Proprietary & Confidential ESXi Hosts 10GB NICs vCenter NSX vROPS NSX Control Cluster Internet OVH Managed Networks Management Resources Customer Resource Pool Customer Managed Networks Virtual SAN SAME TOOLS, SAME INTERFACE 29
- 30. ©2017 OVH US | Proprietary & Confidential ©2017 OVH US | Proprietary & Confidential Cloud and Hybrid Cloud Considerations Latency Technical Experience Bandwidth Initial Setup Troubleshooting Security Hardware Maintenance Project Timelines Network Availability Replacement Hardware People Design Time to Respond to Failure Travel & Telecommuting Connectivity Production & Shipping Times Loss of Control Flexibility Visibility HYBRID CLOUD CHALLENGES 30
- 31. ©2017 OVH US | Proprietary & Confidential ©2017 OVH US | Proprietary & Confidential FULL ACCESS & REMOTE MANAGEMENT 31
- 32. ©2017 OVH US | Proprietary & Confidential ©2017 OVH US | Proprietary & Confidential vScope – Monitoring for Private Cloud, designed by OVH. All useful information on a single page covering physical or virtual resource CPU, RAM or Network metrics. Daily, weekly, monthly, or even annual use metrics available. VISIBILITY 32
- 33. ©2017 OVH US | Proprietary & Confidential ©2017 OVH US | Proprietary & Confidential RTM (Real Time Monitoring) – All maintenance events or incidents are documented and available publicly for all services. Weather map Weather Map - Real time network traffic load of the OVH private network is available through an easy to read graphical interface on the OVH Weather map. Real Time Monitoring TRANSPARENCY 33
- 34. ©2017 OVH US | Proprietary & Confidential ©2017 OVH US | Proprietary & Confidential CPU With things like: • High performance • Security • Transparency • Scalability • Industry Tenure • Self Service • Automation • Green Data Centers and Servers • Cross product connectivity • Affordability Why wait to come to cloud? CLOUD DOESN’T MEAN COMPROMISE 34
- 35. ––– Q&A
- 36. ©2017 OVH US | Proprietary & Confidential ––– HOW TO CONTACT US 36 VMworld Booth Location – 406 @ovh_us and @vcloudair_ovh ovhus and vcloudair.ovh OVH and vCloud Air powered by OVH ovh.com/u s
- 37. ©2017 OVH US | Proprietary & Confidential ––– OVH AT VMWORLD 37 Session ID Session Title Time LHC3295BUS OVH: Why Optimizing Layer 0 matters Tuesday, Aug 29, 11:30 a.m. - 12:30 p.m. LHC3297BES How far is too far? The Hybrid Cloud Distance Factor. Monday, Aug 28, 1:00 p.m. - 2:00 p.m. LHC3296BUS Shields Up! Building a True Security Barrier in the Cloud Wednesday, Aug 30, 2:30 p.m. - 3:30 p.m. LHC1951BU Automate Cloud Recovery For When You Are Nuked From Orbit: It’s the Only Way to Be Sure Tuesday, Aug 29, 3:30 p.m. - 4:30 p.m. LHC2673BU Clearing Cloud Confusion Wednesday, Aug 30, 2:00 p.m. - 3:00 p.m. GRC2676BU Building a Paper Trail: How to Secure and Audit a Public CloudMonday, Aug 28, 11:00 a.m. - 12:00 p.m
- 38. ––– THANK YOU
Editor's Notes
- OVH – we host you “On Vous Héberge” Sounds like “Ahn ne vouz he-bear-zhe”
- OVH is the largest hosting provider you have never heard of. While you may have not heard of it, OVH is the third largest cloud provider in the world. The link at the bottom is to the Netcraft report that shows the ranking of Service providers around the world.
- Details on DC Builds
- Building own servers, from the racks, to the housing, to the servers themselves
- With OVH you get access to almost any type of infrastructure you will need. If you are like most businesses you have a large number of Vmware based VMs running on-prem. OVH’s private cloud is based on Vmware’s SDDC stack and with the acquisition of vCloud Air, connecting your on-prem to a private cloud has never been easier. If you are looking for public cloud burstability OVH has you covered with Public Cloud provided and run on Openstack. But let’s say you have a workload that has specific requirements and you want access to all parts of the software stack. OVH has Bare Metal servers for you. OVH not only provides differing product platforms to address specific project needs of customers, we also allow the integration of these resources to allow for easy setup and communication between these platforms with our vRack product. A customer may have a piece of each of these all combined into a single solution that suites their needs. Private cloud – vSphere SDDC allowing ease of management by leveraging the same tools you’re used to from VMware. Public Cloud – Get virtualized machines at a per hour/minute cost by leveraging OVH’s public cloud built with Openstack. Dedicated Servers – Have full control of every aspect of your environment by starting from bare metal. Have root and BIOs level access to your hardware, and install what you want.
- Elaborate in detail on each of these: Initial setup, order process, provisioning process, initial testing HW Maintenance, (mainly a co-lo related) Replacement HW (Mainly co-lo related) People – needing additional resources near the cloud environment if hardware is something you have access to in a Co-lo. Needing people to learn new and different UI’s, systems, API’s, CLI’s. Or hiring someone to fit the need which can be costly. Employees hired near co-lo space will need to coordinate with local team for any project planning which may be difficult to manage. Travel, if you don’t hire new resources near the co-lo space, you’ll need employees capable of travel.
- Elaborate in detail on each of these: Initial setup, order process, provisioning process, initial testing HW Maintenance, (mainly a co-lo related) Replacement HW (Mainly co-lo related) People – needing additional resources near the cloud environment if hardware is something you have access to in a Co-lo. Needing people to learn new and different UI’s, systems, API’s, CLI’s. Or hiring someone to fit the need which can be costly. Employees hired near co-lo space will need to coordinate with local team for any project planning which may be difficult to manage. Travel, if you don’t hire new resources near the co-lo space, you’ll need employees capable of travel.
- We’ll start with the network. Helping with latency, throughput, Owning its own Fiber, OVH has built a network backbone connecting each of their DC’s together. Allowing for high throughput between DC’s and reduced latency due to a direct path between DC’s.
- This is a global network that spans continents as well. The summation of internet connections equaling 11TBps worth of throughput. These benefits can be passed on to your on-premise environment as well with the expansive list of POPs available. You can bring your own private connection to access your cloud environments through this backbone.
- This is a global network that spans continents as well. The summation of internet connections equaling 11TBps worth of throughput. These benefits can be passed on to your on-premise environment as well with the expansive list of POPs available. You can bring your own private connection to access your cloud environments through this backbone.
- Elaborate in detail on each of these: Initial setup, order process, provisioning process, initial testing HW Maintenance, (mainly a co-lo related) Replacement HW (Mainly co-lo related) People – needing additional resources near the cloud environment if hardware is something you have access to in a Co-lo. Needing people to learn new and different UI’s, systems, API’s, CLI’s. Or hiring someone to fit the need which can be costly. Employees hired near co-lo space will need to coordinate with local team for any project planning which may be difficult to manage. Travel, if you don’t hire new resources near the co-lo space, you’ll need employees capable of travel.
- Elaborate in detail on each of these: Initial setup, order process, provisioning process, initial testing HW Maintenance, (mainly a co-lo related) Replacement HW (Mainly co-lo related) People – needing additional resources near the cloud environment if hardware is something you have access to in a Co-lo. Needing people to learn new and different UI’s, systems, API’s, CLI’s. Or hiring someone to fit the need which can be costly. Employees hired near co-lo space will need to coordinate with local team for any project planning which may be difficult to manage. Travel, if you don’t hire new resources near the co-lo space, you’ll need employees capable of travel.
- Riding on our own private backbone we have a network implementation we refer to as vRack. Using VXLAN aware physical networking components, we’re able to interconnect your environments together and allow communication between your workloads within the same VLAN segments. This is regardless of type of solution as well. Open stack public cloud, connected to Vmware SDDC Private cloud, connected to your own custom bare metal solutions. This type of configuration is completely accessible and configurable from the customer side. No need to open a support case to request to configure connectivity between your OVH DC’s and solutions. With vRack connect, you can also take advantage of these same benefits and bring your local VLAN’s to the cloud. Sharing network space simplifies configurations from a networking perspective at the customer level. Let us deal with the complicated configuration between sites, expensive hardware, and maintenance.
- Riding on our own private backbone we have a network implementation we refer to as vRack. Using VXLAN aware physical networking components, we’re able to interconnect your environments together and allow communication between your workloads within the same VLAN segments. This is regardless of type of solution as well. Open stack public cloud, connected to Vmware SDDC Private cloud, connected to your own custom bare metal solutions. This type of configuration is completely accessible and configurable from the customer side. No need to open a support case to request to configure connectivity between your OVH DC’s and solutions. With vRack connect, you can also take advantage of these same benefits and bring your local VLAN’s to the cloud. Sharing network space simplifies configurations from a networking perspective at the customer level. Let us deal with the complicated configuration between sites, expensive hardware, and maintenance.
- Riding on our own private backbone we have a network implementation we refer to as vRack. Using VXLAN aware physical networking components, we’re able to interconnect your environments together and allow communication between your workloads within the same VLAN segments. This is regardless of type of solution as well. Open stack public cloud, connected to Vmware SDDC Private cloud, connected to your own custom bare metal solutions. This type of configuration is completely accessible and configurable from the customer side. No need to open a support case to request to configure connectivity between your OVH DC’s and solutions. With vRack connect, you can also take advantage of these same benefits and bring your local VLAN’s to the cloud. Sharing network space simplifies configurations from a networking perspective at the customer level. Let us deal with the complicated configuration between sites, expensive hardware, and maintenance.
- Elaborate in detail on each of these: Initial setup, order process, provisioning process, initial testing HW Maintenance, (mainly a co-lo related) Replacement HW (Mainly co-lo related) People – needing additional resources near the cloud environment if hardware is something you have access to in a Co-lo. Needing people to learn new and different UI’s, systems, API’s, CLI’s. Or hiring someone to fit the need which can be costly. Employees hired near co-lo space will need to coordinate with local team for any project planning which may be difficult to manage. Travel, if you don’t hire new resources near the co-lo space, you’ll need employees capable of travel.
- Equipment ready when you are
- Elaborate in detail on each of these: Initial setup, order process, provisioning process, initial testing HW Maintenance, (mainly a co-lo related) Replacement HW (Mainly co-lo related) People – needing additional resources near the cloud environment if hardware is something you have access to in a Co-lo. Needing people to learn new and different UI’s, systems, API’s, CLI’s. Or hiring someone to fit the need which can be costly. Employees hired near co-lo space will need to coordinate with local team for any project planning which may be difficult to manage. Travel, if you don’t hire new resources near the co-lo space, you’ll need employees capable of travel.
- Elaborate in detail on each of these: Initial setup, order process, provisioning process, initial testing HW Maintenance, (mainly a co-lo related) Replacement HW (Mainly co-lo related) People – needing additional resources near the cloud environment if hardware is something you have access to in a Co-lo. Needing people to learn new and different UI’s, systems, API’s, CLI’s. Or hiring someone to fit the need which can be costly. Employees hired near co-lo space will need to coordinate with local team for any project planning which may be difficult to manage. Travel, if you don’t hire new resources near the co-lo space, you’ll need employees capable of travel.