3 More Pitfalls Everyone Should Avoid with Hybrid Multicloud
•Descargar como PPTX, PDF•
0 recomendaciones•465 vistas
You’ve heard that the hybrid multicloud is the path to a digitally successful future for your organization. Back by popular demand, this session builds on the original 3 pitfalls everyone should avoid with hybrid multicloud (https://youtu.be/eACHhV_uxTE) and brings 3 new revelations from real customer experiences. In the first session, we shared some hybrid multicloud pitfalls that just scratched the surface. Let’s take a look at a few more pitfalls on the road to hybrid multicloud for your business as you deliver applications, deal with legacy applications, and make important decisions for your cloud strategies. Join us for 3 more lessons learned from real-life transitions into hybrid multicloud environments.
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Similar a 3 More Pitfalls Everyone Should Avoid with Hybrid Multicloud
Similar a 3 More Pitfalls Everyone Should Avoid with Hybrid Multicloud (20)
Más de Eric D. Schabell
Más de Eric D. Schabell (20)
Último
Último (20)
3 More Pitfalls Everyone Should Avoid with Hybrid Multicloud
- 1. 3 More Pitfalls Everyone Should Avoid with Hybrid Multicloud Roel Hodzelmans Senior Solution Architect, Benelux @roelhodzelmans Eric D. Schabell Portfolio Architect Director @ericschabell
- 3. What’s Multicloud Multicloud is literally using multiple clouds from multiple providers for multiple tasks. Typically, multicloud refers to the use of several different public clouds with the goal of achieving greater flexibility, lowering costs, avoiding vendor lock-in, or using specific regional cloud providers. One of the challenges of multicloud is achieving consistent policies, compliance, and management. Multicloud is more of a strategy.
- 5. Hybrid cloud is a combination of one or more public and private clouds with at least a degree of workload portability, integration, orchestration, and unified management. The key here is that there is an element of interoperability, migration potential, and a connection between tasks running in public clouds and on-premise infrastructure, even if it’s not always “seamless” or otherwise fully implemented. (Otherwise, it’s just a bunch of clouds)
- 7. Hybrid Multicloud in Action AWSOPENSTACK AZURE OPENSHIFT CLOUDFORMS VMs ON PREMISES GLUSTER FUSE 3SCALE
- 8. 1. Portability: Fool’s Gold? I’m doing containers I’m doing Kubernetes I’m portable, right?
- 9. Fool’s gold? What more is there beyond my data and app? ● Logging & Monitoring ● Security ● Back-up and recovery ● Compliancy & Auditing ● Data (see last year’s presentation ● Pipelines ● etc What do we want to port? ● Full stack ● Specific component Why do we need portability? ● Lock-in ● Risk ● Best of breed ● Location
- 10. Even mathematics is working against you
- 12. 2. Security: chasing your tail?
- 16. 3. Governance & Ownership
- 19. Developers decentralized delivery. Operations dealing with deployments and automation. Who owns it all? Who has oversight? Who has high-level overview?
- 20. linkedin.com/company/red-hat youtube.com/user/RedHatVideos facebook.com/redhatinc twitter.com/RedHat Red Hat is the world’s leading provider of enterprise open source software solutions. Award-winning support, training, and consulting services make Red Hat a trusted adviser to the Fortune 500. Thank you
Notas del editor
- Webinar: You’ve heard that the hybrid multicloud is the path to a digitally successful future for your organization. Back by popular demand, this session builds on the original 3 pitfalls everyone should avoid with hybrid multicloud and brings 3 new revelations from real customer experiences. In the first session, we shared some hybrid multicloud pitfalls that just scratched the surface. Let’s take a look at a few more pitfalls on the road to hybrid multicloud for your business as you deliver applications, deal with legacy applications, and make important decisions for your cloud strategies. Join us for 3 more lessons learned from real-life transitions into hybrid multicloud environments.
- The Red Hat Summit 2018 top rated session recording (https://youtu.be/eACHhV_uxTE) available and online free ebook download (https://www.redhat.com/en/engage/multicloud-portability-dummies-s-201903060959?sc_cid=701f20000012pHcAAI).
- That leads into the next level, which is the view of multicloud from Red Hat’s point of view (https://www.redhat.com/en/topics/cloud-computing/what-is-multicloud).
- An IT environment with multiple cloud environments, managed separately, with applications isolated by environment.
- That leads into the next level, which is the view of hybrid cloud from Red Hat’s point of view (https://www.redhat.com/en/topics/cloud-computing/what-is-hybrid-cloud). Hybrid cloud is next generation infrastructure and require organizations to rethink current policies, procedures, and operations methodologies. Simple is better: complexity can destroy any hybrid cloud strategy. Do you really need to connect and/or integrate everything? Do you really need full hybrid orchestration? Do you need to support all of your current APIs?
- At least one public and private cloud (off & on premises) that have a degree of interoperability, application or data portability or common management.
- A customer implemented a hybrid development platform based on Red Hat OpenShift Container Platform deployed across a multicloud environment with Microsoft Azure and AWS plus on-premises virtualization and private cloud with Gluster Storage, CloudForms, Fuse and 3Scale helping make it all work together.
- (Photo: Eric Rolph at English Wikipedia - English Wikipedia)
- https://www.infoworld.com/article/3095894/why-cloud-workload-portability-is-a-pipe-dream.html JUL 18, 2016 https://www.cloudtp.com/doppler/to-port-or-not-to-port-what-to-consider-in-a-cloud-portability-design/
- http://robertgreiner.com/2014/08/cap-theorem-revisited/ Image credit https://vitalflux.com/quick-notes-on-what-is-cap-theorem/
- It’s hard enough to guard your own domains / datacenters, how are you going to bridge to other clouds? (Photo: https://1funny.com/puppy-bites-kittens-tail/)
- https://www.flickr.com/photos/dfataustralianaid/10720755606/ https://www.informationweek.com/cloud/infrastructure-as-a-service/9-worst-cloud-security-threats/d/d-id/1114085 0. Technology is accelerating!!!!!!!!!!!!!!!!!!!!!!!!!!!! 1. Data Breaches 2. Data Loss 3. Account Or Service Traffic Hijacking 4. Insecure APIs 5. Denial Of Service 6. Malicious Insiders 7. Abuse Of Cloud Services 8. Insufficient Due Diligence 9. Shared Technology https://www.security.nl/posting/613418/Europees+keurmerk+voor+veilige+clouddiensten+aangekondigd https://www.customertalk.nl/nieuws/bedrijven-worstelen-met-de-veiligheid-van-nieuwe-technologie/
- https://www.flickr.com/photos/dfataustralianaid/10720755606/ https://www.informationweek.com/cloud/infrastructure-as-a-service/9-worst-cloud-security-threats/d/d-id/1114085 0. Technology is accelerating!!!!!!!!!!!!!!!!!!!!!!!!!!!! 1. Data Breaches 2. Data Loss 3. Account Or Service Traffic Hijacking 4. Insecure APIs 5. Denial Of Service 6. Malicious Insiders 7. Abuse Of Cloud Services 8. Insufficient Due Diligence 9. Shared Technology https://www.security.nl/posting/613418/Europees+keurmerk+voor+veilige+clouddiensten+aangekondigd https://www.customertalk.nl/nieuws/bedrijven-worstelen-met-de-veiligheid-van-nieuwe-technologie/
- Same problems that exist since the days of SOA. Developers generate applications and data use, operations dealing with deployments, but who owns it all. Who has oversight? Who has the high-level view? (Photo: https://scholarlykitchen.sspnet.org/)
- So developers own the decisions and tech
- And Ops are having to deal with all of this
- So who is doing command and control? Are the chapters in control? Are the Enterprise Architects? Who owns the technology beyond the team? Who prevents unlimited occurrences of reinventing the wheel? Who owns the financial business case? There is no right and wrong here. Some organisations want to centralise technology decisions. You can, but you have to balance stiffling innovation vs re-use. If you decentralise it, you get more duplication and reinvents of the wheel. What we seen in practice that the are a lot of claims of doing it one way or the other. In practice, we see more 50 shades of grey