Reminder: This Weekend
-------- Original Message --------
Subject: bugzilla.redhat.com Web UI, Database, XMLRPC Planned Outage |
August 2nd, 2008 - 9:00 AM EST - 7:00 PM EST
Date: Tue, 29 Jul 2008 00:05:42 -0400
From: Dave Lawrence <dkl(a)redhat.com>
O U T A G E R E Q U E S T F O R M
Severity Two (High)
August 2nd, 2008
9:00 AM EST - 7:00 PM EST
Estimated Time Required:
Red Hat Engineering Operations
Users of bugzilla.redhat.com and any services that rely on
bugzilla.redhat.com Web UI, Database, XMLRPC
bugzilla.redhat.com will be unavailable during the posted
time on August 2nd, 2008.
On August 2nd, bugzilla.redhat.com will go down for an
update to the latest upstream code base. During this time
the web servers will be reinstalled with the latest OS
updates as well as the latest Bugzilla code. Also the
database servers will undergo a data migration to be made
compatible with the latest Bugzilla code. The web UI,
database, and all XMLRPC services will be unavailable during
the migration. Services that rely on bugzilla.redhat.com may
not function properly during this time so please let your
users know about the outage as well.
Also please take time to point your services/scripts at our
test server https://partner-bugzilla.redhat.com to make sure
that they will still work with the new system once it goes
live. Care has been taken to make the new system backwards
compatible as much as possible with the old XMLRPC API but
still confirm that they work properly. If you encounter any
problems, please contact bugzilla-owner redhat com or file a
kbaker redhat com
An unplanned outage occurred at approximately 2008-07-31 03:30 UTC and
is mostly resolved as of 2008-07-31 06:20 UTC
Affected Services where:
- Websites - Package DB, Mirror Manager Admin Interface, Bodhi, Translate
- Account System (FAS)
- Any other authenticated requests
- Hosted (Trac authentication)
- Wiki (Read Only, some pages may appear broken as well)
- CVS / Source Control
- Fedora Talk
Reason for Outage:
Our main filer took a turn for the worst, and took down one of our main
database servers and other associated infrastructure.
We have now for the most part resolved the issue, and diagnostic work
has begun, we apologise for any inconvenience.
More information will be made available to
https://fedorahosted.org/fedora-infrastructure/ticket/735 when it comes
Please join #fedora-admin in irc.freenode.net or respond to this email
to track the status of this outage.
= Release planning meeting, 2008-07-30 =
== Attendance ==
''Present:'' Tom Callaway (Engineering/Legal), Paul Frields
(moderator), Jesse Keating (RelEng), Jonathan Roberts (Marketing), Seth
Vidal (Infrastructure), Karsten Wade (Docs)
== Agenda ==
=== Reiterating purpose ===
* Not policy setting, nor decision making
* Progress reporting and schedule debugging only
* Making sure that dependencies that affect releases are being satisfied
across Fedora community teams
* Any action items are potential only, until pushed out into the
community space for discussion and follow-through
=== Current Alpha status (RelEng) ===
* Not finished
** Number of composes happening internally on f13's workstation
** Not enough got done during OLS/OSCON - not enough people doing
anything with looking at bits
** We can't compose yet in PHX, which is why it happens on f13's station
** Chasing down issues with anaconda currently, hopefully on the last
** f13 hopes to have a candidate release tree
** New problem in installer right now
* Not yet in danger of slipping
** If we don't have a tree by tomorrow, that's not good
=== Infrastructure ===
* uncomfortable problems in existing BT server, it keeps dying
** Might be routing, or hardware... testing to figure it out
** skvidal is going to keep a very close eye on making sure the old and
new servers are sync'd
'''DEBUGGING:''' Should f13's routine change? No.
* Space issues? 261GB available on netapps
** many terabytes coming back online "soon"
** drives hopefully coming in next week, then it's just reconfiguring,
no onsite required
=== Docs ===
* Alpha and Beta release notes are a one-sheet on the wiki
** Living document, can change after release day
** QA, Desktop, and RelEng have done a great job of adding some
** Priority is to let testers know what you want them to do with the
'''DEBUGGING:''' We need a list of pre-approved URLs for release
* Docs can handle the majority of the text for the release announcement
email, and check URLs, so releng can concentrate on sending it out when
* Release notes production is hopefully going to change with F10 to use
an in-distro tool, publican, to build
=== Marketing ===
* Not much on plate for Alpha in particular
* Geek news will be all over the Alpha, are we doing anything to
** Paul has been working with Kara on e.g. a press blog entry
** Our announcement should also serve as testing recruitment
=== Legal ===
* Nothing at this time
== Next meeting ==
* Post-partum Alpha meeting would probably be useful
** if no agenda items, no meeting
* Definitely one a few days ahead of Beta freeze
** Announcements to go to fedora-devel-list
And the winner of the Fedora 10 codename is:
The full GPG-signed information from our election coordinator, Nigel
Jones, including vote totals, is located here:
Many thanks to the Board, Paul Frields, and Nigel Jones for their effort
in getting the name candidates and vote set up.
Outage Notification - 2008-07-28 01:20 UTC
There will be an outage starting at 2008-07-28 01:20 UTC, which will last
approximately 1 hour.
To convert UTC to your local time, take a look at
date -d '2008-07-28 01:20 UTC'
CVS / Source Control
Reason for Outage:
Renaming cvsextras group to 'packager'
Casey Dahlin <cdahlin(a)redhat.com>
Please join #fedora-admin in irc.freenode.net or respond to this email to track
the status of this outage.
We've had some issues with notification emails being sent on cvs
commits. Sometimes generating the list of email addresses to notify was
slow, on other occassions it would fail altogether. To alleviate this
we've changed from a dynamic determination of who is notified by
querying the pkgdb to a static one by sending to an email alias
generated from pkgdb information once an hour.
There is one major difference (besides speed) to note in this: Before,
the owner and people in the watchcommits acls received notifications
that a cvs commit was made to a package. Now the owner and people
onwatchcommits and watchbugzilla acls are notified.
The aliases used to send these messages are all
pkg-owner(a)fedoraproject.org in case you have mail filters you want to
setup to handle it.
We have several options for the Fedora 10 codename, and you get to help
decide which we use!
is the URL to cast your vote. Log in with your Fedora Account name and
password. As long as you have signed the CLA and belong to one
additional group in the Fedora Account System, you can cast your vote.
Voting will end and be tallied at 23:59:59 28 July 2008 UTC.
I was recently talking with Paul Frields about how to make the feature
process more accessible... this combined with feedback in the rpm thread
have led to a (hopefully) clearer presentation of how the feature
Paul did a great job reorganizing the content on the main page. None of
the content has changed, but the presentation is a lot simpler and less
I still need to add definitions and guidance for what belongs in each
section of the form.
We are proposing new category names to make it more self-evident which
state a feature page is in. Unless there are objections I plan to run
this past FESCo for a sanity check this coming Thursday and start using
them thereafter--including converting the category names for existing pages.
The new category names would look like this:
Category:FeaturePageIncomplete (was ProposedFeature)--every feature
starts in this category and returns to this category if it is reviewed
or voted on and needs more work.
Category:FeatureReadyForWrangler (was ProposedF10)--feature owner
signals that their feature page is complete and requests that FESco
review and accept it for the release under development
Category:FeatureReadyForFesco (was ProposedF10)--Feature wrangler
changes features to this category when they are ready for FESCo vote
Category:FeatureAcceptedF10 (unchanged)--voted on and accepted by fesco
A draft updated illustration is here:
Thanks also to Paul for his ideas and help on the illustration!