We have a blueprint for Offline validation tool in OpenStack heat and is yet to implemented. But for now, you could use the standalone heat installation from OpenStack
Pls refer https://docs.openstack.org/developer/heat/getting_started/standalone.html Regards Kanagaraj M *************************************************************************************** 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！************************************************************************************** *************************************************************************************** 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 Konstantin Dunaev Sent: Wednesday, May 31, 2017 6:59 PM To: [email protected] Subject: [onap-discuss] is there any heat validator tool? Hello ONAP Community, we are using “VNF Heat Template Requirements for OpenEcomp” to prepare a Heat template, but we don't have running ONAP environment and I can't validate my files. We're in the process to install it, but it requires time and resources and make take longe time. Is there any "offline" validation tool, which we can use to verify/validate Heat templates before we send them to ONAP environment (running at the customer site). When we sent our current Heat files, the customer responded back with the information: ----------------------------------- Validate file aliagnment - heat validator cannot parse templates. ECOMP parameters missing - vf_module_name, vnf_name, and vnf_id Parameter missing vm_type - any parameter associated with a VM must have a vm_type assigned. .... ------------------------------- I could find and correct some problems with naming, but not sure if I see them all. Best regards, Konstantin
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
