Slurm prolog #50
Slurm prolog #50
Conversation
heerener
had a problem deploying
to
aws-sandbox-hpc
GitHub Actions
Failure
|
I need to move the config template file from |
heerener
force-pushed
the
slurm_prolog
branch
2 times, most recently
from
96592db to
98b5a30
Compare
| cat << _EOF_ >> /opt/slurm/etc/scripts/prolog.d/80_cloudwatch_agent_config_prolog.sh | ||
| #!/bin/bash | ||
|
|
||
| CWAGENT_CONFIG=/sbo/data/scratch/CWAgent_config_\$SLURM_CLUSTER_NAME.json |
There was a problem hiding this comment.
This assumes that we have Lustre mounted on the cluster, which I believe it will fail if we enable benchmark but disable lustre?
Can we have that file inside /scripts, for example? Or some other folder we know for sure it will be present?
There was a problem hiding this comment.
I think I had a similar thought but forgot to update this variable!
@WeinaJi does this have to live in the scratch folder, or can it live in /opt/slurm so it gets removed together with the cluster?
There was a problem hiding this comment.
The CWAgent_config*.json is only used by the prolog script. It can live anywhere as long as it can be read by the prolog script.
|
|
||
| if [ ! -f \$CWAGENT_CONFIG ]; then | ||
| echo "Create CWAGENT_CONFIG " \$CWAGENT_CONFIG | ||
| sed "s/\\$CLUSTER_NAME/\$SLURM_CLUSTER_NAME/g" /opt/slurm/CWAgent_config_tpl.json > \$CWAGENT_CONFIG |
We're not going to download it anyway
Minimum allowed line rate is |
|
Failing tests can be ignored on this branch; the fixes will be taken care of in #54. |
No description provided.