You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

Windows PowerShell

Open the PowerShell and the window as shown below appears


Then type the following commands in the PowerShell window:

  • Download and install scoop
iwr -useb get.scoop.sh | iex
  • Test scoop:
scoop help
  • Install git support for scoop
scoop install git


  • Install smallstep
scoop bucket add smallstep https://github.com/smallstep/scoop-bucket.git scoop install smallstep/step


  • Verify smallstep
step



Configuration of the step client

Initialize the client with the command:

step ca bootstrap --ca-url=https://sshproxy.hpc.cineca.it --fingerprint 2ae1543202304d3f434bdc1a2c92eff2cd2b02110206ef06317e70c1c1735ecd 


If everything is fine the following messagg will compare on the shell:


Activation of the ssh-agent

On the system windows 10/11 the ssh-agent is active by default. You can verify it with the command:

Get-Service -Name ssh-agent  

and the output on the Power-shell will be:

If the service is not in "running status"  it can be activated with:


Start-Service -Name ssh-agent  


If is still not working , it is necessary to open the Power-shell as admin:



bla bla bla

Windows Subsystem Linux (WSL)


bla bla bla


RCM?

Starting a simple RCM session under Windows on one of our CINECA clusters:  

The prerequisits are: 

  1. Having a configured step client working in Windows PowerShell (as described in Setup Step Client Windows PowerShell ) 
  1. download from G100 this magic version of RCM (/g100/home/userinternal/lcalori0/RCM.exe) 

Now to open an RCM session: 

  1. get your certificate in the PowerShell with step:  
    step ssh login <email@cineca.it> --provisioner cineca-hpc 
  1. launch RCM, don't get a newer version when asked for, and simply connect to a login node 

 

  • No labels