Anaconda-devel February 2021

anaconda-devel@lists.stg.fedoraproject.org

10 participants
4 discussions

btrfs compression by default
by Chris Murphy 05 Mar '21

05 Mar '21

Hi, This is in regards to this Fedora 34 change: https://fedoraproject.org/wiki/Changes/BtrfsTransparentCompression#Scope The gist is to do 'mount -o compress=zstd:1' anytime Btrfs is used, whether Destination Installation>Automatic or Custom or Advanced-Custom. Apply it during the installation, and add it to /etc/fstab. Somehow I got confused thinking that autopart supports --fsoptions, and that would be the way to do this. But (a) --fsoptions isn't supported with autopart, and (b) it wouldn't be a universal approach anyway. And we want this to be consistent. Now I'm thinking it needs to go somewhere in: https://github.com/storaged-project/blivet/blob/3.4-devel/blivet/devices/bt… Am I on the right track, or does it need to go somewhere else, or in addition to that? Thanks, -- Chris Murphy

7 18

Migrating from pytz to dateutil.tz + zoneinfo
by Miro Hrončok 12 Feb '21

12 Feb '21

Hello fellow serpents. I'm one of the Python maintainers in Fedora and RHEL. I've noticed anaconda-core uses the third party pytz module to work with TZ (timzone) data. Since Python 3.9, there is a zoneinfo module in the Python standard library: https://docs.python.org/3/library/zoneinfo.html https://www.python.org/dev/peps/pep-0615/ Hence we would like to: - deprecate pytz in Fedora - avoid pytz in RHEL 10+ Since anaconda is one of the "important" dependents on pytz from both Fedora and RHEL, I'm reaching out to you in advance. Could you please consider migrating to zoneinfo? I have not done any such migrations yes, so I don't have any useful links or pointers. However, if you'd be interested I can try with anaconda myself. Note that I don't know if anaconda code from the default branch at https://github.com/rhinstaller/anaconda needs to support older Pythons or not. If needed, I can try to make the changes more universal. Let me know if you need some more info, a patch, or just time to handle it yourselves. Thanks, (Please CC me in replies to the list, I don't receive the usual list traffic.) -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

2 2

btrfs mkfs options for root filesystem?
by Matthew Miller 09 Feb '21

09 Feb '21

I wanted to use `--csum xxhash` to create the btrfs filesystem on the system I just installed. Unfortunately, this proves to be impossible, since Anaconda requires that / be formatted by Anaconda. It's a small performance win (33% faster) but also twice the bits for a much smaller collision risk. Is there a way to select or force the options used for btrfs? -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

3 5

Fwd: Re: Fedora 34 Change: Ignore Anaconda kernel boot parameters without 'inst.' prefix (System-Wide change)
by jkonecny＠redhat.com 03 Feb '21

03 Feb '21

Hi everyone, Forwarding this message from the fedora-devel list also to our anaconda devel list to spread the message a bit more. Best Regards, Jirka -------- Forwarded Message -------- From: jkonecny(a)redhat.com To: Development discussions related to Fedora <devel(a)lists.fedoraproject.org>, devel-announce(a)lists.fedoraproject.org Subject: Re: Fedora 34 Change: Ignore Anaconda kernel boot parameters without 'inst.' prefix (System-Wide change) Date: Tue, 02 Feb 2021 17:47:16 +0100 Hello everyone, We've created patch to require 'inst.' prefix for all Anaconda kernel boot arguments. To make transition smoother warnings will stay there. That means that you will get warning but the argument will be ignored and not processed by Anaconda. Pull request for the change: https://github.com/rhinstaller/anaconda/pull/3136 We want to give everyone a bit more time, so we are planning to merge this in two days. If you have any objections please feel free to write those to the pull request. Best Regards, Jirka Konecny On Mon, 2020-12-07 at 10:45 -0500, Ben Cotton wrote: > https://fedoraproject.org/wiki/Changes/Ignore_Anaconda_kernel_boot_paramete… > > == Summary == > Right now Anaconda allows usage of boot options both with the 'inst' > prefix (inst.stage2=) and without (stage2=). We would like to ignore > the use of Anaconda kernel boot parameters which do not contain the > 'inst.' prefix. > > == Owner == > * Name: [[User:jkonecny| Jiří Konečný]] > * Email: <jkonecny(a)redhat.com> > > > == Detailed Description == > Anaconda allows you to use kernel boot parameters with and without > the 'inst.' prefix right now (e.g. inst.repo= / repo=). However, > specifying boot parameters without the 'inst' prefix has not been > recommended for years and has been deprecated since Fedora 33. We > (Anaconda team) would like to make it an official requirement now > that users must specify the 'inst.' prefix all the time. > > The reason for this is frequent parameter conflicts with other > projects. We already had a few issues with conflicts in the past, > such as if the user ran an installation with `debug`. In that case > the installation boot would enable debug mode for the kernel and also > for Anaconda which is probably not what the user intended. > Another reason is to make it readable at first glance what belongs to > Dracut (rd.), kernel (no prefix) or Anaconda (inst.). > > == Feedback == > We have sent mail about doing the deprecation on Fedora 33. The only > issue there was why the prefix is 'inst.' and not 'anaconda.'. > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… > > == Benefit to Fedora == > This change should make crystal clear what kernel boot parameters are > processed by the Anaconda installer. > It will also avoid conflicts with other kernel boot parameters. > > == Scope == > * Proposal owners: Remove support to process arguments without the > 'inst.' prefix and require the 'inst.' prefix for kernel boot > parameters consumed by Anaconda. > > * Other developers: > All configurations using the not-recommended solution without prefix > will have to change the invocation of the kernel boot options > consumed by Anaconda. These users are already warned since Fedora 33 > after boot. > This should not be a problem for ISOs we ship because they already > use the recommended 'inst.' prefix everywhere. However, it will > probably touch some custom PXE configurations and other custom ISO > configurations which are prone to this, because users often want to > save typing and not explicitly write the 'inst.' prefix. Fortunately, > most of these configuration changes shouldn't be that hard to change. > > * Release engineering: [https://pagure.io/releng/issue/9889 #9889] > * Policies and guidelines: This should not be required. All the > documentation should use the recommended 'inst.' prefix already. > * Trademark approval: No (not needed for this Change) > * Alignment with Objectives: No > > > == Upgrade/compatibility impact == > If your custom infra configuration is not updated then new Fedora > installations could not install correctly. Most probably the ISO will > not boot (use of 'stage2=') or your repositories won't be used (use > of 'repo='). > > > == How To Test == > # You need a Virtual Machine and ISO for testing. > # Boot the installation using the ISO and try Anaconda specific > kernel boot parameters. See here to find out the list > https://anaconda-installer.readthedocs.io/en/latest/boot-options.html > . > # Parameters without the prefix should be ignored and with the prefix > should be used. > > > == User Experience == > Users of Fedora official ISOs should not be impacted because all the > Fedora official ISOs should already use the recommended prefix. > > == Dependencies == > Don't know about any packages impacted by this change. > > > == Contingency Plan == > * Contingency mechanism: The Anaconda team will revert code changes > and get back support for boot parameters without the 'inst.' prefix. > * Contingency deadline: Final Freeze > * Blocks release? No > * Blocks product? This won't require changes for any specific > product. > > == Documentation == > I don't think we need to document this change other than in Release > Notes. As mentioned before, the solution without 'inst.' prefix has > not been recommended for years and it should not be used anywhere in > the official documentation. > > > > _______________________________________________ > devel mailing list -- devel(a)lists.fedoraproject.org > To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: > https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Anaconda-devel February 2021