Infrastructure Transition Plan 2014 - Revision history

Neteler: /* Future Needs */ http://trac.osgeo.org/osgeo/ticket/592

2015-04-23T18:15:12Z

Future Needs: http://trac.osgeo.org/osgeo/ticket/592

Wildintellect: /* Storage */

2015-02-22T21:38:31Z

Storage

Wildintellect: Plan is a top level section

2015-02-22T18:03:17Z

Plan is a top level section

Wildintellect: notes on actual plan

2015-02-22T18:02:57Z

notes on actual plan

Wildintellect: /* Hardware */

2015-02-22T06:14:03Z

Hardware

Wildintellect: /* Hardware */

2015-02-21T22:37:22Z

Hardware

Wildintellect: /* Hardware */

2015-02-21T21:48:48Z

Hardware

Wildintellect: /* Hardware */

2015-02-03T17:47:33Z

Hardware

Wildintellect: /* Future Needs */

2015-02-03T17:47:09Z

Future Needs

Neteler: Updated

2015-01-20T21:48:29Z

Updated

@@ Line 34: / Line 34: @@
 * <strike>Long term archive of Foss4g sites</strike> done: http://www.foss4g.org/
 * Upgraded version control hosting.
-** Upgraded Trac
+** <strike>Upgrade Trac (<a href="http://trac.osgeo.org/osgeo/ticket/592">#592</a>)</strike> done: 4/2015
 ** Gitlab

@@ Line 91: / Line 91: @@
 ** Put all files into networked storage mounted via NFS (or something similar)
 ** GlusterFS (supports georeplication)
-** Use XFS (supported in Linux for a long time, works well), ZFS (?), or [http://en.wikipedia.org/wiki/Comparison_of_file_systems something else] good with lots of small files.
+** Use XFS (supported in Linux for a long time, works well),
 * SSD
 ** Static websites, Tile Caches, Downloads, extra disk based caching for web configurations

@@ Line 99: / Line 99: @@
 ** Foss4g Archives
-== Plan ==
+= Plan =
 * Buy a new machine - [http://www.siliconmechanics.com/quotes/284594 current quote]

@@ Line 98: / Line 98: @@
 * 7.2K rpm drives
 ** Foss4g Archives
 [[Category: Infrastructure]]

@@ Line 41: / Line 41: @@
 == Hardware ==
-* Buy new hardware (1U 8 drive [http://www.siliconmechanics.com/quotes/270347?confirmation=141627023 $3000-$5000] USD or [http://www.siliconmechanics.com/quotes/284582?confirmation=1523506908 10Krpm+SSD], 1U 4-6 drives [http://www.siliconmechanics.com/quotes/274487?confirmation=1948640496 $2600] or 1U 6 drive [http://www.siliconmechanics.com/quotes/270350?confirmation=476256389 $2000-3000] USD)
+* Buy new hardware (1U 8 drive [http://www.siliconmechanics.com/quotes/270347?confirmation=141627023 $3000-$5000] USD or [http://www.siliconmechanics.com/quotes/284582?confirmation=1523506908 10Krpm+SSD] or with [http://www.siliconmechanics.com/quotes/284588?confirmation=1814222821 newer cpu], 1U 4-6 drives [http://www.siliconmechanics.com/quotes/274487?confirmation=1948640496 $2600] or 1U 6 drive [http://www.siliconmechanics.com/quotes/270350?confirmation=476256389 $2000-3000] USD)
 ** Possibly use SSDs
 ** or, pick hard disks that will last for years over faster things that need more careful maintenance

@@ Line 48: / Line 48: @@
 ** https://travis-ci.org/
 * Pay for external hosting
 ** github pro or gitlab
 ** hetzner (QGIS is currently renting a server)

@@ Line 33: / Line 33: @@
 * Separate web serving from other operations
 * <strike>Long term archive of Foss4g sites</strike> done: http://www.foss4g.org/
 = Ideas =

@@ Line 3: / Line 3: @@
 = Background  =
-Current Physical Machines hosted at Oregon State University's Open Source Lab ([[OSL]]) are entering the latter part of their life expectancy. With the recent replacement of hard drives and raid card batteries effecting performance it's time to start planning for the next 3-5 years of computing needs. We have a recently acquired large backup machine at [[OSL]], 9TB usable space. OSGeo1 at Peer will be off as of May 2014.
+Current Physical Machines hosted at Oregon State University's Open Source Lab ([[OSL]]) are entering the latter part of their life expectancy. With the recent replacement of hard drives and raid card batteries effecting performance it's time to start planning for the next 3-5 years of computing needs. In 2014 (?), we have acquired large backup machine at [[OSL]], 9TB usable space. OSGeo1 at Peer is off as of May 2014.
 == Past Performance ==
@@ Line 9: / Line 9: @@
 [[Infrastructure_Transition_Plan_2010|Current hardware]] has for the most part met the original stated goals of hosting websites for projects, issue tracking, version control, and mailing lists. Uptime has been generally good, performance occasionally not so good when things aren't configured right (open proxy, excessive WMS requests, large numbers of 404 from bots). Most services were not configured with redundancy as small amounts of downtime were deemed acceptable, which may no longer be the case.
-Our biggest dilemma has been lack of people power. We currently only have about 4-5 people who partake in core system administration. Several other people kindly manage Nabble (mail archive hosting), and some other external resources. Ideas on how to balance the workload and recruit more help is important to being able to keep the systems running.
+Our biggest dilemma has been lack of people power. We currently only have about 4-5 people (or less) who partake in core system administration. Several other people kindly manage Nabble (mail archive hosting), and some other external resources. Ideas on how to balance the workload and recruit more help is important to being able to keep the systems running.
 == Future Needs ==
 * Build services
 ** More projects are using static websites built from version control, primarily with Sphinx.
@@ Line 19: / Line 32: @@
 * More redundancy to increase uptime of important websites.
 * Separate web serving from other operations
-* Long term archive of Foss4g sites
+* <strike>Long term archive of Foss4g sites</strike> done: http://www.foss4g.org/
 = Ideas =
@@ Line 64: / Line 69: @@
 == Admin crew ==
-* Funded sysadmin time? (Short of outsourcing everything, can we find ways to avoid relying solely on volunteer time to support the infrastructure? How can we handle funded sysadmin time in a fair way vs volunteer contributions? Are there good examples to follow in other non-profit orgs?)
+* '''Funded sysadmin time?''' (Short of outsourcing everything, can we find ways to avoid relying solely on volunteer time to support the infrastructure? How can we handle funded sysadmin time in a fair way vs volunteer contributions? Are there good examples to follow in other non-profit orgs? '''Solve at least the urgent stuff from above?''')
 * Have a "fire crew" on alert throughout the entire day, 24x7
 ** at least one "fire crew" member (ready to handle any emergency SAC issues) on alert at any time in the day, which includes one in a North American timezone, one in a European timezone, and one in an Asia/Pacific timezone
@@ Line 82: / Line 87: @@
 ** Put all files into networked storage mounted via NFS (or something similar)
 ** GlusterFS (supports georeplication)
-** Use XFS (supported in Linux for a long time), ZFS, or [http://en.wikipedia.org/wiki/Comparison_of_file_systems something else] good with lots of small files.
+** Use XFS (supported in Linux for a long time, works well), ZFS (?), or [http://en.wikipedia.org/wiki/Comparison_of_file_systems something else] good with lots of small files.
 * SSD
 ** Static websites, Tile Caches, Downloads, extra disk based caching for web configurations