- Infos im HLRS Wiki sind nicht rechtsverbindlich und ohne Gewähr -
- Information contained in the HLRS Wiki is not legally binding and HLRS is not responsible for any damages that might result from its use -

Hawk installation schedule: Difference between revisions

From HLRS Platforms
Jump to navigationJump to search
No edit summary
m (Fix Syntax from https://kb.hlrs.de/platforms/index.php?title=Hawk_installation_schedule&type=revision&diff=6117&oldid=6094)
 
(31 intermediate revisions by 5 users not shown)
Line 8: Line 8:
| end of May 2019|| Installation of a small test system
| end of May 2019|| Installation of a small test system
|-
|-
| September 2nd ... 6th || Reduce Cray XC40 Hazel Hen to ~3800 Nodes and
| September 2nd ... 6th || maintenance and preparation
preparation infrastructure for Hawk  (1st part)
of infrastructure (1st part).
|-
|-
| October 2019|| Installation of 16 racks Hawk, storage, pre-post servers, …
| November 19th || Reduce Cray XC40 HazelHen to ~4488 Nodes and
preparation of infrastructure for Hawk 
|-
| January 17th 2020 || Installation of 8 racks Hawk, storage, pre-post servers, ...
integration, testing, setup for users
integration, testing, setup for users
|-
|-
| November 2019 || Test Phase for pilot users  ~ 4 weeks
| until Februar 18th  || complete Hawk hardware installation
|-
| mid-February  || Test Phase for pilot users  ~ 3 weeks. Due to the delayed delivery, the test phase will also be postponed. The filesystem will be ws9 (Hazel Hen)
|-
| February 24 2020 || Final shutdown and decommission of Hazel Hen
and preparation of infrastructure for the complete installation of Hawk.
|-
| February 25 2020 || hazelhen workspace filesystem (ws9) has been fully integrated with all workspaces into the hawk system.
|-
| until March 1st ||  testing, and integrate additional racks into
first phase (2048 nodes)
|-
| March 9th || general availability for all users
|-
| until March 15 || prepare power and cooling facility for second phase hawk
|-
| July 20th || connect racks 1 ... 16 with tested racks 17 ... 40 This step may need 15 days. We will try to run user jobs on racks 41 ... 44 ||
|-
| July 23th || The 512 node interim system is available for users. These 4 racks will continuously provide computing resources while additional
System tests and benchmarks take place on the 40 Rack Hawk system.
|-
| August || System functionality test. (Large applications, IO-performance, MPI - performance / funtionality, power consumption, system stability, ...).
Optimizations of the cooling system are not yet completed.
|-
| September 18th || System Acceptance. Large benchmarks run successful, user access on Hawk will be possible within the next few days. Start of production
|-
| October 12th|| integrate racks 41 ... 44 into production system. System will be unavailable for ~ 2 weeks
|-
| October 26 || start regular user operation
|-
|-
| December 2019 || Decomission Hazel Hen and prepare infrastructure to
| May 2021 || [[Workspace_migration|Data migration]] by users from ws9 (Hazel Hen) onto ws10 (Hawk) filesystem
complete installation Hawk
|-
|-
| later || complete Hawk hardware installation, testing, and integrate into
| || installation phase finished
fisrt phase
|-
| more later || Acceptance and production
|}
|}
== Terms of Use for installation phase ==
we are pleased to provide early user access to Hawk.
Please note that the system is still far from production status in terms of stability / performance / configuration / usage.
* Both the node configuration (such as numa domains per socket) and the InfiniBand configuration are not yet final und both will be subject to change.
* This means that the performance of the system is not optimal. It also implies that the users should not yet attempt an optimization of their applications based on the current setup.
* No monitoring system active, this may cause failed jobs if compute nodes break down and will be part of subsequent jobs
The usage is granted under the following conditions:
* Do not publish performance measurements of the current system configuration
* Do not monopolize the system. Give other users the opportunity to use the system. Avoid long running jobs.
* If you encounter problems, please report this to the prepared Trouble Ticket System via email to:
    rt-platform-hawk@hlrs.de
* Due to the current state of the system, your application may not yet be operational. In this case, please wait a few more days. The system will be improved very quickly.

Latest revision as of 15:54, 20 November 2024

This page will be updated as new information becomes available. Please be aware, HPC systems are made out of leading edge components. If one of this components is delayed, the complete schedule will change. Do not take this schedule too serious...

time frame action
end of May 2019 Installation of a small test system
September 2nd ... 6th maintenance and preparation

of infrastructure (1st part).

November 19th Reduce Cray XC40 HazelHen to ~4488 Nodes and

preparation of infrastructure for Hawk

January 17th 2020 Installation of 8 racks Hawk, storage, pre-post servers, ...

integration, testing, setup for users

until Februar 18th complete Hawk hardware installation
mid-February Test Phase for pilot users ~ 3 weeks. Due to the delayed delivery, the test phase will also be postponed. The filesystem will be ws9 (Hazel Hen)
February 24 2020 Final shutdown and decommission of Hazel Hen

and preparation of infrastructure for the complete installation of Hawk.

February 25 2020 hazelhen workspace filesystem (ws9) has been fully integrated with all workspaces into the hawk system.
until March 1st testing, and integrate additional racks into

first phase (2048 nodes)

March 9th general availability for all users
until March 15 prepare power and cooling facility for second phase hawk
July 20th connect racks 1 ... 16 with tested racks 17 ... 40 This step may need 15 days. We will try to run user jobs on racks 41 ... 44
July 23th The 512 node interim system is available for users. These 4 racks will continuously provide computing resources while additional

System tests and benchmarks take place on the 40 Rack Hawk system.

August System functionality test. (Large applications, IO-performance, MPI - performance / funtionality, power consumption, system stability, ...).

Optimizations of the cooling system are not yet completed.

September 18th System Acceptance. Large benchmarks run successful, user access on Hawk will be possible within the next few days. Start of production
October 12th integrate racks 41 ... 44 into production system. System will be unavailable for ~ 2 weeks
October 26 start regular user operation
May 2021 Data migration by users from ws9 (Hazel Hen) onto ws10 (Hawk) filesystem
installation phase finished


Terms of Use for installation phase

we are pleased to provide early user access to Hawk.

Please note that the system is still far from production status in terms of stability / performance / configuration / usage.

  • Both the node configuration (such as numa domains per socket) and the InfiniBand configuration are not yet final und both will be subject to change.
  • This means that the performance of the system is not optimal. It also implies that the users should not yet attempt an optimization of their applications based on the current setup.
  • No monitoring system active, this may cause failed jobs if compute nodes break down and will be part of subsequent jobs

The usage is granted under the following conditions:

  • Do not publish performance measurements of the current system configuration
  • Do not monopolize the system. Give other users the opportunity to use the system. Avoid long running jobs.
  • If you encounter problems, please report this to the prepared Trouble Ticket System via email to:
   rt-platform-hawk@hlrs.de
  • Due to the current state of the system, your application may not yet be operational. In this case, please wait a few more days. The system will be improved very quickly.
Retrieved from "https://kb.hlrs.de/platforms/index.php?title=Hawk_installation_schedule&oldid=7585"