Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
hpc-compendium
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
ZIH
hpcsupport
hpc-compendium
Commits
2aaa0c4f
Commit
2aaa0c4f
authored
11 months ago
by
Martin Schroschk
Browse files
Options
Downloads
Plain Diff
Merge branch 'alpha-w' into 'preview'
Review wording See merge request
!1074
parents
9164d348
708dbaf0
No related branches found
No related tags found
2 merge requests
!1075
Automated merge from preview to main
,
!1074
Review wording
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc.zih.tu-dresden.de/docs/jobs_and_resources/alpha_centauri.md
+5
-5
5 additions, 5 deletions
...h.tu-dresden.de/docs/jobs_and_resources/alpha_centauri.md
with
5 additions
and
5 deletions
doc.zih.tu-dresden.de/docs/jobs_and_resources/alpha_centauri.md
+
5
−
5
View file @
2aaa0c4f
...
...
@@ -18,7 +18,7 @@ of the new cluster [`Barnard`](barnard.md).
!!! hint "Maintenance Work"
On **June 4+5**, we will shut down and migrate `Alpha Centauri` to the Barnard Infini
b
and
On **June 4+5**, we will shut down and migrate `Alpha Centauri` to the Barnard Infini
B
and
infrastructure.
As consequences,
...
...
@@ -32,21 +32,21 @@ For your convenience, we already have started migrating your data from `/beegfs`
!!! hint "User Action Required"
The less we have to synchronize the faster the overall process. So clean-up
The less we have to synchronize the faster
will be
the overall process. So
, please
clean-up
as much as possible as soon as possible.
Important for your work is:
*
Do not add terabytes of data to
`/beegfs`
if you cannot "consume" it before June 4.
*
After final successful data transfer to
`/data/horse/beegfs`
you then have to
move it to normal workspaces on
`/data/horse`
.
*
After
the
final successful data transfer to
`/data/horse/beegfs`
,
you then have to
move it to
the
normal workspaces on
`/data/horse`
.
*
Be prepared to adapt your workflows to the new paths.
What happens afterward:
*
complete deletion of all user data in
`/beegfs`
*
complete recabling of the storage nodes (BeeGFS hardware)
*
S
oftware
+F
irmware updates
*
s
oftware
and f
irmware updates
*
set-up of a new WEKA filesystem for high I/O demands on the same hardware
In case of any question regarding this maintenance or required action, please do not hesitate to
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment