JIRA | Owner | Status |
---|---|---|
ONAPARC-350 -MultiCloud K8S plugin - Helm Charts support | Kiran Kamineni | Patch is created with code changes Working on overriding the values in Helm charts Unit testing are pending |
ONAPARC-349 - K8S Plugin in Multi-Cloud to follow the instantiation NB API of Multi-Cloud | Kiran Kamineni | Yet to be done Based on VNF UUID passed by SO, it shall lookup artifacts and then act on it. |
ONAPARC-337 - Multi-Cloud to support storing Cloud specific artifacts | Exposed API to upload cloud specific artifacts in tgz form. Code is merged Unit testing is also done Functional test is to be done To Eric question:
| |
ONAPARC-348 - Multi-Cloud K8S Plugin to support profiles for resource-bundle Environment and Day0 Configurations | Defined the metadata file (Please create a file in the document directory and paste the link in the wiki page) Developing code. | |
MULTICLOUD-454 - Provider network support when OVN is used | Ritu Sood | Create multiple JIRA stories
Status:
|
ONAPARC-351 -Multi-Cloud Network subplugin & OVN support | Ritu Sood | Coding done Unit testing is done. Functional testing is yet to be done |
ONAPARC-364 - vFirewall Helm Charts & CSAR | @Akhila Kishore | Yet to be started |
MULTICLOUD-409 -EdgeXFoundry Helm Charts & CSAR | Kiran Kamineni | Helm charts are created Tested deployment using EdgeXFoundry Helm charts CSAR yet to be done |
ONAPARC-336 - SDC Client in Multi-Cloud | libo zhu | Libo in contact with PTL based on the design document. Libo |
has uploaded the design document here (K8S based Cloud-region support - Documents) | ||
ONAPARC-356 -MultiCloud K8S plugin to use information in A&AI to reach K8S Cloud regions | Getting cloud-region reachability from Multi-Cloud. Victor to check with A&AI PTL on whether there are any size limitations (Kubeconfig can go up to 10K in size) Victor also to check MC code to see who makes calls to A&AI to get cloud reachability information | |
ONAPARC-355 - K8S Cloud region reach ability information in ESR/A&AI | To be done | |
Liang Ding | duplicated by SDC-2041 | |
SDC-2041 - SDC supports K8S plugin to add cloud specific artifacts |
Liang will add the code to support a new artifact type for cloud specific artifacts | ||
SDC-2045 - create User and Password for Multicloud component to access secure api | libo zhu | |
SO-1353 - SO to be made independent of Cloud technologies | Create individual JIRA stories Eric to look at the A&AI updates being done by HeatBridge and then create JIRA story as similar stuff needs to be done by K8S plugin | |
MULTICLOUD-403 -Create CSIT for K8s plugin service | Kiran/Akhila/Ritu | Yet to be done |
ONAPARC-363 - OOM Helm charts for K8S Plugin service | Kiran | Yet to be done |
support full functional service design on k8s based VNF: In SDC service design, designer creates a service composing of 2 k8s based VNFs and a generic network to connecting them. How to support this scenario? Q1: SDC can NOT do this unless it understands the helm chart to extract those 'port' information which could be used to connect to the NS level network. Need to on-board a dummy heat VNF and do service design to see what SDC's distributed internal csar would look like. Q2: How SO understand the NS level network from SDC's distributed internal csar(NOT the onboarding zip) to create 'network' in k8s? Need to check how existing SO deal with heat VNFs about the same situation. | Yet to be done |