The document outlines a presentation by Chris Riley from CloudShare, focusing on cloud-based development and testing strategies, particularly the importance of DevOps and application release automation. It discusses goals such as increasing release frequency and automating the release process, emphasizing the need for cultural shifts and integrated tools. Additionally, it provides an overview of CloudShare's services and resources available for trial and further learning.

1. CONFIDENTIAL
CODE, BUILD, TEST
IN THE CLOUD

2. CONFIDENTIAL|2
Agenda
 Who is Chris?
 The Goal
 Approaches
 A Demo
 Who is CloudShare?
 Resources & Questions
@CloudShare

3. CONFIDENTIAL|3
Presenting
@CloudShare
 Chris Riley
 Technology Evangelist
 @HoardingInfo
 @CloudShare
I represent you,
author things, and
talk a lot

4. CONFIDENTIAL|4
Words
 DevOps: A culture and philosophy
 ALM: Application lifecycle management,
automation up to release
 ARA: Application Release Automation,
last mile after release
 Environments: Infrastructure plus it’s
configuration and deployed code
@CloudShare

5. CONFIDENTIAL|5
The BIG Goal
 Increase the number of releases
 Months? Weeks? Days?
 HOURS!?
 Fully automate releases
 “Test in production”
 Fail Fast, Revert Fast
A.K.A Continuous Integration
@CloudShare

6. CONFIDENTIAL|6
But it requires
 A culture change
 Changes in the team
 More, and better integrated tools
 Has to be built bottom up – Uh ohs!
@CloudShare

7. CONFIDENTIAL|7
Types of Organizations
1. DevOps: Continuous Delivery
Champions. Release hourly.
2. ALM & ARA: Bi-Monthly, Bi-Weekly
releases with dedicated QA team and
release Managers. Release weekly.
3. Traditional Dev: Monthly releases with
full QA cycles and testing.
@CloudShare

8. CONFIDENTIAL|8
It’s not all about “maturity”
@CloudShare
DevOps
ALM & ARA
Traditional Dev
Web and
Mobile
High
Low
BigData,
Client/Server, etc.
ProductionEnvironmentComplexity
TypesofApplications

9. CONFIDENTIAL|9
How can you move up the
DevOps chain without killing
your application and team?
@CloudShare

10. CONFIDENTIAL|10
Step One:
IaaS
@CloudShare

11. CONFIDENTIAL|11
Components of Dev/Test
1. Code: IDE, limited in-cloud experience
2. Build: Source & Release Tools
3. Test: Manual & Automated Testing
4. Release to production – App Dependent
@CloudShare

12. CONFIDENTIAL|12
What you NEED in a Dev/Test Cloud
1. Environments: Not just VMs, complete multi-machine
environments with vLAN, Configuration, and Memory State.
2. Environment Snapshots: Versioning disks with snapshots is
easy, but developers need whole versioned configurations.
3. Cloning and Sharing: Developers need to be able to clone
identical environments in their exact network and memory
state. “I need 50 instances of this identical environment now”
4. Speed: Get a cloned environment in mins not days.
5. Programmable Infrastructure: An API that allows the creation,
the provisioning, the access, the sharing of VMs and whole
environments
6. Integrated tools: Integration with your IDE and Build tools.
@CloudShare

13. CONFIDENTIAL|13
Demo
@CloudShare

14. CONFIDENTIAL|14
What is CloudShare?
A Public Cloud Built Specifically
for Development & Testing
@CloudShare

15. CONFIDENTIAL|15
CloudShare Overview
 Founded in 2007
 Offices in Israel &
California
 Patented Environment
Creation Technology
 Thousands of
Environments created
per day
@CloudShare

16. ProPlus
TeamLabs
CloudShare
for Sales Demos
CloudShare
for Training

17. CONFIDENTIAL|17
Resources & Questions
 TeamLabs Trial: Email me
 ProPlus Trial: http://bit.ly/1dugbim
 Cloud Dev/Test Article: http://bit.ly/142aAvs
 TFS Video: http://bit.ly/14bmgH0
 Eclipse Video: http://bit.ly/17oJOue
 Full Team Labs Demo: http://bit.ly/18nBH01
 Cloud Testing Podcast: http://bit.ly/196ZuHY
 How Releases impact Marketing: http://bit.ly/187xq1U
@CloudShare
@HoardingInfo
Chris@CloudShare.com