Presentation is loading. Please wait.

Presentation is loading. Please wait.

TMForum-ONAP API Comparison Abinash Vishwakarma(Netcracker), Nigel Davis(Ciena) 08 , 2017.

Similar presentations


Presentation on theme: "TMForum-ONAP API Comparison Abinash Vishwakarma(Netcracker), Nigel Davis(Ciena) 08 , 2017."— Presentation transcript:

1 TMForum-ONAP API Comparison Abinash Vishwakarma(Netcracker), Nigel Davis(Ciena)
08 , 2017

2 Agenda NS,VNF, PNF Concept in ONAP and TMF
ONAP Service API Vs.TMForum RF ONAP VNF Instance API Vs.TMForum RF Next steps

3 NS,VNF, PNF Concept in ONAP and TMF
Service – a collection of one or more resources that are connected together and are connected to other services to provide functional capabilities that, when deployed in a service provider’s network, can be packaged into a Product/Offer. It is an E2E service from provider point of view and CFS from order point of view. Resource – an individual functional capability that can be combined/connected with other individual capabilities to form a Service. This is a basic building block that is modeled generically, and when included in a service, can be customized to meet the needs of the service. Virtual Function (VF) / Virtual Network Function (VNF) Virtual Function Component (VNFC) Connection Point Virtual Link (VL) Allotted Resource (AR) Collectors and other Resource types Services are further divided as Infrastructure services - deployed prior to any customer request for a service, assumed to be up and running and ready to provide their services when a customer order is received. General infrastructure - Can be used for/by many services. Specific infrastructure - Functions required and used solely by the Specific customer service. Customer service -Deployed on a per customer order basis, utilizing the various infrastructure services. TMForum: TMForum defined an entity called ResourceFunction, according to TMForum concept VNF, PNF and NS all can be realized through single entity ResourceFunction. A ResourceFunction specifies a function as a behavior to transform inputs of any nature into outputs of any nature independently from the way it is provided. It is typically created by a function designer who may not have specific knowledge on realization architecture (for example using English text explanations with diagrams, as in RFC standards, or preferably a machine interpretable language). NetworkFunction, OfficeFunction as well as GameFunction are examples of specialization (of ResourceFunction). A ResourceFunctionSpec is associated to a ResourceFunction in order to indicate the expected mandatory and optional characteristics. Document used for comparison of the APIs: TMForum : TMF664_Resource_Function_Activation_and_Configuration_API_REST_Specification_R17.0.0 ONAP: OpenEcomp_VID_MSO_API

4 ONAP Service API Vs.TMForum RF
ONAP Service Instance Create: Only create NS Instance. Instance is created in AA&I. In ONAP a service instance is associated with customer and its subscription which is part of A&AI and must be created before service instance. The scope of NS is very close to CFS in TMForum SID model. TMForum RF Create: ResourceFunction represents both NS, VNF and PNF hence all can be created. Created instance is part of Entity model. There is no concept of infrastructure or customer centric RF in TMF. ONAP Service Instance Delete: Is only the NS Instance deleted or its constituent resource too. TMForum RF Delete: Resource function instance is deleted. ONAP Service Instance Update: Indirect update see VNF create TMForum RF Delete: Direct update ONAP Service Instance Query: Not available TMForum RF Query: Available

5 ONAP VNF Instance API Vs.TMForum RF
ONAP VNF Instance Create: VNF is part of NS when created. Hence ultimately updates the NS. TMForum RF Create: Standalone create is possible. ONAP VNF Instance Delete: VNF which is part of NS can be deleted. TMForum RF Delete: Standalone delete is possible.

6 Next Steps The present analysis is done at high level. Detailed analysis is to be done as part of next step. Analysis is done between the APIs only. Do we need to consider the RESTful design principle and guidelines too as part of analysis? VNF Instance management is very interesting topic. Though ETSI implementation is not in the scope of this analysis but ETSI Os-Ma reference point doesn’t support VNF instance management. It will be good to consider ETSI implementation too in this analysis. We can start liaison with TMForum to validate our understanding and with question too.


Download ppt "TMForum-ONAP API Comparison Abinash Vishwakarma(Netcracker), Nigel Davis(Ciena) 08 , 2017."

Similar presentations


Ads by Google