I'd like opinions and answers on the following items:
- Has the idea of abstracting NF out of VNF and PNF been considered in the TOSCA node types proposed for ETSI NFV? I think this is of interest to the PNF team and the VES team. See the code block and then following discussion for questions.
- I know that use of TOSCA semantics was avoided in the SOL001 spec to not require a consumer of the SOL001 spec to need to use TOSCA orchestration. That means to me that SOL001 is a logical data model (LDM) that just happens to use TOSCA vs. an implementation-specific data model. ONAP is an implementation therefore it should be possible for different components to prune and refactor the model to something most useful. If a component or set of components wants to use TOSCA semantics for orchestration those component(s)are thus free to change the model. It means we could change the TOSCA proposed in SOL001 into TOSCA that DOES leverage TOSCA semantics. In the code block, you can see that capabilities are used to capture some of the information that was documented in the LDM that was captured in a node.
- I would make the following changes but it would be good to get the explanation as to how software was expected to use the following constructs:
- configurable_properties: I would move these to be the inputs of the configure operation in the interface.
tosca.nodes.nfv.NF
# There is no need to derive VNF or PNF node types at the *data model* level # Use composition to cover the differences tosca.nodes.nfv.NF: derived_from: tosca.nodes.Root properties: descriptor_id: type: string # GUID required: true descriptor_version: type: string required: true provider: type: string required: true product_name: type: string required: true software_version: type: string required: true product_info_name: type: string required: false product_info_description: type: string required: false localization_languages: type: list entry_schema: type: string required: false default_localization_language: type: string required: false # configurable_properties: # Move to interface operation for configure # type: tosca.datatypes.nfv.VnfConfigurableProperties <== remove Vnf prefix? # required: true # modifiable_attributes: #Move to interface operation for modify # type: tosca.datatypes.nfv.VnfInfoModifiableAttributes <== remove Vnf prefix? # required: true # lcm_operations_configuration: # what use is made of this and by whom? # type: tosca.datatypes.nfv.NfLcmOperationsConfiguration # description: Describes the configuration parameters for the NF LCM operations # required: true # monitoring_parameters: # type: list # entry_schema: # type: tosca.datatypes.nfv.NfMonitoringParameter # description: Describes monitoring parameters applicable to the NF. # required: false flavour_id: type: string required: true # flavour_description: # type: string # required: false # get from NFDF definition # vnfm_info: Doesn't belong in the model - want to modify list dynamically # type: list # entry_schema: # type: string # required: true #capabilities: # monitoring_parameter: # modelled as ad hoc capabilities in the VNF node template requirements: - virtual_link: capability: tosca.capabilities.nfv.VirtualLinkable relationship: tosca.relationships.nfv.VirtualLinksTo node: tosca.nodes.nfv.VirtualLink # Change to remove vnf occurrences: [ 0, UNBOUNDED ] #Work with OASIS on normative representations of compute, storage, architecture, etc. I'll just call them ExecutionEnvironmentAspects for this example tosca.capabilities.nfv.Moveable: derived_from: tosca.capabilities.Root # Only PNFs could have this capability tosca.capabilities.nfv.PhysicallyMoveable: derived_from: tosca.capabilities.nfv.Moveable # Only VNFs could have this capability tosca.capabilities.nfv.VirtuallyMoveable: derived_from: tosca.capabilities.nfv.Moveable tosca.capabilities.nfv.PurposeBuiltHostingPlatform: derived_from: tosca.capabilities.Root properties: provider: type: string required: true serial_number: type: string required: false attributes: serial_number: type: string required: true valid_source_types: []
I need to understand what all the subtyping and indirection is doing here: