Skip to content

Update VSCode cluster connection instructions for new configuration#324

Open
CarlosLopezElorduy wants to merge 1 commit intomainfrom
289-update-vscode-cluster-instructions
Open

Update VSCode cluster connection instructions for new configuration#324
CarlosLopezElorduy wants to merge 1 commit intomainfrom
289-update-vscode-cluster-instructions

Conversation

@CarlosLopezElorduy
Copy link
Copy Markdown
Member

Revise the documentation to reflect changes in the cluster configuration, including updated resource allocation commands and SSH settings for connecting to the IRB cluster.

Copy link
Copy Markdown
Member

@FedericaBrando FedericaBrando left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the update Carlos,

Actually I do it in a different way - I use the SBATCH command to submit the job and I always call the same node, cpus and memory directly in the sbatch file. This is my current header:

❯ cat .local/bin/vscode-it
#!/bin/bash

#SBATCH --job-name="code-client"
#SBATCH --cpus-per-task=16
#SBATCH --nodelist=irbccn25
#SBATCH --partition=bbg_cpu_zen4
#SBATCH --mem=32G
#SBATCH --qos=interactive
#SBATCH --time=30-00:00:00     # walltime

set -xe

/usr/sbin/sshd -D -p 3131 -f /dev/null -h ${HOME}/.ssh/id_ecdsa

then I run it from the login node with:

sbatch vscode-it

This avoids the problem of allocating a different node every time and then losing the history for your opened sessions on a specific node in vscode, then it reduces the steps from 3 to just one, since the job is directly launched from the login node, no need for a screen nor an interactive session.


Having said so, your method works as well, and it's fine to me, up to you. If you want to merge go ahead!

🚀 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

BBGwiki | [update] Update VSCode in cluster instructions for new cluster

2 participants