... | ... | @@ -27,11 +27,11 @@ In order to migrate an experiment, an configuration of the migrate parameters fo |
|
|
The mandatory configuration consists of:
|
|
|
|
|
|
* USER_TO = <target_user>
|
|
|
* TEMP_DIR = <hpc_temporary_directory> *
|
|
|
* TEMP_DIR = <hpc_temporary_directory>
|
|
|
|
|
|
Temp_dir is a dir on the remote platform to which both users must have access. Ideally, this dir should have these permissions (RWX|RWX|---), however (RWX|RWX|RWX) also works.
|
|
|
|
|
|
Another important point to have into account is that if your experiment data is in a shared filesystem ( example, dt-transfer and marenostrum4) you only have to fill TEMP_DIR on the dt-transfer platform.
|
|
|
Another important point to have into account is that if your experiment data is in a shared filesystem ( example, dt-transfer and marenostrum4) you only have to fill **TEMP_DIR** on the dt-transfer platform.
|
|
|
|
|
|
ex:
|
|
|
```
|
... | ... | @@ -60,15 +60,15 @@ USER_TO = bsc32523 |
|
|
TEMP_DIR = /gpfs/scratch/bsc32/bsc32070/temp_dir
|
|
|
```
|
|
|
|
|
|
Finally, is mandatory that this folder is in the same filesystem.
|
|
|
Finally, is mandatory that this folder is in the **same filesystem**.
|
|
|
|
|
|
You can expand this basic configuration as follow:
|
|
|
You can expand this **basic configuration** as follow:
|
|
|
|
|
|
* SAME_USER = false|true # Default, FALSE, used for mantain the same remote_user
|
|
|
* PROJECT_TO = <project> # Optional, if not specified project will remain the same
|
|
|
* HOST_TO = <cluster_ip> # Optional, avoid alias if possible, try use direct ip.
|
|
|
|
|
|
Before running the experiment with the new user, remind them to change queue parameter (example CLASS_A to bsc_es) if necessary.
|
|
|
**Before running** the experiment with the new user, remind them to change the **queue** parameter (example CLASS_A to bsc_es) if necessary.
|
|
|
|
|
|
# Perform the migration
|
|
|
|
... | ... | @@ -77,11 +77,11 @@ Once configured, double-check that you're using the AS v3.13.0+. |
|
|
There are two modes of running `autosubmit migrate`, both of them consist of a two-step procedure:
|
|
|
|
|
|
* Migrate everything:
|
|
|
* (User-Owner) autosubmit migrate <expid> -o
|
|
|
* (User-Target)autosubmit migrate <expid> -p
|
|
|
* * (User-Owner) `autosubmit migrate <expid> -o`
|
|
|
* * (User-Target)`autosubmit migrate <expid> -p`
|
|
|
* Migrate only remote files. (usefull if the local user is the same)
|
|
|
* (User-Owner) autosubmit migrate <expid> -o --onlyremote
|
|
|
* (User-Target) autosubmit migrate <expid> -p --onlyremote
|
|
|
* * (User-Owner) `autosubmit migrate <expid> -o --onlyremote`
|
|
|
* * (User-Target) `autosubmit migrate <expid> -p --onlyremote`
|
|
|
|
|
|
|
|
|
# Tests done
|
... | ... | |