Hello Yuanhong In ONAP Dublin, there is no CFS and no RFS.
There is only “service” class and NBI allow only to order “service”. And “service” is composed of VF and/or Virtual Links. My personal mapping : “service” notion is equal to the “RFSspecification” notion If you need a “two-level” service layer (CFS and RFS), then you need an external application such as Service Resolver. https://gitlab.com/Orange-OpenSource/lfn/onap/service-resolver With Service Resolver, we do not transfer CFS “inputs” to RFS “inputs”. We order CFS and Service Resolver then order each RFS that composes the CFS. We think that ONAP CDS system will be able to resolve all RFS “inputs” thanks to predefined templates/blueprint files. Those templates explain to ONAP CDS how to get “input” values. For example, if RFS need an IP address, the template explain how to get an IPaddress value when instantiating that RFS. Best regards De : dengyuanhong [mailto:dengyuanh...@chinamobile.com] Envoyé : mardi 6 août 2019 09:09 À : onap-discuss@lists.onap.org; ROBERT René TGI/OLN Objet : 答复: [onap-discuss] How to call API to create a service order Hello Rene, Thank you very much. The example you have given is CFS order, but I think it is same with service order API of NBI since they are both based on TMF API. However, I still have question about how to transfer CFS “inputs” to RFS “inputs”. Do you have any idea about this? Thanks and regards, Yuanhong 发件人: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] 代表 Rene Robert via Lists.Onap.Org 发送时间: 2019年8月5日 23:25 收件人: onap-discuss@lists.onap.org; dengyuanh...@chinamobile.com 主题: Re: [onap-discuss] How to call API to create a service order Hello Yanhong “target” is no necessary (only in the east-west usecase, with two ONAP instances) you are right about ServiceCharacteristic : this is the place where to put “inputs” of the service. Here after, an other example with a ServiceCharacteristic curl -X POST \ 'http://{{url-serv-resolv-service-order}}/cfsOrder' \ -H 'Content-Type: application/json' \ -H 'cache-control: no-cache' \ -d '{ "category": "mailBox service", "description": "service order for mailBox customer service", "externalId": "Customer_01", "note": { "author": "Orange", "date": "May 2019", "text": "" }, "notificationContact": "", "orderItem": [ { "action": "add", "id": "1", "service": { "name": "mailBox_01", "place": [ { "id": "", "name": "", "role": "" } ], "relatedParty": [ { "id": "JohnDoe", "name": "JohnDoe", "role": "customer", "href": "" } ], "serviceCharacteristic": [ { "name": "featureLevel", "value": "simple" } ], "serviceSpecification": { "id": "{{auto_mailBox_cfs_spec_id}}", "name": "mailBox", "version": "1" }, "serviceState": "active", "serviceType": "" } } ], "priority": "1", "relatedParty": [ { "id": "JohnDoe", "name": "JohnDoe", "role": "customer", "href": "" } ] }' Some documentation (maybe you have already seen) : https://onap.readthedocs.io/en/latest/submodules/externalapi/nbi.git/docs/offeredapis/offeredapis.html https://onap.readthedocs.io/en/latest/guides/onap-user/instantiate/instantiation/nbi/index.html De : onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] De la part de Deng Yuanhong Envoyé : lundi 5 août 2019 12:36 À : onap-discuss@lists.onap.org Objet : [onap-discuss] How to call API to create a service order Hi Team, I am trying to call API of NBI to create a service order. According to the document, serviceOrder and target should be provided in request. I have the followed question about these parameters: 1. Where should I set the inputs of the service? I think the inputs should be set in ServiceOrder -> ServiceOrderItem -> Service -> ServiceCharacteristic, is it right? 2. What is target? I can’t find any explanation for it. What value should I set for it? Thank you in advance for your help. Best regards, Yuanhong _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#18441): https://lists.onap.org/g/onap-discuss/message/18441 Mute This Topic: https://lists.onap.org/mt/32741175/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
