Attendees:
HPA Telemetry
Q&A:
Q: Delivery plan:
A: Start it in C. Release, no commitment what can be delivered
Q: Seed code:
A: N/A
Q: Deployment topology: will be a single collector running for any kind of underlying VIM/Cloud type.instance?
A: Not clear yet.
Q: Configuration API/portal:
A: N/A for now, but eventually be there,
Q: Will the API/IM be generic to be VIM/Cloud agnostic ?
A: not clear yet
Q: Is there any dependency to AAI model/schema
A: There is a schema change to AAI in progress (Dileep)
Q: Is this schema be generic (VIM/Cloudagnostic?)
A: Supposed to be generic
Q: Will the collector? Be impacted by different agent on VIM/Cloud ?
A: not clear yet
Q: Why not DCAE VES collector /microservice? Please evaluate this option.
A: no answer yet
suggestion (Bin Yang ) If there can be just 1 collector for all VIM/Cloud instance/types, you can have dedicate repo
Otherwise, share the existing repos following the broker/plugin topology
AI: Eric Multanen figure out the questions above, then decide whether a dedicated repo needed.
Update from each plugin owners:
OpenStack plugin:
Huang Haibin
Pike: submitted all patch
Test plan: in Intel lab. Pairwise testing, no e2e testing.
Refactor HPA common codes into newton_base
Defer StarlingX to D. release
SRIOV-NIC support : In progress
Test plan: CMCC lab, pairwise, E2e: vCPE with VFC, (tosca based VNF), any support from integration ? Not yet , Alex will going to check that?
HPA telemetry data collection and persistence
Under discussion
VIO plugin:
Consistent ID: In progress
Test plan: CMCC lab
Server action API: (for VFC) In progress
Test plan: CMCC lab
SO/MC API: In progress
Test plan: Integration lab (Besides Wind River Titanium Cloud, VMware VIO is also deployed – Link: Physical Labs) or VMware Open DMZ Lab (In progress)
Onappyloggying for python3: In progress
Upgrading plugin to support VIO 5.0
SR-IOV: not sure, depend on bandwidth
Risk: speed up review process. Any blocking issue? No.
K8S plugin:
Seed code: merged
Translation of
KRD? K8s reference design, a base for k8s
Present the workflow of k8s plugin
Wind River plugin:
Consistent ID:
Done,
Test plan: Integration lab, CMCC lab
UC: CCVPN, vFW/vDNS
Upgrade for Wind River TitaniumCloud:
Multi-region onboarding:
Done,
Testing plan: pairwise test in integration lab
SO/MC API :
API handler stub ready
Test plan: vCPE (heat based) in integration lab
Deploy MultiCloud service to edge cloud with AAI in centralized ONAP
Not started yet
Cloud Region Decommion:
Not yet
SR-IOV:
Will share with OpenStack plugin
Azure plugin:
Not clear
Security enhancement: (secured communciation, RBAC)
Done by MSB PTL,
Pairwise:
CMCC lab, with VFC
Cloud agnostic intent:
Follow the HPA approach: discovery via flavor, no specific logic to realize (who will translate the intent to your specific capability/feature) it except flavor id updating?
AI: Bin Yang Offline discussion with Ethan
sdc client
Q: What is the best repo
AI: Bin Yang Share the multicloud architecture with rama
AI: ramamani yeleswarapu figure out how a plugin could access the artifacts distributed to the SDC client, then the above question of repo could be answered.