Cloud computing migration issues
•Download as PPTX, PDF•
1 like•495 views
Alena Matokhina, Cloud Computing Solution Architect, EPAM Systems – Main issues during migration to cloud and process unification.
Recommended
More Related Content
What's hot
What's hot (20)
More from Olga Lavrentieva
More from Olga Lavrentieva (20)
Recently uploaded
Recently uploaded (20)
Cloud computing migration issues
- 1. Migration to Cloud Main issues and process unification
- 2. What is Cloud Computing? • On-demand self-service • Broad network access • Resource pooling • Rapid elasticity • Measured service Essential Characteristics from The NIST Definition
- 3. Effort from both sides • Cloud Computing Services provider • Project development and deployment
- 4. Multiple projects issues • Static environment configuration • Cache invalidation issue • Unmeasured performance • Untrusted security • Blame cloud?
Editor's Notes
- http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdfOn-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. 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). 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. 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. Measured service. Cloud systems automatically control and optimize resource use by leveraging a metering capability1 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.
- Let’s assume that you’ve selected a trusted CC service provider. Is it enough to meet the NIST definition of what Cloud Computing is?It’s not and it often has multiple reasons, because so many applications were not developed having CC architecture in mind
- Many customers don’t have a clear picture of the process. So they give a task to project manager: migrate to cloud.It’s modern hot topic, it doesn’t require any hardware maintenance thus it’s cheaper, and it’s scalable and pay-as-you-go etc.What many of them don’t understand is that developers should think cloud-wise while writing source-code.Performance tests should be able to provide statistics for further decisions on scaling policies.Security should be verified.It can be a real pain if the process of cloud migration is as simple as run some machines and send an army of maintenance engineers to configure them.Then just trust these cloud guys with all the High Availability and Scalability and if anything goes wrong in their cloud – blame the cloud.
- Having all the issues in mind we came up with process unification: you should start migration process with showing it to the customer to skip sudden failovers and making this hot topic a taboo and a nightmare he survived.First of all, you select a virtual hosting provider: consider your project specifics and costs and make your choice.As a part of CCCC in EPAM we go through this process with project team and get a knowledge of pros and cons of every service provider for every technology stack.Then we run environment and give IP-addresses of launched instances, SSH or RDP or any other access and credentials. And there you go, you have your machines “in the cloud”.We can move to step 3: deployment engineers setup everything they need and they are satisfied with the “cloudness” of their applications.Most of them just stop there and won’t move forward to get all the essential requirements of Cloud Computing term met.There still are 5 more steps I’d like to focus on.First of all machines configuration has to be fully automated. How do you plan to have Multi-platform, multi-technology oriented solution. EPAM projects contain multiple decisions, sometimes legacy, sometimes it’s optimal, other platforms are monogam.Azure Fabric Controller.AWS Elastic beanstalkHeroku