Yes the code in the demo repo that marco wrote assumed the old way of naming before systemd changed things. 1404 should let things work
Daniel Rose ECOMP / ONAP com.att.ecomp 732-420-7308 From: [email protected] [mailto:[email protected]] On Behalf Of FREEMAN, BRIAN D Sent: Wednesday, April 25, 2018 4:07 PM To: Joe Kidder <[email protected]>; [email protected] Subject: Re: [onap-discuss] quick question on vFW demo ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. I think it should be the Ubuntu 14.04 image for the vFW demo. Brian From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> On Behalf Of Joe Kidder Sent: Wednesday, April 25, 2018 3:47 PM To: [email protected]<mailto:[email protected]> Subject: [onap-discuss] quick question on vFW demo When I launch the vFW demo heat template (from Amsterdam, I believe), the ubuntu 16.04 image that I have installed on OpenStack (grabbed from http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-disk<https://urldefense.proofpoint.com/v2/url?u=http-3A__cloud-2Dimages.ubuntu.com_xenial_current_xenial-2Dserver-2Dcloudimg-2Damd64-2Ddisk&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=1e5LECa3kcHh89TxJXaUYpkcrq3HzmcBCWk1cZwJwts&s=ojLHaTDvuP6-Mj_VT-0Nhpq7Gt_HpsJEoFhZ0mBbhBM&e=>1.img) has ethernet interfaces named "ens3", "ens4", "ens5". However, the v_sink_install.sh, for example, tries to perform actions on eth1 and eth2 (skipping eth0, as it's not interesting other than providing a path to the internet). Am I missing a step? Should I have massaged my ubuntu 16.04 image to have interfaces named "ethx" rather than "ensx"? Thanks, Joe
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
