CHGI Transition - Revision history

Darcy: /* Status */

2021-04-21T19:35:41Z

Status

← Older revision		Revision as of 19:35, 21 April 2021
Line 43:		Line 43:
	Crick - Restricted access.		Crick - Restricted access.

	Synergy - ~~In process~~.		Synergy - moved to ARC, users transitioned.

	== Background ==		== Background ==

Darcy: /* Status */

2020-10-28T19:35:11Z

Status

← Older revision		Revision as of 19:35, 28 October 2020
Line 38:		Line 38:

	Hyperion - moved to ARC, users transitioned.		Hyperion - moved to ARC, users transitioned.

	Theia - moved to ARC, users transitioned.		Theia - moved to ARC, users transitioned.

	Crick - Restricted access.		Crick - Restricted access.

	Synergy - In process.		Synergy - In process.

Darcy: /* Status */

2020-10-28T19:34:41Z

Status

← Older revision		Revision as of 19:34, 28 October 2020
Line 34:		Line 34:
	\| Changes from baseline Dec/2019 \|\| \|\| \|\| 20 \|\| \|\| 138 \|\| 12		\| Changes from baseline Dec/2019 \|\| \|\| \|\| 20 \|\| \|\| 138 \|\| 12
	\|}		\|}

			Cluster status:

			Hyperion - moved to ARC, users transitioned.
			Theia - moved to ARC, users transitioned.
			Crick - Restricted access.
			Synergy - In process.

	== Background ==		== Background ==

Darcy: /* Status */

2020-05-14T21:31:28Z

Status

← Older revision		Revision as of 21:31, 14 May 2020
Line 19:		Line 19:

	== Status ==		== Status ==
			User account status in CHGI and transition
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
Line 33:		Line 34:
	\| Changes from baseline Dec/2019 \|\| \|\| \|\| 20 \|\| \|\| 138 \|\| 12		\| Changes from baseline Dec/2019 \|\| \|\| \|\| 20 \|\| \|\| 138 \|\| 12
	\|}		\|}


	== Background ==		== Background ==

Darcy: Adding status for people to see.

2020-05-14T21:29:42Z

Adding status for people to see.

@@ Line 17: / Line 17: @@
 * Define ongoing maintenance governance, processes, data privacy, retention and other related processes
 * Transition data, users and workflows to RCS managed infrastructure
 == Background ==

Darcy: /* Schedule/Milestones */

2020-04-29T05:36:28Z

Schedule/Milestones

← Older revision		Revision as of 05:36, 29 April 2020
Line 75:		Line 75:
	\| Implementation Plan \|\| Q3/2019		\| Implementation Plan \|\| Q3/2019
	\|-		\|-
	\| Transition to ARC of ~~identified Quick Wins~~ \|\| Q3/2020		\| Transition to ARC of appropriate users and workflows \|\| Q3/2020
	\|-		\|-
	\| Analysis of remaining equipment and users \|\| Q3/2020		\| Analysis of remaining equipment and users \|\| Q3/2020

Darcy at 20:16, 28 April 2020

2020-04-28T20:16:42Z

← Older revision		Revision as of 20:16, 28 April 2020
Line 1:		Line 1:
	To improve the sustainability of the CHGI cluster compute and storage infrastructure, the decision was made to integrate this infrastructure with the University of Calgary's High Performance Computing site managed by Research Computing Services (RCS).		To improve the sustainability of the CHGI cluster compute and storage infrastructure, the decision was made to integrate this infrastructure with the University of Calgary's High Performance Computing site managed by Research Computing Services (RCS).
	This will allow CHGI users to leverage the ~~existing~~ RCS staff and infrastructure ~~providing access to~~ more ~~physical resources and system/software analysts~~.		This will allow CHGI users to leverage the extensive RCS staff and infrastructure.
			For more information on RCS services, please see the [[ RCS Home Page ]].

	== What does this really mean? ==		== What does this really mean? ==

Darcy at 19:35, 28 April 2020

2020-04-28T19:35:29Z

← Older revision		Revision as of 19:35, 28 April 2020
Line 1:		Line 1:
	To ~~meet building code requirements,~~ the CHGI ~~Data Centre (DC) in HSC B151 must be decommissioned. To facilitate this change~~, the ~~storage and compute capabilities housed in the DC are being transferred~~ to the University of Calgary's High Performance Computing site managed by Research Computing Services (RCS).		To improve the sustainability of the CHGI cluster compute and storage infrastructure, the decision was made to integrate this infrastructure with the University of Calgary's High Performance Computing site managed by Research Computing Services (RCS).
			This will allow CHGI users to leverage the existing RCS staff and infrastructure providing access to more physical resources and system/software analysts.

	== What does this really mean? ==		== What does this really mean? ==

Darcy at 19:06, 28 April 2020

2020-04-28T19:06:57Z

← Older revision		Revision as of 19:06, 28 April 2020
Line 14:		Line 14:
	* Develop a transition plan for the equipment and technical services CHGI offers		* Develop a transition plan for the equipment and technical services CHGI offers
	* Define ongoing maintenance governance, processes, data privacy, retention and other related processes		* Define ongoing maintenance governance, processes, data privacy, retention and other related processes
	* Transition data, users and workflows to ~~IT/~~RCS managed infrastructure		* Transition data, users and workflows to RCS managed infrastructure

	== Background ==		== Background ==
Line 20:		Line 20:

	The CHGI in collaboration with RCS is working on a planned transition of CHGI data, services and workflows to infrastructure managed by RCS. This will allow CHGI researchers to:		The CHGI in collaboration with RCS is working on a planned transition of CHGI data, services and workflows to infrastructure managed by RCS. This will allow CHGI researchers to:
	* Focus on core duties instead of IT services		* Focus on core duties instead of managing IT services
	* Open the potential for scalability in the infrastructure		* Open the potential for scalability in the infrastructure
	* Standardize several common services to ~~IT’s~~ offerings.		* Standardize several common services to RCS offerings.

	== Approach ==		== Approach ==
	The project team interviewed 15 Principal Investigators and researchers in the Analysis phase to understand the current use of the equipment and services provided by CHGI. This engagement took four weeks during which we interacted with the CHGI manager, System Administrators and PIs that leverage CHGI's equipment for their research. An important aspect in the interviews was the investment made in equipment.		The project team interviewed 15 Principal Investigators and researchers in the Analysis phase to understand the current use of the equipment and services provided by CHGI. This engagement took four weeks during which we interacted with the CHGI manager, System Administrators and PIs that leverage CHGI's equipment for their research. An important aspect in the interviews was the investment made in equipment.

	The project team took the information available and discussed the technical options based on current ~~IT’s~~ practices~~. The equipment, services and workflows have been categorized into 2 groups which was determined based on their ease of transition: ''Quick Wins'' and ''Medium to High Complexity''~~.		The project team took the information available and discussed the technical options based on current RCS practices.

	== Implementation ==		== Implementation ==
	Tasks identified as Quick Wins will be used as the first step in the implementation and will be used build trust with the CHGI user base. Quick Wins will be transitioned into based on the schedule defined below. Quick Wins include:		Tasks identified as low impact include:
	* CHGI workflows and services that can be ~~easily~~ transitioned into existing ~~IT/~~RCS infrastructure		* CHGI workflows and services that can be transitioned into existing RCS infrastructure
	* CHGI Workflows and services with very little impact and costs.		* CHGI Workflows and services with very little impact and costs.
	* CHGI equipment which are off or almost off warranty and have low dependence on storage.		* CHGI equipment which are off or almost off warranty and have low dependence on storage.

	All other tasks, CHGI web related services, or workflows heavily dependent on the IBM storage will ~~be identified as Medium to High Complexity~~ and ~~will be implemented 12 months into the transition~~. The longer transition period will give researchers extra time to prepare and integrate their processes into RCS infrastructure. Equipment and workflows ~~under~~ this ~~category~~ will remain in their current location.		All other tasks, CHGI web related services, or workflows heavily dependent on the the IBM storage system will require deeper analysis and more preparation time. The longer transition period will give researchers extra time to prepare and integrate their processes into RCS infrastructure. Equipment and workflows requiring this extra work will remain in their current location.

	Two years into the transition, a decision whether to physically move any remaining equipment to ~~IT/~~RCS infrastructure will be determined.		Two years into the transition, a decision whether to physically move any remaining equipment to RCS infrastructure will be determined.

	== End of Warranty Issues ==		== End of Warranty Issues ==
Line 47:		Line 47:

	== On Going ==		== On Going ==
	~~Once~~ the ~~first wave of~~ transition ~~happens, a revision to~~ the ~~plan will be made to decide whether to forklift part or all~~ the ~~remaining equipment to an IT data center~~.		Continuous monitoring of the transition will guide the implementation and may improve the transition process.

	== Critical Success Factors ==		== Critical Success Factors ==
Line 57:		Line 57:

	=== In Scope ===		=== In Scope ===
	* Develop a consistent process to transition users, data, workflows from CHGI to ~~IT/~~RCS infrastructure		* Develop a consistent process to transition users, data, workflows from CHGI to RCS infrastructure
	* Define ongoing maintenance governance, processes, data privacy, retention and other related processes		* Define ongoing maintenance governance, processes, data privacy, retention and other related processes
	* Transition Individual Researchers from CHGI to ~~IT/~~RCS infrastructure.		* Transition Individual Researchers from CHGI to RCS infrastructure.

	=== Out of Scope ===		=== Out of Scope ===
	* IT and CHGI will agree when equipment is ready for decommissioning. CHGI is responsible to put in the requests to dispose of equipment.		* RCS and CHGI will agree when equipment is ready for decommissioning. CHGI is responsible to put in the requests to dispose of equipment.

	== Schedule/Milestones ==		== Schedule/Milestones ==

Lleung: /* Implementation */

2020-04-22T21:21:24Z

Implementation

← Older revision		Revision as of 21:21, 22 April 2020
Line 35:		Line 35:
	* CHGI equipment which are off or almost off warranty and have low dependence on storage.		* CHGI equipment which are off or almost off warranty and have low dependence on storage.

	All other tasks, CHGI web related services, or workflows heavily dependent on the IBM storage will be identified as Medium to High Complexity and will be implemented 12 months into the transition. The longer transition period will give researchers extra time to prepare and integrate their processes ~~with IT~~ infrastructure. Equipment and workflows under this category will remain in their current location.		All other tasks, CHGI web related services, or workflows heavily dependent on the IBM storage will be identified as Medium to High Complexity and will be implemented 12 months into the transition. The longer transition period will give researchers extra time to prepare and integrate their processes into RCS infrastructure. Equipment and workflows under this category will remain in their current location.

	Two years into the transition, a decision whether to physically move any remaining equipment to IT will be determined.		Two years into the transition, a decision whether to physically move any remaining equipment to IT/RCS infrastructure will be determined.

	== End of Warranty Issues ==		== End of Warranty Issues ==