- [Instructor] There's been a dizzy explosion of tools
in devops from source code management
to database management to build,
continuous integration, repo management,
testing, deployment, config and provisioning,
containerization, cloud, IaaS, PaaS, SaaS,
release management, collaboration, BI, monitoring,
logging and security and the list goes on.
Mostly these tools are point solutions
that can be interconnected
versus monolithic product suites.
This collection of connected point solutions
is referred to as your devops tool chain.
There are three characteristics you'll want
for your devops tool chain.
First, you want your tool set to be programmable.
That means, tools with just the UI
and no command line interface and API are out.
Second, you'll want your tool set to be verifiable.
That means, it exposes clearly what it's doing
and provide some manner of validating
that it did what it was supposed to do correctly.
And thirdly, you'll want your tool set to be well-behaved.
That means, it plays nicely with other tools in your chain
both from a dev and ops perspective.
Obviously, the key intersection between devops tools
and ITIL-driven shops
is service management technology and architecture.
One thing you can do here
is to review your tool set against these criteria
and for example substitute a tool
that has a command line interface and API
for one that does not.
Another good place to start
is with configuration management tools.
In devops, configuration management is version control,
a shift left from the idea in ITIL
of configuration management
as a logical picture of your environment.
Remember, we're dealing with cattle, not pets here
in a devops world.