Dev/Test in the Cloud - A Business Case
17
CONFIDENTIAL CODE, BUILD, TEST IN THE CLOUD
-
Upload
chris-riley -
Category
Technology
-
view
529 -
download
1
description
How do you move your organization to the world of DevOps without killing the team and the product? The key is IaaS. Take baby steps moving your development process to the Cloud with infrastructure you control, and behaves how developers need. From webinar: http://www.youtube.com/watch?v=IIsV9dGygLE
Transcript of Dev/Test in the Cloud - A Business Case
CONFIDENTIAL
CODE, BUILD, TEST
IN THE CLOUD
CONFIDENTIAL|2
Agenda
Who is Chris?
The Goal
Approaches
A Demo
Who is CloudShare?
Resources & Questions
@CloudShare
CONFIDENTIAL|3
Presenting
@CloudShare
Chris Riley
Technology Evangelist
@HoardingInfo
@CloudShare
I represent you, author things, and talk a lot
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
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
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
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
CONFIDENTIAL|8
It’s not all about “maturity”
@CloudShare
DevOps
ALM & ARA
Traditional Dev
Web and Mobile
High
Low
BigData, Client/Server, etc.
Pro
duct
ion
Env
ironm
ent C
ompl
exity
Types of Applications
CONFIDENTIAL|9
How can you move up the DevOps chain without killing your application and team?
@CloudShare
CONFIDENTIAL|10
Step One:IaaS
@CloudShare
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
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
CONFIDENTIAL|13
Demo
@CloudShare
CONFIDENTIAL|14
What is CloudShare?
A Public Cloud Built Specifically for Development & Testing
@CloudShare
CONFIDENTIAL|15
CloudShare Overview
Founded in 2007
Offices in Israel & California
Patented Environment Creation Technology
Thousands of Environments created per day
@CloudShare
ProPlus
TeamLabs
CloudShare for Sales Demos
CloudShare for Training
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
