Weekly meeting (02/05/2019)

Seq	JIRA	Owner	Status

Seq	JIRA	Owner	Status
1	ONAPARC-350 -MultiCloud K8S plugin - Helm Charts support	@Kiran	Patch is created with code changes Updating with override is values done. Unit testing are pending (Will be done after return from vacation)
2	ONAPARC-349 - K8S Plugin in Multi-Cloud to follow the instantiation NB API of Multi-Cloud	@Kiran	Yet to be done Based on VNF UUID passed by SO, it shall lookup artifacts and then act on it. TBD: VNF UUID that is passed today to MC is not the VSP ID. I guess we need to raise JIRA for SO to pass additional IDs that help in looking up VSP artifacts in MC (Changes to API) - Create JIRA (AR: Srini)
3	ONAPARC-337 - Multi-Cloud to support storing Cloud specific artifacts	@Kiran	Done To Eric question: All artifacts are stored in MongoDB. Indexed by VSP IDs.
4	ONAPARC-348 - Multi-Cloud K8S Plugin to support profiles for resource-bundle Environment and Day0 Configurations	@Kiran	Defined the metadata file (Please create a file in the document directory and paste the link in the wiki page) Code done Manual functional testing is done Tested with Helm charts. Unit testing yet to be done (Kiran to do once return from vacation) Config-map is not yet done (configure file override from configuration profile) - Only override values are taken care (Kiran to do once return from vacation)
5	MULTICLOUD-454 - Provider network support when OVN is used Stories: MULTICLOUD-471 MULTICLOUD-472 MULTICLOUD-473 MULTICLOUD-474	@Former user (Deleted)	Create multiple JIRA stories for the following items To update KRD to use non-NAT libvirt networks. Explore creation of multiple providers networks and place PODs in multiple provider networks as well as virtual networks. Discovery of provider networks Create specification on how deployments describe provider networks K8S plugin enhancements & route operator in K8S regions - to Update routes in minion nodes that are hosting provider network gateways. Status: Created Multiple Jira stories for the above items Updated KRD to use routed libvirt networks and now traffic can flow both ways Working on setting up routes in the Pod through annotations needed for Provider network work Also setting up demo with a Pod, a VM and 3 Gateways

6	ONAPARC-351 -Multi-Cloud Network subplugin & OVN support	@Former user (Deleted)	Coding done Unit testing is done. Functional testing is yet to be done
7	ONAPARC-364 - vFirewall Helm Charts & CSAR	@Victor Morales @Akhila Kishore	Create helm charts and test directly using K8S plugin (Akhila and Victor) CSAR creation (once SDC client is done and SO changes are done) Status: Worked on fixing Helm and Tiller mismatch issue. Did some dry run with some helm charts. Working on understanding config map and some examples. Will try with vFW next.
8	MULTICLOUD-409 -EdgeXFoundry Helm Charts & CSAR	@Kiran	Helm charts are created Tested deployment using EdgeXFoundry Helm charts CSAR yet to be done
9	ONAPARC-336 - SDC Client in Multi-Cloud	@libo zhu	the design spec has been reviewed with MultiCloud PTL Libo has uploaded the design document here (K8S based Cloud-region support - Documents) details discussion about currently k8s API and flow. the SDC client in Multicloud is supposed to : acts as a sidecar, running with the plugin like k8s which are interested in the same pod retrieve the artifacts from SDC's distribution store it on shared volume based on specified rule (perhaps using UUID from artifact metadata) inform the plugins 's callback API. the callback API is supposed to be ONLY one, and be added into the configuration file for the each client. the API of k8s could access the artifacts from shared volume and store it into mongoDB as own choice. To provide an example configuration file.
10	ONAPARC-356 -MultiCloud K8S plugin to use information in A&AI to reach K8S Cloud regions	@Victor Morales	Getting cloud-region reach-ability 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) Got clarity on what to be done in Plugin Status: Code to talk to endpoints from MC to AAI is done. AFAIK we need make changes to the schema to store the Kubeconfig information. This still needs to be decided.
11	ONAPARC-355 - K8S Cloud region reach ability information in ESR/A&AI	@Victor Morales @Akhila Kishore	To be done Schema change ESR Change
12	_ONAPARC-335_{-Supporting Cloud specific artifacts in CSARs}	@Former user (Deleted)	duplicated by SDC-2041
13	SDC-2041 - SDC supports K8S plugin to add cloud specific artifacts	@Former user (Deleted)	Liang is modifying the code to support a new artifact type for cloud specific artifacts
14	SDC-2045 - create User and Password for Multicloud component to access secure api	@libo zhu	need check with SDC PTL about what's additional step need to do besides change catalog-be/sdc-backend-init/chef-repo/cookbooks/sdc-catalog-be-setup/templates/default/consumers.py.erb file
15	SO-1353 - SO to be made independent of Cloud technologies	@Eric Multanen @Marcus Williams	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 Status: Added stories to the EPIC and updating the wiki page https://lf-onap.atlassian.net/wiki/display/DW/SO+Adapter+to+Multicloud+Improvements All the stories are on this page. Need to run it by SO PTL and in SO call tomorrow to get feedback. Still awaiting feedback from the PRC folks. More confidence in the stories after all these discussions and stories are refined. Open: Who is working on connecting the Generic NB Multicloud Instantiation API (which will be called by SO at instantiation time) to specific plugins like K8s?
16	MULTICLOUD-403 -Create CSIT for K8s plugin service	Kiran/Akhila/Ritu	Yet to be done
17	ONAPARC-363 - OOM Helm charts for K8S Plugin service	Kiran	Yet to be done
18	https://jira.onap.org/browse/MULTICLOUD-464	@Kiran	Yet to be done