From Fedora Project Wiki
m (→‎Benefit to Fedora: Adding the space required for NetworkManger in F22)
 
(6 intermediate revisions by 2 users not shown)
Line 21: Line 21:


<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
= Change Proposal Name Cloud Systemd Networkd =
= Cloud Systemd Networkd =


== Summary ==
== Summary ==
Line 55: Line 55:
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
-->
-->
* Tracker bug: <will be assigned by the Wrangler>
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1238427 #1238427]


== Detailed Description ==
== Detailed Description ==

Latest revision as of 08:55, 6 August 2015


Cloud Systemd Networkd

Summary

We will use systemd-networkd to configure network in Cloud base image.

Owner

  • Name: Kushal Das
  • Email: kushaldas@gmail.com
  • Release notes owner:
  • Product: Cloud
  • Responsible WG: Cloud

Current status

Detailed Description

systemd-networkd is a system daemon that manages network configurations. It detects and configures network devices as they appear. Cloud base image will use systemd-networkd for its network.

systemd is a default package in Fedora, and we can use its latest feature to control the network configurations. We will remove the hacks we have in the current kickstart file, and use systemd tools for network configuration.

Benefit to Fedora

We will be getting rid of difficult-to-maintain legacy network scripts, and having only one unified network system. As we already have systemd on the image, it will help us by not adding any extra package in the Cloud base image. On a F22 cloud base, if we do dnf install NetworkManger, the package and dependencies take around 25MB of space. We can save this amount space by using networkd.


Scope

  • Proposal owners: The Cloud base image.
  • Other developers: N/A (not a System Wide Change)
  • Release engineering: N/A (not a System Wide Change)
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

N/A (not a System Wide Change)

User Experience

N/A (not a System Wide Change)

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No
  • Blocks product? product

Documentation

N/A (not a System Wide Change)

Release Notes