Re: Release criteria proposal: networking requirements
That all sounds reasonable to me. Does wifi fall into this as well? Stephen On Fri, 2020-08-21 at 17:11 -0700, Adam Williamson wrote: > 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 > ___ > test mailing list -- test@lists.fedoraproject.org > To unsubscribe send an email to test-le...@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/test@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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/test@lists.fedoraproject.org
Re: btrfs missing/broken from anaconda install dialogues
Hello George, BTRFS is definitely supported by Anaconda. I installed Fedora 33 Silverblue Rawhide onto BTRFS. I believe the installer uses a default layout if you choose the btrfs option with automatic partition layout. Of course I haven't tried a VM of it. F32 (current stable release) is able to do this too with the exception of boot options needing manual intervention in order to boot ostree based systems. There is a good discussion here https://discussion.fedoraproject.org/t/btrfs-push-with-fedora-where-does-that-leave-silverblue/21760 Regards, Stephen On Thu, 2020-08-13 at 15:29 +, George R Goffe via test wrote: > Hi, > > I was reading about filesystems in Linux, specifically RedHat > systems, and there was a lot about btrfs and how good it is. > > With this in mind, I tried to install my favorite Fedora Core system > (Currently FC33) uner QEMU, but saw in the custom partitioning part > of the dialogues that btrfs was missing. This was where ext3, ext4, > xfs, etc were listed. There was a place where btrfs was listed so I > tried installing from there. I have pre-partitioned a virtual drive > and made btrfs the filesystem on these partitions (except for swap). > Anaconda did sense these partitions and filetypes but when I got > around to assigning partitions to mount points, the process would not > let me make a mount point for "/". For one, the sort of the display > was NOT by device, i.e., /dev/sda1, but rather some other sort > "field". I was expecting a similar partitioning process but this is > not the case. > > I guess I'm asking two questions here. 1) is btrfs supported by > anaconda, 2) is it the process broken for btrfs? > > Of course, my thanks to all who respond but also to the whole group. > You "guys, gals" are AWESOME! > > Best Regards, > > George... > ___ > test mailing list -- test@lists.fedoraproject.org > To unsubscribe send an email to test-le...@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/test@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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/test@lists.fedoraproject.org
Re: Introduction
I'm pleased to be a part of the group. Thank you for sponsoring me.
Stephen
On Sun, 2020-08-09 at 20:55 +0200, Alessio wrote:
> Hello jakfrost!
>
> Welcome to Fedora QA, I have sponsored your QA group request.
>
> You can start off by testing updates in <
> http://bodhi.fedoraproject.org/> for Fedora 31, Fedora 32, and Fedora
> 33 (Rawhide). Update testing is where a tester tests a package and
> gives out a +1 Karma for PASS and -1 Karma for FAIL. You can go to
> bodhi.fedoraproject.org where you can sort the packages with Fedora
> Releases and tags with "pending" & "testing". You can read much about
> update testing here [1]. You can also use the command fedora-easy-
> karma
> from your terminal for giving out feedbacks.
>
> You can start with Release Validation testing. In Release Validation
> all you need to do is to check the nightly/TC/RC against certain
> criteria. For example, let's take the latest compose (Fedora 33
> Rawhide
> 20200804.n.0), you can run the test cases which are mentioned here
> [2]
> and submit your results in the test matrix.
>
> Note that each of the test cases[3] will have "How to test" section
> which will have the steps (to be executed sequentially) and if the
> results match with the expected results you can mark it as pass by
> editing the wiki page {{result|PASS|}}. Always make
> sure
> to check for "Associated release criterion" which can be found on the
> top of test case page, if your test case fails you can mark it fail
> by
> editing the wiki page {{result|FAIL|}} and file a bug
> at
> RHBZ [4] under Fedora.
>
>
> You can always find the ‘current’ validation pages using these
> addresses:
>
> <
> https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
> >
>
>
>
>
>
>
> Keep an eye to Fedora Test Days, they will be announced here and
> usually in the Community Blog or on the Magazine. They are events
> useful to test some new feature or big change.
>
>
> For Automation, you can start looking at Open QA <
> https://fedoraproject.org/wiki/OpenQA>;.
>
>
> Other Blogs to read:
> - <
> https://communityblog.fedoraproject.org/getting-started-fedora-qa-part-1/
> - <
> https://communityblog.fedoraproject.org/getting-started-fedora-qa-part-2/
> - <
> https://communityblog.fedoraproject.org/getting-started-fedora-qa-part-3/
>
> [1]
> [2] <
> https://fedoraproject.org/wiki/Test_Results:Fedora_33_Rawhide_20200731.n.0_Summary
> [3] i.e.
> [4]
Introduction
Hello Fedora QA, My name is Stephen Snow aka jakfrost, and have been a Fedora user since the beginning. I am currently a writer and editor for Fedora Magazine, and have contributed to the Silverblue documentation in a small way. I also spend some time helping out at discussion.fp.o as a moderator and support wherever I can. For my day job, I design/implement/service industrial control systems for my customers. I would like to get more technically involved in the community and feel helping with testing is a good place to begin. The more testers the better the Fedora. I am looking forward to joining the group, and thank you for the opportunity to contribute back into the community. Regards, Stephen Snow -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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/test@lists.fedoraproject.org
