Pros and Cons of Moving to Cloud and Managed Services
•
3 j'aime•1,175 vues
Many organizations are exerting top-down pressure to examine cloud and as-a-service models in general. To the IT managers and administrators in the data center, losing control of your data and/or applications can be a scary thing. There is also a complex web of fiscal and technical items that must be considered. In this presentation, we will help you build a base understanding of the three core as-a-service models. We will then go on to discuss what we see working with our customers in the real world; these are opportunities that can offload some of the drudgery in your data center, while at the same time demonstrating to your organization that you are embracing the cloud. This presentation provides an in depth discussion surround the pros and cons of moving applications, and or infrastructure over to cloud and managed services.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (18)
Similaire à Pros and Cons of Moving to Cloud and Managed Services
Similaire à Pros and Cons of Moving to Cloud and Managed Services (20)
Dernier
Dernier (20)
Pros and Cons of Moving to Cloud and Managed Services
- 1. Eagle Technologies, Inc. © Copyright 2016 Understanding the Pros and Cons of Cloud Computing Models Brian Anderson, Senior Solutions Architect
- 2. Eagle Technologies, Inc. © Copyright 2016 What Camp Are You In? Looking to Understand Cloud Computing Looking for Cloud Wins 1 2 Looking for Ammunition 3
- 3. Eagle Technologies, Inc. © Copyright 2016 3 • Pros: Elasticity / Agility / Self-Service / Ease of Provisioning/Deployment • CIO’s like Operational Expense (OpEx) – Capital Expense (CapEx) can be unpredictable and painful – There is a perception that the cloud is more cost-effective • Talent is expensive and hard to find – Cloud allows the delivery of IT services without the labor and technology costs associated with maintaining complex computer systems • IT shops have much to do • Large cloud vendors are shaping the conversation Why the Push for Cloud?
- 4. Eagle Technologies, Inc. © Copyright 2016 What is the Cloud? 4
- 5. Eagle Technologies, Inc. © Copyright 2016 5 cloud com·put·ing noun Cloud computing is a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. The cloud model is composed of: – Five essential characteristics – Three service models – Four deployment models Source: National Institute of Standards and Technology What is the Cloud?
- 6. Eagle Technologies, Inc. © Copyright 2016 The Five Essential Cloud Characteristics 6
- 7. Eagle Technologies, Inc. © Copyright 2016 On-Demand Self-Service – A consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with each service provider. Cloud Computing: Five Essential Characteristics
- 8. Eagle Technologies, Inc. © Copyright 2016 Broad Network Access – Capabilities are available over the network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, tablets, laptops, and workstations). Cloud Computing: Five Essential Characteristics
- 9. Eagle Technologies, Inc. © Copyright 2016 Rapid Elasticity – Capabilities can be elastically provisioned and released, in some cases automatically, to scale rapidly outward and inward commensurate with demand. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be appropriated in any quantity at any time. Cloud Computing: Five Essential Characteristics
- 10. Eagle Technologies, Inc. © Copyright 2016 Resource Pooling – The provider’s computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand. There is a sense of location independence in that the customer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter). Examples of resources include storage, processing, memory, and network bandwidth. Cloud Computing: Five Essential Characteristics
- 11. Eagle Technologies, Inc. © Copyright 2016 Measured Service – Cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency for both the provider and consumer of the utilized service. Cloud Computing: Five Essential Characteristics
- 12. Eagle Technologies, Inc. © Copyright 2016 • On-Demand Self-Service – Provision without human interaction with the service provider • Broad Network Access – Access from nearly anywhere, no location dependence • Rapid Elasticity – Scale rapidly outward or inward • Resource Pooling – Multi-tenant model, pooled resources, location independence • Measured Service – Metering capabilities (monitor, control, report) Wrap-Up: Essential Characteristics
- 13. Eagle Technologies, Inc. © Copyright 2016 The Three Cloud Computing Service Models 13
- 14. Eagle Technologies, Inc. © Copyright 2016 • Examples: – Co-located Data Centers (CoLo) – Amazon Web Services (AWS) – Microsoft Azure – Rackspace 14 • IaaS providers are responsible for: – Physical security – Power – Cooling – Compute, Storage, & Networking • Consumer is responsible for: – OS & Applications – Compute, Storage, & Networking Cloud Computing Service Models Infrastructure as a Service (IaaS) IaaS
- 15. Eagle Technologies, Inc. © Copyright 2016 • Examples: – Microsoft Azure – Google App Engine – Force.com – Connectria 15 • PaaS providers are responsible for: – Physical security – Power – Cooling – Compute, Storage, & Networking – Software Development Environment – Web & Application Hosting • Consumer is responsible for: – Application Development & Maintenance Cloud Computing Service Models Platform as a Service (PaaS) IaaS PaaS Saa
- 16. Eagle Technologies, Inc. © Copyright 2016 16 • SaaS providers are responsible for: – Physical security – Power – Cooling – Compute, Storage, & Networking – Software Development – Web & Application Hosting – The Application *Consumer manages nothing but the application settings. Cloud Computing Service Models Software as a Service (SaaS) • Examples: – Gmail – LinkedIn – Twitter – Facebook – Salesforce.com – Office365 – WebEx IaaS PaaS SaaS
- 17. Eagle Technologies, Inc. © Copyright 2016 IaaS PaaS SaaS 17 Cloud Computing Service Models Gmail Facebook LinkedIn Rackspace Amazon Web Services (AWS) Google App Engine Microsoft Azure Connectria
- 18. Eagle Technologies, Inc. © Copyright 2016 The Four Cloud Computing Deployment Models 18
- 19. Eagle Technologies, Inc. © Copyright 2016 19 Details • Infrastructure provisioned for use by general public • Exists on premises of cloud provider Deployment Models: Public Cloud Control/Access • Compute resources are shared • Public has access • Provider controls security Examples • Gmail • Twitter • Salesforce.com • Office365 • WebEx
- 20. Eagle Technologies, Inc. © Copyright 2016 20 Details • Infrastructure provisioned for exclusive use by single organization • Exists on or off premises Deployment Models: Private Cloud Control/Access • Compute resources are NOT shared (outside the company) • Access limited to business consumers • Business controls security Examples • OpenStack • VMware • Microsoft SC
- 21. Eagle Technologies, Inc. © Copyright 2016 21 Details • Infrastructure provisioned for exclusive use by a community of organizations with shared concerns • Exists on or off premises Deployment Models: Community Cloud Control/Access • Compute resources are shared • Access is restricted outside of community user groups • Business controls security Examples • Research • LinkedIn • Facebook
- 22. Eagle Technologies, Inc. © Copyright 2016 22 Details • The combination of two or more distinct cloud infrastructures • Data and application portability is key • Parts may be managed remotely by MSP’s Deployment Models: Hybrid Cloud Use Cases • Cloud Bursting • Data Protection • Disaster Recovery
- 23. Eagle Technologies, Inc. © Copyright 2016 Cloud Computing Considerations 23
- 24. Eagle Technologies, Inc. © Copyright 2016 24 • Vendor Lock-in • Less Flexibility • Reduced Governance • Data Location / Data Ownership • Compliance Limitations • Increased Attack Surface • User Education • Node Maintenance (no vMotion) • Backups / Data Integrity Cloud Computing Considerations • Reduced Monitoring/Visibility • Extreme Outages • Region Failures • Operational Expense • Bandwidth Costs & Throughput • Service Level Agreements • Long-term Contracts • Cost Overruns • Platform Maturity
- 25. Eagle Technologies, Inc. © Copyright 2016 25 • Traditional mindsets in the datacenter treat servers like pets – Server gets sick, you make it better • In the cloud you should act like a chicken farmer – Server gets sick, you isolate it and get rid of it • This idea is often called “Cloud Native” or “Cloud Aware” – Use stateless microservices/containers – Rely on orchestration & configuration management Cloud Computing Considerations Pets vs Chickens
- 26. Eagle Technologies, Inc. © Copyright 2016 26 There are plenty of great use cases for cloud. Where are the easy wins? The Cloud Is Here To Stay
- 27. Eagle Technologies, Inc. © Copyright 2016 Cloud Computing: What are the Easy Wins? Low-Hanging Fruit 27
- 28. Eagle Technologies, Inc. © Copyright 2016 28 • Benefits – Most system administrators loathe managing Exchange (get rid of it). • Examples – Google Apps, Microsoft Office365 • Considerations: – Make sure you consider your compliance and retention requirements – This is a core business app, do your homework Low-Hanging Fruit – Email (SaaS)
- 29. Eagle Technologies, Inc. © Copyright 2016 29 • Benefits – Get rid of facilities management – Improve your infrastructure – Does not fundamentally change how IT is done • Considerations – Must sign contract with a term (3-5 years) Low-Hanging Fruit – Co-located Data Centers (IaaS)
- 30. Eagle Technologies, Inc. © Copyright 2016 30 • Benefits – Take advantage of the cloud model – Elasticity – Ease of provisioning – OpEx • Examples – Holidays, tax season – QA & Dev environments – Building out new environments Low-Hanging Fruit Seasonal Workloads & Pilot Projects (IaaS & PaaS)
- 31. Eagle Technologies, Inc. © Copyright 2016 31 • Embracing the cloud doesn’t mean every part of a solution has to live there. • This is not difficult or disruptive • Offsite Backup Copies + Local Retention – Overcome availability concerns by keeping backup copies local. • Cost-effective Offsite Data Protection – Many business can avoid secondary DR infrastructure (CoLo or owned) with a hybrid backup solution. Low-Hanging Fruit – Hybrid Backup
- 32. Eagle Technologies, Inc. © Copyright 2016 32 • Benefits – Availability and time-to-restore concerns are low with archive • Examples – CommVault • AWS, Glacier, DASH • Considerations: – Make sure you consider your SLA’s and availability requirements Low-Hanging Fruit – Archive / Extended Retention
- 33. Eagle Technologies, Inc. © Copyright 2016 33 If you were in a bare metal situation, would you start with bare metal? • Benefits – Fewer up-front investments (costs don't go away, but are evenly distributed) – Get going quickly – Scale up fast (when you need to) – When you grow from scratch using the cloud, you’re less likely to hit a major obstacle Gartner: Startups that can leverage the cloud have an early advantage. Low-Hanging Fruit New IT Startups
- 34. Eagle Technologies, Inc. © Copyright 2016 34 • Benefits – In-house equipment with monthly/yearly payments – Pay for what you use, even when usage shrinks • Examples – On-premise storage with monthly chargeback – Support costs that covers hardware refreshes – Leasing traditional infrastructure • Considerations: – This are not necessarily the most cost-effective options Low-Hanging Fruit – OpEx Models for Traditional Infrastructure
- 35. Eagle Technologies, Inc. © Copyright 2016 35 • SaaS: Lots of opportunities to look at cloud: – Document imaging/management – Video and teleconferencing – Training – Customer relations – Accounting • Considerations: All of them! Low-Hanging Fruit – SaaS in General
- 36. Eagle Technologies, Inc. © Copyright 2016 In Conclusion 36
- 37. Eagle Technologies, Inc. © Copyright 2016 37 • Run your data center like a managed service provider: – Think of applications in terms of how many resources they consume: • Memory • Compute • Storage – Employ showback or chargeback methods • Show your company what each workload costs – Make wise hardware decisions and communicate your expenses well in advance – Take another look at OpEx models Treat Your DC Like The Cloud Bad data center management makes a great case for the cloud.
- 38. Eagle Technologies, Inc. © Copyright 2016 38 Your Boss (or your Boss’s Boss), they just want to: – Spend less money (CapEx or OpEx) – Avoid surprises in the budget – Mitigate risk – Be more agile – Make money and grow the business “It is just applications, data, and plumbing… where the plumbing resides, and who owns it is a business decision.” “It’s All Just Plumbing”
- 39. Eagle Technologies, Inc. © Copyright 2016 40 How you add value in IT has changed. Hybrid Cloud is inevitable! Summary Educate yourself… understand the attributes of cloud computing Remember the considerations and pain points of cloud/managed solutions Take a look at some low-hanging fruit Take care of your current data center first Learn how to speak “C-Level”
- 40. Eagle Technologies, Inc. © Copyright 2016 Got questions? We’ve got answers. 41
- 41. Eagle Technologies, Inc. © Copyright 2016 Thank you! Brian Anderson Senior Solutions Architect brian.anderson@eagleinc.com
Notes de l'éditeur
- Embracing Cloud in a Traditional Data Center “Many organizations are exerting top-down pressure to examine cloud and as-a-service models in general. To the IT managers and administrators in the data center, losing control of your data and/or applications can be a scary thing. There is also a complex web of fiscal and technical items that must be considered. In this presentation, Eagle Technologies will help you build a base understanding of the three core as-a-service models. We will then go on to discuss what we see working with our customers in the real world; these are opportunities that can offload some of the drudgery in your data center, while at the same time demonstrating to your organization that you are embracing the cloud.”
- There is actually a fourth: folks who are looking for a place to sit down and play on their phone. Let’s make them all happy! Bosses are driving cloud adoption, how can I give my boss a win...
- Gartner says the primary driving benefit of adopting a cloud model should not be a cost savings, instead it's around increased agility and dynamic scalability, which can improve speed to market.
- The National Institute of Standards and Technology (NIST) has created a robust, comprehensive cloud definition that has been well-accepted across the IT industry. It covers five essential cloud characteristics, three service models, and four deployment models.
- On-demand, self-service, shared resources, rapid provisioning and elasticity. Let’s talk about the three pillars of the NIST definition.
- There are five key attributes of a true cloud service. While there may be some variations in certain cases or environments, a cloud service should adhere to these traits.
- This is a key attribute of a true cloud service. A customer must be able to request the usage of a cloud service through an automated interface (such as a web portal, kiosk, mobile app, etc.) without the need to speak with a middleman or sales person. The consumer can request this at any time. This feature should also enable the consumer to cancel the usage of a cloud service at any time. From the consumer's perspective, engaging a cloud service and releasing a cloud service should be as convenient and hassle free as possible. For example, there should be no need to speak with a call center representative or request/release a cloud service only during working hours.
- A true cloud service must be accessible and usable through a broadly available communication network. Generally speaking, it means that as long as a consumer has Wi-Fi, broadband, or landline network connectivity, then he/she can utilize the cloud service. There should be no location dependency for the cloud service. Furthermore, a cloud service should be accessible with minimal dependency on the device used for accessing the cloud service.
- A powerful attribute of a cloud service is that it can scale up or down as required automatically and in real-time (or near real-time). This means that varying workloads will be met with the right level of resource capacity (CPU power, storage, network bandwidth, etc.), adjusting to real-world demands from end users.
- The underlying computer resources in a cloud service are shared across multiple customers. This multi-tenancy model has certain privacy and security concerns that is shared by all cloud users, therefore, all users must take the necessary precautions and risk-management activities for protecting and guarding their assets, be it data or otherwise.
- A measured cloud service provides the underpinning for the pay-as-you-go model. This allows a cloud provider to charge consumers for only the resources or services that are actually consumed by the customer. The old model of having a fixed IT budget that pays for IT resources regardless of whether they are underutilized or over utilized, which no longer applies in cloud computing.
- In practice, there are other service models available. However, even these additional service models are a variation or combination of these three basic service models. For each service model, we state the NIST definition, elaborate on key principles, and illustrate the service model with three real-world case studies.
- IaaS layer is the fastest growing segment of cloud. IaaS only provides the lowest-level data center resources in an easy-to-consume way, and doesn't fundamentally change how IT is done. "Infrastructure as a Service (IaaS). The capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, and deployed applications; and possibly limited control of select networking components (e.g., host firewalls).“ The IaaS model allows IT administrators to operate and manage traditional data center resources in the cloud. All of the traditional IT infrastructure layers (servers, storage, network, and so forth) are available virtually from a cloud IaaS provider. Customers are responsible for managing the OS layer and higher, while the cloud provider focuses on the hypervisor layer and below (server hardware, network connectivity, power/cooling, HVAC, etc).
- I like to refer to this as the “Operating System Down”. "Platform as a Service (PaaS). The capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages, libraries, services, and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, or storage, but has control over the deployed applications and possibly configuration settings for the application-hosting environment." The PaaS service model provides a powerful development platform for software developers. Most PaaS providers support a range of programming languages for developers to use. All leverage Web Services (i.e., web-based API) to create cloud-based application. The underlying infrastructure is opaque to the developer as it is fully managed by the PaaS provider.
- "Software as a Service (SaaS): The capability provided to the consumer is to use the provider’s applications running on a cloud infrastructure. The applications are accessible from various client devices through either a thin client interface, such as a web browser (e.g., web-based email), or a program interface. The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user specific application configuration settings." The SaaS service model generates the most interest to business users and managers. Through SaaS-based applications, IT and business units can focus on supporting and enabling business operations and functions. The SaaS model manages the underlying software and IT infrastructure. IT is released from the day-to-day activities of running a data center, IT operations, and maintenance.
- The takeaway on this slide is that you can often figure out what kind of service model is by looking at who is consuming it (sys admins, developers, or end-users),
- NIST outlines four cloud deployment models. For each deployment model, we state NIST's definition, elaborate on key principles, and provide two case study examples. In all four models, there are three determining factors: who controls security, who has access to the data, and whether the resources are shared or dedicated.
- "The cloud infrastructure is provisioned for open use by the general public. It may be owned, managed, and operated by a business, academic, or government organization, or some combination of them. It exists on the premises of the cloud provider." For public cloud services, it is assumed that it is multi-tenant and the underlying resources are shared among multiple customers. The public cloud provider owns and controls the security and protection of data between one customer and another customer.
- "The cloud infrastructure is provisioned for exclusive use by a single organization comprising multiple consumers (e.g., business units). It may be owned, managed, and operated by the organization, a third party, or some combination of them, and it may exist on or off premises." In private cloud deployment, the IT assets are fully dedicated to a single company, with no sharing of resources outside of the corporate entity. Security and data protection is owned by the same business entity. Case Study Examples of Private Cloud Deployment 1) OpenStack OpenStack is an open source cloud platform that provides private cloud computing services for IaaS model. Some companies use it to deliver IaaS services internally to their business units. As a cloud technology, it can also be used by organizations to deliver IaaS to the public. OpenStack started in July 2010 as a joint project by NASA and Rackspace. Ownership and management of its development was transitioned in September 2012 to the OpenStack Foundation, a non-profit entity. Support for OpenStack has grown tremendously and numerous vendors committed their support for its ongoing development. Some vendors include: VMware, Red Hat, HP, IBM, EMC, and Oracle. OpenStack uses a very modular structure in which each component delivers a specific IaaS resource. Some of these are: Compute (Nova), Object Storage (Swift), Block Storage (Cinder), Networking (Neutron), Orchestration (Heat), and Database (Trove). Some key companies who use OpenStack internally include Intel, Argonne National Laboratory, CERN, and NeCTAR. 2) vCloud vCloud Suite is a private cloud technology platform from VMware. Customers use the vCloud Suite to implement a private cloud computing IaaS type environment. The vCloud Suite consists of several core products: vSphere, vCenter Site Recovery Manager, vCloud Network and Security, Automation Center, Operations Management Suite, and vCloud Director. Together, these key VMware products enable a cloud-based virtual data center. IT organizations can deliver cloud services to their internal business units with the same scalability and pay-as-go-go capabilities that public cloud providers deliver. The vCloud Suite is available in three configurations: Standard, Advanced, and Enterprise. Key customers of vCloud include: Columbia Sportswear, Catholic Health Initiatives, and Microstrategy.
- "The cloud infrastructure is provisioned for exclusive use by a specific community of consumers from organizations that have shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be owned, managed, and operated by one or more of the organizations in the community, a third party, or some combination of them, and it may exist on or off premises.“ This deployment is effective for consortium groups and special interest user groups. Generally, security and data access between members of a consortium or user group is permitted. However, outside of the consortium or user group, access is restricted.
- "The cloud infrastructure is a composition of two or more distinct cloud infrastructures (private, community, or public) that remain unique entities, but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load balancing between clouds)." There are several use cases or cloud configurations that employ a hybrid cloud deployment model. One is cloud bursting, which means going from private cloud to public cloud. Another is backup and disaster recovery, also going from private cloud to public cloud.
- I hate to use the word “cons”, because it has a negative connotation, but there are many things to consider when you look at embracing the cloud computing model.
- Your providers limitations ultimately limit your business capabilities and/or objectives. Extreme Outages – A cloud provider faces the same business risk as your company (in a more competitive landscape). Bankruptcy, loss of facility, or litigation are just a small list of ways you can lose access to your data for a long period of time. Denial of Service attacks against one customer can affect others. For example, when Amazon services a node in EC2, there is no vmotion. If they shut down a node that you have an instance running on, your instance is going to reboot. This can happen at any time, so you'll need to plan on clustering things that require exceptional uptime You should also be prepared to deal with AZ (single datacenter) failures, or the occasional region failure depending on availability concerns. If you have services are that depend on shared storage, you're rolling it yourself (until EFS gets released anyhow.) - and you have to plan for possible failure of that share at any time
- Pets vs. Chickens is one popular way to describe it. If your oracle server in your data center goes down you try to fix it. This is your pet, you're taking it to the vet. If you are a chicken farmer and a chicken get's sick you don't take it to the vet, you isolate it so it won't make your other chickens sick then you get rid of it. Cloud Native / Cloud Aware / 12factor (pick a term, there are others) applications are made up of microservices. Microservices are the chickens, if they get sick you get rid of the box/container and spin up a new one and let your orchestration / configuration management do the work.
- The cloud is here to stay, at the very least, in order to stay competitive, organizations are going to have to be open to embracing the cloud computing model and looking at opportunities to augment their on-premises solutions with cloud.
- So let’s look at what is working with our customers.
- Mention that you often need something to facilitate, or automate, archiving.
- Many traditional software companies are turning their attention to SaaS.
- So what does Eagle have to say about all of this?
- One of the best things the cloud has done to traditional IT shops is that it has created competition (don't forget that on-prem infrastructure and local hardware has a lot of competitive advantages). “We see folks moving to cloud when they are in crisis in their own datacenter.”
- Shadow IT: If you fail to extend your mobility (often done by embracing certain cloud solutions) you run the risk of having your employees find their own ways to become more mobile and collaborative.
- Shadow IT: If you fail to extend your mobility (often done by embracing certain cloud solutions) you run the risk of having your employees find their own ways to become more mobile and collaborative.
- One of the best things the cloud has done to traditional IT shops is that it has created competition (don't forget that on-prem infrastructure and local hardware has a lot of competitive advantages too). Use a managed service provider mentality and have your own private cloud Remember that IT management issues don’t go away with cloud solutions How you add value in IT has changed… it’s no longer just keeping the lights on. If you need help determining what fits, well… that is what we do.
- So, in closing, at Eagle we have a cradle-to-grave mentality with our productions and solutions. We size it, we sell it, implement it, and then we stick around to support it. We work hard to be experts and stay up-to-date on all things related to data and information management, and we’d love the opportunity to earn your business.
- Let me know if you want a copy of the presentation!