Introduction
Purpose of This Document
This documentation describes how to integrate Paragon Active Assurance with a network service orchestrator via the Control Center NETCONF & YANG API. Hands-on examples are given of the principal tasks involved, including: creating and deploying Virtual Test Agents, running tests and monitors, and retrieving results from these activities.
In this document, the freely available Python NETCONF client
ncclient
is used in the role of orchestrator.
Conventions
The following abbreviations are used in this document:
Abbreviation | Meaning |
---|---|
CLI | Command Line Interface |
EM | Element Manager |
ES | Errored Second |
MEP | MEG (Maintenance Entity Group) End Point (ITU-T Y.1731 definition) |
or Maintenance End Point (Cisco definition) | |
NFV | Network Function Virtualization |
NFVO | Network Function Virtualization Orchestrator |
NSD | Network Service Descriptor |
RPC | Remote Procedure Call |
SIP | Session Initiation Protocol |
SLA | Service Level Agreement |
S-VNFM | Special VNF Manager |
VNF | Virtual Network Function |
vTA | Virtual Test Agent |
Notes on Backward Compatibility
In versions 2.35.4/2.36.0 of the NETCONF & YANG API, the validation of certain requests was made more stringent to adhere to the NETCONF standard. This means that client code based on older versions of this guide might now be rejected.
For example, in previous Python example code, no namespace attribute was provided. The namespace now needs to be supplied in the request XML whenever you want to modify a ConfD resource.