Closed jamacku closed 2 years ago
@davide125 could you please tell us your opinion from Facebook point of view?
Thanks for the heads up @jamacku. Splitting the repos shouldn't be an issue at all, and network-scripts
is already its own separate package in RHEL 8. The move to EPEL isn't ideal for us, but in practice it won't be too much of a burden (especially now that we know it's coming and can plan for it).
Our plan for RHEL 9 is to re-evaluate internally network-scripts
vs NetworkManager
vs systemd-networkd
and conduct some testing between now and then, so that we can make an informed decision on whether we want to stay on network-scripts
or not in the future.
I'm due for an update on this ticket. After internal evaluation, Facebook will be deploying systemd-networkd
for the CentOS Stream 9 cycle, with the fallback option to use network-scripts
in case we hit issues around networkd for specific workloads/usecases that can't be timely resolved. We're maintaining our systemd backport (which includes systemd-networkd
) as part of the CentOS Hyperscale SIG. By the time CentOS Stream 10 comes around we would expect to have dropped network-scripts
completely. cc @anitazha who is driving the networkd migration on our end.
Great, thank you for update.
We are planning to divide initscripts package into two packages for RHEL9+. Where network-scripts will be in there own package in EPEL (unsupported) and initscripts as such will remain supported.
Reason being to encourage people to use NetworkManager instead of legacy network-scripts.
We are now in planning phase and we are looking for your opinions, so don't hesitate to reach to us.