⛅ Backporting azure-cli to EPEL9
by Major Hayden
👋🏻 Hey there,
Now that azure-cli is working well in Fedora 35/36/37, I've been approached to get it ready in EPEL9. Packaging the azure-cli package and some of the python-azure-* packages it needs doesn't look too difficult.
However, there are a lot of dependencies to consider. I maintain quite a few of these already, but there are many I do not maintain.
I'm starting to pile things into a COPR[0] to get an idea of what will be involved.
Would azure-cli be useful to anyone in EPEL?
If so, would you want to help with dependencies? 😉 😉 😉
Thanks for reading this far!
[0] https://copr.fedorainfracloud.org/coprs/mhayden/azure-cli-epel9/monitor/
--
Major Hayden
1 year
F36 testing needed: cloud-on-real-cloud
by Ben Cotton
Hello, my cloudy friends,
Adam noted in yesterday's Go/No-Go meeting that we're short on test
coverage with Cloud images on real clouds. We'll have a new RC coming
in a few days to address some outstanding blockers, but in the
meantime, if we could start filling in the test matrix[1], I expect
most tests should carry over just fine.
As a reminder, our next go/no-go meeting is Thursday 5 May.
[1] https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
1 year
[F36] Testing for Cloud Images
by Duncan, David
Hi all,
If you working on testing images, I’ll be hanging around in Matrix (@davdunc:fedora.im) and Libera chat (davdunc) this weekend and working on testing for Azure, AWS, and GCP.
Let me know if you run into issues or need additional support for testing.
- David
1 year
Fedora Cloud Meeting Minutes 2022-04-14
by Duncan, David
Meeting ended Thu Apr 14 15:58:53 2022 UTC.
Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-04-14/fedora_clou...
Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2022-04-14/fedora_clou...
Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-04-14/fedora_clou...
=======================================
#fedora-meeting-1: fedora_cloud_meeting
=======================================
Meeting started by davdunc at 15:01:03 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-1/2022-04-14/fedora_clou...
.
Meeting summary
---------------
* roll call (davdunc, 15:01:17)
* Action items from last meeting (davdunc, 15:04:02)
* ACTION: davdunc to complete the img-mash packaging by April 16, 2022
(davdunc, 15:07:01)
* ACTION: davdunc to write or delegate a blog post for f36 release
(davdunc, 15:10:57)
* LINK: https://pagure.io/cloud-sig/issue/375 (davdunc, 15:12:37)
* coordinating default/fallback hostname changes (dustymabe, 15:14:27)
* LINK: https://pagure.io/cloud-sig/issue/376 (dustymabe, 15:31:10)
* LINK: https://pagure.io/cloud-sig/issue/376 (davdunc, 15:31:25)
* Publish AWS aarch64 AMI for Fedora 35 (davdunc, 15:31:58)
* LINK: https://pagure.io/cloud-sig/issue/365 (davdunc, 15:32:13)
* F36 Test days (davdunc, 15:36:32)
* LINK: https://instances.vantage.sh/ doesn't list an m5g.metal
(dustymabe, 15:44:17)
* Proposed: Build a "NeuroFedora Cloud Image" (davdunc, 15:51:30)
* LINK: https://pagure.io/cloud-sig/issue/374 (davdunc, 15:51:47)
* Open Floor (davdunc, 15:57:19)
Meeting ended at 15:58:53 UTC.
Action Items
------------
* davdunc to complete the img-mash packaging by April 16, 2022
* davdunc to write or delegate a blog post for f36 release
Action Items, by person
-----------------------
* davdunc
* davdunc to complete the img-mash packaging by April 16, 2022
* davdunc to write or delegate a blog post for f36 release
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* davdunc (118)
* dustymabe (56)
* zodbot (9)
* mhayden (8)
Generated by `MeetBot`_ 0.4
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
1 year, 1 month
Fwd: [Now Playing] Fedora 36 Test Days
by Luna Jernberg
---------- Forwarded message ---------
From: Luna Jernberg <droidbittin(a)gmail.com>
Date: Fri, Apr 8, 2022 at 12:26 PM
Subject: Re: [Now Playing] Fedora 36 Test Days
To: For testing and quality assurance of Fedora releases <
test(a)lists.fedoraproject.org>, <coreos(a)lists.fedoraproject.org>, <
cloud(a)lists.fedoraproject.org>, Sumantro Mukherjee <sumukher(a)redhat.com>,
Luna Jernberg <bittin(a)fedoraproject.org>, Martin Jernberg <
droidbittin(a)gmail.com>
Cc: <test-announce(a)lists.fedoraproject.org>, Community support for Fedora
users <users(a)lists.fedoraproject.org>, <kernel(a)lists.fedoraproject.org>
Hey!
Helping out here and there when i can over the week :)
On Fri, Apr 8, 2022 at 12:10 PM Sumantro Mukherjee <sumukher(a)redhat.com>
wrote:
> Hey Fedorans,
>
> As most of you might know, we have Fedora testing events happening where
> you all
> can participate. As of today, we are running 3 events in parallel.
>
> 1. Kernel 5.17 Test Week [0]
> 2. Fedora 36 CoreOS [1]
> 3. Fedora Cloud Test Day [2]
>
> These are events that are easy to start off if you are new to Fedora
> and some of them
> even reward you with a Fedora Badge as token of gratitude and reward
> for your time and energy
> that you spent contributing!
>
> The wikis below will guide you through the instructions and how to
> participate. In case of an
> unlikely event of things not working as intended. File a bug and if
> you have any questions,
> reach out to @test list directly.
>
> In the coming week, we have two of the most community impacting topics
> that we will test for
> the Audio and Upgrade path to Fedora 36 from Fedora 35 and Fedora 34.
> More details can you found
> in this Fedora Magazine Article[3]
>
> [0]
> http://fedoraproject.org/wiki/Test_Day:2022-04-03_Kernel_5.17_Test_Week
> [1] http://fedoraproject.org/wiki/Test_Day:Fedora_36_CoreOS_2022-04-04
> [2]
> http://fedoraproject.org/wiki/Test_Day:2022-04-08_Fedora_36_Cloud_Testday
> [3]
> https://fedoramagazine.org/contribute-at-the-fedora-kernel-5-17-coreos-cl...
>
>
> --
> //sumantro
> Fedora QE
> TRIED AND PERSONALLY TESTED, ERGO TRUSTED
> _______________________________________________
> test mailing list -- test(a)lists.fedoraproject.org
> To unsubscribe send an email to test-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/test@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>
1 year, 1 month
Fedora 36 validation testing event: let's do full testing of Fedora
36 Branched 20220401.n.0
by Adam Williamson
Hi folks! Trying something a bit new here. I've nominated today's
Fedora 36 nightly compose for validation testing. We do this regularly
in any case, but I'm sending this out to a wider group and asking folks
to treat this nightly as it it were a release candidate, and try to
complete the *full* set of Final validation tests on it. The idea is to
try and make sure we get all the tests done well ahead of the Go/No-Go
Meeting, so we can identify any remaining blocker bugs *now*, not have
to try and deal with them in a hurry later.
Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/36 . You can use this
to prioritize tests that have not yet been run at all.
You can see all results, find testing instructions and image download
locations, and enter results on the Summary page:
https://fedoraproject.org/wiki/Test_Results:Fedora_36_Branched_20220401.n...
The individual test result pages are:
https://fedoraproject.org/wiki/Test_Results:Fedora_36_Branched_20220401.n...
https://fedoraproject.org/wiki/Test_Results:Fedora_36_Branched_20220401.n...
https://fedoraproject.org/wiki/Test_Results:Fedora_36_Branched_20220401.n...
https://fedoraproject.org/wiki/Test_Results:Fedora_36_Branched_20220401.n...
https://fedoraproject.org/wiki/Test_Results:Fedora_36_Branched_20220401.n...
https://fedoraproject.org/wiki/Test_Results:Fedora_36_Branched_20220401.n...
The goal is to try and hit every test marked as Basic, Beta or Final
(hitting the Optional ones too is great but not required). It'd be
particularly good to cover things that often don't get done until late
- aarch64 tests, Cloud tests in real clouds, and the full set of Server
Active Directory tests, for instance. If you hit a significant failure
in a test, please file a bug, and most likely propose it as a release
blocker using https://qa.fedoraproject.org/blockerbugs/propose_bug .
If you have any questions or need any help with testing or reporting
results, please contact us on the test@ list or the QA IRC/Matrix
channel (#fedora-qa on IRC, "Fedora QA (Quality Assurance)" on Matrix).
Thanks a lot, folks!
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
1 year, 1 month
