Hi Sirisha Ok, Was guessing its vCPE Tosca you were working on based on the question. Thanks for clarifying it. There is no mandate for all the calls of E2E service to end up at VFC. The E2E service has a resource loop execution that is received by the csar distributed by the SDC (/config file) and the decision for the calls to corresponding adapters is taken on runtime. Coming to the specific issue you are facing here, is it possible to share the NSD yaml file /the details of model of what you are trying to orchestrate to make me help you better.
Thanks and Regards, M Seshu Kumar Senior System Architect Single OSS India Branch Department. S/W BU. Huawei Technologies India Pvt. Ltd. Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield Bengaluru-560066, Karnataka. Tel: + 91-80-49160700 , Mob: 9845355488 [Company_logo] ___________________________________________________________________________________________________ This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! ------------------------------------------------------------------------------------------------------------------------------------------------------------------- From: [email protected] [mailto:[email protected]] On Behalf Of Gopigiri, Sirisha via Lists.Onap.Org Sent: Wednesday, September 18, 2019 4:04 PM To: Seshu m <[email protected]> Cc: [email protected] Subject: Re: [E] RE: [onap-discuss] #so Network Service and E2E Service distribution Issues in SO Hi Seshu, Thank you for the reply! I am referring to vCPE tosca usecase. Did you notice any exception in the ASDC controller pod logs esp while parsing? - No I guess it is expected as you mentioned If the VF has heat artifacts only then the catalog DB vnf_resource/vf_modules tables are getting populated. Is it expected -- If it is expected the what is the approach for E2E Service types? I understand that the tosca based Network Service details not getting populated in catalog DB as the instantiation is happening through VFC. My concern is about the E2E service type which has the NSD VF in it whose details are not getting populated in the DB as there are no heat artifacts associated with it and the Service instantiation is failing because of this. Do you have any documentation related to E2E Service creation? To brief on how I created the E2E service, it has only one NSD VF with providing_service_uuid/providing_service_invariant_uuid populated. Am I missing something with E2E Service creation is SDC? Best Regards Sirisha Gopigiri On Wed, Sep 18, 2019 at 3:42 PM Seshu m <[email protected]<mailto:[email protected]>> wrote: Are you referring to the Vcpe Tosca usecase or the Vcpe Heat usecase here? Did you notice any exception in the ASDC controller pod logs esp while parsing? If the VF has heat artifacts only then the catalog DB vnf_resource/vf_modules tables are getting populated. Is it expected The heat templates are populated for the case where we have the VFM for a given VNF. Thanks and Regards, M Seshu Kumar Senior System Architect Single OSS India Branch Department. S/W BU. Huawei Technologies India Pvt. Ltd. Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield Bengaluru-560066, Karnataka. Tel: + 91-80-49160700 , Mob: 9845355488 [Company_logo] ___________________________________________________________________________________________________ This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! ------------------------------------------------------------------------------------------------------------------------------------------------------------------- From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Gopigiri, Sirisha via Lists.Onap.Org<http://Lists.Onap.Org> Sent: Wednesday, September 18, 2019 3:28 PM To: [email protected]<mailto:[email protected]> Subject: [onap-discuss] #so Network Service and E2E Service distribution Issues in SO Dear SO Team, I have ONAP Dublin OOM based setup installed. I am trying to create vCPE Service from CSAR packages available in the git demo repository https://github.com/onap/demo/tree/dublin<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_onap_demo_tree_dublin&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=5PWCtn_zD8jT6xuuwP7DpGwXiA7-u1RBXx8E9Vrv2NI&m=IOyQUutm5b5yy9zpWJ-2qjzmP14UNvUsk69uvH5WBsM&s=l0ZhIs0SBJsc4GPXrOWdoYvF2HDZpoUEzABxeGA-OSQ&e=> . When I distribute the Service from SDC, the distribution was successful to SO, it didn't report any errors. But the VF/VNF details are not populated in the SO catalog DB tables. If the VF has heat artifacts only then the catalog DB vnf_resource/vf_modules tables are getting populated. Is it expected. I have the same issue when I create E2E service where the VF in it doesn't have the VF modules in it. As the DB is not populated properly I am unable to instantiate the Service as well in case of E2E Service. Am I missing something here? Could you please help me with the issue? Thank you in advance! Best Regards Sirisha Gopigiri -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#18995): https://lists.onap.org/g/onap-discuss/message/18995 Mute This Topic: https://lists.onap.org/mt/34186338/21656 Mute #so: https://lists.onap.org/mk?hashtag=so&subid=2740164 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
