JIRA
Owner
Status
Updating AAI upon successful instantiation of resource bundle.
Monitor Resources and Update AAI and any other data stores
Map AAI model to kubernetes resources and their status
Jira 457 - Thamlur Raju - Raju will validate the vServer to Pod mapping. Raju to send out email to start discussion
Jira 675 Kiran Kamineni Patch in review for Operator for collecting data. Working on adding the API endpoint that will give the information
Jira 754 - In Progress. Kiran provided information to Raju.
Add support for logging
Logging support wiki was updated with the API flow and details about the various logging options.
No update from Raju yet.
wiki for Logging Support with details
Figure out how to keep track of dependent resources
Cache kubernetes clients instead of creating one everytime
Convert two part api to a single multipart API
Add Find/Get method to get instance for a particular profile
label resources created via instances
Use docker like names to identify instances instead of random strings
Cloud Security and Authentication using ISTIO
Subtasks:
Provide Helm chart for ISTIO installation
Modify helm charts for micro services to enable Auto istio-injection
Testcase to Create users and give them access to only specific resources
Provide Authentication and Authorization by OAuth (Insider Cluster)
Add Helm charts of SSHSM, SMS and Multicloud k8s into ONAP4K8S
Jira 710 was merged. This Installs Isitio Operator.
Jira 711 This configures Isitio. The review is complete. Ready to be merged.
Jira 714 - Authentication server functionality. Adds authorization support to ISITIO. Still working on POC with ORY/Hydra and ORY/Oathkeeper.
Jira 713 - Will figure out more details once the PoC is done
Jira 771 - Patch is submitted. Tested and deployed in local server.
OVN Network Operator
Completed testing CRD for adding Networks with KUD and also updated KUD to use this new framework. Uploaded patch for integrating with KUD.
https://gerrit.onap.org/r/#/c/multicloud/k8s/+/93602/
The plugin is renamed to NFN (Network Function Networking) Operator.
Patches need review.
OVN Provider Network and Routes operator
Started work on adding support for Provider Network CRD Controller. Added an agent that runs on all the nodes to configure local changes required on specific nodes
investigate the aai update schema used by workloads
Done
Examples are being documented here: AAI Update after Resource Instantiation#ExampleofAAIdataforvFW(non-K8S)usecase
investigate calls used to update AAI
Done
Examples are being documented here: AAI Update after Resource Instantiation#Heatbridgecode
Determine heat template needed to avoid preload for k8s workload
Work in Progress. Plan to finish it in El Alto.
Is there some way to avoid interaction with SDNC? Is it a VID issue?
Distribution error for type SO for CLOUD_TECHNOLOGY_SPECIFIC_ARTIFACTSOPEN
Support v1 and v2 vnf adapter api
Work in progress. Did some experimentation. Seems like it works.
Plan to finish it in El Alto.
support for secure communications between SO and Multicloud
Investigate running closed loop with K8S vFW
SO-2234 - Add a Service to allow netconf mount to packet generator OPEN
SO-2235 - Define the Data for a vfw K8S vserver object in AAI OPEN
SO-2236 - Support taking in parameters for the vFW k8s OPEN
SO-2237 - support an instance specific sourceName for vFW K8S VES event OPEN
Added vServer item for vFW in AAI and configured policy changes. With this able to see vFW events and DCAE collector is receiving it. Policy is reacting to k8s events. Intermittent failures.
Using the nodeport IP (host IP) and port to communicate with APPC. This information needs to be manually configured for APPC.
Able to mount netconf from APPC. Created a new service for packetgen. Able to communicate/query from APPC to packetgen running in K8s cluster. vFw Helm chart will need to be modified.
VFW sends out VES events. Those are sent to DCAE collector. Script was enabled with correct configuration and triggered manually. To automate will require a change to Helm chart to pass in correct parameters.
Wiki was created on how to setup vFW closed loop
Setting up Closed Loop for K8S vFW - initial pass
2234 - in progress
2235 - example done - suggest vserver as pod name
2236 - should just require adding parameters to the profile
2237 - uses pod name if openstack metadata service blocked
Update wiki for broker issue
Outdated container in the multicloud-k8s-4.0.0 chart
Jira 718 - Patch was submitted.
Liang will update wiki.
KUD plugin.sh test fails for vnf instantiation as cloud-region not found
MULTICLOUD-676
Tweak install scripts to enable clean reinstall on the same machine
MULTICLOUD-686
Enable testing for working plugins during installation
Merged. CI issues. Virtlet tests are failing.
MULTICLOUD-707
Provide KUD-testing CI visibility at gerrit review level
On hold (waiting for LF response)
LFN contacted with Konard and explained them what is needed. TSC approval may be required. Konard sent an email summarizing the issue. No response to the email on the mailing list.
Add to TSC mailing list and add to agenda for next week.
MULTICLOUD-708
vFw testing with Plugin
MULTICLOUD-690
Correct issues in KUD Addons installation