The document discusses how DevOps and cloud computing can enable faster application delivery. It notes that traditional software development involved long release cycles, while Agile development aims for more frequent releases. However, the gap between development and operations teams can slow releases. DevOps bridges this gap through practices like continuous integration, infrastructure as code, and automated testing in cloud environments. The document also describes how tools from BMC can help with planning, coordinating, automating and managing the full release lifecycle from development to production.

1. DevOps + Cloud = Faster
Application Delivery
Clyde Logue
© Copyright 11/12/2013 BMC Software, Inc
1

2. People’s expectations of IT have
changed
Overnight a gift
© Copyright 11/12/2013 BMC Software, Inc
Buy a latte
with your
phone
New
insurance in
minutes
Your data,
anywhere
2

3. Deliver Applications Faster –
Enabling Business
Overnight a gift
© Copyright 11/12/2013 BMC Software, Inc
Buy a latte
with your
phone
New
insurance in
minutes
Your data,
anywhere
3

4. Traditional Software Development Life Cycle
Linear Flow to Release
Some friction between SLDC and ITIL - but low cadence
“Life was simpler back then…”
Release
Event
SDLC
Business
© Copyright 11/12/2013 BMC Software, Inc
Development
ITIL
Operations
4

5. Low Release Cadence
Rare Release Events – Annual, Quarterly, Monthly
Effort Peaks, Higher Accumulated Change, Higher Risk
“Flood of change at release time…”
Release Event
Time
© Copyright 11/12/2013 BMC Software, Inc
5

6. Agile Release Cadence Idea
Frequent Release Events
Smoother Effort, Lower levels of accumulated change,
Less Risk
“Change is flowing into production…”
Release Event
Change
Volume
Time
© Copyright 11/12/2013 BMC Software, Inc
6

7. Agile Release Cadence Impact
Business Goal - accelerate software delivery and
quality
Operations is not on the same cadence
“Agile drives attempted release activity…”
SDLC
Agile
Business
Development
“Sprints”
© Copyright 11/12/2013 BMC Software, Inc
Release
Event
ITIL
Operations
“Marathons”
7

8. DevOps Gap
Faster Releases run into Operational Controls
Release Process is slow, manual and error prone
DevOps
Gap
Agile
Business
© Copyright 11/12/2013 BMC Software, Inc
Development
Release
Event
Operations
8

9. Today’s Process - Lots of Moving Parts
Multiple Tiers
Multiple Environments
Multiple Teams
Dev
Portal
Agile Team
Multiple Deploys
Ops
Dev
5
QA
Dev
Dev
QA
SIT,
Perf,
UAT
…
5
1
1
1
51 4
1
3
1
11 4
32
3
32
13 4
2
3
Stage
Prod
Dev
DB
Multiples of Everything:
Tiers, Teams, Environments, Deployments
© Copyright 11/12/2013 BMC Software, Inc
9

10. Multiple Change Types
Non-Prod
Non-prod Teams
Prod
Prod Teams
Release Management Team
Code Deploys
Code changes
Development team
Configuration Changes
Data Changes
Code
Config
Implementations
Dev Infra team
Config.
Data changes to
application
DBA team
Data
3 Core Change Types: Code, Configuration and Data
All need to be accurately communicated to the prod team – to avoid
production outages during release
© Copyright 11/12/2013 BMC Software, Inc
10

11. Dev/Test Environment Provisioning is Slow/Error Prone
Environment provisioning problems – as part of DevOps
Can’t continuously deliver without easy to setup and tear down
environments
When environments are provisioned they are usually wrong – or have
defects
Environments are unreliable and inconsistent
© Copyright 11/12/2013 BMC Software, Inc
11

12. Traditional Responses
Manual processes,
Spreadsheets, Conference Calls, Emails
“We have issues but some releases make it out…”
DevOps
Gap
Agile
Business
© Copyright 11/12/2013 BMC Software, Inc
Development
Release
Event
Operations
12

13. DevOps Responses
Building Bridges with DevOps Methodologies
DevOps teams, Infrastructure as Code, Toolchains
Cloud Environments for Dev/Test
DevOps
Gap
Agile
Business
© Copyright 11/12/2013 BMC Software, Inc
Development
Release
Event
Operations
13

14. DevOps – Key Solution Areas
Planning
-
What is in the release?
When is the release?
What is the status of the release?
Coordination
-
How are we deploying?
Where are we deploying?
When are we deploying?
Automation
-
How is the change implemented?
What is the version?
Environments
-
Where are the servers?
Create a new environment?
How is the environment configured?
© Copyright 11/12/2013 BMC Software, Inc
14

15. Creating the DevOps Cycle
Collaborative Planning
-
Increase Dev and Ops team visibility into release planning process
Connecting Dev and Ops Tooling
 Dev Issue Tracking (eg. JIRA)
 IT Service Management (eg. BMC Remedy)
Coordinating release process
-
Tightening up deployments and transition events
Improving communication and collaboration
Reducing Pre-production environment downtime
Increasing Automation
-
Extend and rationalize current automation
Standardize documentation
Improve Monitoring
-
Focus on end-user experience monitoring
Map deployments and releases to monitoring data feeds
© Copyright 11/12/2013 BMC Software, Inc
15

16. BMC Release Lifecycle Management
Ops
Dev
Development Change Management
ITSM – Change Management
ALM, SCM, Issue Tracking, Build Automation
Tracking, Approval
BMC Release Lifecycle Management
Release Process Management - BRPM (fmr. StreamStep)
Integrates, executes processes & monitors automated and manual steps
Enables process visibility, team collaboration and executive oversight
Release Package and Deploy – BRPD
(fmr. Varalogix Q)
Intelligent Packaging & Deployment, Artifact
Repository, Automation Library
In-House
Scripts
Manual
Processes
Existing
Automation
Dev Environments
Application Automation - BAA
Bladelogic and Agents
(Option to use BladeLogic Automation)
BMC Middleware
Automation - BMA**
J2EE Server Configuration &
App Deployment
Open Source
Tools
BMC Database Automation
BMC Atrium Orchestrator
Test Environments
… Other Pre-Prod Environments
Cloud Lifecycle Management – CLM
Integrates, executes processes & monitors automated and manual steps
Enables process visibility, team collaboration and executive oversight
© Copyright 11/12/2013 BMC Software, Inc
16

17. DevOps - RLM and CLM
Dev Teams
Code
Changes
BMC RLM
BMC Release Lifecycle Management
Application Release for Complex Enterprise
Applications
Build
Package
Ops Teams
Ops Teams
BMC Cloud Lifecycle Management
Provision Full Stack and
Manage Hybrid Environments
Provision
Monitor
Retire
Deploy
Portal
Service A
Configure
Migrate DB
Test
Code
Portal
Service B
DB
© Copyright 11/12/2013 BMC Software, Inc
…
Service A
Service B
DB
…
Portal
…
Service A
Service B
DB
17

18. RBC without RLM – Highly Manual Process
QA Environment – Typical Build and Deploy Process
Dev
Request
build
Emai
l
End
SharePoint
PS Eng.
Emai
l
Open
JIRA
JIRA
Check QC
Check QC
Check
status QC
status
status
QC
Run
Run
Run
Build
Build
Build
Jenkins
Manual
Enter
build info
JIRA
Email
QA
Enter
Env info
JIRA
Email
Specify
deploy env.
JIRA
Multiple tools
for process
coordination
© Copyright 11/12/2013 BMC Software, Inc
Email as
collaboration
tool
Run
Deploy
Emai
l
End
Manual
Email
Deploy
accept?
Emai
l
End
Manual
Lots of manual
script work
18

19. RBC with RLM – Single Global View for Release
Common Dashboard and Controls for Self-service Build and Deploy
Dev
Automatic (PS Eng.)
QA
Request
build
Automatic
(PS Eng.)
QA
All
Review
deploy
End
BMC – Release Lifecycle Management RLM
Open
JIRA
Check
QC status
Run
Build
JIRA
QC
Jenkins
Push button,
self-service
deploys
© Copyright 11/12/2013 BMC Software, Inc
Single Global
View for all
teams
deploy
environ?
Run
Deploy
Accept
deploy?
BMC
BladeLogic
Automation
Open Web
Service and CLI
integrations
Deep integration
with BMC
BladeLogic
Built-in RBAC
for apps and
environments
19

20. Automated provisioning of cloud services
Provision complete cloud services
From hardware…
…To fully configured services
Infrastructure
• Physical machines
• Virtual machines
• Physical or virtual
networks
• Operating Systems
Platforms
•
•
•
•
•
LAMP/WAMP
IBM Websphere
Microsoft SQL & .NET
Oracle Databases
Tibco
Applications
• Exchange
• Sharepoint
• Blackberry Enterprise
Server
• SAP
Monitoring , compliance, configuration management
Deliver a broad range of complete cloud services
© Copyright 11/12/2013 BMC Software, Inc
20

21. Automate configuration compliance in cloud
environments
Maintain configurations and compliance
Audit
Best Practices
Running
Configuration
© Copyright 11/12/2013 BMC Software, Inc
Remediate
CONTINUOUS
ENFORCEMENT
Differences
Change
Configuration
Validate
Report
Consistent
Configuration
21

22. 8
Minutes to provision a service
– down from 6 days
650%
Increase in the server : admin ratio
0
Minutes of administrative
work to deploy a new
service – down from 4 hours
12
Months to achieve
return on $2 million
investment
90
Days to full deployment
of the JDA cloud
© Copyright 11/12/2013 BMC Software, Inc
22

23. Learn more at www.bmc.com
© Copyright 11/12/2013 BMC Software, Inc
23