Hybrid Cloud Journey - Maximizing Private and Public Cloud
•Transferir como PPTX, PDF•
3 gostaram•419 visualizações
This presentation walks through the elements of private and public cloud and how to start looking at use cases for hybrid cloud architectures. It covers benefits, statistics, trends and practical next steps for your hybrid cloud journey. Live presentation of some of this content: https://www.youtube.com/watch?v=9_5yJr0HKw4&t=13s
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Semelhante a Hybrid Cloud Journey - Maximizing Private and Public Cloud
Semelhante a Hybrid Cloud Journey - Maximizing Private and Public Cloud (20)
Último
Último (20)
Hybrid Cloud Journey - Maximizing Private and Public Cloud
- 1. PAGE1 BusinessPlan PPT Template SlideDeckStor y Hybrid Cloud Journey Maximizing Private and Public Cloud Ryan Lynn VP – Emerging Architecture Mountain States
- 3. PAGE3 BusinessPlan PPT Template SlideDeckStor y Who We AreTransformation of Private Cloud Maturity With Public Cloud Trace3 Best Practices & Considerations Takeaway “How do I plan the journey toward hybrid cloud using the best of what private and public cloud has to offer?” The Journey To Hybrid Cloud
- 4. AND
- 5. The Case For Private Cloud
- 6. 15% Reduction 1.4% Increase 6.2% Increase Are there a lack of use cases for private cloud? 6.1% Increase
- 7. CONTROL
- 8. COMPLIANCE
- 10. COST
- 13. FEAR
- 14. The Case For Public Cloud
- 15. AGILITY
- 16. ELASTICITY
- 17. EARLY ADOPTION
- 18. FOCUS
- 19. COST
- 20. The Case For Hybrid Cloud
- 21. Best Venue Optimal Placement Hybrid Cloud Models • Decision tree of requirements • Choose filters workload subscribes to • Places workload on the best cloud • Initial placement or ongoing optimization of workload Application Portfolio App 1 App 2 App 3 App 4 App N ... Requirement Filters Performance Cost Security Compliance Location Vendors Resource Pools (Cloud Options) AWS Azure Private Cloud DC#1 Private Cloud DC#2 App 1 App 3 App 4 App 2 App 5 App 6 > >
- 22. Lifecycle Based Dev/Test/Production Hybrid Cloud Models • Production runs on private cloud • Dev/Test runs on public cloud • Production runs on public cloud • Dev/Test runs on private cloud • New applications on public cloud • Optimized moved back to private Dev Test QA Prod Public Cloud Private Cloud Speed Agility Rapid Innovation Rapid Feedback in Public Test in Private Match Production Check App in Private Closest Match to Production Running on Private Steady State Application
- 23. Disaster Recovery Business Continuity Hybrid Cloud Models • Warm or cold standby • DR site located on public cloud • DR site located on private cloud • Active in both locations with replication Web Web Web Web Web App App App App DB-Master DB-Slave Web Web Web Web Web App App App App DB-Slave DB-Slave Private Cloud Public Cloud DB Replication Storage Replication
- 24. Split Tier Web/App/Database Hybrid Cloud Models • Logically separate application into tiers • Place tiers on the best cloud • Latency must be examined • Example: • Web located on public • App located on public • Database located on private Web Web Web Web App App App DB-Master DB-Slave Private Cloud Public Cloud Low Latency
- 25. Cloudbursting Scaling Applications Hybrid Cloud Models • Application logically separated into tiers • Tiers with dynamic scaling are identified • Traffic and latency considered in scaling up application • Servers are activated when needed Web Web Web Web App App App DB-Master DB-Slave Private Cloud Public Cloud Capacity On-Demand Web Web Web Web
- 26. 53% 68% 11% 35% 53% 18% 42% 18% 14% 23% 19% 26% 43% 27% 29% 18% 66% 46% 21% 39% 31% How Your Peers Are Distributing Applications Test and Dev Applications E-Business Hosting Customer Facing Enterprise Applications Collaboration Applications Cloud-native Applications Batch Computing Applications Back-office Enterprise Applications On-prem Private Cloud Hybrid Cloud External Public Cloud and SaaS Source: 451 Research 2017
- 27. PAGE27 BusinessPlan PPT Template SlideDeckStor y …84% of companies operate with more than 1 cloud - but only 38% truly have hybrid. 451 Research - 2017
- 28. PAGE28 BusinessPlan PPT Template SlideDeckStor y Who We Are Virtualization + Automation != Private Cloud
- 29. Core Tenets of Cloud 1. Accessible 2. Programmatic management 3. Multi-tenant 4. Accounting granularity 5. Scalable and elastic 6. Rapid provisioning and self service 7. Virtualization and hardware independent
- 30. Private Cloud Elements of Maturity
- 31. Infrastructure in place that enables open and flexible integration between compute, storage, network and workload while adding unique value. Modernized Infrastructure Arrange the infrastructure in a way to optimize user experience for availability and scalability. Environment should sustain downtime and outages. Available / Scalable / Resilient Software should enable self-service consumption in addition to allowing operations to manage capacity and performance. Software Consumed and Operated Automation and orchestration should allow for cost containment and compression in addition to more predictable life cycles. Cost Optimized 01 02 03 04 Private Cloud Maturity Goal: Match the needs and speed of the business.
- 32. COMPUTE STORAGE WORKLOAD Processing Enhancements In-Memory Computing HCI and Composable Capacity & Footprint Memory/Storage Technology Hyper-Converged Containerization Serverless Deployment Automation Modernizing the Infrastructure NETWORK Speeds (100G/200G/400G) Programmatic Management Intent-Driven Networking
- 33. COMPUTE STORAGE WORKLOAD Processing Enhancements In-Memory Computing Capacity & Footprint Memory/Storage Technology Containerization Serverless Deployment Automation NETWORK Speeds (100G/200G/400G) Programmatic Management Intent-Driven Networking Modernizing the Infrastructure HCI and Composable Hyper-Converged
- 34. COMPUTE STORAGE WORKLOAD Processing Enhancements In-Memory Computing Capacity & Footprint Memory/Storage Technology Containerization Serverless Deployment Automation NETWORK Speeds (100G/200G/400G) Programmatic Management Intent-Driven Networking Modernizing the Infrastructure HCI and Composable Hyper-Converged
- 35. COMPUTE STORAGE WORKLOAD Processing Enhancements In-Memory Computing Capacity & Footprint Memory/Storage Technology Containerization Serverless Deployment Automation NETWORK Speeds (100G/200G/400G) Programmatic Management Intent-Driven Networking Modernizing the Infrastructure HCI and Composable Hyper-Converged
- 36. COMPUTE STORAGE WORKLOAD Processing Enhancements In-Memory Computing Capacity & Footprint Memory/Storage Technology Containerization Serverless Deployment Automation NETWORK Speeds (100G/200G/400G) Programmatic Management Intent-Driven Networking Modernizing the Infrastructure HCI and Composable Hyper-Converged
- 37. Available / Scalable / Resilient Regions and Availability Zones AZ #1 Chicago DC AZ #2 Columbus DC Region #1 Region #2 AZ #1 New Jersey DC AZ #2 Arlington DC Seattle DC Denver DC Region #1 Region #2 Regions Only Regions + Availability Zones Understand Business and Application Needs!
- 38. Software Consumption Strategies Automation / Orchestration / APIs Computing Network Security Storage Workload Infrastructure Determine Number of Programming Interfaces RR SS SS S Fabric Individually System Create Your Own Platforms Vendor Ecosystems Infrastructure Automation Virtualization Platform API HCI Platform API Ansible + Platform API Vendor + Custom API Understand Options For Programming Develop Set of Functions or Capabilities Develop Service Workflow / Orchestrate / Expose Orchestration Orchestration Platform Deploy App Deploy VM Deploy Container . . . 1 2 3 4 This starts off as art and finishes as science.
- 39. Operational Intelligence Active / Proactive / Predictive Predictive Applying a level of analytics and data science to the operational data allows for predictive models to be created that can inform on things before they happen. Proactive This implies collecting metrics and understanding trends within the system. Capacity and performance management are key elements in this model. Active Awareness of the running state of the system. This requires tools that understand each functional area and the sensors and alarms necessary to trigger when there is a problem. Analyze Service • Define functional areas • Analyze dependencies • Identify key metrics for health Analyze Service Components • Understand component purpose • Define interdependencies • Identify key metrics for health Iterate and Optimize • Seek ways to simplify system • Normalize monitoring data • Build scale and resiliency
- 40. Cost Optimization Top Factors Affecting Cost Optimization 2.6% 4.0% 7.3% 8.6% 11.3% 14.6% 16.6% 17.2% 17.9% 11.3% 8.6% 7.3% 4.0% 2.6% Capacity planning tools -> increasing utilization 17.9% 17.2% 16.6% 14.6% Favorable software licenses terms Automation tools reducing labor overhead Cost / budgetary management tools Favorable hardware procurement terms Favorable colocation / data center terms Reuse of existing data center hardware Governance / approval tools Reuse of existing software licenses Source: 451 Research 2017
- 41. PAGE41 BusinessPlan PPT Template SlideDeckStor y Public Cloud Elements of Maturity
- 42. Provisioning and operations of the public cloud IaaS is consistent within the organization. Delivery and support organizations are proficient in supporting public cloud environment. Infrastructure Parity - IaaS Best practices have been documented and implemented. Availability, resiliency and scalability have all been addressed with architecture using services, regions and zones. Optimized Architectural Framework Public cloud usage is well defined, governed, supported and delivered. New features are systematically introduced with minimal disruption. Operational Excellence Frequent analyzing of public cloud usage for cost optimization and containment. Understanding cost benefit across different clouds. Cost Optimized 01 02 03 04 Public Cloud Maturity Goal: Match the needs and speed of the business.
- 43. Automating Public Cloud Automation / Orchestration / APIs Computing Network Security Storage Workload InfrastructureInfrastructure Automation Virtualization Platform API HCI Platform API Ansible + Platform API Vendor + Custom API Security Network Storage WorkloadAPI API API API Public Cloud Native Workflows Customer Developed Workflows Deploy AppDeploy VM Deploy Container . . . Orchestration Autoscaling Load Balancing Scripts Config Mgmt 3rd Party Software . . . Define service workflow(s)1 Use cloud native services when possible2 Use cloud native workflows when possible3
- 44. Hybrid Cloud Bringing It All Together
- 45. Cloud Management Platform Workflows IaaS Public Cloud Public Cloud Private Cloud Private Cloud IaaS Infr. Automation Infr. Automation Hybrid Cloud Management Cloud Management Platforms PaaS PaaS PaaS PaaS API API API API Orchestration Optimization Cost Management Compliance Service Catalog Workload Mobility Configuration and provisioning blueprints for applications or services Software rules and constructs instructing PaaS and IaaS tiers for instantiation. Metrics used for workload placement based on capacity or performance. Metrics ensuring workloads are utilizing most effective cost structures. Policy and rules to guarantee security and governance are adhered to. Expose services and applications to consumers through self-service catalog.
- 46. 0 0.5 1 1.5 2 2.5 3 3.5 4 4.5 5 Existing Maturity Desired Maturity Infrastructure Modernization Available / Resilient / Scalable Software Consumption and Automation Cost OptimizedCost Optimized Software Consumption and Automation Optimized Architectural Framework Infrastructure Parity Cloud Management Platform Service Catalog Workload Mobility Compliance Public Cloud Private Cloud Hybrid Cloud Cloud Maturity Model Private / Public / Hybrid Scale 0 to 5 -0 is non-existent -5 is strong
- 47. Best Practices For Hybrid Journey 1. Strategic road map 2. Open and flexible interfaces 3. Technologies with dual cloud strategy 4. Use software to extend lifecycle 5. Commoditize 6. Adherence to open industry standards 7. If closed system -> ensure entry point 8. Commit and invest in people, teams and process
- 48. Research Emerging Technology VC Briefings Consulting Modernization Advanced Services (SDI) – Software Defined Infrastructure (CIA) – Collaboration Infr. and Assessments (CBX) – Connected Business eXperience (DMG) – Data Management Group APPLICATION MIGRATION SERVICES MANAGED SERVICES PROFESSIONAL SERIVCES INNOVATION LIFECYCLE Our Unique Value
Notas do Editor
- Hello – and welcome Thank you so much for taking the time to join me today – to talk about private, public and hybrid cloud Introduction – introduce yourself
- I love this photo. . . Do you ever feel like this? 1 case – you’re asked to move fast and accomplish a lot with very little (i.e. travel to space with a tin rocket and skateboard) 2 case – it could be that you’re a dreamer – you know the destination and can imagine getting there Final case – you – last weekend after a few too many drinks . . . The technology world we live in requires us to move at rapid speed, sometimes without the right equipment and without a known destination.
- Accomplish in short time My hope is that you leave today with fresh ideas on your journey toward hybrid cloud while transforming and maturing your existing private and public cloud environments
- Public cloud – burst onto scene 15 years ago Young, inexperienced, dreamer – much like our young friend with the rocket ship Crash / burn – but hasn’t – it’s showing us new ways the business wants to use technology we should not look at this as an “or” discussion – but an “and” Goal should be the beautiful hybrid between what public cloud can teach us – and evolving and modernizing private cloud while exposing the unique features that each offers.
- Let’s explore the state of private cloud and some of the use cases
- Why is on-premise private cloud not growing? Are the use cases shrinking? In conversations with clients – that’s not the case.
- Controlling Performance, Security, Privacy and Solidifying Data Ownership
- Legalities and regulation restrict or prohibit public cloud – with a preference on on-premise private -> Healthcare, Insurance, Financial, Utilities, SPs
- Investments into real estate, lifecycle refreshes of infrastructure and operational investment
- Some believe that private cloud is more cost effective Not always true – but not always false Capacity optimization and automation lead to some cost savings
- Challenges with moving, refactoring or modifying core business applications
- Pushing applications closer to the edge -> enhancing user experience CDN -> paved the way Smart Cities Automated vehicles AR and VR Mobile Edge Computing – reduce network bandwidth usage -> 5G
- Still a real issue Fear keeps companies from exploring public cloud BUT – also – FOMO drives companies to hasty decisions
- Let’s explore some of the use cases of public cloud
- Rapid ability to move or change directions -> help business move with the market
- Quickly being able to expand or contract resources On-demand usage Not carrying any more than you need
- Services are iterating faster on public cloud Opportunity to test and validate these services with minimal investment
- You can focus on application and services with main goal of value to users Not distracted with low-level infrastructure overhead, operations or maintenance Rightsizing your environment
- Efficient usage of resources and benefits of cost structure OPEX model may be better for you Automation leads to even more cost savings
- So we know there are use cases for private Certainly know the benefits of public cloud Again – the advantage is private cloud AND public – true hybrid Let’s take a look at some of the most popular hybrid cloud models
- Best venue – also called optimal placement Assign applications a set of filters (or questions) that lead to the workload being placed on the best cloud
- Lifecycle based – follows the software development lifecycle approach Various groups are placed onto the cloud that matches their specific needs for speed/agility, scale, etc.
- Disaster recovery is one of the most popular Production running in private cloud – warm or cold standby running in public cloud Active / active is also an option (although very dependent on infrastructure and application)
- Application is logically divided into tiers Tiers are then placed on the cloud that meets the tier’s requirements (scale, performance, security, etc.) Latency is a big concern here Not for everyone
- Similar to tiered approach Used for tiers that see spikes in usage – not consistently Use another cloud to augment that demand by bursting Loosely coupled applications are better here
- I’m often asked for insight on how others are distributing applications and on which clouds Survey by 451 in 2017 Types of apps and where clients are running them On-prem –> heavy back-office, batch and customer facing applications Public and SaaS -> cloud native, collaboration and E-Business Fairly balanced with hybrid comfortably in the middle
- You might be sitting in the audience thinking “ok – so we should have massive adoption of hybrid cloud”
- We’re not there yet. Clients have deployed virtualization + automation and called it private cloud It’s a great step – but that’s all – a step Continue to understand the benefit of public consumption -> transform private cloud to match
- Reminder of cloud characteristics We do #7 very well. But think about the others and how mature these are in your orgs Modernization means – embracing these principles and planning your strategy around them
- When transforming your private cloud – there are things you can focus on to help with the maturation process.
- Modernizing the infrastructure means bringing our compute, network and storage up to certain levels in terms of performance, capability and operations Architecting and designing our systems for demand and failure Software should begin to enable the business to consume resources at their pace while making it easier for operations Finally – optimizing the environment with automation and efficiency to lower costs Goal: We have to remember that the business need is what is driving here.
- Let’s zoom into the infrastructure for a few minutes and look at a few areas of modernization that we’re working with several clients on I’ve separated into 4 areas – although this is not an exhaustive list.
- Processing Traditional x86 procs -> cores, clock speeds Instruction sets adding more features – enabling higher network IO, advanced visibility (packets), AES encryption, video encoding ARM processors -> smartphones , tablets -> now IOT Co-processing (GPU and FPGA) -> parallel processing - machine learning and analytics CHOICE!!! HCI and Composable Similar -> both Software Defined and flexible infrastructure HCI – distributed system that pools compute and storage together to be managed as one Easier integration points for as a service consumption Modular -> easier lifecycle and overall maintenance Evolving to leverage analytics for things like workload optimization CS – software defined infrastructure Use software to define the hardware components of a system -> cpu, memory, storage and fabrics On-DEMAND Uses unified API to control and provide integration into Think of self-configured infrastructure -> application dictates what it needs – what platform – composable makes that happen
- Capacity and Footrping 14TB HDDs -> continue to improve magnetic recording 30TB SSD with 100TB SSD just announced -> THINK ABOUT THAT Goal – to pack 1PB into 1RU Whether you’d want to. . . Memory/Storage Technology All Flash is mainstream SATA and SAS bottleneck -> NVMe NVMe -> initially servers – now arrays -> what does this do to networks? Bridging gap between storage and memory - 3DXpoint – Non-volatile memory – speeds between NAND and DRAM Being built into arrays Several exciting partners mixing and matching these technologies to offer several options
- Programmatic management Southbound APIs -> YAY! New ways to operate and monitor networks Automation platforms Vendor automation Roll your own – ansible, puppet, scripts Platforms Intent-driven networking Describe desired outcome Algorithms that translate to device commands “Create new VLAN on Boston Core Switch 1” Interesting companies -> Chatbots, NLP - - Also – operational tools that can theorize changes
- Workload or processing unit Containers At EVOLVE – we performed a live crowdsource of container usage – here’s what we found Stand up if active conversations or usage of containers (~50%) Stay standing if you have any workload (dev/test/prod) using containers (~%40) Stay standing if you have any production workloads (~25%) Stay standing if you have a revenue generating application on containers (~10%) EXCITED -> but practical Great tool for speed, distributed apps and HYBRID (portable) Let use case drive usage Work to do -> Security and Networking Serverless Award for the worst technology name goes to -> Serverless Instead of serverless – we will furthermore refer to it as “Mike” So what’s really happening here? Entry point into the code (VM = app level, Container = process level, Mike – function level) Abstraction down to the function level Triggered events – more transaction based – IOT devices RIGHT TOOL, RIGHT JOB
- Making our clouds available, scalable and resilient starts with properly aligning needs of the applications with the architecture of the infrastructure Public clouds have had the idea of regions and availability zones Private data centers should adopt the principles here Regions only Failure domains are at the data center level (physical) Data centers are a region Operate in active/standby mode Regions + Availability Zones Subdividing the region into availability zones Availability zone = a data center Zones work together to protect a region
- Maturing our private cloud environments to offer more automation, orchestration and self-service consumption We start with the infrastructure and determine how many interface touch points we can live with Individually – means there could be a whole lot of integration work System – means we’re relying on a vendor to have built an ecosystem Spectrum of choice Create your own (ansible, puppet, chef, scripts) Other end – vendor ecosystem – possible lock-in Platform players in the middle (as we discussed – modeling used to abstract) Develop our strategy to automate the infrastructure Think about each area of the infrastructure and what functions or services need to be enabled Define your services and the workflows needed to activate those services Orchestration (will be discussed in more detail in hybrid cloud) – coordinates all of the automation needed to enable a service This starts off as an art form (end state of consumption) and ends with science (detailed steps)
- Another aspect of maturing with private cloud – is elevating operations The foundational level is active awareness -> this means knowing the running-state of the system – and relying on alarms, sensors or anything else to tell you something is not running correctly Next level is getting proactive – which involves turning operational data into information – trending – things like capacity and performance management Finally – applying a level of analytics and data science to our environment to have algorithms help us predict situations that may occur One possible path to maturing operations would be: Analyzing the service (define those functional areas, identify dependencies and key metrics for health) Analyze the components that make up the service (their purpose, interdependencies and key metrics for health) Optimize the environment continually – seek ways to simplify – normalize your data
- Looking at optimizing the costs of private cloud – we pulled some research on the ways that most clients are accomplishing this The top way is through capacity planning – maximizing your use of the resources you have – this is what public cloud does very well Automation tools are number three – which allow you to reduce that operational overhead Reusing data center hardware is an interesting one – and attainable if you can properly leverage software to help somewhat “commoditize” infrastructure Walk through anything else you feel is pertinent
- Public cloud – while certainly mature in certain areas – continues to challenge clients with properly architected environments, cost, governance and usage control
- Infrastructure parity really means that in a hybrid model – we have capabilities that are similar across private and public. More than that – we are getting parity in how we manage these environments Has our public cloud been properly architected according to best practices for all services? Is it documented? Do we have proper systems in place to deal with usage, governance and control. Can we introduce new services into public cloud without impacting existing services? Once again – are we optimized to have the best cost structure possible given the needs of the application Same goal – provide what the business needs
- Remember our private cloud automation story? We start the public cloud discussion with that infrastructure automation already done for us The public cloud has exposed APIs to us in each area AND they have already written native workflows for using those services If we needed nothing more – we would be done. If we have needs outside of what the public cloud offers OR we are using a hybrid architecture – we have some developing to do on our own Once again – we need to define what our service workflows look like Leverage what’s provided to us when we can
- Ok – so we have a mature private cloud We also have a mature public cloud These precursors will make it MUCH easier to attack hybrid cloud efficiently Let’s put these pieces together
- We have our clouds – in this case – two public and two private Each of them has maturity to offer IaaS and PaaS with exposed APIs to operate and provision in those clouds We now introduce the idea of Cloud Management Platforms CMPs are there to perform a lot of the hybrid cloud functionality including: Workflows Orchestration and some low-level automation Optimizing the cloud and workload placement Controlling and reporting cost usage Ensuring compliance Finally – we need to expose our capabilities to consumers to use We do this through a service catalog
- Here is an example of a cloud maturity model This model can help show the maturity of nearly anything – we could focus exclusively on private cloud or public cloud – or a specific area of the infrastructure Here we are showing private, public and hybrid cloud maturity We’re listing strength of a scale of 0 to 5 – where 0 is non-existent and 5 is mastery Inside of each area – we have different elements that we’re measuring – where we are today – and where we’d like to be in the future (aspirational) If we look at this example – we can see that our client currently has mastery goals for infrastructure modernization – but currently is only at a 3 The visual shows them areas they need to develop in order to reach maturity goals Walk through other examples on this diagram Point is: We can help clients build these as part of vision/strategy
- Spend time visualizing and documenting your plan – if you don’t have a plan – you’re guessing. You may be right – but statistics do not favor you Ensure that your infrastructure is truly open Talk with partners about parity across clouds Hardware is harder to change than software Low value lifecycles -> commoditize Stay close to industry trends Use closed only if you have to Invest
- So we’ve walked through a lot here. How can we help? Walk them through our unique value prop