From Fedora Project Wiki
No edit summary |
(Mark easy items, add monitoring item.) |
||
| Line 1: | Line 1: | ||
Good beginner/introductory items are marked with (*), but feel free to | |||
ask about any item that interests you! | |||
== Fix all the things that we have == | == Fix all the things that we have == | ||
* Upgrade TurboGears1 apps to TurboGears2 | * Upgrade TurboGears1 apps to TurboGears2 | ||
| Line 10: | Line 13: | ||
* Move blogs to wordpress.com | * Move blogs to wordpress.com | ||
* Move publictest to the cloud and create a sundown on them | * Move publictest to the cloud and create a sundown on them | ||
* Automated hosted projects | * Automated hosted projects (*) | ||
* Automated build overrides | * Automated build overrides (*) | ||
* Automated creation of new machines -- run one command and it's up | * Automated creation of new machines -- run one command and it's up | ||
* puppet staging vs production | * puppet staging vs production | ||
| Line 23: | Line 26: | ||
* Split db to get fas to a different db server | * Split db to get fas to a different db server | ||
* Replicate db so that we don't have a SPOF | * Replicate db so that we don't have a SPOF | ||
* logging sucks | * logging sucks (*) | ||
** IPs hit proxies but we also need them to hit the app servers. | ** IPs hit proxies but we also need them to hit the app servers. (*) | ||
** Fas needs to log more actions to its database | ** Fas needs to log more actions to its database (this is in a new version of FAS, we just need to upgrade) | ||
* Do periodic reinstallations of guests (like app servers) so that we know there's nothing changed not in puppet. | * Do periodic reinstallations of guests (like app servers) so that we know there's nothing changed not in puppet. | ||
* fix backups | * fix backups | ||
** Make sure we're backing up everything | ** Make sure we're backing up everything (*) | ||
** Stop backing up sysadmin data (/usr) | ** Stop backing up sysadmin data (/usr) | ||
** Reduce koji's resources | ** Reduce koji's resources | ||
* Finish and deploy coprs | * Finish and deploy coprs | ||
* go through list of rpm -Va on all hosts (in /var/tmp/global-rpm-va on | * go through list of rpm -Va on all hosts (in /var/tmp/global-rpm-va on puppet01) and make sure all the files there have counterparts in puppet to explain their changes (*) | ||
* monitor more things for possible problems (*) | |||
** mail queues on SMTP machines, particularly bastion (*) | |||
** puppet reports to make sure that puppet is being run regularly on all managed machines. (*) | |||
== Done items == | == Done items == | ||
** Upgrade quota to 2GB | ** Upgrade quota to 2GB | ||
Revision as of 19:52, 4 February 2011
Good beginner/introductory items are marked with (*), but feel free to ask about any item that interests you!
Fix all the things that we have
- Upgrade TurboGears1 apps to TurboGears2
- Write automated tests using TG2's test framework
- Fix the FAS authenticators to be less chatty
- Put fas session information into memcached
- Update FAS to have an admin console (no more direct db needs)
- Update pkgdb to have an admin console (no more direct db needs)
- Fix the Django auth providers to be faster
- Move transifex to tx.net
- Move blogs to wordpress.com
- Move publictest to the cloud and create a sundown on them
- Automated hosted projects (*)
- Automated build overrides (*)
- Automated creation of new machines -- run one command and it's up
- puppet staging vs production
- Use yubikey for two-factor auth (instead of either or auth)
- glusterfs/cloudfs fedorapeople filesystem
- glusterfs/cloudfs fedorahosted filesystem
- Talk to mediawiki folks on how to run attachments to mediawiki so that we don't need a special machine (possibly glusterfs again?)
- Split db to get fas to a different db server
- Replicate db so that we don't have a SPOF
- logging sucks (*)
- IPs hit proxies but we also need them to hit the app servers. (*)
- Fas needs to log more actions to its database (this is in a new version of FAS, we just need to upgrade)
- Do periodic reinstallations of guests (like app servers) so that we know there's nothing changed not in puppet.
- fix backups
- Make sure we're backing up everything (*)
- Stop backing up sysadmin data (/usr)
- Reduce koji's resources
- Finish and deploy coprs
- go through list of rpm -Va on all hosts (in /var/tmp/global-rpm-va on puppet01) and make sure all the files there have counterparts in puppet to explain their changes (*)
- monitor more things for possible problems (*)
- mail queues on SMTP machines, particularly bastion (*)
- puppet reports to make sure that puppet is being run regularly on all managed machines. (*)
Done items
- Upgrade quota to 2GB