If you look at the heat template, you could find the following lines, please modify according to your base image:
# Rename network interface sed -i 's/GRUB_CMDLINE_LINUX=.*/GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"/g' /etc/default/grub grub-mkconfig -o /boot/grub/grub.cfg sed -i "s/enp0s3/eth0/g" /etc/network/interfaces sed -i "s/enp0s8/eth1/g" /etc/network/interfaces From: [email protected] [mailto:[email protected]] On Behalf Of Ali, Shaheen Sent: Thursday, May 4, 2017 2:13 AM To: [email protected] Subject: Re: [onap-discuss] Ubuntu 16.04 VM do not have eth0 Hello All, I would like specific instructions on how to modify the heat template so that the robot, sdc and mso instances all correctly configure their network. Recently, Munir posted this helpful reply. Message: 1 Date: Thu, 13 Apr 2017 13:23:51 +0000 From: "Ahmad, Munir" <[email protected]<mailto:[email protected]>> To: Chris Reece <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [onap-discuss] Ubuntu 16.04 VM do not have eth0 Message-ID: <[email protected]<mailto:[email protected]>> Content-Type: text/plain; charset="utf-8" Hello Chris, You need to rename the following two interfaces. ? ens4 to eth0 ? ens3 to eth1 then rerun the /var/lib/cloud/instance/user-data.txt In order to do this do I need console access or a modified heat template? Thanks, Shaheen Ali This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
