[ICN-410] Implement terminateHandler Created: 22/Jul/20  Updated: 17/Dec/20  Resolved: 29/Jul/20

Status: Done
Project: Integrated Cloud Native NFV
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Medium
Reporter: Igor Duarte Cardoso Assignee: Igor Duarte Cardoso
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: DCM dev works
Sprint: ICN Sprint 22
Story Points: 2

 Description   

Currently there is only an applyHandler function to address /apply in DCM's API. So once data is pushed to etcd, it cannot be deleted. Implement a terminateHandler to take care of this and also gRPC into RSync to delete all k8s resources (assumption for now is to blindly delete - more design discussions should be had to decide on appropriate trade-offs in terms of terminating the logical cloud).



 Comments   
Comment by Igor Duarte Cardoso [ 29/Jul/20 ]

Terminate (/terminate) is now fully implemented, all resources being deleted and multiple clusters also being targeted on deletion via the logical cluster -wide AppContext.

Updated DCM patch to incude this new capability: https://gerrit.onap.org/r/c/multicloud/k8s/+/110641/2

Closing story.

Comment by Igor Duarte Cardoso [ 28/Jul/20 ]

Implement handler is now essentially completed as well but can't close task because just like the apply, it is currently limited to a single cluster.

 

Overall recap:

  • apply/terminate work but work with 1 cluster
  • limited to the namespace resource only, for now
  • mongo, etcd, grpc, eventually things show up in k8s
Generated at Sat Feb 10 05:59:43 UTC 2024 using Jira 9.4.5#940005-sha1:e3094934eac4fd8653cf39da58f39364fb9cc7c1.