We've got problems

[Mike McGrath]

Hey everyone, so there's lots or projects going on right now and I'm going
to spend some time to prioritize them and hopefully get help on them.

The wiki:

We need to upgrade the wiki, like yesterday.  We're on an unsupported
branch right now.

Whats the hangup?  HNP is our ACL plugin.  Some might remember when we
said "A wiki is not a CMS" well, now we're being screwed by it.  It has
been made clear to us that certain pages in the wiki must A) stay on the
wiki and B) be editable by only a subset of people.  HNP is not supported
by newer versions of mediawiki.

Ticket #1072

Koji:

The koji database is borked right now.  We're getting by but its a ticking
timebomb.  There was some data corruption with our backplane issues this
last week.  Damaged portions equal no more then 160K at this point (I'm
still doing other measurements).  This is less then .0002% of the data of
that database.  The problem is that when I try to do dumps of the data
pgsql fails.  This is a must fix.

Ticket #1069

nfs1:

NFS1's IO load is just not right.  Something isn't behaving as it should
and I'm just not sure whats going on there yet.  We need to do a full
examination and trend of it.  This involves moving cvs1 to another
location and involves moving releng2 to xen1 to help ease some load.
Additionally we need to move kojipkgs1 to another location (probably xen1)
and enable a proper caching for it.  We also need to finally get a valid
backup of nfs1.  This still hasn't happened.  Its difficult to test
because of the high load on the disks, backups take 4+ days.  lots of
things can go wrong during that time.


Tickets: #1061, #1074, #1075, #1076.

backup2:

DR backups is a project I've been trying to get in shape.  its general
there, needs some polish.  The dr user is there.  But an audit and
verification of everything we need to back up needs to be done.

Ticket: #1077

CSRF:

CSRF is a pretty serious deal, toshio is working on it but I'm sure he can
use some help.

Ticket: #992

FAS:

Ricky has been working on some FAS stuff but some outstanding systems must
be implemented quickly particularly as it relates to stale users.  We need
to get the password expiration stuff in, and we need to document and
define what each user state means and how it will relate to other
applications.

FAS: #83


If you don't have access to the systems of this stuff, we likely won't be
able to sponsor and train you in time to get this stuff done.  Sorry, but
you can still look at the code issues mentioned above or test alternatives
for the wiki.

If you have access and are working on something else, if you are able
please stop doing that thing and work on one of the above issues.  Even
after these issues are done I've got a good 6 months of stuff backed up
before new things can be done.  We've literally exploded in size.  Over
the last two years the services, nodes, etc that we support has grown over
10 times and our core team has only grown by a few members.  We're doing
better then most OSS communities out there, but we can do better.

	-Mike