|
Present the ICN requirement "Adding EAA support for geo-distributed producing and consuming applications" on meeting "Biweekly engineering sync between Openness - ICN" on April 1st 2020. The meeting minutes are below:
- Thanks to Chenjie to bring up the Openness EAA services in the ONAP4K8s - https://gerrit.onap.org/r/c/multicloud/k8s/+/104825
- Chenjie explained regarding the workaround on the root certs -https://gerrit.onap.org/r/c/multicloud/k8s/+/104825/2/kud/tests/openness/eaa/helm/eaa/templates/eaa-tls.yaml, Krishna suggested to work with Patryk to create a JIRA ticket for eaa rbac work for kuberneters cluster
- Krishna suggested Openness 20.03 is having Helm support, suggested Patryk to leverage from the Chenjie patch
- Krishna invited Huifeng, Chenjie and Kural for Openness Jira ticket https://openness.atlassian.net/secure/RapidBoard.jspa?rapidView=3&projectKey=OP
- Chenjie, Krishna and Kural discussed regarding challenges in micro services spread across the multi-cluster in the multiple edge location
- Chenjie and Kural explained regarding the DCM in ONAP4K8s, and how the network connectivity between multiple cluster is abstracted by Isitio Control plane(ISP) per cluster in DCM and logical cloud spread across the edge location
- Huifeng explained regarding the SDWAN CNFs used to along with SDWAN and IPsec controller to create the secure tunneling between edge location, so that both the control plane and data plane between the edge location are secured.
- Krishna showed interest to understand more on the ONAP4k8s details. Kural suggested to have meeting with Ritu Sood for next week to discuss architecture understanding on ONAP4K8s, and how it works with Krishna team
- Krishna suggested to work along in JIRA moving forward and to have technical discussion among engineers.
|