Page History

The Control Loop sub committee led the functional requirement to add a new Filter Guard Policy Type. In addition, the subcommittee ensured that the Native Policy Type work developed in Frankfurt was fully tested through the CLAMP interface.

The sub committee continues to support the DCAE Project Self-Serve control loop enhancements Proof-of-Concept. The PoC made improvements to MOD (NiFi) and configuration for dynamic topic support.

A new Proof-of-Concept was started by the subcommittee to define TOSCA-Based Control Loops. This work was demonstrated at the fall LFN Technical Conference.

The new Filter Guard Policy Type is another guard policy available for ONAP users to use in addition to the others that have been available since Dublin. This allows filters to build more flexible constraints to both whitelist and/or blacklist vnf types, specific vnf id's, services, etc.

In defining a TOSCA specification for Control loops, users can now encapsulate all the details of a control loop within one specification. These specifications are re-usable. CLAMP will eventually be able to be fed a TOSCA specification, and with minimal effort be able to configure and deploy a control loop into the runtime environment.

The modeling subcommittee updates the ONAP VNFD model to align with ETSI NFV IFA011 v2.7.1, supporting key features like virtual ip, VNF exposed interface, etc.

The subcommittee also adds a new model for location information. Taking consideration of multiple existing standards, including ETSI NFV SOL001, RFC4776 and RFC6225, the new model enables an entity to provide its geographical location information.

Update of the VNFD model to the latest ETSI NFV spec allows ONAP to incooperate new features defined in standards.

The new locations model enables entity such as PNF to provide its geographical information, allowing further scheduling and optimization procedures.

Open Lab