Niagara: Difference between revisions

From Alliance Doc
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 1: Line 1:
{{Draft}}
{{Draft}}
{| class="wikitable"
|-
| Availability: Beta-testing Winter, 2018; Compute Canada RAC2018 allocations starting April 1, 20178
|-
| Login node: '''niagara.computecanada.ca'''
|-
| Globus endpoint: '''computecanada#niagara-dtn'''
|}
Niagara will be a large parallel system, located at the University of Toronto (SciNet), and is anticipated to have approximately 66,000 CPU cores. This will be a balanced, tightly coupled high performance computing resource, designed mainly for large parallel workloads. Compute Canada is aiming to deploy this system early 2018, and is including it in the RAC 2018 (which starts April 1, 2018).  
Niagara will be a large parallel system, located at the University of Toronto (SciNet), and is anticipated to have approximately 66,000 CPU cores. This will be a balanced, tightly coupled high performance computing resource, designed mainly for large parallel workloads. Compute Canada is aiming to deploy this system early 2018, and is including it in the RAC 2018 (which starts April 1, 2018).  



Revision as of 14:06, 6 October 2017


This article is a draft

This is not a complete article: This is a draft, a work in progress that is intended to be published into an article, which may or may not be ready for inclusion in the main wiki. It should not necessarily be considered factual or authoritative.




Availability: Beta-testing Winter, 2018; Compute Canada RAC2018 allocations starting April 1, 20178
Login node: niagara.computecanada.ca
Globus endpoint: computecanada#niagara-dtn

Niagara will be a large parallel system, located at the University of Toronto (SciNet), and is anticipated to have approximately 66,000 CPU cores. This will be a balanced, tightly coupled high performance computing resource, designed mainly for large parallel workloads. Compute Canada is aiming to deploy this system early 2018, and is including it in the RAC 2018 (which starts April 1, 2018).

  • Apr.4, 2017: Site visits have taken place, and the vendors are preparing their bids.
  • Mar.27, 2017: RFP was issued, due April 24, 2017.
  • Feb.13, 2017: the RFP is in preparation (final stages) and is expected to be issued by the end of February.
  • Mar.15, 2017: RFP issued.
  • August, 2017: proposals have been reviewed, and vendor chosen.
  • September, 2017: contract negotiations are ongoing.