Thanks Ahmad, I?ll try it out.
Beejal From: Ahmad, Munir [mailto:[email protected]] Sent: Wednesday, April 19, 2017 1:39 PM To: ROSE, DANIEL V <DR695H at att.com>; Beejal Shah <Beejal.Shah at amdocs.com>; WEINSTOCK, ALAN M <aw2574 at att.com>; onap-discuss at lists.onap.org Cc: Michael Ryan <Michael.Ryan at amdocs.com> Subject: Re: [onap-discuss] SDC Heat Manifest Question Hi Shah I have used OTHER when including config files and was able to import to SDC successfully. I changed/added a few lines to your MANIFEST.json it should work now. I { "name": "Test", "description": "Test manifest", "data": [ { "file": "someVNF_base.yaml", "type": "HEAT", "isBase": "true", "data": [ { "file": "someVNF_base.env", "type": "HEAT_ENV" } ] }, { "file": "someVNF_vnfA.yaml", "type": "HEAT", "isBase": "false", "data": [ { "file": "someVNF_vnfA.env", "type": "HEAT_ENV" } ] }, { "file": "nested1.yaml", "type": "HEAT", "isBase": "false" }, { "file": "nested2.yaml", "type": "HEAT", "isBase": "false" }, { "file": "boot_1.sh", "type": "OTHER", "isBase": "false" }, { "file": "boot_2.sh", "type": "OTHER", "isBase": "false" } ] } From: <onap-discuss-bounces at lists.onap.org<mailto:onap-discuss-bounces at lists.onap.org>> on behalf of "ROSE, DANIEL V" <DR695H at att.com<mailto:[email protected]>> Date: Wednesday, April 19, 2017 at 1:32 PM To: "SHAH, BEEJAL" <beejal.shah at amdocs.com<mailto:beejal.shah at amdocs.com>>, "WEINSTOCK, ALAN M" <aw2574 at att.com<mailto:aw2574 at att.com>>, "onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>" <onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>> Cc: Michael Ryan <Michael.Ryan at amdocs.com<mailto:Michael.Ryan at amdocs.com>> Subject: Re: [onap-discuss] SDC Heat Manifest Question Unfortunately no I am not aware. Maybe someone from SDC can comment. Also make sure you are following the naming guidelines (pasting from alan?s email): In order to enable OpenECOMP to understand the relationship between Heat files, the following Heat file naming convention must be followed. ? The file name for the base module Heat template must include ?base? in the filename. o Examples: base_xyz.yml or base_xyz.yaml; xyz_base.yml or xyz_base.yaml ? There is no explicit naming convention for the add-on modules. o Examples: module1.yml or module1.yaml ? All Cinder volume templates must be named the same as the corresponding Heat template with ?_volume? appended to the file name. o Examples: base_xyz_volume.yml or base_xyz_volume.yaml; xyz_base_volume.yml or xyz_base_volume.yaml; module1_volume.yml or module1_volume.yaml (referencing the above base module Heat template name) ? The file name of the environment files must fully match the corresponding Heat template filename and have .env or .ENV extension. o Examples: base_xyz.env or base_xyz.ENV; xyz_base.env or xyz_base.ENV; base_xyz_volume.env or base_xyz_volume.ENV; module1.env or module1.ENV; module1_volume.env or module1_volume.ENV (referencing the above base module Heat template name) ? A YAML file must have a corresponding ENV file, even if the ENV file enumerates no parameters. It is an OpenECOMP requirement. Daniel Rose ECOMP / ONAP com.att.ecomp 732-420-7308 From: SHAH, BEEJAL Sent: Wednesday, April 19, 2017 11:53 AM To: ROSE, DANIEL V <DR695H at att.com<mailto:DR695H at att.com>>; WEINSTOCK, ALAN M <aw2574 at att.com<mailto:aw2574 at att.com>>; onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org> Cc: Michael Ryan <Michael.Ryan at amdocs.com<mailto:Michael.Ryan at amdocs.com>> Subject: RE: SDC Heat Manifest Question Daniel, Do you know if support of SHELL or OTHER file types is a recent addition? When I try to use SHELL or OTHER in my manifest I get validation error. My version of SDC is quiet old though. I have a manifest that looks like { "name": "Test", "description": "Test manifest", "data": [ { "file": "someVNF_base.yaml", "type": "HEAT", "isBase": "true", "data": [ { "file": "someVNF_base.env", "type": "HEAT_ENV" } ] }, { "file": "someVNF_vnfA.yaml", "type": "HEAT", "isBase": "false", "data": [ { "file": "someVNF_vnfA.env", "type": "HEAT_ENV" } ] }, { "file": "nested1.yaml", "type": "HEAT", "isBase": "false" }, { "file": "nested2.yaml", "type": "HEAT", "isBase": "false" }, { "file": "boot_1.sh", "type": "SHELL" }, { "file": "boot_2.sh", "type": "SHELL" } ] } [id:image001.png at 01D2B911.50D73770] From: onap-discuss-bounces at lists.onap.org<mailto:onap-discuss-bounces at lists.onap.org> [mailto:[email protected]] On Behalf Of Beejal Shah Sent: Wednesday, April 19, 2017 11:03 AM To: ROSE, DANIEL V <DR695H at att.com<mailto:DR695H at att.com>>; WEINSTOCK, ALAN M <aw2574 at att.com<mailto:aw2574 at att.com>>; onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org> Cc: Michael Ryan <Michael.Ryan at amdocs.com<mailto:Michael.Ryan at amdocs.com>> Subject: Re: [onap-discuss] SDC Heat Manifest Question Daniel, It?s a shell (.sh) script we are trying to include. Thanks for your response, I?ll try it out. Regards, Beejal From: ROSE, DANIEL V [mailto:[email protected]] Sent: Tuesday, April 18, 2017 4:34 PM To: WEINSTOCK, ALAN M <aw2574 at att.com<mailto:aw2574 at att.com>>; Beejal Shah <Beejal.Shah at amdocs.com<mailto:Beejal.Shah at amdocs.com>>; onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org> Subject: RE: SDC Heat Manifest Question To expand on that here are all the types I have seen "data": [ { "file": "heat.yaml", "type": "HEAT", "data": [ { "file": "env.env", "type": "HEAT_ENV" }, { "file": "vol.yaml", "type": "HEAT_VOL", "data": [ { "file": "env.env", "type": "HEAT_ENV" } ] } ] }, { "file": "heat.yaml", "type": "HEAT", "data": [ { "file": "env.env", "type": "HEAT_ENV" } ] }, { "file": "heat.yaml", "type": "HEAT" }, { "file": "shell.sh", "type": "SHELL" }, { "file": "other.conf", "type": "OTHER" }, 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 WEINSTOCK, ALAN M Sent: Tuesday, April 18, 2017 4:31 PM To: SHAH, BEEJAL <beejal.shah at amdocs.com<mailto:beejal.shah at amdocs.com>>; onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org> Subject: Re: [onap-discuss] SDC Heat Manifest Question ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Beejal, Most cases the type is assigned ?OTHER?. A .sh file will be assigned ?SHELL?. What is your get_file and what type is being assigned in the manifest? Regards, Alan From: onap-discuss-bounces at lists.onap.org<mailto:onap-discuss-bounces at lists.onap.org> [mailto:[email protected]] On Behalf Of SHAH, BEEJAL Sent: Tuesday, April 18, 2017 2:11 PM To: onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org> Subject: [onap-discuss] SDC Heat Manifest Question If I create a heat template that uses ?get_file? directive to pull is a user-data script, does anyone know what the file type should be for this script in MANIFEST.json? Does anyone one have an example they can share? Thanks, Beejal 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<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=yLYuNW5w2gOecrwMfo7-lQ&m=g0I8pqWNNOUfEdXRLS4W0alCIxI15M33quJCmCQjQjM&s=tdolemfec8iwFYh5zLHz0PDaJ6iMV0W6mVXqs0dZzoQ&e=> 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<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=sIUbWnzl4Eag07OShoUMrjlPIrTcU-5R8KAXJw5eVTU&s=AIwEAIZVu2ZUpwINslckICPBZpg2nyWc5BEFAMPACgE&e=> 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<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=sIUbWnzl4Eag07OShoUMrjlPIrTcU-5R8KAXJw5eVTU&s=AIwEAIZVu2ZUpwINslckICPBZpg2nyWc5BEFAMPACgE&e=> 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 <https://www.amdocs.com/about/email-disclaimer> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170419/e9e95f49/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 60242 bytes Desc: image001.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170419/e9e95f49/attachment-0001.png>
