DevOps and the Future of IT Operations
30
DevOps and The Future of IT Operations November 30, 2011
-
Upload
correlsense -
Category
Technology
-
view
2.387 -
download
3
description
The increasing adoption of DevOps principles has led to greater integration between software development (both application and software engineering) and IT operations (both systems administration and infrastructure). In this online seminar, we will explore the DevOps approaches
Transcript of DevOps and the Future of IT Operations
DevOps and The Future of IT Operations
November 30, 2011
• Housekeeping• History of DevOps• Challenges• Use cases• Q&A
Agenda
Housekeeping
• Presentation will last 30 minutes• Submit questions via the chat window• Slides will be made available
Featured Speakers
Amir GabrielliSenior Solutions ArchitectCorrelsense
History of DevOps
• “DevOps” coined by Patrick Debois in 2009
• Ideas from enterprise systems management
• Address rapid app rollouts by agile development
What Is DevOps
Need for DevOps
Development
• Driven by functional
requirements
• Based on business needs
• Use complex coding without
concern for Operations
• Their job is to make changes
Operations
• Driven by non-functional
requirements
• Such as availability, stability,
performance, and monitoring
• Lack knowledge of
application’s internals
• Their job is to avoid changes
Driver 1: Rapid Deployment
• Operational needs to support
agile development
• Applying agile approach to
infrastructure allocation via
virtualization
• Rapid adoption of applications
by operation teams
• DevOps implement automation
and configuration management
tools
Driver 2: Distributed Systems
• Applications no longer monolithic
• Tend to be more service oriented
• SOA allows for reuse of existing
vertical functionalities
• Ops not just managing
infrastructure – also services
• They need expertise both in
infrastructure and services
Driver 3: Application Support
• Growing need for operations to be
more than trouble ticket clerks
• Be more self sufficient supporting
production apps
• Need to decrease development
involvement in production faults
• Provide more precise info for tier 3
and dev support
• More changes, more unexpected
issues, lack of predictability
Driver 4: Integrating Ops and Development• Need better feedback
mechanisms
• Implement measures
and metrics
• Communicate when
things are going well
Challenges1. Facilitating rapid app transition from Dev to Ops2. Providing app-specific knowledge to Ops 3. Getting Dev and Ops teams to communicate better
Tools
• Application dependency discovery and mapping
• Transaction management
Tools – Application Mapping
• Automatically
– Discover and display relationships
between applications
– And supporting IT components
– Known as application
interdependency mapping
• Replaces
– VISIOs /diagrams
– Manual CMDB provisioning
– Long training and handovers
sessions
Tools – Application Mapping
Tools – Transaction Management
• Trace transactions execution path across
complete IT stack
• Understand application behaviors with no
prior knowledge
– Transaction discovery
– Transaction path detection
– Transaction performance models
• Down to interaction between the
supporting infrastructure components
• Indentify transaction delivery failures
across infrastructure
“ the chain is only as strong as its weakest link”
Tools – Transaction Management
• Performance problems with portal application
• Database, LDAP, web server, and app server are “good”
• Dev is blaming the database and network
• And end users complaining about slow application
Use Case 1: When an Application Container Fails
Use Case 1: When an Application Container Fails
Use Case 1: When an Application Container Fails
Use Case 1: When an Application Container Fails
• Everything looks great at UAT– Preview rollout to production– All signs suggest a problem– but why and where?
Use Case 2: When it doesn’t behave as you thought
Use Case 2: When it doesn’t behave as you thought
Workload increasing over time
Use Case 2: When it doesn’t behave as you thought
Use Case 2: When it doesn’t behave as you thought
Average end-user experience is also degrading
Use Case 2: When it doesn’t behave as you thought
Workload increase is attributed to stored procedure To database – “write session”
Use Case 2: When it doesn’t behave as you thought
It gets larger over time as “write session” goes
from 320 B to 2.2 MB, gradually degrading performance
Use Case 2: When it doesn’t behave as you thought
Summary
• DevOps increasingly popular• Moving from SMB to the enterprise• Need new tools• Will challenge IT organizations to change the way
they do business
Questions
Get your free copy SharePath RUM today!
www.correlsense.com/demo
www.real-user-monitoring.com
