Hi folks!
So at this week's blocker review meeting, the fact that we don't have
explicit networking requirements in the release criteria really started
to bite us. In the past we have squeezed networking-related issues in
under other criteria, but for some issues that's really difficult,
notably VPN issues. So, we agreed we should draft some explicit
networking criteria.
This turns out to be a big area and quite hard to cover (who'd've
thought!), but here is at least a first draft for us to start from. My
proposal would be to add this to the Basic criteria. I have left out
some wikitext stuff from the proposal for clarity; I'd add it back in
on actually applying the proposed changes. It's just formatting stuff,
nothing that'd change the meaning. Anyone have thoughts, complaints,
alternative approaches, supplements? Thanks!
=== Network requirements ===
Each of these requirements apply to both installer and installed system
environments. For any given installer environment, the 'default network
configuration tools' are considered to be those the installer documents
as supported ways to configure networking (e.g. for anaconda-based
environments, configuration via kernel command line options, a
kickstart, or interactively in anaconda itself are included).
==== Basic networking ====
It must be possible to establish both IPv4 and IPv6 network connections
using DHCP and static addressing. The default network configuration
tools for the console and for release-blocking desktops must work well
enough to allow typical network connection configuration operations
without major workarounds. Standard network functions such as address
resolution and connections with common protocols such as ping, HTTP and
ssh must work as expected.
Footnote titled "Supported hardware": Supported network hardware is
hardware for which the Fedora kernel includes drivers and, where
necessary, for which a firmware package is available. If support for a
commonly-used piece or type of network hardware that would usually be
present is omitted, that may constitute a violation of this criterion,
after consideration of the [[Blocker_Bug_FAQ|hardware-dependent-
issues|normal factors for hardware-dependent issues]]. Similarly,
violations of this criteria that are hardware or configuration
dependent are, as usual, subject to consideration of those factors when
determining whether they are release-blocking
==== VPN connections ====
Using the default network configuration tools for the console and for
release-blocking desktops, it must be possible to establish a working
connection to common OpenVPN, openconnect-supported and vpnc-supported
VNC servers with typical configurations.
Footnote title "Supported servers and configurations": As there are
many different VPN server applications and configurations, blocker
reviewers must use their best judgment in determining whether
violations of this criterion are likely to be encountered commonly
enough to block a release, and if so, at which milestone. As a general
principle, the more people are likely to use affected servers and the
less complicated the configuration required to hit the bug, the more
likely it is to be a blocker.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
==============================================
#fedora-meeting-2: Workstation WG (2021-07-13)
==============================================
Meeting started by cmurf at 17:40:27 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2021-07-13/workstation.2…
.
Meeting summary
---------------
* Rollcall (cmurf, 17:40:48)
* present: Matthias, Neal, Chris, Tomas, Jens, Michael, Allan
(secr.), Owen (cmurf, 17:40:50)
* regrets: (cmurf, 17:40:52)
* present guests: James Cassell (cmurf, 17:40:54)
* Approval of June 29 minutes (cmurf, 17:40:56)
* LINK:
https://meetbot.fedoraproject.org/teams/workstation/workstation.2021-06-30-…
(cmurf, 17:40:58)
* AGREED: Approved - no objections (cmurf, 17:41:00)
* Announcements, follow-ups, status reports (cmurf, 17:41:02)
* GNOME UI freeze is 14 August - nearly 4 weeks away. 41.alpha is due
out soon, too. (cmurf, 17:41:04)
* Owen has created 2 change proposals for F35. Some questions about
Flathub in the mailing list discussion. It looks like it's going to
be approved. (cmurf, 17:41:08)
* LINK: https://pagure.io/fesco/issue/2641 (cmurf, 17:41:10)
* LINK: https://pagure.io/fesco/issue/2643 (cmurf, 17:41:12)
* Workstation web presence goals (cmurf, 17:41:16)
* LINK: https://pagure.io/fedora-workstation/issue/220 (cmurf,
17:41:18)
* AGREED: Deferred - no updates (cmurf, 17:41:20)
* homed (cmurf, 17:41:22)
* ACTION: Matthias to send an invite for 28 July at 13:30 UTC (cmurf,
17:41:26)
* Review F35 change proposal: Rebase firewalld to upstream v1.0.0
(cmurf, 17:41:28)
* LINK: https://pagure.io/fedora-workstation/issue/234 (cmurf,
17:41:30)
* AGREED: The change proposal doesn't affect us. \o/ (cmurf,
17:41:32)
* Open floor (cmurf, 17:41:34)
* Please report oomd related bugs or confusion against systemd
component, and cc: relevant people (cmurf, 17:41:40)
Meeting ended at 17:42:08 UTC.
Action Items
------------
* Matthias to send an invite for 28 July at 13:30 UTC
Action Items, by person
-----------------------
* **UNASSIGNED**
* Matthias to send an invite for 28 July at 13:30 UTC
People Present (lines said)
---------------------------
* cmurf (31)
* zodbot (7)
* Neal (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot