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. 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 network's point of view.

  • 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 that are 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.

  • Monitoring rules to monitor the service after provisioning by collecting relevant information from all devices on which the service is provisioned.

  • Active data plane tests to test a service after provisioning it in the network.

  • Active data plane tests to continually measure the quality of a provisioned service.

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

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

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

  • E-LAN EVPN CSM service design to provision and monitor EVPN services in the network.

  • E-Line L2circuit NSM service design to provision and monitor L2 circuit services in the network.

  • Routing and L3 resource designs to configure network resource pools for infrastructure services.

  • L2 resource design to configure network resource pools for EVPN services.

  • Topology resource design to configure topology resource pools (site and PE details) for L3VPN and EVPN services.

  • VPN-resources resource design to configure VPN resource pools (route targets, route distinguishers, and virtual circuits) for the L3VPN, EVPN, and L2 circuit services.

Paragon Automation supports up to three concurrent versions of each service and resource design. The service and resource 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 manage the service design catalog by using the service orchestration cMGD CLI. See About the Service Orchestration cMGD CLI.

Related Documentation