Book Image

DevOps for Networking

By : Steven Armstrong
Book Image

DevOps for Networking

By: Steven Armstrong

Overview of this book

Frustrated that your company’s network changes are still a manual set of activities that slow developers down? It doesn’t need to be that way any longer, as this book will help your company and network teams embrace DevOps and continuous delivery approaches, enabling them to automate all network functions. This book aims to show readers network automation processes they could implement in their organizations. It will teach you the fundamentals of DevOps in networking and how to improve DevOps processes and workflows by providing automation in your network. You will be exposed to various networking strategies that are stopping your organization from scaling new projects quickly. You will see how SDN and APIs are influencing DevOps transformations, which will in turn help you improve the scalability and efficiency of your organizations networks operations. You will also find out how to leverage various configuration management tools such as Ansible, to automate your network. The book will also look at containers and the impact they are having on networking as well as looking at how automation impacts network security in a software-defined network.
Table of Contents (19 chapters)
DevOps for Networking
About the Author
About the Reviewer

Load balancing immutable and static infrastructure

With the introduction of public and private cloud solutions such as AWS and OpenStack, there has been a shift towards utilizing immutable infrastructure instead of traditional static servers.

This has raised a point of contention with pets versus cattle or, as Gartner defines it bi-modal (

Gartner has said that two different strategies need to be adopted, one for new microservices, cattle, and one for legacy infrastructure, pets. Cattle are servers that are killed off once they have served their purpose or have an issue, typically lasting one release iteration. Alternately, pets are servers that will have months or years of uptime and will be patched and cared for by operations staff.

Gartner defines pets as Mode 1 and cattle as Mode 2. It is said that a cattle approach favors the stateless microservice cloud-native applications, whereas a pet, on the other hand, is any application that is a monolith...