Hi Tal Halfon, Thanks for the reply..
i agree with you that during Design-time user can set HEAT env files with actual cloud infrastructure details. But as SDC catalog maintain the Resources(VFC/VNF), Services(VF), products as a re-usable building blocks. so i am trying understand how re-suability of these building blocks is achieved. i can think Resources(VNFs) can be reused during Service Design-time(by updating the VNFs HEAT env parameters).. and Service(VF) can be reused during deployment(Run-time) through VID for different tenants, so Run-time may be need to modify HEAT env parameters based on the tenant. Please correct me if I am missing something. Regards, Ramu N ________________________________ *************************************************************************************** This e-mail and 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: Halfon Tal [mailto:halfon....@amdocs.com] Sent: Thursday, May 18, 2017 5:35 PM To: Ramu n; onap-discuss@lists.onap.org Cc: Aruna kumar padhi Subject: RE: [onap-discuss] question on SDC Hi Ramu Let me clarify my answer below - ENV file set default values, so in some case user would want to set values that in normal flow will be run time just for making testing/certification easier. Saying the above, ONAP do recommend that for production, HEAT env file will include only pseudo constant values (design time parameters) and not run time Best regards Tal Halfon Development Manager @ Amdocs P. +972 54 2213763 From: onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Halfon Tal Sent: Thursday, May 18, 2017 2:39 PM To: Ramu n <ram...@huawei.com<mailto:ram...@huawei.com>>; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Cc: Aruna kumar padhi <aruna.pa...@huawei.com<mailto:aruna.pa...@huawei.com>> Subject: Re: [onap-discuss] question on SDC Hi Ramu Regarding the first Q, The env file in the heat is used as default value, in run time different values can be provided. Best regards Tal Halfon Development Manager @ Amdocs P. +972 54 2213763 From: onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Ramu n Sent: Thursday, May 18, 2017 1:44 PM To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Cc: Aruna kumar padhi <aruna.pa...@huawei.com<mailto:aruna.pa...@huawei.com>> Subject: [onap-discuss] question on SDC Dear All, 1) as mentioned in https://wiki.onap.org/display/DW/Pre-Onboarding link, create a tenant and note tenant ID and in https://wiki.onap.org/display/DW/Resource+Onboarding#ResourceOnboarding-CVSPCreateaVendorSoftwareProduct link, attach Heat.zip package to the Vendor Software Product which contain Heat template & env files. As the Heat env contains the environment parameters (like Tenant, Network details) which are Service provider's cloud infrastructure details. why these environment parameters need to be provided during Design-time(On-boarding), because i think these are required only during Run-time(Instantiation). 2) >From the below diagram, as per my understanding Stage-1(VNF Provider) is out >of scope of ONAP, i.e. it is done in VNF Providers development environment. [cid:image001.png@01D2D00F.BF207D30] Please anyone clarify if my understanding is correct. Regards, Ramu N ________________________________ *************************************************************************************** This e-mail and 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! This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss