| CDS | Design Time - CDS GUI Designer Client [New] - Phase 1 of 3
- Package List Search
- Package Creation
- Meta Data Definition
- Template & Mapping Management
- Script Management
- Imports
- Designer Mode
- Scripting Mode
Run Time - Enable Blueprint Processor Rolling Upgrade leveraging Hezelcast
- Add PY-Executor 3.6 Microservice
- Add Error Catalog Library & integration with Blueprint processor
- Certify the blueprint processor imperative workflow orchestration for provisioning activities.
- Prioritization Service
- CLI Executor
- Bootstrap API for loading models, dictionary & CBA
- Audit Service
- Added gRPC TLC Service & Properties Implementation
ONAP Component integration - CLAMP integration with CDS via REST API for cba action specification retrieval for a given CBA Name & Version.
- Policy integration with CDS Blueprint processor microservice for LCM action execution.
- SO Controller Execution Building Block integration with CDS for controller action execution in generic.
Use Case: - E2E Automation for instantiation& Post instantiation via SO building & CDS for vLB VNF
- Control Loop of vFW VNF use case with Config Modify via DCAE, CLAMP Policy, CDS
- PNF Plug & Play with Netconf execution using CDS CBA package
- PNF Software upgrade using CDS CBA Package
- E2E Automation for instantiation via SO building, MultiCloud & CDS for CNF.
- 5G NRM Integration using CDS Package.
| Design Time - Simplify the CBA Package creation/.management via CDS UI.
Run Time - Upgrade clients individually with no interruptions to other clients
- Support a python executor 3.6 to execute python scripts via the CDS package.
- Have a consistent way of report errors for all the CDS components and microservices.
- Enable operation/designer for creating custom workflow and embedding customer workflow to the CDS CBA Package for parallel or sequential execution thus enabling faster delivery product to market.
- CDS should provide Correlation-based message prioritization based on Kafka Stream Consumption.
- Enable operations to execute any CLI based commands for PNF & VNF.
- CDS load model types, dictionaries, and CBA multiple times based on cluster size. This commits avoid autoloading, and provides an API to bootstrap, if necessary.
- Allows external components to trigger action(s) based on CDS execution and also gives visibility on every requests that was sent to CDS.
ONAP Component integration - Render the CBA Action in Clamp GUI without code changes.
- ONAP management of lifecycle action in generic & model-driven mechanism.
- ONAP Orchestration of controller execution model-driven mechanism.
Use Case - Pivot to a model-driven implement of provisioning & controller management using a network intent package via CDS implement for all the use cases.
.
NOTE: - Controller Design Studio [CDS]
- Controller Blueprint Archive [CBA]
|
