Recording: 20200717 CNF Weekly Meeting.mp4
Pending Initial Tasks (REQ 394 Needs Prioritization into a Release and Contributors assigned to its items) Beyond Guilin Timeframe
1.Describe the Information Element in words
-Please provide any relevant references, such as other standards, etc.
2.Define the properties (e.g., attributes, known relationships, etc.)
3.Where does this information come from? (i.e. originator)
4.Who uses this information inside & outside of ONAP? (i.e. consumers)
-How do they use it?
5.Who updates this information inside & outside of ONAP? (i.e. producers)
6.Where will this information stored and maintained in ONAP? (i.e. steward)
7.Perform UML Modeling (including mapping to existing concepts)
8.Prioritization for ONAP Releases
9.Identify impacted ONAP schemas & APIs
-Are there existing schemas be used or extended?
10.Develop implementation schema (identify component impacts on schema changes)
Project tickets for modeling effort:
AAI-2929 - Getting issue details... STATUS
Information Elements
We need to understand which are the key elements ONAP needs to be aware of. Those should be driven from the use case flows.
This Week's Agenda:
Lukasz Rajewskiwill discuss the health check use case broken down into more details
Milind Jalwadi to share some details on the work he has been doing
Next Week's Agenda:
TBD
Attendees:
@Marian Darula (Ericsson)
| Topic | Contributors | Comments |
|---|---|---|
| Inventory mS architecture | Milind Jalwadi | Presented his existing use case use of the aai model with some cnf details (modeled as vservers and vf-modules) |