Topic Leader(s)
- Huu Trung THIEU, Nakjung CHOI
- Timo Perala
Topic Overview
| Excerpt |
|---|
Helm hook is becoming more and more important in CNF deployment which can give fine-grained control in CNF life cycle management. For complex CNFs using this feature, a support of helm hook in multicloud-k8s plugin will not only simplify the onboarding process but also maintain the same behavior/workflow in deployment/deletion process on these CNFs. Another improvement is the instantiation status report of CNF deployment, e.g., k8s resource monitoring, which is not the case in the current implementation. |
Slides & Recording
Agenda
Helm hook support motivation: Helm provides a hook mechanism to allow chart developers to intervene at certain points in a release’s life cycle.
...
Proposed enhancements
Demo
Minutes
Chat log of the session
Srini Addepalli (Intel)
Hi, this is very good problem statement. Can we continue the discussion offline? My email is : Srinivasa.r.addepalli@intel.com. In EMCO v2, we have a module called 'rsync'. Depedencies among K8s resources is a problem statement. Some times, we can't install a resource without other instance is UP and running. We have dependency graph definition on per NS basis. RSYNC module honors this dependency graph.
...
Victor Morales
@Srini, ideally the CNF internal dependencies has to be solved by CNF developer but it’s not always the case
Action Items
- Presenters to engage with ONAP CNF TF to further discuss, enhance and contribute their ideas as presented.