I'd like to provide information on a number of service related nodes and attributes within the A&AI OXM schema. A number of them can be considered deprecated for the purposes of ONAP, but need to remain in place until the feature to support multiple OXM files is stable and committed in A&AI. This will allow ONAP users to separate the platform pieces from information they might require internally.
Service-capability – this node type is deprecated. It is a legacy item that filled the gap when the SDC component was being created.
Service-type (within the service-subscription node type) – this attribute maps to the service-type within the service capability node type and is also a legacy item that filled the SDC gap. Consider it deprecated.
Service – this node type was an intermediate step between service-capability and full SDC availability. It should also be considered deprecated. The SDC models themselves should fill the role of this node.
The service-description attribute thus can be considered legacy. Consider it deprecated.
The service-id attribute within generic-vnf, l3-network, and others is also deprecated and should not be used.
The vnf-type attribute is being superceded by the nf-type, nf-role, and nf-function attributes.
1 Comment
Chesla Wechsler
I'd like to provide information on a number of service related nodes and attributes within the A&AI OXM schema. A number of them can be considered deprecated for the purposes of ONAP, but need to remain in place until the feature to support multiple OXM files is stable and committed in A&AI. This will allow ONAP users to separate the platform pieces from information they might require internally.
Service-capability – this node type is deprecated. It is a legacy item that filled the gap when the SDC component was being created.
Service-type (within the service-subscription node type) – this attribute maps to the service-type within the service capability node type and is also a legacy item that filled the SDC gap. Consider it deprecated.
Service – this node type was an intermediate step between service-capability and full SDC availability. It should also be considered deprecated. The SDC models themselves should fill the role of this node.
The service-description attribute thus can be considered legacy. Consider it deprecated.
The service-id attribute within generic-vnf, l3-network, and others is also deprecated and should not be used.
The vnf-type attribute is being superceded by the nf-type, nf-role, and nf-function attributes.