welcome: please sign in

Diff for "ClintonEbadi"

Differences between revisions 23 and 40 (spanning 17 versions)
Revision 23 as of 2013-01-08 08:43:50
Size: 6326
Editor: ClintonEbadi
Comment: adjust timelines... some things bumped back, others forward. Not too far behind schedule.
Revision 40 as of 2013-07-27 21:02:15
Size: 6577
Editor: ClintonEbadi
Comment: cleanup
Deletions are marked like this. Additions are marked like this.
Line 11: Line 11:
 * January 2013: New website online, navajos and bog both up with new members using them  * (./) January 2013: New website online, navajos and bog both up with new members using them
Line 21: Line 21:
 * March 2013: Catch the sales on the last generation Dell 2U/2-socket machines and create a clean counterpart to fritz.    * FTP
   * Webalizer
* March/April 2013: Catch the sales on the last generation Dell 2U/2-socket machines and create a clean counterpart to fritz.
Line 29: Line 31:
   * IPv6, mediagoblin, diaspora, gitorious, xmpp works again (and ability to use vanity domains), ...    * IPv6, mediagoblin, diaspora, gitorious, (./) xmpp works again (and ability to use vanity domains), ...
Line 44: Line 46:
= Immediate Tasks =

 * Networked domtool-tail
 * Possible donations for new server
 * Backups (blocked by lack of hardware)
 * Spec out new server
 * Consolidate web stuff onto navajos
   * Upgrade squirrelmail
   * webdav/svn
     * Can we support gssapi negotiate? Seems like it should be trivial on the server side.
 * Wiki user reg spam: http://paste.conkeror.org/?236
   * At least sab mag faq has it (11k users!), we need to help members fix this unfortunate interaction between moin, the file system, and evildoers.
Line 46: Line 61:
== Terrible Things == == fastcgi setup notes ==
Line 48: Line 63:
Since we are having a roll call soon, we need to deal with these. Notes to self about configuring fastcgi for at least php
Line 50: Line 65:
 * phpVersion needs to change http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html
Line 52: Line 67:
=== Mail ===  * Depend on `libapache2-mod-fcgid`
 * `a2enmod fcgid` in postinst (the package seems to enable itself, but en/dis anyway)
 * Need to install our own `mods-available/fcgid.conf`
   * Do NOT enable `fcgid-script` script hander by default, require use of `fastCgiExtension` in DomTool
   * `FcgidFixPathinfo 1` to let php work properly (seems to not affect anything else)
   * Need to configure process limits (expire fairly quickly to prevent issues with tokens/memory exhaustion)
 * Have to write a wrapper shell script to exec `php5-cgi`, placed within `/afs/hcoop.net/` (but where?)
   * Wrapper script needs to gain kerberos/afs credentials... but `$USER` is not available (`whoami` works however)
   * suexec also wants the file to be owned by the user... hrm.
Line 54: Line 77:
 * Change `DefaultAlias` to false in the vain hope it makes gmail like us more. Side effect is less spam for everyone.
   * Really need to support $user+$local addresses for this to work well
   * Ideally we could drop spam and whatever, but that's a lot of work and possibly not the right thing
 * x Change SPF for `hcoop.net` to mandate that all mail come from `mail.hcoop.net`.
   * x And something like `addHcoopSPF` for members to set the same record if they want to forward through us
   * "-all" spf for mire/navajos/fritz/hopper.hcoop.net ? Possibly no, need to figure out rewriting to make sure no mail gets out with the hostname
 * ? Don't generate backscatter when spammers send mail to users forwarding offsite
   * Really not sure how to do this and not violate various RFCs
   * Looks basically impossible for gmail, best strategy is to mitigate spam sent to them in the first place
   * It appears we actually bounce to the local postmaster so we might be OK
 * x https://support.google.com/mail/bin/answer.py?hl=en&answer=175365
   * x Inform members what they can do...
     * Add receipt address to send as, exim filter rule to nuke spam, ...
     * Can we add SPAM to the subject of all messages going to gmail that are marked as such by SA?
http://code.google.com/p/modwsgi/wiki/ConfigurationDirectives WSGI looks much easier to set up, at least enough for moin. We could get away with enabling it and supporting only `WSGIScriptAlias` initially. Not sure about interaction with mod_waklog.
Line 69: Line 79:
Immediate steps: == etc. ==
Line 71: Line 81:
 * x Change SPF records for hcoop.net and define `addDefaultSPF` (`mx -all`, making it effectively universal)
 * x Recommend DefaultAlias = false
 * x Point members at google forwarding docs
   * x Directly suggest "send as..." change
   * Don't forward spam if possible (solicit an exim rule from a member...)
 * Fix exim TLS certificate (deleuze instead of mail)
 * default DirectoryIndex does not include index.shtml, should this be changed?
Line 78: Line 83:
'''DONE''' Update docs with warnings for gmail users about steps they need to take to avoid having all hcoop mail rejected: == Website ==
Line 80: Line 85:
 * [[MemberManual/Email]] (new section, canonical location that everywhere else references)
 * MemberManual/GettingStarted/AccountCreated
 * NavajosBogMigrationGuide
(create Website bugzilla product and move these there)

 * Convert hcoop.net into domtool config (looks trivial, a few rewrites... except for userdir support?)
   * On the topic of user dirs: allow members to register a redirect for hcoop.net/~foo?)
 * Replace facebook links with other "get to know the members" text
   * Inspire members to join the planet
   * Make the locations tool usable again (something we can use with Openstreetmap).
 * Give BtTempleton and LaurenMcNees write access as needed

=== Wiki ===

 * [[http://moinmo.in/MacroMarket/ChildPages|child pages macro]] for listing the section of the member manual in the sidebar?
Line 87: Line 101:
 * SSL improvements (SNI, intermediate certificates, ...)
Line 89: Line 102:
 * FastCGI
   * Seems like the most straightforward of the fancy CGI to persistent server replacement to gets working, and has wide support. MoinMoin can use it... and it's a lot less tricky for members to get working than proxied servers on another host.
   * Ideally, support wsgi and whatnot later, assuming they can do suexec
Line 94: Line 104:
 * Improve `fwtool` as needs become clearer
   * `fwtool regen` without node to regen all nodes, `fwtool verify` and possibly something akin to `visudo`
   * Programmitic interface to adding/removing/etc rules?
     * At least need a way to kill rules when destroying the user, ideally just disabling them? (existing code ignores users who do not exist, so it sort of works to ignore it, but cleanliness of the rules file will become a problem).
   * "Proper" parser. Read rules into typed structure using the magic of SML, and work on that form (more natural, type safe, etc.)
   * groups or similar for common ports
     * We need a way to grant users who just want general net access a reasonably unrestrictive firewall, without needlessly opening things for members who don't use our shell services extensively. Since we can't restrict socket permissions generally, defining groups that provide common firewall rules seems like an ok solution.
 * Improve `fwtool` as needs become clearer (FirewallTool)

== Major Sysadmin Tasks for 2013 ==

 * Acquire and install new server, cleaning up the back of the rack in the process
 * Get everything off of deleuze
 * Clean up keytabs (at least `$user.mail` for mail delivery, sync to as few nodes as needed, etc.)
 * Overhaul mail delivery
   * Revisit routing/transport; the current routing config has too many entry and exit points making changes extremely complicated (i.e. likely to break mail delivery)
   * Take advantage of new exim features like DKIM.
   * Secondary MX
 * The great DES to AES openafs rekeying
   * Major pain: we have to upgrade all client and servers machines to openafs 1.6.5

= Board Stuff =

 * What address should we be using for the "owner" of hcoop services? It's a mix of the current treasurer, registered agent, and data center right now... is the registered agent correct? Do we need to get a PO Box or something?
 * We need a private wiki of some sort for filing sensitive information like welcome emails for services and various credentials... is it safe enough to do that using the public moin and acls? I'm not sure sure...

I am Clinton Ebadi. I am the reluctant President of the coop (someone has to do it), and the current lead sysadmin / DomTool maintainer / lo-fi AdamChlipala replacement.

1. Board Statements

See /BoardStatements

2. General Coop Goals

Unstructured musing on when/what I think the coop ought to be.

  • (./) January 2013: New website online, navajos and bog both up with new members using them

  • February 2013->December 2013: Big push for new members. New website should make us seem more alive, we've finally fixed about 3/4 of the "temporary" hacks from when we first moved to Peer1, etc. mire is gone (less work: we just have to get people off of it), but also work toward getting rid of deleuze. Web services first (low hanging fruit), even if it means punting on fully converting to domtool managed sites (at least packaged and documented). AFAICT other than those we're just left with:

    • DomTool dispatcher

    • Master DNS
    • Exim
    • IMAP (might have to patch courier-authdaemon)
    • A few straggling openafs volumes (+ AFSDB records?)
    • Backups
    • MailMan

    • The portal
    • FTP
    • Webalizer
  • March/April 2013: Catch the sales on the last generation Dell 2U/2-socket machines and create a clean counterpart to fritz.
    • Minimal KVM host setup for base OS. We might run the KDC and OpenAFS on the bare metal, not entirely certain.
    • Create new wheezy based VMs, duplicating (and turning into master) services hosted in VMs on fritz
      • For the first time, this is realistic: all of those months packaging our configuration pay off by sparing future-me from herculean efforts. And SteveKillen, BtTempleton, and I are probably available for a road trip to Peer1.

  • March 2013->July 2013: Transition remaining services off of deleuze onto KernelVirtualMachines on new kvm host

  • April 2013: Election and hopefully 120 members. Mire has been turned off for at least a month at this point.
  • Winter 2013: Assuming 150+ members, perhaps more bandwidth is in order. Deleuze should be safe to turn off by now at the latest.
  • Spring 2014: Ponies for everyone.
    • IPv6, mediagoblin, diaspora, gitorious, (./) xmpp works again (and ability to use vanity domains), ...

3. Contact

  • <clinton at unknownlamer dot org> (Email)

  • unknownlamer (AOL Instant Messenger)
  • <clinton at hcoop dot net> (Jabber)

  • unknown_lamer on freenode (IRC) in #hcoop

  • +1 443 538 8058 (Phone, SMS preffered)

4. Websites

5. Immediate Tasks

  • Networked domtool-tail
  • Possible donations for new server
  • Backups (blocked by lack of hardware)
  • Spec out new server
  • Consolidate web stuff onto navajos
    • Upgrade squirrelmail
    • webdav/svn
      • Can we support gssapi negotiate? Seems like it should be trivial on the server side.
  • Wiki user reg spam: http://paste.conkeror.org/?236

    • At least sab mag faq has it (11k users!), we need to help members fix this unfortunate interaction between moin, the file system, and evildoers.

6. Admin Stuff

6.1. fastcgi setup notes

Notes to self about configuring fastcgi for at least php

http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html

  • Depend on libapache2-mod-fcgid

  • a2enmod fcgid in postinst (the package seems to enable itself, but en/dis anyway)

  • Need to install our own mods-available/fcgid.conf

    • Do NOT enable fcgid-script script hander by default, require use of fastCgiExtension in DomTool

    • FcgidFixPathinfo 1 to let php work properly (seems to not affect anything else)

    • Need to configure process limits (expire fairly quickly to prevent issues with tokens/memory exhaustion)
  • Have to write a wrapper shell script to exec php5-cgi, placed within /afs/hcoop.net/ (but where?)

    • Wrapper script needs to gain kerberos/afs credentials... but $USER is not available (whoami works however)

    • suexec also wants the file to be owned by the user... hrm.

http://code.google.com/p/modwsgi/wiki/ConfigurationDirectives WSGI looks much easier to set up, at least enough for moin. We could get away with enabling it and supporting only WSGIScriptAlias initially. Not sure about interaction with mod_waklog.

6.2. etc.

  • default DirectoryIndex does not include index.shtml, should this be changed?

6.3. Website

(create Website bugzilla product and move these there)

  • Convert hcoop.net into domtool config (looks trivial, a few rewrites... except for userdir support?)
    • On the topic of user dirs: allow members to register a redirect for hcoop.net/~foo?)
  • Replace facebook links with other "get to know the members" text
    • Inspire members to join the planet
    • Make the locations tool usable again (something we can use with Openstreetmap).
  • Give BtTempleton and LaurenMcNees write access as needed

6.3.1. Wiki

6.4. domtool plans

  • Feature backlog
  • Networked domtool-tail
  • default CSymbol = Value for binding default environment variable settings

    • Expands the scope of extensions that can be written in pure DomTool, slight flexibility gains

  • Improve fwtool as needs become clearer (FirewallTool)

6.5. Major Sysadmin Tasks for 2013

  • Acquire and install new server, cleaning up the back of the rack in the process
  • Get everything off of deleuze
  • Clean up keytabs (at least $user.mail for mail delivery, sync to as few nodes as needed, etc.)

  • Overhaul mail delivery
    • Revisit routing/transport; the current routing config has too many entry and exit points making changes extremely complicated (i.e. likely to break mail delivery)
    • Take advantage of new exim features like DKIM.
    • Secondary MX
  • The great DES to AES openafs rekeying
    • Major pain: we have to upgrade all client and servers machines to openafs 1.6.5

7. Board Stuff

  • What address should we be using for the "owner" of hcoop services? It's a mix of the current treasurer, registered agent, and data center right now... is the registered agent correct? Do we need to get a PO Box or something?
  • We need a private wiki of some sort for filing sensitive information like welcome emails for services and various credentials... is it safe enough to do that using the public moin and acls? I'm not sure sure...


CategoryHomepage

ClintonEbadi (last edited 2021-11-06 17:50:12 by ClintonEbadi)