Devops Field Guide
Devops Field Guide
Field Guide
Download the current version of the IBM
Cloud DevOps Field Guide
http://ibm.biz/Ibm-cloud-devops-field-guide
What’s inside?
This field guide provides a high-level overview of the IBM Cloud
DevOps strategy.
Learn more
2
LEARN IT
Make way for new roles, stakeholders, and beneficiaries. The Site
Reliability Engineer (SRE) role speaks to the resurgence of service quality
(availability, scalability, maintainability) in delivery; throw some love at
IT Security, early....like real early, for the sake of your digital reputation.
Learn more
4
GET STARTED
DevOps Reference
Architecture
People, process, tools and technology are critical to DevOps. When
compared to people, tools and technology are the easy part of modern
delivery. People are your greatest asset. Create an agile culture and
give your people the tools they need to be successful.
Learn more
6
Continuous planning. A healthy rank-ordered backlog includes new
features, technical debt, defect remediation, and end user feedback.
Along with the squad, the product owner prioritizes, estimates and
clarifies user stories.
DevOps trends
Look at DevOps through a new lens to cope with modern client
challenges. DevOps is not just for applications anymore, nor is it just
about development and operations. Here are some trending ways in
which DevOps is being applied. Some are new and some are perennial
favorites.
Learn more
8
DevSecOps. Look at DevOps with a focus on secure design, development
and delivery. Note how security is architected into cloud-native
applications and platform constructs like clusters, namespaces,
deployment configurations, SDN, roles, and pipelines.
AIOps (AI for IT Operations). Apply deep and machine learning (ML)
to model behavioral patterns in operations using the data that cloud
native applications generate to arrive at predictions. When applied to IT
operations, AIOps provides insight about a system and can give rise to
predictive alerts, reduction in mean time to repair (MTTR), and outage
avoidance.
DevSecOps
DevSecOps is DevOps with a lens for security: secure design and
development of code, secure delivery through the pipeline, and secure
operations on Day 2. The challenges introduced with decentralized
workloads on the cloud, developers empowered with self-service,
and unprecedented accountability requires careful re-examination of
separation of duties, policy implementation, and how that translates to
modern cloud platform constructs.
Mitigate the right amount of risk. Boldly question every pipeline task
that hinders velocity. Be sure it addresses a liability or mitigates an
unacceptable risk to the enterprise’s digital reputation. What risk is
taken if a pipeline task is not done?
Learn more
10
Declarative approaches to platform compliance leave the
control flow logistics to the platform to achieve the “desired
state”, making continuous compliance achievable.
GET STARTED
AIOps
Traditional monitoring is changing. Teams can no longer rely on
administrators to define a set of monitors and associated thresholds
that might or might not detect an issue as it occurs. This lack of insight
into a system means that significant events can occur with almost no
foresight or warning.
“AI for IT Operations takes data from tickets, metrics, and log sources,
and uses deep learning and AI to gain insights from the data. This
data is then infused into processes to provide expert guidance for the
operations teams.” –Richard Wilkins, IBM Distinguished Engineer
Learn more
12
Collect relevant data. Monitoring products collect large amounts of
data that is streamed into a common centralized data lake, which
enables AI models to create a system performance baseline. Relevant
data must be defined collaboratively by application and system
stakeholders.
ModelOps
ML models must be trained (tested) and iteratively refined to achieve
the predictions needed to bring greater insight to a problem. ML
models consist of code, an analogous build to package and publish a
binary artifact, which is the runtime deployment of the model, and an
endpoint in which the model is consumed.
Consider the lifecycle of model data. ML models are fed with data
from the collect and organize rungs of the IBM AI Ladder. Raw data
is collected from a variety of sources and pre-processed to prepare it
for consumption by an ML model.
”Day 2” for ML models. Models and their predictions are only as good
as the data they ingest. Data changes over time, ML models “decay,”
which signals an opportunity to iterate on the model and examine
the data it consumes to make its predictions. Continuous learning is
key for the life cycle of ModelOps, which may result in a model being
updated or retired.
Learn more
14
AI is built on the strength of the machine learning (ML)
models that provide good actionable predications.
GET STARTED
BizDevOps
The fast pace of cloud adoption and change leads successful agile
organizations to place a much greater emphasis on the quality and
business effectiveness of new digital capabilities. After adopting DevOps
practices and technology to streamline your IT team, removing blockers,
and building a pipeline, you continuously deliver faster than ever before.
However, you must ensure you are delivering what the market demands.
Clearly define the business and user problem. Enterprise Design Thinking
is a proven way to clarify the definition of your desired business outcomes.
Technology enables you to deliver the solution.
Learn more
16
Ensure you deliver what the market demands!
GET STARTED
GitOps
Infrastructure, platform, and operations engineers are essential roles in a
modern enterprise. With the adoption of cloud platforms, configurations
for applications, clusters, policies, roles, monitors, chatbots, and operators
are version controlled coded assets with their own pipeline and lifecycle.
Git is a well-known version control system for coded assets. Use it or your
favorite version control system to enable GitOps.
System engineers are coders. System operators are engineers who code.
Their code is a valuable asset to the enterprise and must be treated as a
“first class citizen,” just like application code. Ensure your engineers have
the tools they need to maintain and curate their assets.
Learn more
18
GET STARTED
Learn more
20
If DevOps is the only facet of your transformation, you’re doing it
wrong.
GET STARTED
Learn more
22
Open source
tools
Existing tools
and toolchains
Instrumented
security
Learn more
24
Ne
Deploy workloads in
your frankencloud
Ma.
GET STARTED
Just enough
Technical
architecture
underpinnings
Build MVP
Frame
MVP
Learn more
26
Align on vision and desired business outcome. Whether it’s
strengthening your enterprise’s position in the market with innovative
products for consumers, or being responsive to market conditions,
DevOps must be placed in proper context to bring value to the business.
This results in defining your “diamond”, which includes more than
DevOps.
Frame your MVP. Use Enterprise Design Thinking to align business and
IT with an end user experience and roadmap that meets the desired
business outcome. Identify, define, and scope your MVP experiment in
the context of a roadmap. Be sure to identify risks and assumptions.
Build an MVP. With new ways of working, modernize, deploy, and test
the application with a DevOps pipeline. Test hypotheses against the
stated business outcome.
Build out. Iterate across multiple MVPs to refine your solution until
you achieve the stated business outcome. Then, scale your production
environment and applications.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult your
local IBM representative for information on the products and services currently available in your area. Any reference
to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or
service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM
intellectual property right may be used instead. However, it is the user’s responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The
furnishing of this document does not grant you any license to these patents. You can send license inquiries, in
writing, to:
The following paragraph does not apply to the United Kingdom or any other country where such provisions are
inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION
“AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions;
therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made
to the information herein; these changes will be incorporated in new editions of the publication. IBM may make
improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time
without notice.
Statements regarding IBM’s future direction or intent are subject to change or withdrawal without notice, and
represent goals and objectives only.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp.,
registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other
companies. A current list of IBM trademarks is available on the web at “Copyright and trademark information” at
www.ibm.com/legal/copytrade.shtml.
IBM CLOUD DEVOPS STRATEGY
© 2020, 2021 IBM CORPORATION