Going through this issue this morning with some of you - it looks like we have a couple questions that we will get answers for in the noon meeting
1) Do we use the older vFW template or the new split vFWCL template with the PORTAL-409 fix from the 4th nov - or both 2) Does the ssh key in the older vFW still get overridden by any sdc distribute override 3) Does the ssh key we manually add at design time to the vFWCL env(2) files get overridden by any override in SDC distribute as well 4) I would expect any default key in the env to work out of the box otherwise Observation: the vFW sink on Integration SB-00 on 10.12.6.60 works (no closed loop yet via (dcae/policy/appc) and generates the :667 graph in a curl/browser - so we have a good target I tried getting into this one with the default key but I don't know whether it was generated by 1 or 2 or SDC overridden In cases where the private and assigned IPs are still not accessible - even from robot - attach a 3rd floating ip - as the vFW has its own subnet. These questions are on top of the other ones we will verify (preload via robot/post or both, appc mount via robot/post or both) Basically, we should have some documentation on these today/this week as we finish with the distribute step See you later at 1200EDT. https://wiki.onap.org/display/DW/Vetted+vFirewall+Demo+-+Full+draft+how-to+for+F2F+and+ReadTheDocs /michael From: FREEMAN, BRIAN D [mailto:[email protected]] Sent: Monday, November 27, 2017 08:52 To: Arun Arora (c) <[email protected]>; [email protected]; PLATANIA, MARCO <[email protected]> Cc: Ramki Krishnan <[email protected]>; Ramesh Tammana <[email protected]>; Gaurav Gupta (c) <[email protected]>; Michael O'Brien <[email protected]> Subject: RE: [onap-discuss] vFW Demo Stack Create Fails with ""Message: No valid host was found. There are not enough hosts available., Code: 500"" Arun, I dont know what problem you are getting into. Assigning the floating IP's after the fact seems strange but theres nothing that would be different for the 3 VM's that I know of that would work for one and not the other 2 wrt logging in. Perhaps using the concole port to see if the VM cloud-init log has any indications. Without an external IP I'm not sure the applications can do their install so I think you need to get the external network configuration working. Brian From: Arun Arora (c) [mailto:[email protected]] Sent: Friday, November 24, 2017 9:38 AM To: [email protected]<mailto:[email protected]>; FREEMAN, BRIAN D <[email protected]<mailto:[email protected]>>; PLATANIA, MARCO <[email protected]<mailto:[email protected]>> Cc: Ramki Krishnan <[email protected]<mailto:[email protected]>>; Ramesh Tammana <[email protected]<mailto:[email protected]>>; Gaurav Gupta (c) <[email protected]<mailto:[email protected]>>; OBRIEN, FRANK MICHAEL <[email protected]<mailto:[email protected]>> Subject: RE: [onap-discuss] vFW Demo Stack Create Fails with ""Message: No valid host was found. There are not enough hosts available., Code: 500"" Hi All, Brian, Marco, Out of the 3 VMs for vFW demo, I am able to login to only Traffic Generator VM. The floating IPs of rest 2 VMs are not pingable and I am not able to ssh in them as well. FYI, all three VMs have same key pair and for all floating IP was assigned manually as mentioned in my last email. Wanted to know in your setup are you able to login to all vFW VMs? Also, has anyone seen this error in your setup? Pls suggest any pointers to resolve this issue... Thanks, Arun From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Arun Arora (c) Sent: 24 November 2017 12:46 To: FREEMAN, BRIAN D <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Subject: Re: [onap-discuss] vFW Demo Stack Create Fails with ""Message: No valid host was found. There are not enough hosts available., Code: 500"" Hi Brian, Figured out the issue. Looks like when giving public net id in vFW env file, this issue comes. I used internal network id instead and with it all 3 VMs are created and the VF module stack creation succeeds. I then have to assign floating IP to 3 VMs manually though. That said, still need to characterize the issue as a genuine bug or some local setup issue. But importantly, passed step 5 of 6 :-) Thanks, Arun ________________________________ From: Arun Arora (c) Sent: Friday, November 24, 2017 9:58:32 AM To: FREEMAN, BRIAN D; [email protected]<mailto:[email protected]> Subject: Re: [onap-discuss] vFW Demo Stack Create Fails with ""Message: No valid host was found. There are not enough hosts available., Code: 500"" debugmso.log in VnfAdpater say the same error. Nothing more verbose in it w.r.t. this error. Arun ________________________________ From: FREEMAN, BRIAN D <[email protected]<mailto:[email protected]>> Sent: Friday, November 24, 2017 9:10:13 AM To: Arun Arora (c); [email protected]<mailto:[email protected]> Subject: RE: [onap-discuss] vFW Demo Stack Create Fails with ""Message: No valid host was found. There are not enough hosts available., Code: 500"" I've only run into that when the Hosting platform didnt have enough memory or other resource (sometimes ports ) you'll have to look at errors on the VMware side. Dont know if Marco or Kang have run into this particular message before. Did debugmso.log in the VnfAdapter directory have any more details or was it the same No valid host was found message ? Brian From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Arun Arora (c) Sent: Thursday, November 23, 2017 9:24 AM To: [email protected]<mailto:[email protected]> Subject: [onap-discuss] vFW Demo Stack Create Fails with ""Message: No valid host was found. There are not enough hosts available., Code: 500"" Hi All, We are working to bring up the vFW demo on VIO 4.0. For that we run demo.sh init from robot VM and then service instantiation is done from VID. We have reached a point where MSO sends the Heat Request to VIO for Demo Stack creation, however each time the stack creation fails with error ""Message: No valid host was found. There are not enough hosts available., Code: 500"" We have enough resources for the 3 VMs created as part of vFW demo. However, still receiving the following errors: vsn_0<https://urldefense.proofpoint.com/v2/url?u=https-3A__10.110.209.230_project_stacks_stack_b7161f32-2D91cf-2D4f06-2Db4c3-2D3f5b5e1ab96c_vsn-5F0_&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=gzKgE4TNJPXXTd0gyIIB1i9Me-bWT--wW7GqVISXrMI&s=JKQzrMkyWbTvis0j0UEpBDDzyNI0YO09YLhEHgfcGZY&e=> 7f5f2a96-065b-49d7-a6a4-281ff85df8db<https://urldefense.proofpoint.com/v2/url?u=https-3A__10.110.209.230_project_instances_7f5f2a96-2D065b-2D49d7-2Da6a4-2D281ff85df8db_&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=gzKgE4TNJPXXTd0gyIIB1i9Me-bWT--wW7GqVISXrMI&s=37NPVDYMTeIn5gaxMZk8GZiQ8tld76TieX1YQMxweSE&e=> OS::Nova::Server 14 minutes Create Failed ResourceInError: resources.vsn_0: Went to status ERROR due to "Message: No valid host was found. There are not enough hosts available., Code: 500" vpg_0<https://urldefense.proofpoint.com/v2/url?u=https-3A__10.110.209.230_project_stacks_stack_b7161f32-2D91cf-2D4f06-2Db4c3-2D3f5b5e1ab96c_vpg-5F0_&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=gzKgE4TNJPXXTd0gyIIB1i9Me-bWT--wW7GqVISXrMI&s=PboBWDIXmYMAAizjWOkS891HEl_xwSAUoftSr0yQ3xM&e=> 385d207f-97ff-4a3a-8107-c8a77c37b33b<https://urldefense.proofpoint.com/v2/url?u=https-3A__10.110.209.230_project_instances_385d207f-2D97ff-2D4a3a-2D8107-2Dc8a77c37b33b_&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=gzKgE4TNJPXXTd0gyIIB1i9Me-bWT--wW7GqVISXrMI&s=qsyPLUDRYMNdqzIDWm-HT6mZpT5wBnu2O4Vzsye_1fg&e=> OS::Nova::Server 14 minutes Create Failed ResourceInError: resources.vpg_0: Went to status ERROR due to "Message: No valid host was found. There are not enough hosts available., Code: 500" I see that other resources creation is OK but the VMs creation fail. Attaching the topology snapshot for reference. Has anyone seen this issue in your setup? Ayn pointers to fix this are highly appreciated. Thanks, Arun 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
