...
- Agenda bashing:
- PNF instance model
- UML generation: more trouble shooting, Jacqueline will look at it
- PNF instance model
- ETSI NFV release 3 enhancement for VNFD/NSD
- contribution: SOL(20)000121r2
View file name ETSI NFV SOL_WG_release_2_and 3_status_for_ONAP Modeling.pdf height 150
- contribution: SOL(20)000121r2
- latest published version of SOL release 2 specs: v2.7.1 (Jan, 2020), feed into testing and conformance
- main content for the maintenance:
- security
- extend construct of VNF packging
- SOL001:
- SOL004:
- adding signing requirement/description
- next step: v2.8.1 targeting for 2020-6-30
- SOL release 3 work:
- stage 1 and stage 2 work are complete and under maintenance (v3.4.1), feature including: host reservation, VNF snapshot, VNF software modification, network slicing, multi-site services, etc.
- stage 3: SOL009 and SOL011 are completed; SOL010, 012 and 017 are under working
- SOL001 v3.3.1 planning:
- VNFD impacted feature: VNF software modification, VNF snapshot, VNF software modification
- NSD impacted feature: network slice, multi-site, SAL
- question for modeling subcommittee:
- are there any features ONAP willing to work on?
- only network slicing for now
- policy management framework could be a potential topic
- software modification currently is PNF related in ONAP (different from ETSI)
- are there any features ONAP willing to work on?
- contribution: SOL(20)000121r2
- Modeling Documentation
- comments:
- need diagrams
- readthedocs may not be sufficient
- J
- Jacqueline would discuss with Michela to come up with a better solution
- arc team is working on documentation as well: https://safratech.net/onapdocs/
- will continue discussion once Jacqueline and Michela are ready
- comments:
- Model Proposals
- license management - review comments
- check root proposal to see the inheritance of the license classes
- agreed, will update
- agree on the scope of the license, VNF/VNFD or broader (also relate to "software" definition in the descriptions)
- current scope is only VNF
- will update "software" to "VNF descriptor"
- clarify the usage of asset management system (which is outside ONAP) and relationship with the classes in the proposal
- for further discussion
- LicenseKeyInstance and EntitlementInstance will be experimental classes, attributes will be further reviewed (Michela suggest to remove the attributes)
- Andy will check if Asset Inventory is needed, remove the descriptions if they are not described within ONAP
- give descriptions to the relationship classes
- double check the SDC UI info with the current proposal to align the attributes definitions
- Andy has created a wiki page for SDC reference: SDC Deployment Artifacts
- enlarge the scope to include "vendor" class (party proposal) and its super classes
- will add vendor and its super classes to the proposal
- relationship between VNF/VNF instance and license needs further discussion: the proposed/as-built model may be different from what vendor thinks
- further updates for typos/missing diagrams/...
- Andy will have another call with Jacqueline and Michela on Wednesday (same time slot as resource IM call) for discussing the remaining issues
- check root proposal to see the inheritance of the license classes
- 5G RAN service model
- allotted resource
- license management - review comments
- Modeling Process Discussion
- arc team involvement for M3
...