[prev in list] [next in list] [prev in thread] [next in thread]
List: vdsm-devel
Subject: =?utf-8?q?=5Bovirt-devel=5D?= Fwd: Fedora 30 System-Wide Change: Deprecating /etc/sysconfig/nfs
From: Sandro Bonazzola <sbonazzo () redhat ! com>
Date: 2018-10-29 13:10:01
Message-ID: CAPQRNTnXrZPpEJt+2Ce+QxWiSR_7uPDcHjnBNGat4OZNouZa3A () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
FYI
---------- Forwarded message ---------
From: Ben Cotton <bcotton@redhat.com>
Date: mer 17 ott 2018 alle ore 15:29
Subject: Fedora 30 System-Wide Change: Deprecating /etc/sysconfig/nfs
To: <devel@lists.fedoraproject.org>, <devel-announce@lists.fedoraproject.org
>
https://fedoraproject.org/wiki/Changes/nfs.conf
== Summary ==
Deprecate /etc/sysconfig/nfs and only use /etc/nfs.conf to configure
NFS daemons.
== Owner ==
* Name: Steve Dickson
* Email: steved@redhat.com
== Detailed Description ==
Since the beginning /etc/sysconfig/nfs has been used to configure
the NFS server daemons by supply command line arguments
to the daemons or commands via SysVinit scripts.
Then systemd(1) came along and the idea of daemons
self-configuration was started. Meaning daemons and commands
would get their configurations from a file, not the command
line like with SysVinit scripts.
Back in late 2016, Neil Brown from SuSe, implemented this changed.
He built into each daemon the ability to read from
one central file, /etc/nfs.conf. See nfs.conf(5) for details.
After this work made it upstream, I a wrote patch that added
back the ability to use /etc/sysconfig/nfs to maintain
backwards compatibility which has lasted for the last few Fedora releases.
I think at this point, the timing is right to introduce this single
file configuration to Fedora 30.
== Benefit to Fedora ==
* Having a single file configuration will help IT automation systems
like Ansible configure NFS servers.
* This change also simplifies the systemd scrips.
* Having two ways of configuring NFS is not desirable. The only
reason there has been no problems is because nobody know about
/etc/nfs.conf
* There is a new command, nfsconf(8), that checks the correctness of
/etc/nfs.conf
== Scope ==
* Proposal owners: Steve Dickson <steved@redhat.com>
* Other developers: Justin Mitchell <jumitche@redhat.com>
* Release engineering: [https://pagure.io/releng/issue/7864 #7864 F30:
Deprecating /etc/sysconfig/nfs]
** List of deliverables: nfs-utils-2.3.3-1.fc30
* Policies and guidelines: The guidelines to use /etc/nfs.conf are
already being install with nfs.conf(5) and nfsconf(8) manpages
* Trademark approval: No trademarks are being changed so no approval is
needed.
== Upgrade/compatibility impact ==
In [https://bugzilla.redhat.com/show_bug.cgi?id=1619270 BZ1619270] a
python script that will convert a sysconfig/nfs config into nfs.conf
config. There are a couple thoughts on how to use it.
On clean installs, when sysconfig/nfs does not exist, sysconfig/nfs
wil still be installed with directions to use nfs.conf to do the
configuration.
When sysconfig/nfs does exist, the configuration will '''not''' be
overwritten, but the systemd scripts will not use the file to
configure NFS.
The two thoughts on how to use python script:
# Have the upgrade run the script and maybe throw out a message that
the configuration has now been moved to nfs.conf
# Throw a message indicating the NFS configuration has changed and
then have the admin run the script
The first thought is probably the cleanest but changing configurations
behind admin's back is not very nice... I am very open on how to use
this script.
== How To Test ==
With the new nfsconf(8) command, the nfs.conf can be tested for
correctness, other than that, we should do the same testing as we do
today
== User Experience ==
After the initial shock, I think users will embrace the new
configuration. Being able to configure NFS via IT automation systems
(aka Ansible) is a step in the right direction. Having a command to
check the correctness of the configuration will be welcome.
== Dependencies ==
There are no dependencies that I know of.
== Contingency Plan ==
* Contingency mechanism: Revert the commit that removed support for
/etc/sysconfig/nfs.
* Contingency deadline: 2019-03-05 (Beta Freeze)
* Blocks release? No
* Blocks product? No
== Documentation ==
There are two man pages, nfs.conf(5) and nfsconf(8).
== Release Notes ==
The new way of configuring NFS should be release noted.
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
--
SANDRO BONAZZOLA
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo@redhat.com
<https://red.ht/sig>
<https://www.redhat.com/en/events/red-hat-open-source-day-italia?sc_cid=701f2000000RgRyAAK>
[Attachment #5 (text/html)]
<div dir="ltr">FYI<br><br><div class="gmail_quote"><div dir="ltr">---------- \
Forwarded message ---------<br>From: <strong class="gmail_sendername" dir="auto">Ben \
Cotton</strong> <span dir="ltr"><<a \
href="mailto:bcotton@redhat.com">bcotton@redhat.com</a>></span><br>Date: mer 17 \
ott 2018 alle ore 15:29<br>Subject: Fedora 30 System-Wide Change: Deprecating \
/etc/sysconfig/nfs<br>To: <<a \
href="mailto:devel@lists.fedoraproject.org">devel@lists.fedoraproject.org</a>>, \
<<a href="mailto:devel-announce@lists.fedoraproject.org">devel-announce@lists.fedoraproject.org</a>><br></div><br><br><a \
href="https://fedoraproject.org/wiki/Changes/nfs.conf" rel="noreferrer" \
target="_blank">https://fedoraproject.org/wiki/Changes/nfs.conf</a><br> <br>
== Summary ==<br>
Deprecate /etc/sysconfig/nfs and only use /etc/nfs.conf to configure<br>
NFS daemons.<br>
<br>
== Owner ==<br>
* Name: Steve Dickson<br>
* Email: <a href="mailto:steved@redhat.com" target="_blank">steved@redhat.com</a><br>
<br>
== Detailed Description ==<br>
<br>
Since the beginning /etc/sysconfig/nfs has been used to configure<br>
the NFS server daemons by supply command line arguments<br>
to the daemons or commands via SysVinit scripts.<br>
<br>
Then systemd(1) came along and the idea of daemons<br>
self-configuration was started. Meaning daemons and commands<br>
would get their configurations from a file, not the command<br>
line like with SysVinit scripts.<br>
<br>
Back in late 2016, Neil Brown from SuSe, implemented this changed.<br>
He built into each daemon the ability to read from<br>
one central file, /etc/nfs.conf. See nfs.conf(5) for details.<br>
<br>
After this work made it upstream, I a wrote patch that added<br>
back the ability to use /etc/sysconfig/nfs to maintain<br>
backwards compatibility which has lasted for the last few Fedora releases.<br>
<br>
I think at this point, the timing is right to introduce this single<br>
file configuration to Fedora 30.<br>
<br>
== Benefit to Fedora ==<br>
<br>
* Having a single file configuration will help IT automation systems<br>
like Ansible configure NFS servers.<br>
* This change also simplifies the systemd scrips.<br>
* Having two ways of configuring NFS is not desirable. The only<br>
reason there has been no problems is because nobody know about<br>
/etc/nfs.conf<br>
* There is a new command, nfsconf(8), that checks the correctness of<br>
/etc/nfs.conf<br>
<br>
== Scope ==<br>
* Proposal owners: Steve Dickson <<a href="mailto:steved@redhat.com" \
target="_blank">steved@redhat.com</a>><br>
* Other developers: Justin Mitchell <<a href="mailto:jumitche@redhat.com" \
target="_blank">jumitche@redhat.com</a>><br>
* Release engineering: [<a href="https://pagure.io/releng/issue/7864" \
rel="noreferrer" target="_blank">https://pagure.io/releng/issue/7864</a> #7864 \
F30:<br> Deprecating /etc/sysconfig/nfs]<br>
** List of deliverables: nfs-utils-2.3.3-1.fc30<br>
<br>
<br>
* Policies and guidelines: The guidelines to use /etc/nfs.conf are<br>
already being install with nfs.conf(5) and nfsconf(8) manpages<br>
<br>
* Trademark approval: No trademarks are being changed so no approval is needed.<br>
<br>
== Upgrade/compatibility impact ==<br>
In [<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1619270" rel="noreferrer" \
target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1619270</a> BZ1619270] \
a<br> python script that will convert a sysconfig/nfs config into nfs.conf<br>
config. There are a couple thoughts on how to use it.<br>
<br>
On clean installs, when sysconfig/nfs does not exist, sysconfig/nfs<br>
wil still be installed with directions to use nfs.conf to do the<br>
configuration.<br>
<br>
When sysconfig/nfs does exist, the configuration will \
'''not''' be<br> overwritten, but the systemd scripts will \
not use the file to<br> configure NFS.<br>
<br>
The two thoughts on how to use python script:<br>
# Have the upgrade run the script and maybe throw out a message that<br>
the configuration has now been moved to nfs.conf<br>
# Throw a message indicating the NFS configuration has changed and<br>
then have the admin run the script<br>
<br>
The first thought is probably the cleanest but changing configurations<br>
behind admin's back is not very nice... I am very open on how to use<br>
this script.<br>
<br>
== How To Test ==<br>
With the new nfsconf(8) command, the nfs.conf can be tested for<br>
correctness, other than that, we should do the same testing as we do<br>
today<br>
<br>
== User Experience ==<br>
After the initial shock, I think users will embrace the new<br>
configuration. Being able to configure NFS via IT automation systems<br>
(aka Ansible) is a step in the right direction. Having a command to<br>
check the correctness of the configuration will be welcome.<br>
<br>
== Dependencies ==<br>
There are no dependencies that I know of.<br>
<br>
== Contingency Plan ==<br>
* Contingency mechanism: Revert the commit that removed support for<br>
/etc/sysconfig/nfs.<br>
* Contingency deadline: 2019-03-05 (Beta Freeze)<br>
* Blocks release? No<br>
* Blocks product? No<br>
<br>
== Documentation ==<br>
There are two man pages, nfs.conf(5) and nfsconf(8).<br>
<br>
== Release Notes ==<br>
The new way of configuring NFS should be release noted.<br>
<br>
-- <br>
Ben Cotton<br>
Fedora Program Manager<br>
TZ=America/Indiana/Indianapolis<br>
_______________________________________________<br>
devel mailing list -- <a href="mailto:devel@lists.fedoraproject.org" \
target="_blank">devel@lists.fedoraproject.org</a><br> To unsubscribe send an email to \
<a href="mailto:devel-leave@lists.fedoraproject.org" \
target="_blank">devel-leave@lists.fedoraproject.org</a><br> Fedora Code of Conduct: \
<a href="https://getfedora.org/code-of-conduct.html" rel="noreferrer" \
target="_blank">https://getfedora.org/code-of-conduct.html</a><br> List Guidelines: \
<a href="https://fedoraproject.org/wiki/Mailing_list_guidelines" rel="noreferrer" \
target="_blank">https://fedoraproject.org/wiki/Mailing_list_guidelines</a><br> List \
Archives: <a href="https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org" \
rel="noreferrer" target="_blank">https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org</a><br>
</div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature" \
data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div \
dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div \
dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><p \
style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-weight:bold;margin:0px;padding:0px;font-size:14px;text-transform:uppercase"><span>SANDRO</span> \
<span>BONAZZOLA</span></p><p style="margin:0px 0px 4px"><span \
style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:10px;text-transform:uppercase">MANAGER, \
SOFTWARE ENGINEERING, </span><font color="#000000" face="overpass, sans-serif"><span \
style="font-size:10px;text-transform:uppercase"><span style="margin:0px"></span>EMEA \
R&D RHV</span></font></p><p \
style="font-family:overpass,sans-serif;margin:0px;font-size:10px;color:rgb(153,153,153)"><a \
href="https://www.redhat.com/" style="color:rgb(0,136,206);margin:0px" \
target="_blank">Red Hat <span>EMEA</span></a></p><p \
style="font-family:overpass,sans-serif;margin:0px 0px \
6px;font-size:10px;color:rgb(153,153,153)"><span style="margin:0px;padding:0px"><a \
href="mailto:sbonazzo@redhat.com" style="color:rgb(0,136,206);margin:0px" \
target="_blank">sbonazzo@redhat.com</a> </span></p><table border="0" \
style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:medium"><tbody><tr><td \
width="100px"><a href="https://red.ht/sig" target="_blank"><img \
src="https://www.redhat.com/files/brand/email/sig-redhat.png" width="90" \
height="auto"></a></td></tr></tbody></table><a \
href="https://www.redhat.com/en/events/red-hat-open-source-day-italia?sc_cid=701f2000000RgRyAAK" \
target="_blank"><span></span><span></span><img \
src="http://images.engage.redhat.com/EloquaImages/clients/RedHat/%7B98cb2f7e-01c6-4d72-b84d-99545fa13c39%7D_RH_OSD_ITALY_Banner_350x50_esign.png"></a><table \
border="0" style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:medium">< \
tbody><tr></tr></tbody></table></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
[Attachment #6 (text/plain)]
_______________________________________________
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/OCC5BCAMJT5WAHBL27PEU2KZV4DLUEP6/
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic