#3190 Change: Enable Consistent Device Naming in Cloud Images
Closed: Accepted a month ago by zbyszek. Opened 2 months ago by amoloney.

This proposal aims to remove the net.ifnames=0 kernel command line entry from the Fedora cloud kickstarts so that consistent device naming is enabled for cloud instances. This change brings Fedora Cloud in line with Fedora Server, Workstation, and CoreOS.

Owners, do not implement this work until the FESCo vote has explicitly ended.
The Fedora Program Manager will create a tracking bug in Bugzilla for this Change, which is your indication to proceed.
See the FESCo ticket policy and the Changes policy for more information.

REMINDER: This ticket is for FESCo members to vote on the proposal. Further discussion should happen in the devel list thread linked above.


(Note that we don't change kickstarts anymore, this is adjusting the kiwi descriptions, but I'm accepting it on the intent that was written)

@davdunc:

+1

This is only for FESCo members voting, so while we appreciate your support for this, it doesn't have much effect here. :sweat_smile:

@ngompa while we're at it, you only get one vote here :wink:

Hi FESCo, there are 5 +1 votes after over a week so I will go ahead and mark this change as APPROVED (+5, 0, 0) as per policy.

Let me know if this needs to change.

Thanks!

Metadata Update from @amoloney:
- Issue tagged with: pending announcement

a month ago

I missed the vote on this one. In general I support this, and I think if we were only talking about new images, there wouldn't be much to discuss. The tricky part is upgrades: I don't know enough about cloud image deployments to know how much of a problem this will be. Let's hope it goes smoothly.

@zbyszek This is a change to the images only, so if someone is upgrading, they won't see this change. Their old network device naming rules would still be applied.

Hi FESCo, there are 5 +1 votes after over a week so I will go ahead and mark this change as APPROVED (+5, 0, 0) as per policy.

Probably doesn't matter but I think there are only 4 +1 votes, because @ngompa voted twice.

@tstellar Good point. I should have jumped in with a +1, but then again, I'm the change owner. 🙃

I thought I voted on this one already, but I guess not. ;(

+1 in any case...

Metadata Update from @zbyszek:
- Issue untagged with: pending announcement
- Issue close_status updated to: Accepted
- Issue status updated to: Closed (was: Open)

a month ago

Login to comment on this ticket.

Metadata