https://fedoraproject.org/wiki/Changes/IoTArtifactsWithOSBuild
== Summary ==
Build the key Fedora IoT artifacts such as the raw images and the
traditional anaconda installer with osbuild.
== Owner ==
* Name: [[User:pwhalen| Paul Whalen]]
* Email: [mailto:pwhalen@redhat.com| pwhalen(a)redhat.com]
* Name: [[User:obudai| Ondřej Budai]]
* Email: [mailto:obudai@redhat.com| ondrej(a)budai.cz]
* Name: [[User:pbrobinson| Peter Robinson]]
* Email: [mailto:pbrobinson@fedoraproject.org| pbrobinson(a)fedoraproject.org]
== Detailed Description ==
The intention for Fedora IoT was to always use osbuild for building
release artifacts but it wasn't initially ready to do that. With the
work being done as part of "RHEL for Edge" the Fedora IoT deliverables
now sadly trail behind the features and functionality of the
downstream. This will move all existing deliverable artifacts over to
being created with osbuild which will allow us to bring Fedora IoT
back to being the true upstream for RHEL for Edge and allow us to use
the leading edge that is Fedora to continue to innovate in the Edge
and IoT space.
== Benefit to Fedora ==
The benefit to Fedora is to allow the IoT Edition to go back to being
the true upstream for RHEL for Edge and for Fedora to be where all the
cool new innovation on the edge is being done.
== Scope ==
* Proposal owners:
** Test building IoT artifacts with osbuild to ensure they're
consistent with the existing ones
** Update to Fedora IoT profiles in osbuild
** Update to pungi configs to move over the artefact creation
* Other developers:
** No impact
* Release engineering: [https://pagure.io/releng/issue/10722 #10722]
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
There is no upgrade impact. Existing IoT users will upgrade as before
as only new release artifacts will use the new mechanism. The
deployment of the artifacts should not initially change with them
being created with osbuild. There may well be new enhancements in the
future but those are out of scope of this change.
== How To Test ==
* All Fedora IoT artifacts should be consumable and testable as before.
== User Experience ==
There should be no IoT users, there is no impact to non IoT Edition users.
== Dependencies ==
N/A (not a System Wide Change)
== Contingency Plan ==
* Contingency mechanism: Roll back to the current means of generating images.
* Contingency deadline: Beta
* Blocks release? No.
* Blocks product? No.
== Documentation ==
N/A (not a System Wide Change)
== Release Notes ==
N/A
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
Fedora Linux 36 Beta Released
------------------------------------------
The Fedora Project is pleased to announce the immediate availability
of Fedora 36 Beta, the next step towards our planned Fedora 36 release
at the end of April.
Download the prerelease from our Get Fedora site:
* Get Fedora 36 Beta Workstation:
https://getfedora.org/workstation/download/
* Get Fedora 36 Beta Server: https://getfedora.org/server/download/
* Get Fedora 36 IoT: https://getfedora.org/iot/download/
Or, check out one of our popular variants, including KDE Plasma, Xfce,
and other desktop environments, as well as images for ARM devices:
* Get Fedora 36 Beta Spins: https://spins.fedoraproject.org/prerelease
* Get Fedora 36 Beta Labs: https://labs.fedoraproject.org/prerelease
* Get Fedora 36 Beta ARM: https://arm.fedoraproject.org/prerelease
## Beta Release Highlights
* Fedora 36 Workstation Beta includes GNOME 42
* Update of programming languages and libraries: LXQt 1.0, Golang 1.18,
Ruby 3.1
For more details about the release, read the full announcement at
* https://fedoramagazine.org/announcing-fedora-36-beta/
or look for the prerelease pages in the download sections at
* https://getfedora.org/
Since this is a Beta release, we expect that you may encounter bugs or
missing features. To report issues encountered during testing, contact
the Fedora QA team via the test(a)lists.fedoraproject.org mailing list or
in #fedora-qa on Libera Chat or the #qa:fedoraproject.org Matrix room.
Regards,
Tomas Hrcka
Fedora Release Engineering.
https://fedoraproject.org/wiki/Changes/FIDODeviceOnboarding
== Summary ==
Package and enable the
[https://fidoalliance.org/fido-alliance-creates-new-onboarding-standard-to-s…
FIDO Device Onboarding] software stack for Zero Touch Onboarding on
Fedora IoT.
== Owner ==
* Name: [[User:pbrobinson| Peter Robinson]]
* Email: [mailto:pbrobinson@fedoraproject.org| pbrobinson(a)fedoraproject.org]
* Name: [[User:runcom| Antonio Murdaca]]
* Email: [mailto:amurdaca@redhat.com| amurdaca(a)redhat.com]
== Detailed Description ==
The ability for an IoT or Edge device to be plugged in and
automatically onboard itself with zero user interaction is critical to
be able to scale IoT/Edge to millions of devices. To do this in a
secure way with open standards across the industry is even more
critical. The FIDO IoT working group has worked with leaders in the
silicon industry such as Intel and Arm to produce the FIDO Device
onboarding spec which allows a device credential, a root and chain of
trust to ensure the secure onboarding of a device without the need of
stored credentials.
== Benefit to Fedora ==
The benefit to Fedora is to allow the IoT Edition to demonstrate the
use of leading edge open industry protocols for onboarding IoT and
Edge devices.
== Scope ==
* Proposal owners:
** Package the rust implementation of the FIDO device onboarding stack
including client, rendezvous service, owner onboarding service and
prototype manufacturing service.
** Enable the client service by default for IoT Edition
** Add the client service to the IoT Edition deliverables
* Other developers:
** No impact
* Release engineering: [https://pagure.io/releng/issue/10720 #10720]
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
There is no upgrade impact. FIDO FDO is a single use onboarding
protocol and will not impact existing IoT user systems.
== How To Test ==
* Test with FDO all-in-one services. Documentation will be available
for testing.
== User Experience ==
No impact to non IoT Edition users.
The user experience for the IoT Edition is still evolving and this
will be updated as things fall into place later in Spring and early
Summer 2022.
== Dependencies ==
N/A (not a System Wide Change)
== Contingency Plan ==
* Contingency mechanism: Not shipping FDO as a package in Fedora or
including it in the IoT Edition
* Contingency deadline: GA
* Blocks release? No.
* Blocks product? No.
== Documentation ==
N/A (not a System Wide Change)
== Release Notes ==
Fedora IoT Edition supports the FIDO Device Onboarding 1.1
specification for zero touch onboarding of IoT and Edge devices.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
Planned Outage - Updates / Reboots - 2022-03-31 21:00 UTC
There will be an outage starting at 2022-03-31 21:00 UTC
which will last approximately 4 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2022-03-31 21:00 UTC'
Reason for outage:
We will be updating all our instances and rebooting hardware nodes into new kernels.
This will catch us up on security updates before next weeks Fedora Linux 36 Final freeze.
Affected Services:
All services may experience slowdowns or short outages as servers are rebooted
and return to service. We will try and minimize disruptions, but users/maintainers
are advised to avoid activity in the outage window.
Ticket Link:
https://pagure.io/fedora-infrastructure/issue/10613
Please join #fedora-admin or #fedora-noc on irc.libera.chat
or add comments to the ticket for this outage above.
I have returned from PTO, so you're getting this reminder ~2 hours
prior to the meeting instead of the usual "the day before." But in any
case, the Fedora Linux 36 Beta Go/No-Go[1] meeting
is scheduled for Thursday 24 March at 1700 UTC in #fedora-meeting. At
this time, we will determine the status of the F36 Beta for the 29
March target date #2[2]. For more information about the Go/No-Go
meeting, see the wiki[3].
[1] https://calendar.fedoraproject.org/meeting/10209/
[2] https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html
[3] https://fedoraproject.org/wiki/Go_No_Go_Meeting
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one. Please adopt the affected package or
retire your depending package to avoid broken dependencies, otherwise your
package will fail to install and/or build when the affected package gets retired.
Request package ownership via the *Take* button in he left column on
https://src.fedoraproject.org/rpms/<pkgname>
Full report available at:
https://churchyard.fedorapeople.org/orphans-2022-03-22.txt
grep it for your FAS username and follow the dependency chain.
For human readable dependency chains,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
================================================================================
atomic-reactor cverna, infra-sig, 0 weeks ago
maxamillion, orphan, twaugh,
vrutkovs
augeas-vala orphan 3 weeks ago
beanstalk-client orphan 2 weeks ago
gela-asis orphan, reznik 0 weeks ago
gimp-fourier-plugin orphan 3 weeks ago
gocl orphan 3 weeks ago
golang-github-mdlayher-wifi go-sig, orphan 1 weeks ago
javahelp2 orphan 6 weeks ago
lua-ldap orphan 2 weeks ago
matreshka orphan, reznik, rombobeorn 0 weeks ago
mingw-llvm orphan 0 weeks ago
python-aiohttp-cors orphan, python-sig 2 weeks ago
python-aiohttp-negotiate orphan 2 weeks ago
python-blessings orphan 2 weeks ago
python-fastimport orphan 2 weeks ago
python-hkdf orphan 3 weeks ago
python-lrparsing orphan 2 weeks ago
python-magic-wormhole orphan 3 weeks ago
python-magic-wormhole-mailbox- orphan 3 weeks ago
server
python-magic-wormhole-transit- orphan 3 weeks ago
relay
python-ofxparse orphan 2 weeks ago
python-plyvel orphan 2 weeks ago
python-pystalk orphan 2 weeks ago
python-spake2 orphan 3 weeks ago
python-txtorcon orphan 3 weeks ago
qcommandline orphan 2 weeks ago
qt5-qtcanvas3d kde-sig, orphan 0 weeks ago
qt5-qtenginio kde-sig, lupinix, orphan 0 weeks ago
rpg-cli orphan, rust-sig 5 weeks ago
rubygem-database_cleaner orphan 4 weeks ago
rust-diffus orphan, rust-sig 0 weeks ago
rust-diffus-derive orphan, rust-sig 0 weeks ago
rust-newsblur_api orphan, rust-sig 0 weeks ago
rust-opml orphan, rust-sig 0 weeks ago
rust-xmltree orphan, rust-sig 0 weeks ago
sems orphan 0 weeks ago
w_scan orphan 5 weeks ago
yecht orphan 1 weeks ago
The following packages require above mentioned packages:
Report too long, see the full version at
https://churchyard.fedorapeople.org/orphans-2022-03-22.txt
See dependency chains of your packages at
https://packager-dashboard.fedoraproject.org/
See all orphaned packages at https://packager-dashboard.fedoraproject.org/orphan
Affected (co)maintainers (either directly or via packages' dependencies):
cverna: atomic-reactor
eclipseo: golang-github-mdlayher-wifi
go-sig: golang-github-mdlayher-wifi
ignatenkobrain: rust-xmltree, rust-diffus, rust-diffus-derive,
rust-newsblur_api, rust-opml
infra-sig: atomic-reactor
kde-sig: qt5-qtcanvas3d, qt5-qtenginio
kwizart: python-aiohttp-cors
lupinix: qt5-qtenginio
maxamillion: atomic-reactor, python-blessings
nucleo: python-aiohttp-cors
python-sig: python-aiohttp-cors
reznik: gela-asis, matreshka
rkuska: python-blessings
rombobeorn: matreshka
rust-sig: rust-xmltree, rpg-cli, rust-diffus, rust-diffus-derive,
rust-newsblur_api, rust-opml
salimma: python-blessings
terjeros: python-blessings
twaugh: atomic-reactor
vrutkovs: atomic-reactor
--
The script creating this output is run and developed by Fedora
Release Engineering. Please report issues at its pagure instance:
https://pagure.io/releng/
The sources of this script can be found at:
https://pagure.io/releng/blob/main/f/scripts/find_unblocked_orphans.py
Due to outstanding blocker bugs[1], we do not have an F36 Beta RC. As
a result, F36 Beta is NO-GO by default and today's Go/No-Go meeting is
cancelled.
The next Fedora Linux 36 Beta Go/No-Go meeting[2] will be held at 1700
UTC on Thursday 17 March in #fedora-meeting. We will aim for the
"target date #1" milestone of 22 March. The release schedule[3] has
been updated accordingly. This change does not impact the final
release date.
[1] https://qa.fedoraproject.org/blockerbugs/milestone/36/beta/buglist
[2] https://calendar.fedoraproject.org/meeting/10209/
[3] https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis