Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
DevOps for Networking

You're reading from   DevOps for Networking Bringing Network Automation into DevOps culture

Arrow left icon
Product type Paperback
Published in Oct 2016
Publisher
ISBN-13 9781786464859
Length 364 pages
Edition 1st Edition
Tools
Concepts
Arrow right icon
Author (1):
Arrow left icon
Steven Armstrong Steven Armstrong
Author Profile Icon Steven Armstrong
Steven Armstrong
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. The Impact of Cloud on Networking 2. The Emergence of Software-defined Networking FREE CHAPTER 3. Bringing DevOps to Network Operations 4. Configuring Network Devices Using Ansible 5. Orchestrating Load Balancers Using Ansible 6. Orchestrating SDN Controllers Using Ansible 7. Using Continuous Integration Builds for Network Configuration 8. Testing Network Changes 9. Using Continuous Delivery Pipelines to Deploy Network Changes 10. The Impact of Containers on Networking 11. Securing the Network Index

Deployment pipeline tooling


Deployment pipelines involve chaining different tools together to create Continuous Delivery processes.

Being able to track the process flow through the Continuous Delivery tooling is integral, as it is important to be able to visualize the pipeline process, so it is easy for operators to follow.

Having visibility of a process makes debugging the process easy if errors occur, which may happen as errors will occur in any process and are inevitable. The whole point of the Continuous Delivery pipeline, aside from automating delivery of changes to environments, is to provide feedback loops. So if a pipeline is not easy to follow and debug, it has failed one of its main objectives.

Building automatic clean-up into pipelines should be implemented if possible, so if a failure occurs mid-deployment then changes can be reverted back to the last known good state without the need for manual intervention.

At a high level, the following tooling is required when creating a deployment...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image