AWS DevFarm: One Click Development Infrastructure

AWS DevFarm
One Click Development
Infrastructure
4-Nov-2015

US | UK | BENELUX | ME | IND©1996-2015 Aspire Systems, Inc.
Speakers
Janaki Jayachandran
Jothi Rengarajan
Cloud Solutions Architect,
Aspire Systems
Principal Architect – Cloud Solutions,
Aspire Systems
An ardent cloud enthusiast and a prolific speaker at NASSCOM &
Cloud Connect Events
15+ years of software development experience, he is instrumental in
driving Cloud and SaaS Centers of Excellence at Aspire
Enables Enterprises and ISVs to define their cloud strategy
14+ years of experience in architecting cloud and SaaS solutions
for both ISVs and Enterprises
Chief architect in designing and constructing TechCello framework
Plays consultative role with customers in implementing cloud
solutions

About Aspire
Global technology services firm with core DNA of software engineering
Specific areas of expertise around Software Engineering, Enterprise
Solutions, Testing and Infrastructure & Application Support
Vertical focus among Independent Software Vendors and Retail,
Distribution & Consumer Products
1400+ employees; 100+ active customers
ISO 9001:2008 and ISO 27001 : 2005 certified
Presence across US, UK, Benelux, Middle East and India
Recognized five consecutive times as “Best Place to Work for” by
GPW Institute

Housekeeping Instructions
• All phones are set to mute. If you have any questions, please type them in
the Chat window located beside the presentation panel.
• We have already received several questions from the registrants, which will
be answered by the speakers during the Q & A session.
• We will continue to collect more questions during the session as we receive
and will try to answer them during today’s session.
• In case if you do not receive answers to your question today, you will
certainly receive answers via email shortly.
• Thanks for your participation and enjoy the session!

Agenda
• Introduction to DevOps
• Overview of DevOps Tools offered by AWS
• Complexities introduced by agile practices
• DevFarm – working model
• Scenarios suitable for DevFarm
• DevFarm implementation architecture
• Security best practices in maintaining development environments on cloud
• DevFarm Cost benefits and TCO comparison between on-premise and Cloud
infrastructure

Introduction to DevOps
IT and Developers often lack common ground
D
e
v
e
l
o
p
e
r
s
I
T
Control
Visibility
Compliance
Agility
Productivity
Time to Market

DevOps Cycle

Overview of DevOps Tools Offered by AWS
• AMI
• AWS Cloud
Formation
Programmable
Infrastructure
• AWS Code Deploy
• AWS Code Pipeline
• AWS Code Commit
Continuous
Deployment
• AWS Elastic
Beanstalk
• AWS OpsWorks
Automation
• AWS Service Catalog
Self Service
• Identity and Access
Management
Access Control
• AWS Cloud Watch
• Cloud Trail
Governance

AWS – Programmable Infrastructure
November, 2014
• Digital template for EC2 Instances
• Contains Software configurations including OS
• AWS Published, Third party or Custom created
• Preloaded and Dynamic installation of applications
AMI
• Deploy collection of AWS resources
• Describe dependencies
• Modularization of templates
• Templates can be versioned and stored in repository
AWS Cloud Formation
Custom AMI
Third Party
AMI

Sample cloud formation

AWS – Continuous Deployment
November, 2014
• Managed source control service
• Seamless working with Git
• Enables faster development lifecycle
Code Commit
• Deploy applications across EC2 fleet
• Minimum downtime
• Centralized control
Code Deploy

Sample Appspec File

AWS – Code Pipeline
•Design your development workflow
•Integration of third party tools
•Automation of build, test and release process
Code Pipeline

Deployment Automation
•Automated Application Deployment
•Takes care of provisioning and configuration
•Multiple platform choices
•Automatic logging and notification
•Supports “Rolling Deployments"
AWS Elastic Beanstalk
•Application Life Cycle Management
•Define application as configurable stacks
•Application stacks are organized in to
architectural layers for ease of maintenance
•Simplifies Auto Scaling and Load Balancing
AWS OpsWorks

AWS Tools for DevOps

Self Service
•Standardized environments accessed by end users
•Support for multiple products and portfolios
•Integration with Cloud Formation for launching AWS resources
•One click deployment of “complete stack”
•Zero dependency with IT team
AWS Service Catalog

Access Control
• Access Control Service
• Support For SSO
• Support For MF
• Json Based Polciies
• Support for Groups
and Roles
IAM

Governance
• Real-time data of all AWS resources
• Configure Alarms to send Notifications
• Provision for custom metrics
• Integration with Analytics
AWS Cloud Watch
• Tracking of AWS API calls
• Used by operations team for support
• Security teams for governance
• Verification source for billing
AWS Cloud Trail

Cloud Trail

Cloud Watch

Complexities Introduced by Agile Practices
Faster Turnaround
More Dependencies
Increased Coordination
Multi Level Collaboration
Consistency across teams

Agile Needs
• The development environments (as a stack) should be available
on–demand at the disposal of developers
• Team should have self-servicing capability to create their
development environments without any intervention from IT
teams
• Each team should be able to make progress without any
dependency with other development teams
• Teams should be able to easily share/access common
environments, easing the collaboration efforts
• Templatized environments should be used across the teams for
ensuring consistency

DevOps – The Bigger Picture
• DevOps spans across Development (Build), Deployment and
Managing the environment
• The complexity of “Build” increases multi-fold with larger teams
and multiple products
• Each team or product may run as separate tracks, thus, making
the DevOps more complex to implement
• Each stack may contain multiple environments
• IT becomes a major bottleneck in these scenarios, as
provisioning and managing multiple team’s environment is a
nightmare
• Requires huge capex to setup this environment on-premise
• IT will still need to be involved for provisioning/deprovisioning

DevFarm – Working Model
November, 2014
Pre-Created Images
DevFarm Admin
Create
Environment
Team #1
Team #2
Team #n
Monitoring and
Image Management
Sets up the
images with the
baseline
software to be
used by all devs
Devs can launch the
environment at
their own will
Independent stacks
for each teamCompletely Automates the
environment setup as well as
app related configurations
Support team monitors
for resource usage,
cost and image
updates

AWS Service Catalog - Overview
Service
Catalog
Portfolio
Product
Versions
Stacks
IT Control
Developer
Control

Portfolio Creation

Product Creation – Step 1

Product View

Product – Additional Settings

Developer - Launching a New Stack

Service Catalog – Product Listing

Scenarios Suitable for DevFarm
• Companies that deal with multiple parallel releases within a single application. In this case,
each team can have it’s own dev environment without affecting other tracks.
Timeline
T1
T2
T3
T4
R1
R2
R3
R4
Application
Development
Testing
Teams
Releases
Scenario #1

• Leverage a task based approach for developers. Developers can handle multiple tasks
across different dev environments. This allows Companies to move away from “effort per
release” to “effort task per release”
T1
T2
T3
T4
App1
App2
Dev Env1
Dev Env2
Report Env
Tasks
Scenario #2

• Companies that deal with multiple applications release. Each teams can be working on
different dev environments. Workload of IT gets drastically reduced in these cases.
App Suite 1
App2
M
1
M
2
Dev Int
QA
1
QA
2
IM
IM
QA
QA Stg
Stg
Scenario #3

• In Support, where multiple older versions of the products have to be maintained.
Developers can fire up the version of dev environment to be worked, complete the work
(bug fix, etc.) and remove the environment. This approach tremendously increases the
productivity of support teams.
V2.0
V3.0
V4.0
V5.0
Application Versions
X
X
X
X
Scenario #4

• Cross team working – where you need the flexibility to have the developers work on
multiple projects. Instead of providing them 3-4 laptops/desktops – you can simply provide
them access to as many environments as required.
T1 T2 T3 T4
App1
Env
App2
Env
App3
Env
App4
Env
Scenario #5

DevFarm Architecture

TCO Analysis

TCO Analysis
3 Years Cost Breakdown
88% yearly savings
3 year total savings of $164,657

TCO Analysis
On-Premise AWS

TCO Comparison
$-
$50,000
$100,000
$150,000
$200,000
$250,000
$300,000
$350,000
$400,000
$450,000
25 50 75 100 150 200
$187,276
$220,969
$252,863
$286,557
$352,144
$446,306
$22,619
$45,033
$67,399
$89,765
$134,498
$179,231
$164,657
$175,936
$185,464
$196,792
$217,646
$267,075
Number of VMs
On-premise AWS Diff Cost
On-premise vs. AWS: 1vCPU, 4GB RAM, 100GB Storage

TCO Comparison
On-premise vs. AWS: 2vCPU, 8GB RAM, 100GB Storage
$-
$100,000
$200,000
$300,000
$400,000
$500,000
$600,000
$700,000
$800,000
25 50 75 100 150 200
$214,049
$274,517
$333,184
$420,426
$539,560
$760,077
$42,525
$84,749
$126,974
$169,198
$253,228
$321,242
$171,524
$189,768
$206,210
$251,228
$286,332
$438,835
Number of VMs
On-premise AWS Diff Cost

TCO Calculator by AWS
https://awstcocalculator.com

Contact Us
Web : http://www.aspiresys.com/
General Enquiry : info@aspiresys.com
janaki.jayachandran
@aspiresys.com
jothi.rengarajan@
aspiresys.com

AWS DevFarm: One Click Development Infrastructure

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to AWS DevFarm: One Click Development Infrastructure

Similar to AWS DevFarm: One Click Development Infrastructure (20)

More from Aspire Systems

More from Aspire Systems (20)

Recently uploaded

Recently uploaded (20)

AWS DevFarm: One Click Development Infrastructure