ted got a working image. We're waiting on bug 769428 where we're going to test that other people can successfully do so and run tests on it.
Panda chassis has been racked in SCL1. Still needs to be done: * network cabling * PSU plate secured * update boot.src with pxe chainloading set * inventory/dhcp updated
Network cabling completed
PSU mounting plate has been installed.
Inventory/dhcp and DNS have been updated.
Next Steps: * Needs a power cycle to update IP addresses from DHCP * Verify each board is booting with the correct IP * Bear and I will need to test the relay board to verify each relay works and is associated with the correct panda. * update boot.scr file
Power cycle is complete and all boards have the updated boot.scr file Starting Nmap 6.00 ( http://nmap.org ) at 2012-07-12 17:56 PDT Initiating Ping Scan at 17:56 Scanning 13 hosts [2 ports/host] Completed Ping Scan at 17:56, 0.06s elapsed (13 total hosts) Initiating Parallel DNS resolution of 13 hosts. at 17:56 Completed Parallel DNS resolution of 13 hosts. at 17:56, 0.02s elapsed Nmap scan report for panda-relay-01.build.scl1.mozilla.com (10.12.52.109) Host is up (0.022s latency). Nmap scan report for panda-010.build.scl1.mozilla.com (10.12.52.110) Host is up (0.020s latency). Nmap scan report for panda-011.build.scl1.mozilla.com (10.12.52.111) Host is up (0.023s latency). Nmap scan report for panda-012.build.scl1.mozilla.com (10.12.52.112) Host is up (0.022s latency). Nmap scan report for panda-013.build.scl1.mozilla.com (10.12.52.113) Host is up (0.024s latency). Nmap scan report for panda-014.build.scl1.mozilla.com (10.12.52.114) Host is up (0.025s latency). Nmap scan report for panda-015.build.scl1.mozilla.com (10.12.52.115) Host is up (0.025s latency). Nmap scan report for panda-016.build.scl1.mozilla.com (10.12.52.116) Host is up (0.025s latency). Nmap scan report for panda-017.build.scl1.mozilla.com (10.12.52.117) Host is up (0.026s latency). Nmap scan report for panda-018.build.scl1.mozilla.com (10.12.52.118) Host is up (0.025s latency). Nmap scan report for panda-019.build.scl1.mozilla.com (10.12.52.119) Host is up (0.027s latency). Nmap scan report for panda-020.build.scl1.mozilla.com (10.12.52.120) Host is up (0.031s latency). Nmap scan report for panda-021.build.scl1.mozilla.com (10.12.52.121) Host is up (0.031s latency). Read data files from: /opt/local/bin/../share/nmap Nmap done: 13 IP addresses (13 hosts up) scanned in 0.09 seconds
It's 12 of them. 10 will be used for releng staging work on bug 725845 as spoken with Jake.
Summary: Image and set-up 8 panda boards as staging/production on rack and all other needed changes → Image and set-up 12 panda boards as staging/production on rack and all other needed changes
I guess 10 should be the real number since only 10 will be used by releng.
Summary: Image and set-up 12 panda boards as staging/production on rack and all other needed changes → Image and set-up 10 panda boards as staging/production on rack and all other needed changes
To bring ted and clint into the loop, these 10 panda boards are already up and in scl1.
Great, Armen correct me if I'm wrong, but our next step should be to get the agent on these and try running tests? I can see that the boards are alive, but it doesn't appear that the agent is installed or running. Jake is there a way to get adb over IP turned on for these? That'd be the simplest way to install the agent remotely.
to turn on adb/ip: adb to the device: setprop service.adb.tcp.port 5555 stop adbd start adbd then from the host: adb connect <ip> It would be nice to see some tests running on there. Do we need a foopy? Can we use the mozharness talos bits that :callek has been working on? In my controlled 100% full access environment at home, I have trouble running tests repeated. One thing that we MUST do on fresh boot is: adb shell svc power stayon true otherwise the device will go into suspend mode and we lose the sutagent (not necessarily the adb server, although we seem to reset the networking as well).
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.