From Fedora Project Wiki
(add nagios note) |
(add note about new community) |
||
Line 30: | Line 30: | ||
Adjust nagios or fix things so we can go 1 week at a time without any nagios alerts for anything. | Adjust nagios or fix things so we can go 1 week at a time without any nagios alerts for anything. | ||
New community / Tagger: | |||
* Deploy in production | |||
* Figure out any issues with AGPL and how to handle them. | |||
* Document deploy and release process. Document AGPL compliance needs. |
Latest revision as of 02:43, 16 January 2012
This is a placeholder page. Infrastructure (and anyone else who is interested) can work on filling it in at fudcon 2012.
Staging revamp:
- No branches, use forks/topic and seperate puppetmaster for new env.
- Spin up env for stg
- dev boxes are production instances for developers.
- Isolate services into seperate app/db's. Silo ize them so forks/stg would be easier to create.
- Possible cloud to spin up topic instances.
2 factor auth:
- fork, clean up and package pam_otp
- write server cgi side to accept pam_otp requests and process them.
- get 2factor pass + yubikey working
- target sudo for sysadmin-main folks first.
Reset mgmt passwords and check console on all.
Retire torrents?
Do clean base installs on junk boxes so they are ready for use in testing.
Adjust nagios or fix things so we can go 1 week at a time without any nagios alerts for anything.
New community / Tagger:
- Deploy in production
- Figure out any issues with AGPL and how to handle them.
- Document deploy and release process. Document AGPL compliance needs.