[ICN-382] Design+document APIs for Service Mesh deployment controller Created: 17/Jun/20 Updated: 22/Oct/20 Resolved: 22/Oct/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 20, ICN Sprint 21 |
| Story Points: | 2 |
| Description |
|
According to request from Srini to Itohan: "Can you also develop APIs for 'Service Mesh deployment controller" too. As Pramod Raghavendra Jayathirth mentioned, there are few parameters that need to be deployed in addition to deploying workloads. It is good to come out with that API to ensure that we are all on the same page."
|
| Comments |
| Comment by Igor Duarte Cardoso [ 22/Oct/20 ] |
|
Abandoned. This is like what will become the cacontroller in EMCO. |
| Comment by Igor Duarte Cardoso [ 22/Jul/20 ] |
|
Moving this back into the backlog as it's not needed at this time. |
| Comment by Igor Duarte Cardoso [ 17/Jun/20 ] |
|
See https://wiki.onap.org/pages/viewpage.action?pageId=76875956 |