...
- Introductions
- Modeling Update Kevin Scaggs Former user (Deleted)
- References across sub-models is having issues (may be Papyrus issue). For now, remove circular references in models.
- R2 model is in Papyrus, R3 updates are in progress
- Runtime contribution on VNF and VNFC being modeled
- About 90% of VES model is incorporated.
- Doing updates in working branch (does not indicate any level of approval)
- But needs commits into repo
- May need additional committers for model repo (ONAP Modeling Project)
- Master branch commits need to follow review process before commits.
- Whole sub-model needs to move to Master branch (Gerrit "Cherrypick") when "approved"
- Need process to use stereotypes to represent maturity of pieces of sub-model.
- Discussion on ETSI VNFD on External Connection Points Arun Gupta
- VNF Ext CPD maps to either VDU CPD or Virtual Link Desc
- In cases where Ext CPD Maps to Virtual Link Desc, how is this Ext CPD realized? Is it a CP on an internal Router
- First check SOL001 to understand DM representation. Perhaps follow-up with ETSI SOL and Editor of IFA015 to see get better understanding.
- Resource definition in HEAT and TOSCA Alex Vul
- vCPE VNFs being translated from HEAT to TOSCA. There is infrastructure flavor id for VNF in HEAT.
- How is this infrastructure flavor transformed into TOSCA VNFD (encoding of infrastructure is not present)?
- Flavor ID should be mapped to TOSCA VNFD requirements.
- Last time
- Introductions
- VES Descriptor inclusion into VNF Package alok411
- Kevin is updating model in Papyrus
- VES On-boarding requirements and sample
- VES support for infrastructure and PNFs (need inventory and topology in AAI and blueprints in SDC)
- The VES requirements may be found here: ONAP SA VES Specification 7.0.pptx
...