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

Network continuous integration


So why should network engineers be interested in continuous integration? A network team should be interested in continuous integration if they want to improve the following points, which were focused on in Chapter 3, Bringing DevOps to Network Operations:

  • Velocity of change

  • Mean time to resolve

  • Improved uptime

  • Increased number of deployments

  • Cross skilling between teams

  • Removal of the bus factor of one

The ability to easily trace what has changed on the network and see which engineer made a change is something that continuous integration brings to the table. This information will be available by looking at the latest commit on a continuous integration build system.

Roll-back will be as simple as deploying the last tagged release configuration as opposed to trawling through device logs to see what changes were applied to a network device if an error occurs.

Every network engineer can look at the job configuration on the continuous integration build system and see how...

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