Delivering Software as a Service in the cloud requires agility and speed. Sadly, those are two attributes that big companies aren’t usually good at doing. Instead of organizing to deliver results, companies tend to build silos where development, operations, QA and security operate as separate entities. DevOps unites these groups to deliver services faster and provide results that matter.
This talk will arm you with the DevOps patterns to follow as well as point out specific anti-patterns to avoid. To show you how to implement DevOps in your org, this talk will cover sample architectures and Open Source tooling. Come hear how to start delivering results with increased agility and speed.
The DevOps Way of Delivering Results in the Enterprise
1. The DevOps Way
of Delivering Results
in the Enterprise
James Wickett
james_wickett@mentor.com
twitter: @wickett
mentor.com/embedded
Android
is
a
trademark
of
Google
Inc.
Use
of
this
trademark
is
subject
to
Google
Permissions.
Linux
is
the
registered
trademark
of
Linus
Torvalds
in
the
U.S.
and
other
countries.
2. I want you to be
successful and
make a difference
4. Experience
• Started using AWS cloud in early 2008
• 2.5 years working on a DevOps team
• History of working in the enterprise and
in startups and in startups inside the
enterprise
• DevOps Days Austin Organizer
5. Conclusions
The cloud necessitates a new approach
to our operations (business and tech)
DevOps has worked for startups and can
work for the enterprise
Rugged DevOps fills some of the needs
of the enterprise
Use a Behavior Driven Infrastructure
approach
6. DevOps Antipatterns
• Rebrand your Ops team as the DevOps team
• Use a machines to people hiring ratio to
determine headcount
• Deploy software manually
• Believe chef/puppet/cfengine will solve all your
problems
• Test only the application code
• Deploy to a production-like environment only
after development is complete
• Rely on the standard logs for metrics
• Hide stuff from your team
9. “Cloud? I’ve been doing that since 1988.
It’s just the same old thing with a new
name."
- Technohipster
“Rugged DevOps will help you build your cloud” - http://bit.ly/rugged-devops
10. OSSM
On-Demand
Scalable
Self-service
Measured
Dave Nielsen > http://www.rackspace.com/blog/on-definitions-keeping-it-simple-with-ossm/
14. New landscape
Are New Skills Required for Cloud Computing?
Cloud computing requires new skills - 74%
Cloud computing does not require new skills - 26%
source: The 2011 (ISC)2 Global Information Security Workforce Study
15. Specific New Skills Required
for Cloud Computing
A detailed understanding of cloud
computing - 92% agree
Enhanced technical knowledge - 82% agree
Contract negotiation skills - 49% agree
source: The 2011 (ISC)2 Global Information Security Workforce Study
69. DevOps and
Enterprise
are unlikely
traveling companions
70. “there is nothing to suggest that
devops can’t work in the enterprise”
-Patrick Debois
Cutter IT Journal,Vol. 24, No. 12, pg 3
71. “The main challenge will be reevaluating the
existing people and processes from
a constant collaboration viewpoint,
keeping the business goals in mind.”
-Patrick Debois
Cutter IT Journal,Vol. 24, No. 12, pg 3
77. 2% of an engineering
dev team are
working on security
- BSIMM 2012 data, http://bsimm.com/
78.
79. I recognize that my code will be attacked by talented
and persistent adversaries who threaten our physical,
economic, and national security.
I recognize that my code will be used in ways I
cannot anticipate, in ways it was not designed,
and for longer than it was ever intended.
I am rugged, not because it is easy, but because it is
necessary... and I am up for the challenge.
88. Building solutions to handle
adversity will cause
unintended, positive benefits
that will provide value that
would have been unrealized
otherwise.
RUGGEDIZATION
THEORY
slide from http://bit.ly/rugged-devops
89. NO PAIN, NO GAIN
slide from http://bit.ly/rugged-devops
97. Behavior Driven
Infrastructure
Write failing tests describing the
infrastructure you wish you had
Make them pass by writing infrastructure
automation code (chef/puppet)
Repeat
99. Culture is the most
important aspect to DevOps
succeeding in the enterprise
-me, 30 minutes ago
100. Conclusions
The cloud necessitates a new approach
to our operations (business and tech)
DevOps has worked for startups and can
work for the enterprise
Rugged DevOps fills some of the needs
of the enterprise
Use a Behavior Driven Infrastructure
approach
101. DevOps Antipatterns
• Rebrand your Ops team as the DevOps team
• Use a machines to people hiring ratio to
determine headcount
• Deploy software manually
• Believe chef/puppet/cfengine will solve all your
problems
• Test only the application code
• Deploy to a production-like environment only
after development is complete
• Rely on the standard logs for metrics
• Hide stuff from your team
102. The DevOps Way
of Delivering Results
in the Enterprise
James Wickett
james_wickett@mentor.com
twitter: @wickett
mentor.com/embedded
Android
is
a
trademark
of
Google
Inc.
Use
of
this
trademark
is
subject
to
Google
Permissions.
Linux
is
the
registered
trademark
of
Linus
Torvalds
in
the
U.S.
and
other
countries.