We list here functionality that should be integrated into CLAMP in the coming releases. Inclusion into Casablanca or any other release will depend on resource availability.
- Enhance TOSCA Policy model support. This will improve flexibility to allow runtime possibility to add new type of mS into CLAMP:
- Better parsing of TOSCA Policy model.
- get policy definition from policy API(if API available). This will allow runtime knowledge of mS configuration pattern.
- Improve dashboard integration into CLAMP UI. (currently only 2 separates UI kibana/CLAMP UI) but we need a bridge in CLAMP UI towards kibana reports for specific KPI’s (to be discussed with Ops.)
- Improve blueprint parsing of Control Loop definition coming from DCAE-D:
- Move from "blueprint"(tied to Cloudify orchestration) to "service_template"(more generic Tosca file and independent from orchestration type) for Control Loop description/definition.
- “MariaDB+Galera cluster” (helm chart to be provided by OOM team in Casablanca).
- Generic filtering mechanism to associate to a Control Loop to the Network. the filter would be based on the data provided by A&AI:
- VNF instance
- VNF location
- ...
- A faster way to disable/re-enable a Control Loop at runtime(currently there is several steps involved: stop/undeploy/....)
- disable/re-enable Control loop at different level, e.g.: disable for some VNF inside a service instead of disabling for all VNF inside the service.
- show, into a runtime dashboard view, the condition which are disabled on that Control loop.
- A&AI integration to get realtime view of network topology. This will support capability to specify conditions for control loop configuration and operation.