Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Service Design Overview

Service orchestration in Paragon Automation automates provisioning of a service in the network and monitoring the service after provisioning. Service designs provide guidelines and templates to onboard devices, configure network resources for a service, provision a service, and monitor the service after provisioning. A service design includes the following:

  • A service model that defines the service structure and elements. Typically written in the YANG language, a service model includes a customer service model (CSM) and a network service model (NSM). The CSM is intent-based and describes a service from the customer's point of view. The NSM is implementation-based and describes a service from the point of view of the network.

  • Rules to validate whether a service instance that is configured based on a service design conforms to the service model in the service design. Validation rules are usually embedded in the CSM or NSM.

  • Rules for allocation of resources (placement) to implement a service instance. Placement rules are complex JQuery filters encapsulated in a YAML file.

  • Translation templates that describe how to transform service instances to service configurations for deployment on target devices. Translation templates are Jinja2 files that differ for different devices, vendor OSs, or software versions.

  • Paragon Insights playbooks to monitor the service after provisioning by collecting relevant information from all devices on which the service is provisioned.

  • Paragon Active Assurance test templates to test a service instance after provisioning it in the network.

  • Paragon Active Assurance probe templates to measure the service quality on an ongoing basis after provisioning.

Paragon Automation provides the following service designs for onboarding devices, adding L3VPN network resources, and provisioning L3VPN services:

  • Infrastructure service design to onboard and deploy devices to the network.

  • Routing and Layer 3 address service designs to configure network resource pools for the infrastructure service.

  • Topology and VPN service designs to configure network resource pools [route targets, route distinguishers, point-of-presence (POP), and so on] for the L3VPN service.

  • L3VPN service design to provision and monitor L3VPN services in the network.

Paragon Automation supports up to three concurrent versions of each service design. The service designs are automatically installed when you install Paragon Automation.

The Service Designs page (Orchestration > Service > Service Catalog) lists all the service designs and the available versions of each service design.

A root user can view the service design catalog by using the service orchestration cMGD CLI. See About the Service Orchestration cMGD CLI.

Related Documentation