Infrastructure Transition Plan - Revision history

Jive at 06:21, 7 May 2018

2018-05-07T06:21:13Z

Neteler at 11:00, 27 August 2007

2007-08-27T11:00:22Z

Warmerdam: Reverted edit of ElqU5s, changed back to last version by Jasonbirch

2007-04-11T19:16:57Z

Reverted edit of ElqU5s, changed back to last version by Jasonbirch

Show changes

Wiki-ElqU5s at 03:44, 11 April 2007

2007-04-11T03:44:34Z

Show changes

Wiki-Jasonbirch: /* Provider Matrix */

2006-10-26T15:34:50Z

Provider Matrix

Warmerdam: /* Provider Matrix */

2006-10-19T18:00:51Z

Provider Matrix

Warmerdam: /* Provider Matrix */ added iweb.ca option.

2006-10-19T18:00:00Z

Provider Matrix: added iweb.ca option.

Wiki-Jasonbirch: /* Provider Matrix */

2006-10-19T16:47:21Z

Provider Matrix

Wiki-Jasonbirch at 16:46, 19 October 2006

2006-10-19T16:46:07Z

Wiki-Jasonbirch: /* Hosting Provider */

2006-10-19T16:45:38Z

Hosting Provider

← Older revision		Revision as of 06:21, 7 May 2018
Line 1:		Line 1:
		+	#REDIRECT Archived
		+
	''This is a reduced form of the Translation Plan available at https://board.osgeo.org/servlets/GetAttachment?list=board&msgId=22236&attachId=2. ''		''This is a reduced form of the Translation Plan available at https://board.osgeo.org/servlets/GetAttachment?list=board&msgId=22236&attachId=2. ''

← Older revision		Revision as of 11:00, 27 August 2007
Line 209:		Line 209:
	\| Since 1994 Concentrate on business needs		\| Since 1994 Concentrate on business needs
	\|-		\|-
		+
		+	[[Category:Infrastructure]]

@@ Line 147: / Line 147: @@
 | Fedora
 | [http://iweb.ca/en/index.php?page=dedie&contenu=architectureReseau 4 Tier 1 peers]
-| good experience with gdal.org hosting
+| good experience with gdal.org hosting.  Since 1996 19, 916 sites hosted PEER1 part of iWeb's carrier network
 |-

@@ Line 146: / Line 146: @@
 | 1Gb
 | Fedora
-| [http://iweb.ca/en/index.php?page=dedie&contenu=architectureReseau|4 Tier 1 peers]
+| [http://iweb.ca/en/index.php?page=dedie&contenu=architectureReseau 4 Tier 1 peers]
 | good experience with gdal.org hosting
 |-

@@ Line 133: / Line 133: @@
 | ?
 | Recommended by the OSL sys admin.  Waiting for contact from CEO.  Change process seems rigiorous, and they can arbitrarily refuse installation.
 |-

@@ Line 59: / Line 59: @@
 {|  border="1" class="wikitable" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaaaaa solid; border-collapse: collapse;"
-  ! style="background:#efefef;" | Provider Name
+  ! style="background:#ffdead;" | Provider Name
   ! style="background:#ffdead;" | Package
-  ! style="background:#efefef;" | Cost
+  ! style="background:#ffdead;" | Cost
   ! style="background:#ffdead;" | Network/Physical Plant SLA
-  ! style="background:#efefef;" | Hardware SLA
+  ! style="background:#ffdead;" | Hardware SLA
-  ! style="background:#efefef;" | Managed/Colo details
+  ! style="background:#ffdead;" | Managed/Colo details
-  ! style="background:#efefef;" | Root Access
+  ! style="background:#ffdead;" | Root Access
-  ! style="background:#efefef;" | Disk Space
+  ! style="background:#ffdead;" | Disk Space
-  ! style="background:#efefef;" | Bandwidth (In/Out)
+  ! style="background:#ffdead;" | Bandwidth (In/Out)
-  ! style="background:#efefef;" | CPU
+  ! style="background:#ffdead;" | CPU
-  ! style="background:#efefef;" | Memory
+  ! style="background:#ffdead;" | Memory
-  ! style="background:#efefef;" | OS
+  ! style="background:#ffdead;" | OS
-  ! style="background:#efefef;" | Connectivity
+  ! style="background:#ffdead;" | Connectivity
-  ! style="background:#efefef;" | Comments
+  ! style="background:#ffdead;" | Comments
 |-
 | RackSpace

← Older revision		Revision as of 16:46, 19 October 2006
Line 55:		Line 55:
	* Members of Indictrans team available now to work on [[Drupal Portal]] work, notably the [[Membership Application]], and [[Service Provider Directory]] as well as a more general drupal front end for managing the ldap groups for users.		* Members of Indictrans team available now to work on [[Drupal Portal]] work, notably the [[Membership Application]], and [[Service Provider Directory]] as well as a more general drupal front end for managing the ldap groups for users.
	* Preliminary [[BuildBot Configuration]] build and smoke tests rolled out at telascience by Mateusz Loskot.		* Preliminary [[BuildBot Configuration]] build and smoke tests rolled out at telascience by Mateusz Loskot.
		+
		+	= Provider Matrix =
		+
		+	{\| border="1" class="wikitable" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaaaaa solid; border-collapse: collapse;"
		+	! style="background:#efefef;" \| Provider Name
		+	! style="background:#ffdead;" \| Package
		+	! style="background:#efefef;" \| Cost
		+	! style="background:#ffdead;" \| Network/Physical Plant SLA
		+	! style="background:#efefef;" \| Hardware SLA
		+	! style="background:#efefef;" \| Managed/Colo details
		+	! style="background:#efefef;" \| Root Access
		+	! style="background:#efefef;" \| Disk Space
		+	! style="background:#efefef;" \| Bandwidth (In/Out)
		+	! style="background:#efefef;" \| CPU
		+	! style="background:#efefef;" \| Memory
		+	! style="background:#efefef;" \| OS
		+	! style="background:#efefef;" \| Connectivity
		+	! style="background:#efefef;" \| Comments
		+	\|-
		+	\| RackSpace
		+	\| Basic package
		+	\| Starting at $425
		+	\| 100% uptime, or 5% of monthly fee credited per ½ hour downtime
		+	\| 100% uptime, or 5% of monthly fee credited per 1 hour downtime
		+	\| Managed hardware, OS, and???
		+	\| Yes?
		+	\| 80 GB EIDE
		+	\| Unltd/150Gb
		+	\| Athlon 64 3200
		+	\| 1Gb
		+	\| RHEL
		+	\| Tier 1 multihomed
		+	\| These guys have a rep for excellent service, but also for charging a premium for their reputation. I would have had to actually phone them to get a quote.
		+	\|-
		+	\| LiquidWeb
		+	\| Pro Dedicated 2 Managed Server
		+	\| $339 for this config
		+	\| 100%, exclusive of maintenance and malicious attacks, 10x downtime credit
		+	\| Replacement within 2 hours of problem identification. 10x downtime credit
		+	\| Managed hardware, OS, and Common Daemons
		+	\| Yes
		+	\| 120Gb SATA RAID1 + 120Gb SATA single
		+	\| 1Tb/1Tb
		+	\| Dual Xeon or Athlon64
		+	\| 2Gb
		+	\| CentOS
		+	\| Tier 1 multihomed
		+	\| I hadn't run across LiquidWeb before, but they have good reviews and reasonable prices. A tech answered my technical presales questions within a couple minutes. Here's an excerpt: [JB] OK, so with managed hosting, you would take care of OS and standard application patches & upgrades, but we would still have the freedom to do our own application installs as root? [LW]Yes, this is correct. We handle everything related to the Operating System and a lot of popular Daemons (MySQL, Apache, Exim, etc) but do not provide support for all of them (We're smart, but don't have time to learn about every piece of software developed extensively)
		+	\|-
		+	\| ev1servers
		+	\| Dedicated server (unmanaged)
		+	\| Starting at $299
		+	\| Could not find SLA
		+	\| Could not find SLA
		+	\| Managed hardware
		+	\| Yes
		+	\| 2x 73Gb SCSI
		+	\| 2Tb
		+	\| Dual Xeon
		+	\| 2Gb
		+	\| RHEL
		+	\| Tier 1 multihomed
		+	\| Look like a reasonable value offering. We could optionally hire a management company to do OS and basic software management.
		+	\|-
		+	\| EasyStreet
		+	\| Co-Managed Software
		+	\| ?
		+	\| Variable with management plan. 1 week credit for each hour of downtime caused by EasyStreet
		+	\| Variable with management plan. 1 week credit for each hour of downtime caused by EasyStreet
		+	\| Managed Hardware and OS
		+	\| Yes (sort of)
		+	\| ?
		+	\| ?
		+	\| ?
		+	\| ?
		+	\| ?
		+	\| ?
		+	\| Recommended by the OSL sys admin. Waiting for contact from CEO. Change process seems rigiorous, and they can arbitrarily refuse installation.
		+	\|-

@@ Line 3: / Line 3: @@
 = Hosting Provider =
-The proposed hosting solution is to use OSL for hosting most of the components listed in the Tool Requirements section below: web site, code repository, wiki, mailing lists, bug tracker.  The additional items could be moved there as well, but some movement has already been made to host them on Telascience services which seems like a good use of those resources and fits with the goals of Telascience as a group. It is proposed to use Telascience hardware as the primary North American mirror for offsite backups of OSL hosted services.
+Because OSUOSL needs to retain their non-commercial status, we are unable to obtain an SLA through them, so we will be looking at other hosting options.  See grid at bottom of page.
-There are several benefits to going with OSL: they have staff available to aid in hosting administration, they support many other open source projects, they are flexible, have good communication infrastructure and are interested in helping provide a solution for us.
+The proposed hosting solution is to use our selected provider for hosting most of the components listed in the Tool Requirements section below: web site, code repository, wiki, mailing lists, bug tracker.  The additional items could be moved there as well, but some movement has already been made to host them on Telascience services which seems like a good use of those resources and fits with the goals of Telascience as a group. It is proposed to use Telascience hardware as the primary North American mirror for offsite backups of our other hosted services.
-We would purchase a server through them, for hosting in their data center. It is proposed that we hire a systems administrator for a few months to aid in setting up our services and help migrate content over to this new service. This will help address the tight timelines that we have for migrating by the end of the calendar year. Afterward, we would have an administrator on retainer (e.g. ¼ time) to help maintain our system over time. It will be critical to maintain a Service Level Agreement (SLA) with OSL to guarantee access to
+It is proposed that we hire a systems administrator for a few months to aid in setting up our services and help migrate content over to this new service. This will help address the tight timelines that we have for migrating by the end of the calendar year. Afterward, we would have an administrator on retainer (e.g. ¼ time) to help maintain our system over time. It will be critical to maintain a Service Level Agreement (SLA) with OSL to guarantee access to
 engineering resources and the resolution of issues in a timely manner. Much of the day-to-day work would be maintained by volunteers through WebCom and SAC.