image-2020-09-29-20-35-03-747.png
[ICN-466] Reimplement Terminate operation as async Created: 30/Sep/20 Updated: 17/Dec/20 Resolved: 03/Oct/20 |
|
| Status: | Done |
| Project: | Integrated Cloud Native NFV |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | High |
| 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 | ||
| Attachments: |
image-2020-09-29-20-35-03-747.png
|
| Epic Link: | DCM dev works |
| Sprint: | ICN Sprint 27 |
| Story Points: | 3 |
| Description |
|
With the recent changes ot Rsync n terms of rsync registration, status query, appcontext status and others, DCM now has to asynchronously check when the appcontext status has become Terminated before finally claiming that a Logical Cloud is not applied and consequently removing all respective appcontext etcd handles. |
| Comments |
| Comment by Igor Duarte Cardoso [ 02/Oct/20 ] |
|
Additional work needed, but now close: https://gerrit.onap.org/r/c/multicloud/k8s/+/113445 |
| Comment by Igor Duarte Cardoso [ 01/Oct/20 ] |
|
After discussing with Ritu more about the status framework, abandoning https://gerrit.onap.org/r/c/multicloud/k8s/+/113346. Will reimplement terminate so that it doesn't thread and doesn't delete etcd resources on termination. Adding an extra story point. |