Proposal to Add: Log In/Out Blocker Criteria
by Geoffrey Marr
At today's blocker review meeting[0], we ran across a bug[1] that we
believe is bad enough to warrant blocker status, but as the criteria
currently stand, does not violate any particular criterion. The bug in
question has to do with logging out of one user account and logging into
another account that has already been accessed before during that boot. The
criterion listed in the bug[2] doesn't seem to fit, as it is more focused
on what happens after the system is booted (which does work in the case of
this bug). There is a Final criterion[3] that covers switching between two
accounts, where the data in the account switched out of is retained, but
that is not the case presented here (as this bug has to do with "logging
in/out" of accounts, not "switching" as they are defined technically).
Intellectually, we believe this type of bug should violate the criteria, as
it seems a common use-case, and so we are bringing it up as a possible
addition as there is nothing that currently covers this kind of bug.
The new criterion could look something like "A system with multiple user
accounts must be able to log in and out of said accounts as presented by
all release-blocking desktops in their default configuration."
We would appreciate feedback on this idea and the wording of the criterion.
Should this be a beta or a final blocker? If nothing is heard in a
reasonable amount of time (before next week's blocker review meeting), we
will assume there is no issue with the proposal and add it to the criteria
at that time.
Thanks for reading,
Geoff Marr
IRC: coremodule
[0]
https://meetbot.fedoraproject.org/fedora-blocker-review/2020-08-03/f33-bl...
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1861700
[2]
https://fedoraproject.org/wiki/Basic_Release_Criteria#Expected_installed_...
[3]
https://fedoraproject.org/wiki/Fedora_33_Final_Release_Criteria#User_swit...
3 years, 8 months
Btrfs by default status updates, 2020-08-09
by Chris Murphy
Update on features not yet enabled by default:
+ RFE: kickstart option to control discard configuration
https://bugzilla.redhat.com/show_bug.cgi?id=1860720
This can happen by using Anaconda kickstart argument '--fsoptions
discard=async' which will add the mount option to /etc/fstab. Not
decided is whether it's important enough of an optimization to do for
Fedora 33, or make it opt-in for now and consider it by default for
Fedora 34. Facebook has been using it in production for > 6 months,
it's solved many problems with no regressions. Fedora already enables
weekly fstrim via fstrim.timer by default. The advantage of
'discard=async' is mainly for workloads with heavy writes and deletes.
Once per week fstrim might not be frequent enough. Both fstrim and
discard=async mount option can peacefully co-exist.
+ RFE: enable compression on btrfs installs
https://bugzilla.redhat.com/show_bug.cgi?id=1851276
Btrfs offers two ways to enable compression: a mount option with
granular level (amount of compression); an XATTR that can be set per
subvolume, directory or file. Further there is a NOCOMPRESS flag that
could be set to selectively inhibit either of the prior two on a per
subvolume, directory or file basis.
The current idea is use kickstart argument '--fsoptions
compress=zstd:1' to enable compression file system wide with the
"least effort" compression level; and a kickstart %post script to
'btrfs property set -ti /home compression none' to disable compression
on /home.
Why? This isolates compression to system related things. While most
systems are expected to see performance improvement due to compression
and decompression reducing read and write latency, any write
performance hit would be limited to system writes which are generally
inconsequential: certain logs, configuration files, rpm+dnf+PackageKit
databases, and binaries during system updates. And this also leaves it
up to desktop integration for user selected compression.
Caveat? New subvolumes created in ~/home will not inherit this no
compression flag. New subvolumes will be compressed by default (so
long as the compress mount option is set). Also, it's not obvious what
is and isn't compressed. UI/UX in this area is limited. Improvements
are planned, but not in the Fedora 33 release time frame. There is a
'compsize' package in Fedora (all releases) that can show compression
information on directories and files.
It's not difficult for folks to opt in to both of these features if we
don't enable them by default in Fedora 33. In fact you can opt in now
with F31, F32, and F33. However, it is more difficult to figure out a
way, and commit, to enabling these features on upgrades from
F32/F33->F34.
Documentation:
+ LVM to Btrfs secret decoder ring
https://fedoraproject.org/wiki/User:Chrismurphy/lvm2btrfs
This isn't brand new but not previously shared in these updates. The
LVM to Btrfs idea is Langdon's. Calling it a secret decoder ring is my
idea because I'm a kid. And it's funny because this all open source so
it's not a secret. :D Ahh so easily amused.
What this needs, besides organizing and formatting, are use cases.
General purpose (common) use cases get higher priority than the
obscure. Feel free to reply to this email, or directly edit the wiki
and add use cases at the bottom. Advantage to no formatting? You don't
have to format your use case! Idea is to move this into Quick Docs.
+ Would it be useful to have a single reliable landing page for Btrfs resources?
https://fedoraproject.org/wiki/Btrfs
This is a bit stale. And in the context of Btrfs by default I think
it'd be more useful as a landing page of some sort. Make it like an
index or a FAQ, and link to the actual resource. For example, the
secret decoder ring! Any ideas about this are welcome.
Fixes:
+ armhfp desktop images are building again, and now have Btrfs enabled
by default. Testing appreciated!
3 years, 8 months
Fedora Workstation WG minutes, 2020-08-04
by Chris Murphy
==============================================
#fedora-meeting-2: Workstation WG (2020-08-04)
==============================================
Meeting started by cmurf at 05:13:38 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2020-08-05/workstation...
.
Meeting summary
---------------
* Rollcall (cmurf, 05:14:06)
* present wg members: cmurf, tpopela, aday, mclasen, Neal, jens,
langdon (cmurf, 05:14:08)
* regrets wg members: (cmurf, 05:14:10)
* present guests: salimma, feborges, dcavalca (cmurf, 05:14:12)
* Approve 28 July minutes (cmurf, 05:14:14)
* LINK:
https://meetbot.fedoraproject.org/teams/workstation/workstation.2020-07-2...
(cmurf, 05:14:16)
* AGREED: No objections - approved (cmurf, 05:14:18)
* Announcements (cmurf, 05:14:20)
* New login/logout release blocking criteria has been proposed
(cmurf, 05:14:22)
* GNOME 3.38 UI freeze is on Saturday (cmurf, 05:14:24)
* Nest starts on Friday (cmurf, 05:14:26)
* LINK: https://flocktofedora.org/ (cmurf, 05:14:28)
* Follow-ups & status reports (cmurf, 05:14:30)
* NVIDIA driver and UEFI secure boot (cmurf, 05:14:36)
* LINK: https://pagure.io/fedora-workstation/issue/155 (cmurf,
05:14:38)
* AGREED: Deferred until we have the right people available (cmurf,
05:14:42)
* Review Fedora 33 issues (cmurf, 05:14:44)
* LINK:
https://pagure.io/fedora-workstation/issues?status=Open&milestone=Fedora+...
(cmurf, 05:14:46)
* Open floor (cmurf, 05:15:10)
* BTRFS recovery experience (cmurf, 05:15:12)
* ACTION: Owen to write up his investigation results in more detail.
(cmurf, 05:15:26)
Meeting ended at 05:15:49 UTC.
Action Items
------------
* Owen to write up his investigation results in more detail.
Action Items, by person
-----------------------
* **UNASSIGNED**
* Owen to write up his investigation results in more detail.
People Present (lines said)
---------------------------
* cmurf (45)
* zodbot (7)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
3 years, 8 months
