Munir,
Can you try the following: in base_vmx.yaml, replace the following line under
resource re0 & resource pfe0
metadata: {vnf_id: {get_param: vnf_id}, vnf_name: {get_param: vnf_name},
vf_module_id: {get_param: vf_module_id}}
with the following three lines
vnf_id: {get_param: vnf_id}
vnf_name: {get_param: vnf_name}
vf_module_id: {get_param: vf_module_id}
Also, remove ?metadata? from the parameter declarations of all three yaml files.
Regards,
Alan
From: onap-discuss-bounces at lists.onap.org<mailto:onap-discuss-bounces at
lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of
Ahmad, Munir
Sent: Thursday, April 13, 2017 9:11 AM
To: LEFEVRE, CATHERINE <cl664y at intl.att.com<mailto:cl664y at intl.att.com>>;
POND, MARK <mpond at amdocs.com<mailto:mpond at amdocs.com>>; PLATANIA, MARCO
<platania at research.att.com<mailto:platania at research.att.com>>
Cc: onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>
Subject: Re: [onap-discuss] Questions about VNF Heat Template
Sorry outlook sent my incomplete email when I pressed enter.
We are facing an issue when we upload ZIP file containing the Heat
templates(formatted according to ONAP standards) to SDC. Below is the exact
error message from SDC UI
Heat base_vmx.yaml: Referenced parameter not found in nested file - re.yaml,
resource name - re0, parameter name ? metadata
Heat base_vmx.yaml: Referenced parameter not found in nested
file - fpc.yaml, resource name - pfe0, parameter name ? metadata
We have one level of nesting and the base_vmx.yaml creates two VNF with the
following types:
type: re.yaml
type: fpc.yaml
I am able to resolve either one the errors above but not both when I add
metadata as parameters to re.yaml or fpc.yaml. Having the following line in
both files causes the upload validation fail in SDC.
parameters:
metadata: {description: this is metadata, type: string}
My understanding is that when we have metadata as parameter in both(re.yaml and
fpc.yaml) and when these are brough up to parent yaml during processing it
conflicts. Therefore we can have only the metadata tag on either one of the
yaml files.
Based on our observations it seems like ONAP supports nesting as long as we are
creating one VNF. Can you confirm/reject our observation?
I have attached the yaml files in question.
Best Regards
Munir Ahmad
From: "ROSE, DANIEL V" <DR695H at att.com<mailto:dr6...@att.com>>
Date: Thursday, April 13, 2017 at 11:51 AM
To: "Ahmad, Munir" <Munir.Ahmad at bell.ca<mailto:Munir.Ahmad at bell.ca>>,
"LEFEVRE, CATHERINE" <cl664y at intl.att.com<mailto:cl664y at intl.att.com>>,
"POND, MARK" <mpond at amdocs.com<mailto:mpond at amdocs.com>>, "PLATANIA,
MARCO" <platania at research.att.com<mailto:platania at research.att.com>>
Cc: "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>>
Subject: RE: [onap-discuss] Questions about VNF Heat Template
Can you post the zip (or a stripped version of the zip that still exhibits the
behavior?)
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:onap-discuss-boun...@lists.onap.org] On Behalf Of
Ahmad, Munir
Sent: Thursday, April 13, 2017 11:49 AM
To: LEFEVRE, CATHERINE <cl664y at intl.att.com<mailto:cl664y at intl.att.com>>;
POND, MARK <mpond at amdocs.com<mailto:mpond at amdocs.com>>; PLATANIA, MARCO
<platania at research.att.com<mailto:platania at research.att.com>>
Cc: onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>
Subject: Re: [onap-discuss] Questions about VNF Heat Template
Thanks guys for the feedback,
We are facing an issue when we upload ZIP file containing the Heat
templates(formatted according to ONAP standards) to SDC.
Heat base_vmx.yaml: Referenced parameter not found in nested file - re.yaml,
resource name - re0, parameter name - metadata
Reference:
1)
https://wiki.onap.org/download/attachments/1015849/VNF%20Heat%20Template%20Requirements%20for%20OpenECOMP.pdf?api=v2<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_download_attachments_1015849_VNF-2520Heat-2520Template-2520Requirements-2520for-2520OpenECOMP.pdf-3Fapi-3Dv2&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=BrK9olX78MsH8vbDM_PKABuX9NcbpbWrEfkQUifnRmw&s=SjqnDaTZht2V_F_Pun47bdFkkBbpbaYa7SV--R4QxDM&e=>
From: "Lefevre, Catherine" <cl664y at intl.att.com<mailto:cl6...@intl.att.com>>
Date: Wednesday, April 12, 2017 at 7:07 AM
To: "POND, MARK" <mpond at amdocs.com<mailto:mpond at amdocs.com>>, "Ahmad,
Munir" <Munir.Ahmad at bell.ca<mailto:Munir.Ahmad at bell.ca>>, "PLATANIA,
MARCO" <platania at research.att.com<mailto:platania at research.att.com>>
Cc: "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>>
Subject: RE: [onap-discuss] Questions about VNF Heat Template
Good morning Mark,
You have probably missed my latest update regarding this thread.
It has been confirmed that the SDC ONAP version is already supporting 3 levels
of nesting.
The documentation will be updated accordingly.
Reference:
https://lists.onap.org/pipermail/onap-discuss/2017-April/000070.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_pipermail_onap-2Ddiscuss_2017-2DApril_000070.html&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=BrK9olX78MsH8vbDM_PKABuX9NcbpbWrEfkQUifnRmw&s=Y5341pf0JfbnSrS-jD8KHDgGn0XARp4c8ZH7cjHlFy4&e=>
Best regards
Catherine
From: onap-discuss-bounces at lists.onap.org<mailto:onap-discuss-bounces at
lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of POND,
MARK
Sent: Wednesday, April 12, 2017 12:50 PM
To: Ahmad, Munir <Munir.Ahmad at bell.ca<mailto:Munir.Ahmad at bell.ca>>;
PLATANIA, MARCO <platania at research.att.com<mailto:platania at
research.att.com>>
Cc: onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>
Subject: Re: [onap-discuss] Questions about VNF Heat Template
Munir,
1. What is the reasoning behind limiting to one level of nesting when
onboarding a VNF module? Any plans to change this?
Simple answer is the limitation was purely down to not dealing with too much
complexity at the start.
The support of a base (used for shared resources), modules (one or more) and a
separate volume all of which can support a single level of nested HEAT template
does provide a lot of flexibility
Re: plans?? 3 levels of nesting is planned and this will be released soon
2. Are there any tools that can be used to ?flatten? nested heat templates?
I am not aware of any tools ? how many levels are you having to deal with?
Regards
Mark
From: onap-discuss-bounces at lists.onap.org<mailto:onap-discuss-bounces at
lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of
Ahmad, Munir
Sent: Tuesday, April 11, 2017 4:05 PM
To: PLATANIA, MARCO (MARCO) <platania at research.att.com<mailto:platania at
research.att.com>>
Cc: onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>
Subject: Re: [onap-discuss] Questions about VNF Heat Template
Thanks Marco,
The section in question is on page 8 (page 13 of pdf doc) and the URL to ?VNF
Heat Template Requirements for OpenECOMP? is:
https://wiki.onap.org/download/attachments/1015849/VNF%20Heat%20Template%20Requirements%20for%20OpenECOMP.pdf?api=v2<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_download_attachments_1015849_VNF-2520Heat-2520Template-2520Requirements-2520for-2520OpenECOMP.pdf-3Fapi-3Dv2&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=66ObImPAUA0o2f1hTGknnnv5ScXvX8EnREJCPHHBY5M&m=l6hR2uzPyXVF6jVHV1M-kWQTsvguBvQVEXqUt3D_B4g&s=bTYI-NwPAbWIhXJOjfUWi8bnuciWUsadeWRGNEOMocc&e=>
From: "PLATANIA, MARCO (MARCO)" <platania at
research.att.com<mailto:plata...@research.att.com>>
Date: Tuesday, April 11, 2017 at 10:58 AM
To: "Ahmad, Munir" <Munir.Ahmad at bell.ca<mailto:Munir.Ahmad at bell.ca>>
Cc: "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>>
Subject: Re: [onap-discuss] Questions about VNF Heat Template
Hello Munir,
Thanks for reaching out. We would like to better understand your question.
Could you please point us to the ?VNF Heat Template Requirements for OpenEcomp??
We?ll investigate these requirements and give you an answer.
Thanks,
Marco
From: <onap-discuss-bounces at lists.onap.org<mailto:onap-discuss-bounces at
lists.onap.org>> on behalf of "Ahmad, Munir" <Munir.Ahmad at
bell.ca<mailto:munir.ah...@bell.ca>>
Date: Tuesday, April 11, 2017 at 10:00 AM
To: "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>>
Subject: [onap-discuss] Questions about VNF Heat Template
Hello ONAP Community,
I am reading ?VNF Heat Template Requirements for OpenEcomp? It indicates Heat
templates for OpenECOMP must only have one level of nesting. I have a couple of
questions.
1. What is the reasoning behind limiting to one level of nesting when
onboarding a VNF module? Any plans to change this?
2. Are there any tools that can be used to ?flatten? nested heat templates?
Best Regards
Munir Ahmad
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=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=66ObImPAUA0o2f1hTGknnnv5ScXvX8EnREJCPHHBY5M&m=l6hR2uzPyXVF6jVHV1M-kWQTsvguBvQVEXqUt3D_B4g&s=Y8sIwLhQvzSZoxqemIK1oE_bVO4iZG7htG_zeIqpfpc&e=>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.onap.org/pipermail/onap-discuss/attachments/20170417/c1b3b84f/attachment-0001.html>
