# ONES Orchestration

## Why do we need Network Orchestration?

Orchestration refers to tasks or actions required to achieve a set of objectives for your Network Infrastructure operations

A centralized application like ONES translates these objectives into a network configuration template, applies and monitors to validate the operational efficiency and functionality

<figure><img src="https://lh5.googleusercontent.com/C7Qfnr4Fwmzi0TOjPKfbHgrsvcsQCDzcE-rEk8PWJd-_43Vpeqq069IKmaV9Z__mTz9MCXsvf7KMx-vTb9bpF0WK6UQa55DhLSOZlPZxRKhvxcV6Zmt8QYRnn8rNFTV51vgnIBKdFtw95aT4DqiLxZw6Ut82SaY-M_28PifwSBXY8NHm4riBkajp71UstQ" alt=""><figcaption><p>Network Orchestration Workflow</p></figcaption></figure>

Automated tasks are performed on your Network Fabric in a purposeful order and each step is verified for success before moving to the next

## ONES Orchestration - Overview

ONES Orchestration function on the application lets you compose, deploy, and validate network configurations across any SONiC, be it a Community version or a Vendor distro.

As part of the initial release, ONES Orchestration supports to&#x20;

* Create and configure CLOS topology for ToR, Leaf, Spine, and Super-Spine layers&#x20;
* Apply and validate configurations pre- and post-deployment&#x20;
* Compare running configs against applied configs at any point&#x20;
* Upgrade devices with a single click via ZTP or custom NOS images
* Automate Configuration of interfaces, layer 3 interfaces, BGP-unnumbered and Common Services like NTP, SNMP, SYSLOG etc.

ONES Orchestration use cases are configured using a set of pre-defined YAML-based templates on ONES Web User Interface

<figure><img src="https://content.gitbook.com/content/6HmS5vpdFi7u1EvmTXSl/blobs/cbPjb2GIiWv14wMkrf7G/image.png" alt=""><figcaption></figcaption></figure>
