Ajay, Yes, there is an open jira on these hardcoded values (changes to your env have no effect over the sample values). Until this is fixed you can only have one instance of the vFW or vLB up.
https://jira.onap.org/browse/UCA-17 /michael From: [email protected] [mailto:[email protected]] On Behalf Of ROSE, DANIEL V Sent: Monday, June 26, 2017 10:38 To: Josef Reisinger <[email protected]> Cc: [email protected]; [email protected] Subject: Re: [onap-discuss] Robot vm script automation You can certainly change anything, just make sure they all sync up. Look at the heat templates for each demo vnf, and as long as the new parameters work it is fine. Since we use a private network for everything there shouldn't be an ip conflict. Thanks, Daniel Rose ECOMP / ONAP com.att.ecomp 732-420-7308 From: Josef Reisinger [mailto:[email protected]] Sent: Monday, June 26, 2017 10:27 AM To: ROSE, DANIEL V <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Subject: Re: [onap-discuss] Robot vm script automation Daniel, if "preload parameters are hard coded", does it mean I should not change them? On one of my environments, I have a conflict with 10.0.0.0/8 network space and configured a 10.0.0.0/16 net, which created some conflict when trying to spin up vFW. To overcome the issues, I move some IP addresses to 10.0.150.X and reran demo.sh preload <my-module>. Even the VMs start (more or less), does this break the demo? Mit freundlichen Grüßen / Kind regards Josef Reisinger From: "ROSE, DANIEL V" <[email protected]<mailto:[email protected]>> To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: 26.06.2017 16:18 Subject: Re: [onap-discuss] Robot vm script automation Sent by: [email protected]<mailto:[email protected]> ________________________________ The properties in robot come from a few places. The first way is the heat template (that's dynamic properties in your terms) and they are saved as vm_properties.py. You can certainly make a script to generate these in a different way if you wanted. The preload parameters are hard coded because they are defined by the demo use case. The robot properties defines the topology of the onap installation and openstack install etc. The microservice bus will render most of these properties useless and they can be removed at that time. Thanks, Daniel Rose ECOMP / ONAP com.att.ecomp 732-420-7308 From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of [email protected]<mailto:[email protected]> Sent: Monday, June 26, 2017 5:29 AM To: [email protected]<mailto:[email protected]> Subject: [onap-discuss] Robot vm script automation Hi, The below configuration files used for demo script uses hardcoded values. Example : /var/opt/OpenECOMP_ETE/runTags.sh -V /share/config/vm_properties.py -V /share/config/integration_robot_properties.py -V /share/config/integration_preload_parameters.py -v GLOBAL_BUILD_NUMBER:1928 -d /share/logs/ETE_1928 -i InitDemo --display 88 The above command uses three config files. 1. integration_robot_properties.py 2. integration_preload_parameters.py 3. vm_properties.py Only 3rd one(vm_properties.py) get populated by environment value, Rest both uses preconfigured values. These two files should also maintain dynamic values (eg. Private IP addresses). Regards, Ajay "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s), are confidential and may be privileged. If you are not the intended recipient, you are hereby notified that any review, re-transmission, conversion to hard copy, copying, circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this message and any attachments from your system. Virus Warning: Although the company has taken reasonable precautions to ensure no viruses are present in this email. The company cannot accept responsibility for any loss or damage arising from the use of this email or attachment."_______________________________________________ onap-discuss mailing list [email protected]<mailto:[email protected]> https://lists.onap.org/mailman/listinfo/onap-discuss<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=67rbu-2TYpYrg3TN-sSsjq6jdYUUSf8F2tvzocWGrt4&s=9pEnGuk1lSn_Ck0UTwqUlm8eWzzRhhAzyzTrlGd97vk&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>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
