Accessing the lab
Ask Raise a ticket to ask for access on the mailing list: ldg-mlab-admins@linaro.org.
Mention what kind of hardware you need and for how long. Also explain if there is any special set up you need for your testing. In the lab at the moment all the machines have one NIC connected and they are all in the same network. This means any tests that require to flood the network need to be coordinated.
to the lab: https://servicedesk.linaro.org/servicedesk/customer/portal/14
Hardware Sharing
You will get two sets of credentials for the lab:
...
You will only be able to use a machine that has been assigned to you (except for admins, who have access to all but will not use this except for troubleshooting).
Note:
Newer Debian OpenSSL is now enforcing TLS 1.2 and mlab VPN server doesn't support it. Hence, the openvpn client needs to enforce TLS 1.0 negotiation with mlab.
You need to run openvpn with --tls-version-min 1.0, or edit /etc/ssl/openssl.cnf to reduce MinProtocol from TLSv1.2 to TLSv1.0.
D03 kernel opts
The recommended kernel opts for D03 (pre-ERP 17.12) is:
console=ttyS0,115200 --- console=ttyS0,115200
This is so that the console is not lost after installing, and then so that the configuration is there after rebooting and booting into the installed system. This was a known issue with D03s that was fixed on ERP 17.12). D05 do not need such config.
...
Hostname can be set either when booting the machine on the kernel cmd line:
netcfg/hostname=r1-m1-c11n1
or when provisioning by adding it to the preseed using {{ hostname }} as if the preseed file were a jinja template.
...