Planned Outage - System upgrades - 2021-04-01 19:00 UTC
by Kevin Fenzi
There will be an outage starting at 2021-04-01 19:00 UTC,
which will last approximately 5 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2021-04-01 19:00UTC'
Reason for outage:
We will be updating and rebooting various servers to bring them up to date and confirm changes from the recent account system migration.
During the outage window services may be up or down as various systems reboot. No one service should be affected very long.
Affected Services:
Most services will be affected, with the exception of: mirrorlists, docs, hotspot, geoip, and getfedora.
Ticket Link:
https://pagure.io/fedora-infrastructure/issue/9814
Please join #fedora-admin or #fedora-noc on irc.freenode.net
or add comments to the ticket for this outage above.
2 years, 5 months
Fedora Linux 34 Beta Release Announcement
by Mohan Boddu
Fedora Linux 34 Beta Released
------------------------------------------
The Fedora Project is pleased to announce the immediate availability
of Fedora 34 Beta, the next step towards our planned Fedora 34 release
at the end of April.
Download the prerelease from our Get Fedora site:
* Get Fedora 34 Beta Workstation: https://getfedora.org/workstation/download/
* Get Fedora 34 Beta Server: https://getfedora.org/server/download/
* Get Fedora 34 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 34 Beta Spins: https://spins.fedoraproject.org/prerelease
* Get Fedora 34 Beta Labs: https://labs.fedoraproject.org/prerelease
* Get Fedora 34 Beta ARM: https://arm.fedoraproject.org/prerelease
## Beta Release Highlights
* BTRFS transparent compression
* Replacing PulseAudio with PipeWire
* Fedora 34 Workstation Beta includes GNOME 40
* A new i3 spin
* And more ...
For more details about the release, read the full announcement at
* https://fedoramagazine.org/announcing-the-release-of-fedora-34-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 Freenode.
Regards,
Mohan Boddu
Fedora Release Engineering.
2 years, 6 months
Planned outage for Fedora Account System 2021-03-24 10:30UTC
by Mark O'Brien
All,
Last week there was an announcement sent on the planned outage due to the
migration to the new Fedora Account System. Unfortunately, we made an error
in the starting date when writing the announcement.
We intend to start the outage on Wednesday 2021-03-24 10:30UTC which will
last for approximately two days. Having the outage on a Wednesday and
Thursday allows an extra working day before the weekend to address any
issues should they arise.
We know this is not ideal and apologize for the short notice of this
correction.
This outage has been planned to migrate systems with as little interruption
as possible to services for users. During this 'outage' time, you may
experience a sudden 'user unknown' scenario. In this case, please try to
re-authenticate into the service after an hour.
If this change causes a major issue please contact us as soon as possible
to let us try to address the situation in advance of the outage.
We had always planned for this outage to be on Wednesday and Thursday, but
misread our own calendar when sending the earlier announcement.
For details on how this effects you please see this mail
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedora...
Apologies,
The Fedora Account System team
2 years, 6 months
*UPDATE* Planned outage for Fedora Account System 2021-03-24
by Mark O'Brien
All,
A mail was sent last week about the planned outage due to the migration to
the new Fedora Account System. There was an error in the date presented in
the mail.
The outage will be for *two days beginning Wednesday 2021-03-24*
Apologies for any confusion or inconvenience caused.
Mark
2 years, 6 months
Re: Planned Outage - Fedora Account System Replacement - 2021-03-25
10:30 UTC
by Mark O'Brien
***Update**: *
The initial date sent out was incorrect and should be *2021-03-22021-03-24 *
The outage will be *Wednesday & Thursday*
On Fri, Mar 19, 2021 at 2:23 PM Mark O'Brien <markobri(a)redhat.com> wrote:
> All,
>
> Fedora infrastructure is getting a new accounts system! To put this in
> place we will need an outage to our services.
>
> There will be an outage starting at 2021-03-25 10:30UTC,
> which will last approximately *TWO* days.
>
> To convert UTC to your local time, take a look at
> http://fedoraproject.org/wiki/Infrastructure/UTCHowto
> or run:
>
> date -d '2021-03-25 10:30UTC'
>
> *Affected Services:*
>
> All Fedora Services
>
>
> - As this is the authentication system there may be issues logging in
> to some services.
> - Users may not be able to access people.fedoraproject.org or
> secondary.fedoraproject.org during the outage
> - Maintainer test instances are a special case and as such will be in
> a "frozen" state for access after the outage. This means that no updates
> will be made to users or ssh keys on these machines.
>
>
> Ticket:
>
> https://pagure.io/fedora-infrastructure/issue/9747
>
> If you have any questions or concerns please use any of the following
> methods of communication.
>
> - Comment on the ticket
> - IRC on #fedora-admin or #fedora-noc
> - Reply to this mail
>
>
2 years, 6 months
New Fedora Account System Production Deployment - What this means for you
by Ant Carroll
Background
For the last 12 + months, the Community Platform Engineering team have
been developing a new service to replace the current FAS2 application
for the Fedora Account System.
The FAS2 application was written over 10 years ago with python2 and
TurboGears1 framework. Due to its dependencies, it is tied to a RHEL6
deployment and could not be moved to a newer OS without rewriting.
Finally FAS2 has a very small deployment base and we had to maintain
it all.
The new account system is based on the widely used IPA product. We
have created a community portal frontend for managing account details
(noggin). This means we only need to maintain the frontend and can
leave the high security parts to IPA. Additionally, noggin may be used
by many more community products.
Key Dates - Subject to Change*
Tuesday 23rd March: Data sync to IPA
Wednesday 24th & Thursday 25th March: System-Wide Outage for machine
config to Noggin
25th March: Final Run-Through of Production Rollout
26th March: Production Rollout Complete
29th March March onwards: Support for post deployment issues
We do not anticipate these dates to change, however our team will meet
for a final review of work on Tuesday 23rd March and once satisfied
all rollback paths are in place and risks have been mitigated, we
intend to deploy to production against the dates listed above. Please
keep an eye on this mail for any potential last minute updates
What This Means for You
Everyone
If you have an otp token enrolled it will be needed everywhere. This
will include logging in through ipsilon or getting a kerberos
ticket(kinit) which was not previously the case.
Outages and interruptions to services during migration dates
System Administrators
All system administrators will need to enroll a new otp token with noggin
Sudo command will ask for First factor and Second factor separately
which is a slight change from the previous password+otp prompt
Packagers & Package Maintainers
Any packager that has otp enabled will have to follow new process in
docs for kinit/pkinit
‘Drive-By’ Contributors
If you are a ‘drive-by’ or more casual contributor to the Fedora
project, you may have to reset your password. We anticipate the number
of people who will need to do this is low, depending on when you last
logged in.
Please re-sign into your Fedora account post migration date.
Post Deployment Support
If you experience issues with your workflow as a result of FAS
changing please log an issue on the fedora infra tracker
https://pagure.io/fedora-infrastructure/issues.
FAS will be left in a read-only state to support any applications that
you might not be in a position to migrate immediately. However, we
don’t recommend using it as the data it contains will quickly become
out of date.
Maintainer-test instances will be left in a “frozen” state which means
any user changes such as new users or new ssh keys will not be
reflected on these machines.
Further Information
Outage ticket link: https://pagure.io/fedora-infrastructure/issue/9747
Community blog post:
https://communityblog.fedoraproject.org/introducing-the-new-fedora-accounts/
Noggin Documentation:
https://noggin-aaa.readthedocs.io/en/latest/userguide.html#user-accounts
--
Ant Carroll
Associate Manager, Software Engineering
Red Hat Waterford
Communications House
Cork Road, Waterford City
ancarrol(a)redhat.com
M: +353876213163 IM: ancarrol
@redhatjobs redhatjobs @redhatjobs
2 years, 6 months