SSH keys can be set manually using the following process:
Save the public SSH key for the root user.
export SCSD_SSH_KEY=$(cat /root/.ssh/id_rsa.pub | sed 's/[[:space:]]*$//')
If a different SSH key is to be used (for example from conman), then set the
SCSD_SSH_KEY environment variable to that key value.
Generate a System Configuration Service configuration via the scsd tool.
The administrator must be authenticated to the Cray CLI before proceeding.
cat > scsd_cfg.json <<DATA
{
"Force":false,
"Targets": $(cray hsm inventory redfishEndpoints list --format=json | jq '[.RedfishEndpoints[] | .ID]' | sed 's/^/ /'),
"Params":{
"SSHKey":"$(echo $SCSD_SSH_KEY)"
}
}
DATA
Inspect the generated scsd_cfg.json file.
Ensure the following are true before running the command below:
SSHKey settings match the desired public keycray scsd bmc loadcfg create scsd_cfg.json
Check the output to verify all hardware has been set with the correct keys. Passwordless SSH to the root user should now function as expected.
Verify access to a node controller in a liquid-cooled cabinet.
SSH into the node controller for the host xname.
For example, if the host xname is x1000c1s0b0n0, then the
node controller xname would be x1000c1s0b0.
If the node controller is not powered up, then this SSH attempt will fail.
ssh x1000c1s0b0
x1000c1s0b0:>
Notice that the command prompt includes the hostname for this node controller