add some definitions, and explain that the user will be able to
login to the jail..
1 month ago
1 changed files
Download Patch File
Download Diff File
@@ -14,6 +14,11 @@ Goal
The goal of this setup is to allow people to be able to install and test
images on various boards remotely.
- User - A person or entity that is able to reserve a system, and test with it.
- Host system - The machine that controls and provides access to the systems.
- Remote power control
@@ -71,6 +76,11 @@ interface exposed on the host will be via an RPC interface, e.g.
`echo function xxx | ssh labhost labcli`, or via a socket from within
The user will be able to log into the jail that is created during the
reservation. Any modifications to the jail will be rolled back and
discarded after the system has been released, or the reservation has
@@ -121,6 +131,9 @@ Once logged in, the jail will have the following services:
nat setup so that all traffic appears from jail's IP.
3. One interface for device
4. Serial port for console access
The configuration will identify which device to put in the jail. For
USB devices, they will be able to be specified via a list of ports on
the hubs so that there is no issue w/ device probe order.
5. dhcpd for device w/ tftp already configured
6. inetd w/ tftpd setup
7. nfsd setup w/ exports configured
@@ -128,6 +141,15 @@ Once logged in, the jail will have the following services:
As the user will have root access, all of these can be modified after.
There are a number of ideas to make developing boards remotely more doable.
We can use devices that support OTG, to be USB devices for test boards. This
means you can simulate a keyboard and or a mouse. With the combination of a
HDMI to ethernet adapter (there are cheap ones for ~$40/each), a developer can
work on making X or other GUI work remotely.