Skip to content

Introduction

Network as Code allows for complete separation of data (defining variables) from logic (infrastructure declaration). With little to no knowledge about automation, users can instantiate Multiple Unified Branches in minutes. This is achieved by separating the *.yaml files which contain the desired Unified Branches state from the underlying automation engine parameters required for automation execution. We refer to this solution as “Branch as Code” that is based on Network as Code framework. The data model and modules used in Network as Code Unified Branch are open-source and available as-is.

This approach allows for consistent and repeatable configuration of Cloud Managed Unified Branches and aligns with Infrastructure as Code (IaC) methodology, where the configuration state is saved in a version control system and managed as code.

Infrastructure as code (IaC) is a DevOps methodology that uses code to manage and provision IT infrastructure, bypassing manual procedures. IaC uses a descriptive coding language to automate the provisioning of servers, operating systems, network devices and more.

The Branch as Code collection allows you to configure, in easy-to-understand YAML, data structures describing the configuration state of a Cisco Unified Branch Small Branch CVD and then deploys this state using Terraform. With little to no knowledge about automation and Terraform, you can use this collection to instantiate a CVD Based Unified Branch.

YAML files are created that contain a pre-determined data schema which is translated into underlying Terraform modules and resources. The terraform modules and provider used in the solution are open source. This solution is designed to be used in a CI/CD pipeline in order to drive this declarative method of configuring Unified Branches.