Service Orchestration

Services, be it an application or others are the business enablers for any organization. Under the hood, it is the network that powers these services and mostly spans across multiple devices platforms catering to the high availability and security of these services. For network teams, provisioning and maintenance of these services are beyond a niggle. Multiple touchpoints for configurations, multiple skillsets to cater to multi-vendor networks, maintaining multiple documents, regular audits, and 24×7 monitoring to ensure SLA compliance are few of the hassles they encounter on a daily basis. Here some of the challenges of traditional provisioning methods.

Device abstraction: In a diverse, multi-vendor deployment, it is extremely difficult to keep track of all services, device communication methods, CLI syntax, proprietary features, etc. to come up with a consistent view of the network.

Service abstraction: Traditionally, configuration management is done in silos by maintaining the configuration templates of each and every device in the network and service-level awareness is often missing in most Management tools.

Vendor-agnostic data representation: Network information such as IP Addresses, VRFs, VLANs, and ACLs, etc. are often represented differently for different vendor platforms making visual comparison and standardization impossible without the use of a data model.

As a result of this complexity, it is expensive for operators to bring services to market or make changes on the go as per customer requests. This also makes them vendor dependent.

A network outage lasting only a single hour can cost a business more than $300,000

- Gartner Research

How does Service Orchestration work?

Benefits of ATOM's Service Orchestration

Extensible, model-driven configuration management using YANG

ATOM supports YANG to represent network configuration and state data. With an extensible framework, ATOM offers out-of-box support for use cases ranging from L2/L3 services to complex use cases such as multiple flavors of L2 and L3VPN, routing and firewall automation.

Device & Service abstraction

ATOM supports various device models using the YANG framework thereby giving the network teams a consistent view of the network data. Be it a Cisco, Juniper or Arista, ATOM masks the complexity relieving the stress of NetOps

Support for CRUD operations

ATOM’s service orchestration helps in maintaining the lifecycle of services. Create it once, update it multiple times, and retire them – ATOM supports it all offering the much-needed flexibility to NetOps.

Supports a high degree of customization

Want to create or customize existing service models to suit your business needs? Use ATOM SDK and augment your DevOps journey by creating and modifying device drivers and service models.

What is unique to ATOM’s Service Orchestration?

Multi-Vendor support

ATOM offers comprehensive support for 45+ different vendors including Cisco, Juniper, Arista, F5, Citrix and many more across all their different platforms. An extensible platform allows quick addition of vendors in a matter of few weeks

Cross-domain support

Be it Branch, Campus, Datacenter or SP core, ATOM offers support for all sets of use cases. Day-0 onboarding through Zero Touch Provisioning & Cisco PnP or Day-N operations, ATOM supports all of it.

Pre & Post validations with workflow automation

Leverage ATOM’s workflow automation to add pre & post validations for service orchestration. Make sure the environment is set and configuration has a successful result by combining the power of both

Transaction support with commit/rollback

What if a device becomes unreachable or unresponsive during a service provisioning? ATOM supports atomic transactions to ensure rollback of services in the event of failure to reach a device during service configuration.