Working with remote boards

Here are some general tips for working with remote boards (that is, boards in remote labs)

using a jump server [edit section]

If you have an SSH jump server, then you can access machine directly in another lab, using the ssh ProxyCommand in the host settings for a board.

I found this page to be helpful:

You should try to make each leg of the jump (from local machine to jump server, and from jump server to remote machine) password-less.

I found that if my local machine's public key was in the remote machine's authorized keys file, then I could log in without a password, even if the jump server's public key was not in the remote machine's authorized keys file.

Using ttc transport remotely [edit section]

If you have a server that already has ttc configured for a bunch of board, you can accomplish a lot just by referencing ttc commands on that server.

For example, in your local ttc.conf, you can put:

Please note that 'ttc status <remote-board>' does not work with ttc version 1.4.4. This is due to internal usage of %(ip_addr)s in the function network_status(), which will not be correct for the remote-board.

setting up ssh ProxyCommand in the Fuego docker container [edit section]

Please note that tests in Fuego are executed inside the docker container as user 'jenkins'.

In order to set up password-less operation, or use of a jump server or ProxyCommand, you have to add appropriate items (config and keys) to: /var/lib/jenkins/.ssh

Please note that this may make your docker container a security risk, as it may expose your private keys to tests. Please use caution when adding private keys or other sensitive security information to the docker container.