General Information:
- Date and Time: 2018, Oct 15, 9pm~10pm Beijing Time, 9am~10am US Eastern
- Meeting Room: https://zoom.us/j/645982535
Agenda:
- Allotted Resource Model
- VES Model
- Brainstorming for R4 planning
Material:
- Allotted Resource
vCPE CSAR from April showing current Allotted Resource TOSCA (note: the Tunnel Xconn is the object of interest).
Useful Links:
- JSONSchema to UML link provided by Jessie S Jewitt
VNF Configuration, Understanding the available options link provided by Thinh Nguyenphu
Minutes:
- Allotted Resource Model
- Example: vCPE use case, Chesla would contact Gil for detailed information, the information would be provided to the mailing list after the call
- Related wiki pages:
- draft IM model: Allotted Resource
- new DM implementation proposal: Allotted Resource Model
- Terminology: FFS
- Question:
- Is VFC using allotted resource? No
- Relationship with "facade" proposal? "facade" is for nesting services, allotted resource is like product of infrastructure service. "facade" is new proposal for R4. Allotted resource has been implemented by SDC.
- VES Model
- wiki available at VES 7.1
- json to uml tool could be used generating the model: https://github.com/SOM-Research/jsonSchema-to-uml
- Question:
- ETSI spec IFA027 defines measurement metrics, suggest to align the VES model with the spec
- How ONAP components (SO, DCAE, etc.) deal with the VES model? Should modeling team discuss "workflow"s as well?
https://wiki.onap.org/display/DW/Casablanca shows some process related to the VES model
- suggest to start with the use case / workflows, and document the requirements (modeling, metrics, etc.), perhaps collaborate with VNF Req team
For CSAR, the ETSI non-MANO extension would be used to capture VES information (VES descriptor)
- R4 plan brainstorming
- not discussed
- Kevin has created a wiki on R4 high level requirements: ONAP R4 Modeling High Level Requirements
1 Comment
Chesla Wechsler
Thinh Nguyenphu - in the deck explaining the configuration, I see sequence diagrams where the VNF instance is called. The VNF is a logical entity made up of VNFC instances. How would, e.g., the NFVO or controller know how to call the VNF? Is it via a particular/standard external connection point? Thanks.