PR#1040: cloud: Consistent device naming - fedora-kickstarts

fedora-kickstarts

#1040 cloud: Consistent device naming

Merged a month ago by ngompa. Opened a month ago by mhayden.

mhayden/fedora-kickstarts device-naming into main

Major Hayden • a month ago

e0561d3

fedora-cloud-base-gcp.ks

file modified

+1 -1

		`@@ -9,7 +9,7 @@`
		`# Don't show bootloader as it's impossible for the user to get to it in time`
		`# So we might as well not waste the 1 second on each boot.`
		`# https://cloud.google.com/compute/docs/import/import-existing-image`
		`- bootloader --timeout=0 --location=mbr --append="no_timer_check net.ifnames=0 console=ttyS0,38400n8d"`
		`+ bootloader --timeout=0 --location=mbr --append="no_timer_check console=ttyS0,38400n8d"`

		# redefine `services` here to drop cloud-init systemd unit enablements from
		`# fedora-cloud-base.ks since we don't use them.`

fedora-cloud-base.ks

file modified

+1 -2

		`@@ -31,8 +31,7 @@`

		`firewall --disabled`

		`- # We pass net.ifnames=0 because we always want to use eth0 here on all the cloud images.`
		`- bootloader --timeout=1 --location=mbr --append="no_timer_check net.ifnames=0 console=tty1 console=ttyS0,115200n8"`
		`+ bootloader --timeout=1 --location=mbr --append="no_timer_check console=tty1 console=ttyS0,115200n8"`

		`services --enabled=sshd,cloud-init,cloud-init-local,cloud-config,cloud-final`

mhayden commented a month ago

Use consistent network device names for network devices instead of
forcing the old "ethX" names from pre-2017. This ensures that
specialized network devices, such as SR-IOV devices, are easy to
recognize and configure inside a Fedora instance on a public cloud or
OpenStack cloud.

FESCo ticket: https://pagure.io/fesco/issue/3190
Change proposal: https://fedoraproject.org/wiki/Changes/EnableConsistentDeviceNamingCloud

Signed-off-by: Major Hayden major@redhat.com