Ramu When creating the Vendor Software Products (VSPs), the YAML files and their corresponding ENV files must be uploaded to SDC. SDC reads the original ENV files and re-generates the ENV files. The original ENV files are discarded in the process. The re-generated ENV files are distributed to MSO.
Regards, Alan From: onap-discuss-bounces at lists.onap.org [mailto:[email protected]] On Behalf Of ROSE, DANIEL V Sent: Monday, April 24, 2017 10:56 AM To: Ramu n <ramu.n at huawei.com>; onap-discuss at lists.onap.org Cc: Aruna kumar padhi <aruna.padhi at huawei.com> Subject: Re: [onap-discuss] SDC Artifacts List question ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. HEAT, Nested HEAT, ENV, get-files (for VF Modules) row is what I am familiar with and that is uploaded during vf module creation. I am not sure if SDC may generate a parent one when you create a service Thanks, Daniel Rose ECOMP / ONAP com.att.ecomp 732-420-7308 From: onap-discuss-bounces at lists.onap.org<mailto:onap-discuss-bounces at lists.onap.org> [mailto:[email protected]] On Behalf Of Ramu n Sent: Monday, April 24, 2017 10:52 AM To: onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org> Cc: Aruna kumar padhi <aruna.padhi at huawei.com<mailto:aruna.padhi at huawei.com>> Subject: [onap-discuss] SDC Artifacts List question Dear All, According to https://wiki.onap.org/display/DW/SDC+Artifacts+List<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_SDC-2BArtifacts-2BList&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=TQyP5ed9iT7gtbq_Cn9gU5wGB2YE4GLmXrAs5W3PyKc&s=f1rFVPcc7FVtFu56UmYVT0zjOgLY4yqVRgqYB93hPVA&e=>, ENV files source is mentioned as SDC generated. But while creating Vendor Software Products (VSPs) HEAT/ENV files are manually uploaded from the artifacts package zip file. Please anyone help me to understand How and When ENV files are generated by SDC ? Artifact Source Stored in SDC as Distribution type Distribution target Base HEAT Template Manual upload Resource TOSCA Model Resource Deployment Artifact HEAT (Base) MSO Base ENV File SDC generated Resource TOSCA Model Resource Deployment Artifact ENV (Base) MSO Volume HEAT Template Manual upload Resource TOSCA Model Resource Deployment Artifact HEAT (Volume) MSO Volume ENV File SDC generated Resource TOSCA Model Resource Deployment Artifact ENV (Volume) MSO Network HEAT Template Manual upload Resource TOSCA Model Resource Information Artifact Manually spun up _ Network ENV SDC generated Resource TOSCA Model Resource Information Artifact Manually spun up _ Inventory Model (subgraph definition) Manual upload Resource & Service Deployment Artifact MODEL_INVENTORY_PROFILE (XML) AAI Inventory Model Named Query Specification Manual upload Resource & Service Deployment Artifact MODEL_QUERY_SPEC (XML) AAI Vendor License Model SDC screens SDC generates artifact Resource Deployment Artifact VENDOR_LICENSE (XML) ALTS VF License Model SDC screens SDC generates artifact Resource Deployment Artifact VF_LICENSE (XML) SDNC, APPC Service Config File Manual upload ISBC has 1 JSON and 2 YAML files Resource Deployment Artifact APPC_CONFIG 1 JSON and 2 YAMLs APPC HEAT, Nested HEAT, ENV, get-files (for VF Modules) Manual upload and screens to collect additional info to include in distribution as metadata Resource Deployment Artifacts HEAT, HEAT_VOL, HEAT_ENV, HEAT_NESTED, HEAT_ARTIFACT, HEAT_NET MSO VF input parameters for VID SDC displays screens to collect info, then maps into TOSCA model VF-level TOSCA Model _ VID through API AAI subgraph models Generated by SDC based on inventory model creation tool Resource and Service _ AAI Named Queries Specifications Generated by SDC based on screen inputs (need to verify) Resource and Service _ AAI PNF Profile Manual upload Resource Deployment Artifact JSON SDNC, MSO 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! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170424/a48e71bf/attachment.html>
