Page History

...

CNF Orchestration Enhancements (REQ-627)

Synchronization of k8s resource objects between k8scluster and AAI as a part of CNF instantiation process

Dedicated CNF Healthcheck Workflow in SO

Control of the order of the CNF and helm package deployment in SO macro request

Various k8s resource management improvements in k8splugin

Helm 3.5 package spec support

Support for Helm pre/post- create and delete Hooks

Improved Config API

Status API returns the real status of deployed helm package

Better aligned with Helm processing spec

Important bug fixes

Nominated Candidate	Reason for Nomination
Lukasz Rajewski	Lukasz was strongly involved in CNF journey: very active in the CNCF Task force, contributions to Service Orchestrator. He brings a lot of support to the community, mentorship by providing tutorials, education people, DDF presentations. He was very active to provide support for the 5G Super Blueprint especially to solve integration isseus issue with Magma. It is also important to state that this work is reused for the 5G SA experimental project PIkeo launched in France. As part of the Istanbul release, Lukasz drove the CNF the CNF Orchestration Enhancements (REQ-627)	- With these changes introduced, information about created CNF resources in k8s cluster are now available. This information can be utilized later on i.e. in closed-loop context. CNF Healthcheck Workflow in SO will let to monitor the status of CNF deployed into k8s cluster and whether it is healthy or not. Further changes in k8splugin related to Helm spec support allow for the better and more reliable deployment of complex CNFs defined as a helm package. In addition, "ONAP for Enterprise" Task Force and "5G Super Blueprint" LFN initiative continously benefit from any CNF requirement led by Lukasz.

Anchor

	proj
	proj

S3P Improvements

...