Versions Compared

Old Version 13

changes.mady.by.user Srinivasa Addepalli

Saved on

compared with

New Version 14

changes.mady.by.user Srinivasa Addepalli

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

ActivityOwnerStatus
K8S Plugin API definition towards rest of ONAP for compute

K8S Plugin API definition towards rest of ONAP for networking

K8S plugin API definition towards rest of ONAP for storage (May not be needed)

SO Simulator for compute

K8S plugin for compute

Instantiation time:

  • Loading artifact
  • Updating loaded artifact based on API information.
  • Making calls to K8S (Getting endpoint to talk to from ESR registered repo)

Return values to be put in the A&AI



Testing with K8S reference deployment with hardcoded flannel configuration at the site (Using EdgeXFoundry) - Deployment yaml files to be part of K8S plugin (uploaded manually)

K8S Plugin implementation for OVN

SO simulator for network

Testing with K8S reference deployment with OVN networking (using EdgeXFoundry)

Testing with K8S reference deployment with OVN with VM and containers having multiple interfaces

K8S plugin - Artifact distribution Client to receive artifacts from SDC (Mandatory - On demand artifact download, pro-active storage is stretch goal)

Above test scenario without harcoding yaml files in K8S plugin

Note: Once above list is decided,  appropriate JIRA stories will be created.


Projects that may be impacted 


ProjectPossible impactWorkaroundownerStatus
SOAbility to call generic VNF API

Until SO is enhanced to support

  • TOSCA orchestartion
  • VNF level Abstract API

SO will be simulated to test the K8S plugin and reference deployment

SO simulation owner: ???



SDC

May not be any impact, but need to see if there any impact

  • for adding new artifacts.
  • supporting download requests on specific artifcacts

Owner : Libo
A&AI AND ESR

May not be any impact, but need to see whether any schema changes are required

  • Add Kubeconfig related data on per cloud-region basis.

Check whether any existing fields in cloud-region can be used to store this information or introduce new attributes in the schema (under ESR)


Owner : Shashank and Dileep
MSB/ISTIO

No impact on MSB. But fixes required to do following:

Integration with ISTIO CA to have the certificate enrolled for communicating with other ONAP servceis

Also to communicate with remote K8S master.





Activities that are in scope for phase1 (Stretch goals)

ActivityOwnerStatus
K8S node-feature discovery and population of A&AI DB with the features

Support for Cloud based CaaS (IBM, GCP to start with)


FOLLOWING SECTIONS are YET TO BE UPDATED

...