Update vscode-tunnel.rst to include KUL/UH sites

[avapirev]

No description provided.

[moravveji]

I have few remarks concerning the KUL-specifics:

• The tunnel name that contains the user VSC id (the one limited to 20 chars) can be different between KUL and VUB; e.g. we use currently a template like vsc-vscXXXXX-wice which is different from that of VUB. This needs to be made clear in the documentation with site-specific tabs.
  Well ... we still have to internally agree on the tunnel name, which will happen outside this repo
• The local VSCode terminal shows that the ttyd module belongs to the 2024a toolchain. This means that users who want to use the Python(-related) modules are restricted to the 2024a toolchain only. This must be made clear in a 'Warning' box
• There is a mention of using Microsoft account, but I tried with my github connection, and it did not bite. The copilot worked as expected. So, perhaps this knot can be loosened a bit
• We also need to clarify that at KUL, we do not offer GPUs for this specific app. Think of it as a 'Note' box
• This may sound trivial but let's also mention that the same blue button at the bottom left also offers the 'Close Remote Connection' button to disconnect from the job when we're done. However, this does not terminate the job and release the resources. So, you may also think of another 'Warning' box.
• Needless to say that while the job is running on the cluster, the tunnel can be resumed by following the same steps above

[avapirev]

I have few remarks concerning the KUL-specifics:

• The tunnel name that contains the user VSC id (the one limited to 20 chars) can be different between KUL and VUB; e.g. we use currently a template like vsc-vscXXXXX-wice which is different from that of VUB. This needs to be made clear in the documentation with site-specific tabs.
  Well ... we still have to internally agree on the tunnel name, which will happen outside this repo
• The local VSCode terminal shows that the ttyd module belongs to the 2024a toolchain. This means that users who want to use the Python(-related) modules are restricted to the 2024a toolchain only. This must be made clear in a 'Warning' box
• There is a mention of using Microsoft account, but I tried with my github connection, and it did not bite. The copilot worked as expected. So, perhaps this knot can be loosened a bit
• We also need to clarify that at KUL, we do not offer GPUs for this specific app. Think of it as a 'Note' box
• This may sound trivial but let's also mention that the same blue button at the bottom left also offers the 'Close Remote Connection' button to disconnect from the job when we're done. However, this does not terminate the job and release the resources. So, you may also think of another 'Warning' box.
• Needless to say that while the job is running on the cluster, the tunnel can be resumed by following the same steps above

The only item left is the note saying we do not offer GPUs here. I think the app submission for is self-explanatory, i.e. there is no GPU offered.

[WouterVanAssche]

Looks good to me.

[smoors]

i prefer not to move the cluster cards into a tab.
the idea is to see in one view all clusters where it's available,
as is done on the other pages.

[smoors]

this works, but for 1 sentence and for only 1 site it's simpler to use a label instead?

Suggested change

	.. tab-set::
	:sync-group: vsc-sites
	.. tab-item:: KU Leuven/UHasselt
	:sync: kuluh
	On KU Leuven Tier-2 clusters, you can request CPU-only resources.
	.. tab-item:: VUB
	:sync: vub
	You may proceed to the next steps.
	|KUL| On KU Leuven Tier-2 clusters, you can request CPU-only resources.

[moravveji]

LGTM

[smoors]

@avapirev @moravveji PR implementing my suggestions: #564