Cloud onboarding and Application Onboarding on AURO Canadian Cloud Computing
•
3 j'aime•681 vues
Discussion on the current state of the Canadian Cloud and best practices to onboard your application workload onto AURO's Canadian Cloud Computing platform.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (14)
Similaire à Cloud onboarding and Application Onboarding on AURO Canadian Cloud Computing
Similaire à Cloud onboarding and Application Onboarding on AURO Canadian Cloud Computing (20)
Plus de Matthew McKinney
Plus de Matthew McKinney (7)
Dernier
Dernier (20)
Cloud onboarding and Application Onboarding on AURO Canadian Cloud Computing
- 1. Cloud Onboarding in Canada Matt McKinney Chief Strategy Officer, AURO Enterprise Cloud @AURO_io ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential.
- 2. State of the Canadian Cloud? ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential.
- 3. Canadian cloud continues to lag with adoption… more than 10% behind the US. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential.
- 4. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. Canada is ranked 9th out of 24 countries for cloud.
- 5. As many as 65% of executives do not feel secure sharing business data with cloud providers. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. As many as 45% feel their company’s information would be unsafe in the cloud.
- 6. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. 43% of businesses think cloud is for large enterprises.
- 7. 4 in 10 small companies said they do not know what cloud can do for them. 1/3 of small business executives admit to “not having a clue” what cloud computing really is. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential.
- 8. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential.
- 9. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. Why does Cloud matter?
- 10. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. Scalability Reduced Capital Expenses Reduced Infrastructure Improved Access Reduced Headcount Minimal Licensing Increased Flexibility
- 11. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. The Workload
- 12. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. Barriers to moving workloads?
- 13. 15% = Apathy/Laziness ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential.
- 14. 44% = Lack of understanding ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential.
- 15. 71% = Control ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential.
- 16. 65% = Policy ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential.
- 17. 34% = Location ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential.
- 18. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. Why does onboarding matter?
- 19. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. To benefit from the cloud, you have to get there first. Unfortunately, most companies don’t make that easy.
- 20. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. Hundreds of companies provide cloud onboarding services. Why’s that?
- 21. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. Example: “In this service, we take a collaborative approach to facilitate the customer’s adoption of our enterprise cloud platform. Additionally, we help the customer empower their internal staff with new skills and the confidence to realize the benefits of our cloud services.”
- 22. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. What does onboarding mean?
- 23. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. Onboarding refers to the deployment of applications and/or data to Cloud infrastructure like AURO (public, private or hybrid).
- 24. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. Successful onboarding is all about prior planning and preparation.
- 25. Cloud is the new reality. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential.
- 26. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. Source: KPCB estimates – based on publicly disclosed company data. 4 trillion gigabytes of data has been stored in 2015… So far.
- 27. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. The Cloud:
- 28. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. Are you cloudy?
- 29. Test and development ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential.
- 30. Collaboration & web applications ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential.
- 31. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. Most companies are not prepared.
- 32. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. Most applications are designed to run on a single server, end-user machine, or on a cluster of front-end and application server nodes backed by a database.
- 33. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. They are running on infrastructure designed for reliability, so hardware failure is taken to be an unlikely exception that requires special backup and disaster recovery procedures.
- 34. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. This is quite different from a cloud environment that has built-in redundancies, and multi-site failover capabilities where the infrastructure design includes ‘expected’ failures and respond to it by switching resources seamlessly.
- 35. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. How hard is it?
- 36. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. Might be a surprise, but Cloud is not a magic formula .
- 37. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. There are lots of reasons to move!
- 38. Existing web hosting is located on servers owned by the company. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. They either wish to relocate these servers to a different location (where the existing IP address space cannot be used)… Or they wish to have a third party take over provision of web hosting services.
- 39. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. The existing web hosting service is either in-house or provided by a third party that is no longer suitable. This could be due to: • Level of service is not acceptable • The requirements of the client have outgrown the capabilities or scale at which the existing provider operates at • Commercial reasons such as pricing are dictating the need to move • The existing service is currently located offshore and there is a desire to make it local • The client wishes to have a greater level of control over the hosting, i.e. currently outsourced and wish to bring in-house
- 40. Your needs dictate your next steps. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential.
- 41. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. The original hosting arrangements will define the options which exist for migration: • Websites are hosted under a reseller plan or some form of shared hosting in which the client does not have control of the server and root access cannot be provided. Websites may or may not all be hosted in the same place or with the same company. • Websites are hosted on a server (either in an office or a datacentre) that is dedicated to the client and which they have full access to and control over.
- 42. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. The Application Workload
- 43. Challenges with application workloads? ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential.
- 44. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. When you're migrating an application to a cloud environment, some of the described elements may not need to be migrated with the application. • If you are moving away from a legacy IT environment, some of the previously used services may no longer be required. • As an example, it's common for some of our enterprise customers to maintain their Active Directory domain controllers in-house, while some of the applications it controls may reside in AURO’s cloud computing environment. • Enterprise applications usually interact with one another. • Cross Platform interactions
- 45. Application onboarding: The Basics ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential.
- 46. Deploying the workload ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential.
- 47. Workload Analysis ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential.
- 48. Ensuring seamless two-way access ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential.
- 49. Testing and validating ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential.
- 50. Getting your application cloud-ready ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential.
- 51. Discontinue the old service ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential.
- 52. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. Things to consider: Because workloads differ in terms of their importance and cost to your business, choosing a workload that is both critical and complex to migrate can be a big risk, but the potential cost savings or other benefits may outweigh the risk. Work to identify and prioritize the best candidate workloads for migration including business and technical factors.
- 53. ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential. Partner Up! Why picking a cloud partner can be your best step forward: • Migration • Application Architecture • Network Architecture • Ease Of Use • Commercials and Billing • Performance Guarantees • Security • Business Continuity • Governance • Support The Quiet Revolution Has Already Begun
- 54. Thank you! Matt McKinney Chief Strategy Officer, AURO Enterprise Cloud @AURO_io mattm@auro.io ©2015 AURO Enterprise Cloud. All rights reserved. Proprietary & Confidential.
Notes de l'éditeur
- Matt McKinney of AURO Cloud Canadian Cloud Computing Provider based in Vancouver, BC with a newly released national network of compute regions for Canadians and customers world wide. Today, I’m here to talk about cloud. Or more precisely cloud in Canada including Cloud Adoption and Cloud Onboarding. So, is Cloud in Canada thriving?
- Equates to lack of understanding and education. Many of these obstacles should be covered or mitigated during any good onboarding process.
- Equates to lack of understanding and education. Many of these obstacles should be covered or mitigated during any good onboarding process.
- Equates to lack of understanding and education. Many of these obstacles should be covered or mitigated during any good onboarding process.
- Obvious benefits that most providers advertise and present on websites.
- Obvious benefits that most providers advertise and present on websites.
- Who knows what their workload consists of?
- Who knows what their workload consists of?
- No plans or haven’t got around to it
- Costs are lower in house, complexity
- Loss of control, on premise, vendor may not survive
- Policy, regulations
- Lack of Understanding = Costs: Opportunity to streamline processes, remove expensive capital expenditures, revisit operations Cloud is viewed by most businesses as a large and potentially costly mystery. In house expertise is around supporting existing workloads and infrastructure Service Levels and downtime Finding new solutions can be time consuming and expensive
- Obvious benefits that most providers advertise and present on websites.
- Google/Bing: does cloud onboarding matter
- Most companies advertise “Cloud Onboarding” but don’t specify what that means?
- Companies like Centurylink, Rackspace, Oracle, Verizon, Microsoft, IBM
- If everything has been properly prepared beforehand, there’s no reason why it shouldn't.
- If you do it right – It’s not that hard! Many companies do recognize the need to move to the cloud or begin leverage what the cloud has to offer. Many find the transition to be one of the single biggest hurdles. Example. One of the things that we have seen is that customers are looking to simplify the onboarding process including moving between workloads. As a business/user, when considering integration, companies need to avoid treating cloud operations and cloud services as a separate entity or risk creating another silo devoid of analytics Compatability, secure (intel TXT) Focus on migration paths that move or 'forklift' applications (or virtual machines and the applications that run on them) into AURO’s private cloud or public cloud environment, without the need for major refactoring or rebuilding. With any decision, it is critical for your IT decision-makers to understand the process and to ensure that any move is both beneficial to your business and to end users.
- Hybrid is showing up as the most dominant form of cloud over the previous 12 months. Example: hybrid cloud but t here are many variations that can work for different companies. Hybrid cloud environments, by definition, is the integration of two or more different cloud environments – this is emerging as one of the dominant model for enterprises. To name a few reasons: Cloud bursting (on-demand extension of the data centre to a cloud environment based on pre-defined policies and monitoring of loads, quality of service, and so on) is a way for enterprises to explore and trial cloud services when they have concerns about the security, stability or performance of the cloud environment. Avoidance of long-term investment in unused capacity to handle demand spikes. It's an attractive solution for enterprises facing periods of system overload and not wanting to over-provision their infrastructure. Migrating an executing workload from one environment to another, based on resource use and performance.
- Many startups today are building their businesses in the cloud. Consumption for new services are more focused on cloud. New users are focused on cloud first, disregard for the stack but focused on the “app”. For enterprise, cloud can be: Test and development: because applications under development are relatively 'stand-alone' in terms of the level of interaction with other applications and services. Collaboration and web applications: because their native architecture is already compatible with running on multiple computing and storage nodes.
- It's hardly surprising that most enterprises choose to start their forays into cloud computing with application workloads that minimize the complexity of onboarding. Examples include: Test and development Collaboration and web applications (ties in directly with popularity of private clouds)
- It's hardly surprising that most enterprises choose to start their forays into cloud computing with application workloads that minimize the complexity of onboarding. Examples include: Test and development Collaboration and web applications (ties in directly with popularity of private clouds)
- For most enterprise applications, there's more work to do in preparing them for a cloud environment because they're not natively designed for it.
- For most enterprise applications, there's more work to do in preparing them for a cloud environment because they're not natively designed for it.
- For most enterprise applications, there's more work to do in preparing them for a cloud environment because they're not natively designed for it.
- For most enterprise applications, there's more work to do in preparing them for a cloud environment because they're not natively designed for it.
- For expediency, I did not include any articles but basically what we are hearing the same thing now…that we heard in 2010. A 2014 survey of Canadian businesses included the following:
- For expediency, I did not include any articles but basically what we are hearing the same thing now…that we heard in 2010. A 2014 survey of Canadian businesses included the following:
- For expediency, I did not include any articles but basically what we are hearing the same thing now…that we heard in 2010. A 2014 survey of Canadian businesses included the following:
- When talking about cloud migration or onboarding, it is common to talk about 'application workloads' rather than just 'applications'. This is because applications don’t typically operate in isolation, 'workload' concept captures the notion of all the work being done by a system when your application(s) is running. As an example, here is a common application setup running in the AURO Cloud: We’ve got customers today utilizing dedicated backend and cloud compute capacity and vice versa.
- Note: Cross-platform interactions are a big part of the complexity of enterprise application onboarding, even for workloads perceived as ‘cloudy’ or ‘cloud-friendly’. It's also one of the reasons that enterprises may look to start with private cloud deployments versus moving directly into a public cloud.
- So, where do we start 6 easy steps….its that easy. Go to visuals with specific points
- Ensuring seamless two-way access with appropriate candidate workloads for cloud migration and understanding their requirements for onboarding
- Discontinuing the old service as the application will perform as required on the target cloud architecture.
- Business impact: How business-critical is the workload? Where does the workload fit in the application lifecycle? What does that mean for its cloud environment requirements? Business requirements: Given the workload's business use, what are the implications for required service levels, transaction rates, response times, number of simultaneous users to be supported, or other relevant availability and performance-related measures? What supporting service requirements does the workload require (e.g., in terms of backup, disaster recovery, monitoring) and what are the implications for cloud deployment? Are there any specific security and compliance requirements (e.g. encryption, isolation, data sovereignty) and what does that mean for cloud deployment? Application architecture: Is the application architecture cloud-friendly in any way (e.g. is it horizontally scalable in the way that native cloud applications are, or only vertically scalable as traditional enterprise applications tend to be)? If not, what's involved in refactoring the application for a cloud environment? Are the time and costs acceptable when weighed against the benefits? Computing resources and dependencies: What OS, databases and application servers are being used and how hard are they to migrate to the cloud? What are the CPU, memory, network and storage requirements and what will it cost to provide these in AURO’s cloud environment? What other software supports the workload? What are the dependencies or integration touch points with other workloads? Operational and support requirements: How many hours/people are required to support the workload and what do they cost? What are the costs of licensing? What are the operational costs for space, power and cooling? For these and other operational and support costs: will anything be saved by migration to a cloud environment?
- AURO is fully compatible with AWS and Google compute with true behavioral fidelity and open APIs.
- Visit our booth!