Skip to content
This repository was archived by the owner on Aug 25, 2021. It is now read-only.

02_ignition_firstboot: Enable networking if Ignition will run#57

Merged
dustymabe merged 1 commit intocoreos:masterfrom
cgwalters:initramfs-net-ignition
Mar 18, 2019
Merged

02_ignition_firstboot: Enable networking if Ignition will run#57
dustymabe merged 1 commit intocoreos:masterfrom
cgwalters:initramfs-net-ignition

Conversation

@cgwalters
Copy link
Member

Today coreos-assembler is hardcoding the initramfs networking kargs to
do DHCP; this is problematic for e.g. bare metal where one often wants
to configure static networking.

Let's only enable initramfs networking if we're doing Ignition.

Today coreos-assembler is hardcoding the initramfs networking kargs to
do DHCP; this is problematic for e.g. bare metal where one often wants
to configure static networking.

Let's only enable initramfs networking if we're doing Ignition.
Copy link
Contributor

@bgilbert bgilbert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM as an interim improvement. Eventually the initramfs itself should be enabling networking as needed.

@dustymabe dustymabe merged commit 8875cbf into coreos:master Mar 18, 2019
cgwalters added a commit to cgwalters/coreos-assembler that referenced this pull request Mar 27, 2019
With this I'll have to find a way to remove my "eth0 FOR LIFE" tattoo.

This came up in a bigger discussion with OpenStack:
coreos/ignition#769 (comment)

The history behind disabling persistent NIC naming in Fedora/RHEL
is...long.

I think we have an opportunity now to do a clean break with that
history.  Let's use persistent NIC naming even for cloud environments
like AWS.

This massively reduces the delta between our "metal" and "openstack"
images.  We just have console tweaks and `no_timer_check`.

Note that with coreos/ignition-dracut#57
we actually do do DHCP on all interfaces anyways, so the hardcoded
`eth0` here made even less sense.
cgwalters added a commit to coreos/coreos-assembler that referenced this pull request Mar 27, 2019
With this I'll have to find a way to remove my "eth0 FOR LIFE" tattoo.

This came up in a bigger discussion with OpenStack:
coreos/ignition#769 (comment)

The history behind disabling persistent NIC naming in Fedora/RHEL
is...long.

I think we have an opportunity now to do a clean break with that
history.  Let's use persistent NIC naming even for cloud environments
like AWS.

This massively reduces the delta between our "metal" and "openstack"
images.  We just have console tweaks and `no_timer_check`.

Note that with coreos/ignition-dracut#57
we actually do do DHCP on all interfaces anyways, so the hardcoded
`eth0` here made even less sense.
ashcrow pushed a commit to ashcrow/coreos-assembler that referenced this pull request May 30, 2019
With this I'll have to find a way to remove my "eth0 FOR LIFE" tattoo.

This came up in a bigger discussion with OpenStack:
coreos/ignition#769 (comment)

The history behind disabling persistent NIC naming in Fedora/RHEL
is...long.

I think we have an opportunity now to do a clean break with that
history.  Let's use persistent NIC naming even for cloud environments
like AWS.

This massively reduces the delta between our "metal" and "openstack"
images.  We just have console tweaks and `no_timer_check`.

Note that with coreos/ignition-dracut#57
we actually do do DHCP on all interfaces anyways, so the hardcoded
`eth0` here made even less sense.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants