Downloaded 48 times
Uploaded byChristian Buckley
Baby-Stepping Into the Cloud with Hybrid Workloads
This document discusses options for moving workloads between on-premises and cloud environments. It notes that while migrations can be slow, Microsoft has options to help with the transition. Different models like private cloud, hybrid cloud, and public cloud are outlined, along with considerations for each approach. Key factors that can influence the choice of cloud options include an organization's size, regulatory requirements, collaboration needs, and service level agreements. Testing is advised to determine the best approach for individual workloads.
More Related Content
Similar to Baby-Stepping Into the Cloud with Hybrid Workloads
Baby-Stepping Into the Cloud with Hybrid Workloads
- 1.
- 2. Christian Buckley ManagingDirector, Americas cbuck@gtconsult.com www.buckleyplanet.com @buckleyplanet
- 3.
- 4.
- 6. SharePoint Growth &Evolution SharePoint Releases Metadata Content
- 7.
- 8. Organizing for theCloud
- 9. • • • •
- 11. • • • • •
- 12. A recent surveyby UBS AG of 101 CIOs in the U.S. and Europe found that more than half would move some workloads to a public cloud, but it would be a gradual process, while a third of respondents said they were moving to a public cloud as quickly as possible. (Wall Street Journal, July 16, 2014)
- 14. Is there riskin moving my data to the cloud?
- 15. of workers usedan unsanctioned cloud service for document storage in the last 6 months 41% 87% $1.8 of these workers knew their company had policies forbidding such practices (billion) estimated annual cost to remedy the data loss New Mobile Survey Reveals 41% of Employees Are Deliberately Leaking Confidential Data http://onforb.es/18h92Nv
- 16. According to IDC: • 74% expect their cloud service to be able to move a cloud offering back on-premise if needed. • 63% expect to have a single major cloud service provider. • 67% expect to purchase a wide variety of services from a single vendor. • 84% want an established relationship with a vendor to trust them as a cloud service provider.
- 18. Of course, migrationscould be faster
- 19. While migrations canbe slow, Microsoft has options
- 20. • • • • •
- 24.
- 25.
- 26.
- 27. On Premises Cloud AD Azure AD
- 28.
- 29.
- 30.
- 31. • • • • • • • •
- 33. Partner Hosted Private Cloud • Dedicated environment • Externally hosted • Externally or internally managed • Internally designed Self Hosted Private Cloud • Dedicated environment • Internally hosted • Internally managed • Internally designed Shared or Dedicated Public Cloud • Shard or dedicated environment • Externally hosted • Externally managed • Externally designed Dedicated Public Cloud • Partially or fully dedicated • Externally hosted • Externally or internally managed • Minimal customization http://social.technet.microsoft.com/wiki/contents/articles/4633.what-is-infrastructure-as-a-service.aspx Traditional on premises
- 34. Private Cloud HybridCloud Infrastructure maintained solely for customer On premises or off Managed by the customer, or by a 3rd party hoster Multiple infrastructure options Components both on premises and off premises Management spread between customer and 3rd party hosters Public Cloud Infrastructure shared by multiple customers Off premises Managed by 3rd party on behalf of customers
- 35. • Standardized (packaged)platform • Provided with Service Level Agreements (SLAs) • Minimal customization • Both software and hardware infrastructure provided within the service
- 36. • Architectural anddevelopment access to application services, storage, and application runtime • Infrastructure Service Level Agreements (SLAs), but work must be conducted within agreed framework • Some customizations allowed, within framework • Both software and hardware infrastructure provided within the service
- 37. • Virtualized hardwareand software, including servers, storage, and network infrastructure • All components delivered as metered services (pay per use) • Complete application control and customization
- 39. • Testing isessential to understanding which workloads should move forward. • Size and geographical distribution of an organization can affect cloud adoption. • Regulatory compliance and governance requirements can limit cloud options. • External collaboration may require on prem farms. • Service-level agreements (SLAs) may limit cloud options. • Enables customers to use preferred features from SharePoint 2013 on prem and SharePoint Online. • It is important to understand the ROI of any proposed solution (and the cost of change). • Hybrid may be more of a transitional environment from on prem to the cloud. http://www.sharepointnutsandbolts.com/2014/02/office-365-sharepoint-hybrid-what-you-do-and-do-not-get.html
- 41. Location / facilities On Premises Cloud Hybrid Need space and maintenance planning Most likely provided Software licenses and support Licensing costs, but also upgrades and ongoing support Included in vendor-hosted solutions Hardware and maintenance Need to purchase, support and maintain, and upgrade as platform matures Included in vendor-hosted solutions Onsite support, personnel skills Administrative, developer, and end user skills and training Still requires administrative and possibly dev skills, end user training Need space and maintenance planning Licensing costs, but also upgrades and ongoing support Need to purchase, support and maintain, and upgrade as platform matures Administrative, developer, and end user skills and training
- 42. Level of OnPremises Cloud Hybrid customization Full control Limited to none in SaaS, some control over PaaS, full control over IaaS Limited ability to integrate depending on SaaS, PaaS, or IaaS Governance, auditing, security, compliance Many limitations OTB, but very robust tools from partners Limited Very complex across on prem and cloud components, very manual Disaster Recovery and Business Continuity Needs to be planned, limited features OTB Defined in SLAs Upgrades and migration Some OTB capabilities, 3rd party for tighter control and predictability Microsoft recommends 3rd party tools Very complex across on prem and cloud components, very manual Some OTB capabilities, 3rd party for tighter control and predictability
- 43.
- 44.
- 45.
- 47. http://bit.ly/1sr15P8 http://bit.ly/1h4EL99 http://slidesha.re/1AiLkgF http://bit.ly/1pvKo4Z http://bit.ly/1t1fnVX http://bit.ly/1oNAK8O http://bit.ly/1kFAwFB http://bit.ly/1ecuEdw http://bit.ly/1AiLqF3 http://bit.ly/XmqBIc http://onforb.es/18h92Nv http://bit.ly/1f26hFm http://bit.ly/1bxabDQ
- 48. Thank you! cbuck@gtconsult.com www.buckleyplanet.com @buckleyplanet
Editor's Notes
- #4 Everything SharePoint Internal products in Umlindi, Umlindi 365 and A-Team
- #5 Discuss E2open background, early forays into cloud infrastructure and what we learned about building SaaS offerings. Electronic Data Interchange (EDI) E-commerce Telecom advances SOAP and XML Service-Oriented Architecture Web Services Virtualization Inexpensive hardware
- #6 Screen shots of OneDrive, Delve, Groups, Yammer Talk about how we connect today Give some examples of team collab
- #15 The real risk is not recognizing that your end users are already putting corporate data in the cloud. Use the puppy analogy. Its all about redirect, but in a more secure, controlled way.
- #16 You can try it, and if you don’t like it, revert back
- #20 The real risk is not recognizing that your end users are already putting corporate data in the cloud. Use the puppy analogy. Its all about redirect, but in a more secure, controlled way.
- #34 Decisions need to be made about build or buy, out source or keep in house
- #36 Customer receives a completed application and functionality with agreed upon SLAs, system uptime, and quality of service (performance). The downside is that there is minimal ability to customize, and new features/updates/changes are driven by market demand or the capabilities of the provider. How do Cloud services differ from traditional managed services? The primary difference is that you say goodbye to the major platform upgrades every 3 or 4 years, and move toward more of an iterative update. As cloud-based service providers, their revenue model changes dramatically as customers move from a high-cost, project-based model to a recurring revenue model.
- #37 An environment that provides great application-level control over the SharePoint environment, including access to cloud storage and other services. However, this greater level of application control shifts support/ownership of the application (SharePoint) to the customer.
- #38 Delivered as virtual environments and cloud storage. Customer is responsible for the entire platform and applications. Generally used by ISVs, SIs, and customers with very complex, unique development requirements.
- #41 These factors will help you decided how much your own organization can support, as well as help you determine the suitability of vendors
- #42 Point out that in this example, cloud = Office365