Cloud A Practitioner Prakat Solutions

Transcription

1 Demystifying the Cloud A Practitioner s Perspective Prakat Solutions

2 Contents Introductions Impacts of Cloud Adoption Other Side of the Cloud Key Business Drivers Testing, Continuous Integration and Production Monitoring Can you really measure Cloud Performance? Testing Planning, Test Development, Test Execution Test Development and Construction Test Execution Test Result Analysis and Reporting

3 Disclosures Many of the examples are based on real projects of our customers To keep the confidentiality we will NOT name any Customer or their Product Customer ABC is a leading global provider of Cloud based solutions for corporate legal teams for use in litigation and compliance Customer XYZ is a provider of a Cloud based solutions in the employee lifecycle management space

4 7 Blind Men Describing the Elephant Server Internet Network Storage Virtualization Distributed Remote Always On Pay as you go

5 Swiss Army Cloud It s different things for different people

6 Defining Cloud Computing

7 Cloud and DevOps Cloud is: Not a technology More than virtualization A fundamentally different way to write applications, provide services, run your business DevOps means engineering teams own: New deployments, upgrades Capacity planning, procurement

8 Cloud Behaviour 1. Demand: Typical pattern of customer requests rise & fall over time 2. Reaction: System automatically adds, removes servers to the application pool 3. Result: Overall utilization stays constant Demand # Servers Utilization

9 Psychology of the Cloud Moving to the cloud has been compared with death all that was physical and grounded is now in some amorphous cloud Our mind faces similar fears of the unknown which manifests as fears of the loss of identity, data, privacy etc. To the spiritual Business Leaders this is moksha freedom from all physical computing infrastructure. To the rest, the journey is tough and involves a lot of work

10 Psychology of the Cloud Freedom from the Physical Infrastructure is obviously fantastic but things which are often not considered are effects on our Architecture? effects on our Development? effects on our Test Planning? effects on our Test Environments? effects on our Test Execution? effects on our Test Reporting & Analytics? A lot of sadhana to get to the final goal

11 Traditional Testing Requirement Study Test Planning Test scenario identification Test Case / Script Writing Coverage Review Test Execution Environment Preparation Test Case / Automated suite execution Defect Reporting and Tracking Record defects Report Defect Non Functional Testing Performance Security/ Vulnerability Accessibility Testing

12 What are the differences in how we test on the Cloud vs traditional testing?

13 Cloud Testing Requirement Study Test Planning Test scenario identification Test Case / Script Writing Coverage Review Test Execution Environment Preparation Test Case / Automated suite execution Defect Reporting and Tracking Record defects Report Defect Non Functional Testing Performance Security/ Vulnerability Accessibility Testing

14 Many ways to Test in the Cloud Virtual Test Lab Test teams love the fact that they can now setup the test environment within minutes. The management loves the fact that they pay for only the time the servers are used if the test teams teardown the servers when the test round is complete. Testing as a Service Several companies have built test tools on the cloud SOASTA, Loadstorm, Browsermob Test and Throw Boxes If your testing messes up the configuration, just start again with a new instance

15 Many ways to Test in the Cloud Easy Repros Keep an image of the environment. No more battles between test and dev during reproducing bugs Web Services based Automation Setup your build system to setup 2 or 3 large instances for couple of hours. Run all your regression and unit tests and even simulate clients from different geos if required. All this automated and costs only a few dollars Testing in Parallel Tests of various kinds can be run in parallel instead of sequentially as we now have no hardware constraints.

16 Failures in the Cloud "Everything fails, all the time Werner Vogels, CTO, Amazon Continually prepare for failure in all the resources you manage This paradox is at the core of various tools that randomly disable or terminate production resources to test and ensure that automatic recovery mechanisms are a part of your infrastructure.

17 Have you used such a tool in your projects or are you aware of any such tools?

18 Chaos Monkey Tools like the Chaos Monkey apply monitoring, diagnostics, randomization, and disruption to the infrastructure to ensure that engineers apply automation to limit the impact users experience when big problems do occur.

19 Example: Chaos Monkey Tools Chaos Monkey AWS Cloudwatch Hyperic HQ Environment AWS Cloud Objectives Destabilize a working setup with a steady 10 user load with mix of transactions Measure performance unavailability and degradations if any Confirm that system can recover smoothly Reused testcases and scenarios from functional tests spanning from data entry to large background processing Test run lasted about 24 hours Targeted server instances and software instances Helped reset product expectations

20 Performance Test Challenges Test Environment needs to scale out, scale in, distribute across zones Cloud and Network specifics to be considered like IP addresses, security policies on firewalls, image moves etc. Elasticity of the cloud makes it difficult to exhaust the resources Test results are in huge volumes creating a challenge for reporting

21 Generating Cloud-scale Loads Distributed Load Injectors Centralized orchestration of transactions Multiple load injectors per VM and multiple VMs Consolidated statistics

22 Have you used such a tool in your projects or are you aware of any such tools?

23 The Grinder Tools like The Grinder provide a load testing framework that makes it easy to run a distributed test using many load injector machines. Other Tools: HP LoadRunner, Borland SilkPerformer

24 Example: The Grinder Tools The Grinder Ground Report Environment Vmware Cloud Objectives Exercise the deployed application with upto 2500 concurrent users sending a mix of transactions Measure performance degradations if any Confirm that system can scale up smoothly Confirm that system can scale down to base level within defined parameters Reused testcases and scenarios from functional tests Test run lasted about 2 hours Additionally 1 hour to scale down Close to 2 million log entries Reports available in 2 hrs but analytics???

25 Key Takeaway Test to validate the requirements and not to see where it breaks

26 Continuous Integration & Testing In a CI environment we monitor source repository for changes Builds are based on changes or time based Automated build and test is kicked off when a clean build is complete Exceptions reported and decision taken on Clean build

27 OUR CONTACTS facebook.com/prakatsolutions