[hcoop/zz_old/ikiwiki] / CurrentSystemGripes.mdwn

The planning of a new system architecture at Hcoop, Inc. is motivated by a set of concerns with the current infrastructure.  This page details these concerns in order to improve ourselves in Hcoop, Inc. v. 2.\r
\r
= What deficiencies in our current set-up do we want to correct? =\r
\r
 * If one machine goes down, then our services will go down, too.\r
 * No way for members to buy arbitrary amounts of disk space\r
 * No automated off-machine backups\r
   * ''Until we get new machine(s) set up, would it be possible to rsync the server contents off-site?  I would be willing to contribute space on my linux workstation to this purpose... or do bandwidth constraints make this unreasonable?  I imagine that our content is relatively static so that might make this possible.'' --JustinLeitgeb\r
 * We don't have a human administration set-up where everyone with an admin job:\r
   * Feels compensated in proportion to the work he does\r
   * Is accessible on a predictable schedule\r
 * PHP scripts have a time limit.  This created problems with Squirrel Mail:\r
   * It is often impossible to attach large files or download large attachments.\r
   * When Fyodor is running its backup, the system becomes slow.  Sometimes folder listings don't display because the php script times out before the folder is read from the imapd.\r
      * ''Can we correct this by "nicing" the backup process?  Might be a quick fix.''  --JustinLeitgeb\r
      * ''Already done, unfortunately.'' --AdamChlipala\r
 * Downloads from www.hcoop.net/~username are not counted toward the user's bandwidth usage\r
   * ''Actually, they are counted as much as any other web activity, though we don't have any formal idea of "bandwidth quota" ATM.  Do you have any information to indicate otherwise?'' --AdamChlipala\r
Commit	Line	Data
ee25310d	1	The planning of a new system architecture at Hcoop, Inc. is motivated by a set of concerns with the current infrastructure. This page details these concerns in order to improve ourselves in Hcoop, Inc. v. 2.\r
	2	\r
	3	= What deficiencies in our current set-up do we want to correct? =\r
	4	\r
	5	* If one machine goes down, then our services will go down, too.\r
	6	* No way for members to buy arbitrary amounts of disk space\r
	7	* No automated off-machine backups\r
	8	* ''Until we get new machine(s) set up, would it be possible to rsync the server contents off-site? I would be willing to contribute space on my linux workstation to this purpose... or do bandwidth constraints make this unreasonable? I imagine that our content is relatively static so that might make this possible.'' --JustinLeitgeb\r
	9	* We don't have a human administration set-up where everyone with an admin job:\r
	10	* Feels compensated in proportion to the work he does\r
	11	* Is accessible on a predictable schedule\r
	12	* PHP scripts have a time limit. This created problems with Squirrel Mail:\r
	13	* It is often impossible to attach large files or download large attachments.\r
	14	* When Fyodor is running its backup, the system becomes slow. Sometimes folder listings don't display because the php script times out before the folder is read from the imapd.\r
	15	* ''Can we correct this by "nicing" the backup process? Might be a quick fix.'' --JustinLeitgeb\r
	16	* ''Already done, unfortunately.'' --AdamChlipala\r
	17	* Downloads from www.hcoop.net/~username are not counted toward the user's bandwidth usage\r
	18	* ''Actually, they are counted as much as any other web activity, though we don't have any formal idea of "bandwidth quota" ATM. Do you have any information to indicate otherwise?'' --AdamChlipala\r