Main Page: Difference between revisions
From HPC documentation portal
| Line 4: | Line 4: | ||
== Decomissioning of Hexagon == | == Decomissioning of Hexagon == | ||
'''DISCLAIMER'''<br> | '''DISCLAIMER'''<br> | ||
'''From 01.07.2017 hexagon is running without hardware support this could increase downtime in case of hardware failure'''.<br> | '''From 01.07.2017 hexagon is running without hardware support, this could increase downtime in case of hardware failure'''.<br> | ||
All dates below are tentatives and further plan changes might come up, but will be communicated on [http://syslog.hpc.uib.no syslog.hpc.uib.no] and also updated here.<br> | All dates below are tentatives and further plan changes might come up, but will be communicated on [http://syslog.hpc.uib.no syslog.hpc.uib.no] and also updated here.<br> | ||
Please don't hesitate to contact us at [[Support]] have you any question. | Please don't hesitate to contact us at [[Support]] have you any question. | ||
===Summary=== | ===Summary=== | ||
* Hexagon will operate with both national, local and IMR CPU accounts until Fram will not be fully operational and relevant Notur projects transferred to Fram. | * Hexagon will operate with both national, local and IMR CPU accounts until Fram will not be fully operational and relevant Notur projects transferred to Fram. | ||
* There will be a window of 2 weeks after official Hexagon decommissioning date out from Notur. This is to allow users to move their data out from Hexagon. Please don't panic if something goes wrong during a copy process, but just simply contact us at [[Support]]. | * There will be a window of 2 weeks after official Hexagon decommissioning date out from Notur. This is to allow users to move their data out from Hexagon. Please don't panic if something goes wrong during a copy process, but just simply contact us at [[Support]]. | ||
* After this 2 weeks window Hexagon will be stopped and reconfigured for local and IMR access only. | * After this 2 weeks window Hexagon will be stopped and reconfigured for local and IMR access only. | ||
* Reconfiguring is strictly required to continue to run Hexagon (as we have | * Reconfiguring is strictly required to continue to run Hexagon (as we don't have any maintenance agreement, it will also reduce power usage footprint of the system). | ||
* We expect that the reconfiguration will take approx. 2 weeks. | * We expect that the reconfiguration will take approx. 2 weeks. | ||
* A few changes to name after reconfiguration: | * A few changes to name after reconfiguration: | ||
| Line 21: | Line 19: | ||
*** /work will shrink by 1/3 (86TB) and will be at about 172TB | *** /work will shrink by 1/3 (86TB) and will be at about 172TB | ||
*** /work-common will be reduced to 176TB size | *** /work-common will be reduced to 176TB size | ||
** /home will be reformatted | |||
** reduced amount of software available through the modules (mostly old and rarely used software will be removed) | ** reduced amount of software available through the modules (mostly old and rarely used software will be removed) | ||
===Data=== | ===Data=== | ||
* | * All data needed from HOME, /work and /work-common must be moved or copied by user. | ||
* Please start moving or copying as soon as possible and we recommend you to move all unused data out from Hexagon as soon as possible. Please plan this well in advance so that we avoid file system and network overload. | |||
* After ceasing job runs on Hexagon, /work and /work-common will be re-mounted '''read-only'''. Users will be given 14 days to move out remaining, newly generated data. According to current time schedule, all data laying on /work and /work-common will be deleted during reconfiguration (see above Summary section). | * After ceasing job runs on Hexagon, /work and /work-common will be re-mounted '''read-only'''. Users will be given 14 days to move out remaining, newly generated data. According to current time schedule, all data laying on /work and /work-common will be deleted during reconfiguration (see above Summary section). | ||
Revision as of 06:56, 24 August 2017
HPC documentation portal
Welcome to the HPC documentation portal. Here you will find documentation for the high performance machines operated by the Vitenskapelig Databehandling (VD) group, part of University of Bergen (UiB). This is also a hub to the machine status, recent events and activities. For latest information please visit syslog.hpc.uib.no or follow us on Twitter @UiB_VD.
Decomissioning of Hexagon
DISCLAIMER
From 01.07.2017 hexagon is running without hardware support, this could increase downtime in case of hardware failure.
All dates below are tentatives and further plan changes might come up, but will be communicated on syslog.hpc.uib.no and also updated here.
Please don't hesitate to contact us at Support have you any question.
Summary
- Hexagon will operate with both national, local and IMR CPU accounts until Fram will not be fully operational and relevant Notur projects transferred to Fram.
- There will be a window of 2 weeks after official Hexagon decommissioning date out from Notur. This is to allow users to move their data out from Hexagon. Please don't panic if something goes wrong during a copy process, but just simply contact us at Support.
- After this 2 weeks window Hexagon will be stopped and reconfigured for local and IMR access only.
- Reconfiguring is strictly required to continue to run Hexagon (as we don't have any maintenance agreement, it will also reduce power usage footprint of the system).
- We expect that the reconfiguration will take approx. 2 weeks.
- A few changes to name after reconfiguration:
- Hexagon will shrink by 2 cabinets, roughly 96 nodes or 3072 cores.
- /work and /work-common will be reformatted:
- /work will shrink by 1/3 (86TB) and will be at about 172TB
- /work-common will be reduced to 176TB size
- /home will be reformatted
- reduced amount of software available through the modules (mostly old and rarely used software will be removed)
Data
- All data needed from HOME, /work and /work-common must be moved or copied by user.
- Please start moving or copying as soon as possible and we recommend you to move all unused data out from Hexagon as soon as possible. Please plan this well in advance so that we avoid file system and network overload.
- After ceasing job runs on Hexagon, /work and /work-common will be re-mounted read-only. Users will be given 14 days to move out remaining, newly generated data. According to current time schedule, all data laying on /work and /work-common will be deleted during reconfiguration (see above Summary section).
Syslog recent entries
<rss max=5 highlight="hexagon fimm" template=MediaWiki:Rss-feed-hpcdoc>http://syslog.hpc.uib.no/feed/</rss>
Resource monitor
hexagon.hpc.uib.no
| CPU | Parallelism |
|---|---|
|
|
fimm.hpc.uib.no
Graphs are temporarily not available.
__NOCACHE__
