Compatible with:
Custom AiiDA scheduler/transport plugins for ARCHER2.
It can be used to add custom plugins under the aiida-scheduler entry point. So, once you have it installed, you will have extra scheduler and transport plugins in addition to ones shipped with AiiDA. When you need to configure the computer, you simply provide the entry point that is compatible with the target machine.
Once all files are in place and entry points are defined accordingly:
pip install -e .The 2.x versions of this package are compatible with aiida-core 1.x, and the 3.x versions are compatible with aiida-core 2.x.
Use verdi computer setup to setup a ARCHER2 computer node.
Choose the archer2.ssh plugin for transport and archer2.slurm for scheduler.
Once done, use the verdi computer configure archer2.ssh <name> to configure the transport for the computer.
The login password should be set under the ARCHER2_PASS environmental variable, or ARCHER2_PASS_<USERNAME> for per-user basis if desired.
At the current state, this plugin should be strictly considered as an workaround rather than production code. This is because your password will be exposed in the environmental variable. Despite that they are only needed when launching daemon or accessing the files interactively, the password are stored in memory in plain text and prone to leaks. It is highly recommanded to use a random generated password specific for ARCHER2, and have it stored safely with password managers such as KeePass.
The following guide may be useful for automate setting and removing the environmental variables:
First, Make a file called archer-pass in ~/.config, containing the following line:
export ARCHER2_PASS_<USERNAME>=<your_password>Then run gpg -c archer-pass, which will prompt you for a password used for encrypting this file. Afterwards, there will be a archer-pass.gpg in the same folder file.
You can delete the original file now.
Next, add the following function to your .bashrc:
archer-pass () {
eval `gpg -d ~/.config/archer-pass.gpg 2>/dev/null`
}
unset-pass () {
unset $(env | grep ARCHER2_PASS | awk -F'=' '{print $1}')
}
After restarting the terminal, you can use the archer-pass function in the shell to add the environmental variables: ARCHER2_PASS_<USERNAME>.
It will ask you to enter the password used for encryption. Once the environmental variable are in place, start/restart the AiiDA daemon so they get picked up.
Then you can use unset-pass to remove them from the environmental variable.
Note that the password needs to be set to use commands using transports, such as verdi calcjob gotocomputer.
Dict(dict={
'resources': {
'tot_num_mpiprocs': cores, # Total number of MPI processes
'num_machines': nm, # Number of nodes to be used
'num_mpiprocs_per_machine': num_mpi_per_machine, # Number of mpi processes per machine - useful if underpopulating is needed
},
'max_wallclock_seconds': int(3600 * hours),
'import_sys_environment': False,
'mpirun_extra_params': ["--distribution=block:block", "--hint=nomultithread"],
'account': '<budget_code>',
'queue_name': '<partition_name>',
}- Updated the authentication order to support the ARCHER2 full system.
- Updated entrypoint name prefixes to comply with the new aiida-core convention. Old entrypoint names remain for now to ensure backward compatibility.
Allow per-user based password settings.
The password should be put into ARCHER2_PASS_<USERNAME> where <USERNAME> is your username in upper case.
Added specialised scheduler for ARCHER2
You may kindly open and PR and add your collection to the package so it can contain all possible combinations and plugins to be used by others as well.