Leverage Cloud Computing to Accelerate Development and Test
•Download as PPTX, PDF•
0 likes•355 views
RightScale Webinar: November 18, 2010 – Watch this webinar to learn more about how you can leverage cloud computing to simplify and accelerate your DB2 development and testing. This DB2 Chat with the Lab is brought to you in collaboration between IBM and RightScale.
Recommended
Recommended
More Related Content
What's hot
What's hot (18)
Similar to Leverage Cloud Computing to Accelerate Development and Test
Similar to Leverage Cloud Computing to Accelerate Development and Test (20)
More from RightScale
More from RightScale (20)
Recently uploaded
Recently uploaded (20)
Leverage Cloud Computing to Accelerate Development and Test
- 1. Leverage Cloud Computing to Accelerate Development and Test In Collaboration between IBM and RightScale.
- 2. 1 > Executive’s Message Sal Vella Vice President, Development, Distributed Data Servers and Data Warehousing IBM
- 3. 2 > Featured Speakers Leon Katsnelson - @katsnelson Program Director, IM Cloud Computing and Emerging Technologies IBM Uri Budnik - @uribudnik Director, ISV Partner Program RightScale 2
- 4. What is Cloud Computing Cloud computing is both a user experience and a business model. It is an emerging style of computing in which applications, data and IT resources are provided to users as services delivered over the network. It enables self-service, economies of scale and flexible sourcing options. It is hottest topic in IT and top of mind for IT executives
- 5. “Cloud Computing- By 2016, all Global 2000 companies will use public cloud services. Cloud computing represents a shift in the relationship between the providers and consumers of IT-based solutions. It constitutes the basis of a discontinuity that amounts to a new opportunity to shape the relationship between those who use IT services and those who sell them. Gartner said worldwide cloud services revenue (including public and private services) is forecast to reach $148.8 billion in 2014.” Source: Gartner Press Release http://www.gartner.com/it/page.jsp?id=1465614 Gartner Identifies Seven Major Projects CIOs Should Consider During the Next Three Years 4
- 6. Cloud: Growing 7X faster than traditional IT 5 Cloud spending = CAGR of 22% through 2015 Traditional IT spending = CAGR of >4% Cloud spending = >9% of total IT spend by 2015 Cloud growth rate = 7X that of traditional IT spending Spending on apps, app dev./deploy, SW, storage, servers Source: IBM estimates, April 19, 2010; QMV2Q10 & IDC March 2010
- 8. Running them longerDB2 paid usage on Amazon EC2 up 800% in the last 12 months
- 10. DB2 Templates on RightScale.com
- 11. Dev & Test Solution Pack on RightScale
- 12. Industry AMIs (include DB2)
- 15. DB2 Templates on RightScale.com
- 17. Database as a Service (DBaaS)Enterprise Users Enterprise Enterprise data center Enterprise data center A B A B Managed private cloud Hosted private cloud Member cloud services Public cloud services Private cloud Third-partyoperated Third-party hosted and operated 7
- 18. Development and Test – Idealized Workload for the cloud Choose to maximize ROI and minimize risk 8
- 20. Lead time for procuring and provisioning equipment
- 21. Maintaining consistent environments throughout the lifecycle
- 22. Maintaining multiple environments in parallel
- 24. “test environment infrastructure” … is a relatively low-risk workload in terms of the business and the overall IT operation. In addition, this workload has the potential for large ROI through gains in speed and cost reduction. Therefore, IBM recommends that test environment infrastructure workloads should be considered a strong candidate for a pilot cloud project in either (private or public) delivery model. Source: IBM Smart Business Thought Leadership White Paper Dispelling the vapor around cloud computing Development and Test Environments: Top workload for Cloud 11
- 25. “Loosely Coupled” Architecture “Content-Centric” Architecture “DB-Centric” Architecture Storage and Data Integration Arch. Idealized Workloads Higher Gain from External Clouds Collaboration Web2.0 Dep’t. BI On-Line Storage Application Test Data Archive SMB ERP Web Scale Analytics [Enterprise Data] Situational Apps DB Migration Projects Lower Pain to Cloud Delivery Higher Pain to Cloud Delivery Transactional Content Application Development Large Enterprise ERP Lower Gain from External Clouds Our general findings are some workloads are better suited for cloud than other workloads
- 26. Development and Test Environments: Perfect for Cloud Quick ROI: 30% to 50% of all servers within a typical IT environment are dedicated to test Most test servers run at less than 10% utilization, if they are running at all! Low risk: Low risk in terms of business and overall IT operations Security/compliance concerns easily mitigated Excellent return on automation Agility Consistent dev and test environments mean fewer errors Self-service 13
- 27. DB2 Development and Test on the CLOUD Making it more real … 14
- 30. DB2, Informix
- 31. WebSphere
- 32. Rational
- 34. OS:
- 35. Novell SuSe Linux Enterprise Server 11
- 36. RedHatEnterprise Linux 5.4IBM Development and Test Cloud Developer, Tester Developer, Tester
- 38. All access to the system via secure VPN
- 39. All servers on a private VLANAdmin Developer, Tester Secure Development and Test Environment Developer, Tester Developer, Tester
- 40. Getting started with Dev and Test on the IBM Cloud 17 http://www.ibm.com/services/us/igs/cloud-development/
- 42. Hypervisor: VMWare, XENor KVM
- 45. 3rd party templates/scriptsAdmin Self-provisioning
- 47. Hypervisor: VMWare, XENor KVM
- 51. Demo Creating Development and Test Ecosystem
- 52. .NET, PHP, Python, Ruby on Rails … Drivers developed and supported by IBM. Support popular languages/frameworks Free tools for developer productivity to build application and database code Http Http .NET Python Rails DB2 DB2 Eclipse-based tools DB2 is not just for Java MS Visual Studio Add-ins for DB2 PHP
- 54. Why RightScale Empower developers and testers with self-service provisioning While maintaining complete control Eliminate errors due to misconfigured environments Agile deployments that embody best practices 24
- 55. DB2 Early Experience Program IBM leveraging the cloud to address our own challenges
- 57. as little as $0.34/hour
- 60. 28
- 61. Getting started has never been easier Development and Test is low risk high ROI activity – perfect fit for the cloud The easiest and the least expensive way to get started is on the public cloud: Set up an account on IBM Dev and Test Cloud: http://www.ibm.com/services/us/igs/cloud-development/ Engage in the DB2 Early Experience Program on the cloud: http://freedb2.com/db2-early-experience-program-on-the-cloud/ Open free Amazon EC2 & RightScale.com accounts and take advantage of pre-built DB2 templates: 29
- 62. 30 > Questions 30
- 63. 31 Thank You! ibm.com/db2/labchats Thank you for attending! 31
Editor's Notes
- Cloud Computing is often described as new and emerging technology. Truth be told, Cloud Computing is not about technology at all. It is first and foremost a business model and a user experience. Cloud computing user experience delivers self-service that lightens the load on the IT personnel while providing line of business users with capabilities they need. It delivers IT resources as a service rather than a collection of hardware components.
- While the analysts are unanimous in their predictions of the bright future for cloud computing, it is always best to gauge this enthusiasm against real life experiences. This graph depicts real usage growth as reported by our partner RightScale.com. They saw a 1000% increase in usage. We also observed similar accelerated usage of DB2 on the Amazon EC2 cloud. During the period of July 2009 to July 2010 we observed 800% increase in the paid usage of DB2 on the Amazon EC2 cloud.
- Here are some specific dev and test challenges we’ve heard from our prospects and customers – and they were surprisingly consistent across industry and co size. Rarely are there enough resources available for experimentation and testing, and equipment is shared and must be configured and re-configured each time a new project or task starts. In many companies it takes as long as 3-5 weeks to procure and provision new equipment, so development organizations must plan ahead or risk delaying projects. Maintaining consistent environments is another persistent challenge. As code moves through development, test, staging and production, configuration changes rarely make it back into earlier stages. If software is to be run in multiple production environments, then each environment needs to be configured and tested. And to troubleshoot problems found in production requires reproducing past environments – easier said than done. Whether the task falls to development, QA or operations, maintaining and reproducing environments is time-consuming and error-prone. Finally, distributed teams just exacerbate the other challenges. Limited resources – In almost every phase, limited hardware poses problems. In architecting new systems there are rarely enough resources to experiment with alternative architectures or new technologies. For developers, limited resources usually means sharing hardware for testing. Testers rarely have enough hardware or time to do all the testing they would like to do - full performance and load testing, testing on complete production architectures, or testing disaster recovery scenarios. And, delays in development often puts pressure on testers to do their work faster to still reach the same deadline. The inability to spin-up additional testing resources at these times causes quality to suffer. The result is that errors are found later in the cycle where they are more expensive to fix. Limited equipment also means staff are constantly provisioning, tearing down, and re-provisioning the same equipment. It takes time, and if environments are not completely wiped clean, additional errors are potentially introduced. Time to procure and provision equipment - As the load on IT departments increases and the release cycles shorten, the wait for equipment to be procured and provisioned takes time away from valuable work. One customer stated it took 3-5 weeks to procure and provision new hardware. Maintaining consistent environments – As code moves through development, test, staging and production, changes to configurations in one stage rarely make it back into earlier stages. As new code is implemented from environments that haven’t been updated, the same errors are re-introduced. Maintaining multiple environments – As if maintaining one consistent environment across many servers isn’t hard enough, most software requires testing on several different types of configurations – different versions of stacks, for different end user environments – one for each possible production scenario. For example, a software company may need to test their software on different operating systems or alongside various software packages. Most companies need to clone production environments to debug problems without impacting the current users.Whether it happens in development or QA - maintaining & reproducing environments is a time consuming task. If the task is distributed across multiple administrators, the coordination of changes made becomes challenging. If the task is consolidated under one administrator, there is a limit to the number of different environments s/he can reliably maintain.Distributed teams or team members – add collaboration requirements and exacerbate all of the issues mentioned.
- There are several usecases for leveraging cloud computing for development and test. We see using the cloud for build and test for applications destined for n-premises deployment as the most popular such usecase.
- We leverage the cloud to reduce your time and effort required to evaluate the early code for the DB2 Galileo. By using the early experience program on the cloud, you avoid the time and effort required to get the hardware, install and patch the OS, install and configure DB2. Most important, you will not have to update or refresh the code every time we deliver a new build (about once a month). You will always be running the latest stable code and will not be dealing with issues that may have already been addressed.