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
656ebaea
Commit
656ebaea
authored
1 year ago
by
Ulf Markwardt
Browse files
Options
Downloads
Patches
Plain Diff
update
parent
be6cd3d2
No related branches found
Branches containing commit
No related tags found
3 merge requests
!899
Preview
,
!897
Draft: Preview
,
!894
Barnard update
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc.zih.tu-dresden.de/docs/jobs_and_resources/barnard_test.md
+54
-54
54 additions, 54 deletions
...zih.tu-dresden.de/docs/jobs_and_resources/barnard_test.md
with
54 additions
and
54 deletions
doc.zih.tu-dresden.de/docs/jobs_and_resources/barnard_test.md
+
54
−
54
View file @
656ebaea
...
@@ -21,15 +21,57 @@ from campus (or VPN). [Fingerprints](/access/key_fingerprints/#barnard)
...
@@ -21,15 +21,57 @@ from campus (or VPN). [Fingerprints](/access/key_fingerprints/#barnard)
*
All users have
**new HOME**
file systems, this means you have to do two things:
*
All users have
**new HOME**
file systems, this means you have to do two things:
1.
Install your public ssh key on the system
1.
??? Install your public ssh key on the system
-
Please create a new SSH keypair with ed25519 encryption, secured with
a passphrase. Please refer to this
[
page for instructions
](
../../access/ssh_login#before-your-first-connection
)
.
-
After login, add the public key to your
`.ssh/authorized_keys`
file
on Barnard.
-
Please create a new SSH keypair with ed25519 encryption, secured with
1.
??? "Transfer Data to New Home Directory"
a passphrase. Please refer to this
[
page for instructions
](
../../access/ssh_login#before-your-first-connection
)
.
Your personal (old) home directory at Taurus will not be automatically transferred to the new Barnard
-
After login, add the public key to your
`.ssh/authorized_keys`
file
system. **You are responsible for this task.** Please do not copy your entire home, but consider
on Barnard.
this opportunity for cleaning up you data. E.g., it might make sense to delete outdated scripts, old
log files, etc., and move other files to an archive filesystem. Thus, please transfer only selected
1.
"Transfer your data for HOME" -- see below.
directories and files that you need on the new system.
The well-known [datamover tools](../../data_transfer/datamover/) are available to run such transfer
jobs under Slurm. The steps are as follows:
1. Login to Barnard: `ssh login[1-4].barnard.tu-dresden.de`
1. The command `dtinfo` will provide you the mountpoints
```console
marie@barnard$ dtinfo
[...]
directory on datamover mounting clusters directory on cluster
/data/old/home Taurus /home
/data/old/lustre/scratch2 Taurus /scratch
/data/old/lustre/ssd Taurus /lustre/ssd
[...]
```
1. Use the `dtls` command to list your files on the old home directory: `marie@barnard$ dtls
/data/old/home/marie`
1. Use `dtcp` command to invoke a transfer job, e.g.,
```console
marie@barnard$ dtcp --recursive /data/old/home/marie/<useful data> /home/marie/
```
**Note**, please adopt the source and target paths to your needs. All available options can be
queried via `dtinfo --help`.
!!! warning
Please be aware that there is **no synchronisation process** between your home directories at
Taurus and Barnard. Thus, with the very first transfer, they will become divergent.
We recommand to **take some minutes for planing the transfer process**. Do not act with
precipitation.
## Data Management
## Data Management
...
@@ -80,50 +122,6 @@ old storages will be purged, probably by the end of November.
...
@@ -80,50 +122,6 @@ old storages will be purged, probably by the end of November.
The process of syncing data from
`/warm_archive`
to
`/data/walrus`
is still ongoing.
The process of syncing data from
`/warm_archive`
to
`/data/walrus`
is still ongoing.
### Transfer Data to New Home Directory
Your personal (old) home directory at Taurus will not be automatically transferred to the new Barnard
system.
**You are responsible for this task.**
Please do not copy your entire home, but consider
this opportunity for cleaning up you data. E.g., it might make sense to delete outdated scripts, old
log files, etc., and move other files to an archive filesystem. Thus, please transfer only selected
directories and files that you need on the new system.
The well-known
[
datamover tools
](
../../data_transfer/datamover/
)
are available to run such transfer
jobs under Slurm. The steps are as follows:
1.
Login to Barnard:
`ssh login[1-4].barnard.tu-dresden.de`
1.
The command
`dtinfo`
will provide you the mountpoints
```console
marie@barnard$ dtinfo
[...]
directory on datamover mounting clusters directory on cluster
/data/old/home Taurus /home
/data/old/lustre/scratch2 Taurus /scratch
/data/old/lustre/ssd Taurus /lustre/ssd
[...]
```
1.
Use the
`dtls`
command to list your files on the old home directory:
`marie@barnard$ dtls
/data/old/home/marie`
1.
Use
`dtcp`
command to invoke a transfer job, e.g.,
```
console
marie@barnard$
dtcp
--recursive
/data/old/home/marie/<useful data> /home/marie/
```
**Note**
, please adopt the source and target paths to your needs. All available options can be
queried via
`dtinfo --help`
.
!!! warning
Please be aware that there is **no synchronisation process** between your home directories at
Taurus and Barnard. Thus, with the very first transfer, they will become divergent.
We recommand to **take some minutes for planing the transfer process**. Do not act with
precipitation.
## Software
## Software
Please use
`module spider`
to identify the software modules you need to load. Like
Please use
`module spider`
to identify the software modules you need to load. Like
...
@@ -140,6 +138,8 @@ on Taurus.
...
@@ -140,6 +138,8 @@ on Taurus.
*
A
**second synchronization**
from
`/scratch`
has started on
**October, 18**
and is nearly done.
*
A
**second synchronization**
from
`/scratch`
has started on
**October, 18**
and is nearly done.
*
The
**data tranfer tools**
now work fine.
*
The
**data tranfer tools**
now work fine.
*
After fixing too tight security restrictions,
**all users can login**
now.
*
After fixing too tight security restrictions,
**all users can login**
now.
*
**ANSYS/2023R1**
now starts after problems: please check if your specific use case works.
*
**ANSYS**
now starts: please check if your specific use case works.
*
**login1**
is under observation, do not use it at the moment.
*
**login1**
is under construction, do not use it at the moment. Workspace creation does
not work there.
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