-
Notifications
You must be signed in to change notification settings - Fork 7
Description
Introduction
This is the second of several issues that describe what needs to be done to add NSI support to the example orchestrator. The two new products that will be added are the NSISTP and NSIP2P.
For questions contact @hanstrompert.
Description
The NSISTP reserves VLAN's on a port, by registering them in a SAP product block, so these VLAN's are reserved for an external NSI Network Service Agent (NSA) to create Point-to-Point circuits on. The external NSA is only allowed to use VLAN's that are reserved by a NSISTP, and therefor cannot use the normal L2VPN product for exact that reason. That is why a new type of product is needed that can make use of NSISTP reserved VLAN's.
Proposal is to create a new NSIP2P product that can be build on top of NSISTP's. This new product is implemented by using the existing L2VPN with just two ports. Needless to say that a NSIP2P can not use NSISTP VLANs that are already used by other NSIP2P.
Implement a new NSIP2P product that uses the existing L2VPN product block. Implement the NSIP2P workflow by making use of existing L2VPN workflow code as much as possible. Only main difference is that for a NSIP2P the L2VPN product block will only have 2 SAPs, and the VLANs used must be in use by (or actually reserved by) a NSISTP subscription but not by any other NSIP2P subscription.