[Copied from  crbug.com/809792  but for panther]

Panther machines currently used in the Wifi test lab are running on:
   fgrep panther routers-DESCRIPTION.txt | sed s'/.*CHROMEOS_RELEASE_DESCRIPTION=//' | cut -d " " -f 1 | sort | uniq -c
       3 7424.0.2015_09_03_1532

Since it's only three machines, could we just replace those with whirlwind devices? Or am I not counting everything?


Due to the update to netperf-2.7, I need to build and deploy a new panther-test-ap image.  This seems like a good idea anyway since we'd like all our APs to be running the same versions of SW.

If it's not possible to replace the panther-test-aps with whirlwind or arkham, here are the steps (roughly, assuming nothing is broken):

1) build panther-test-ap:
   cros tryjob -b release-R65-10323.B -g 900169 -g 902706 --hwtest --committer grundler@google.com panther-test-ap-tryjob

2) lock a host with stumpy in the wificell (see cautotest and use hostview to find one)

3) deploy the test image to the corresponding AP. Something like:
   cros flash chromeos15-row1-rack4-host5-router.cros xbuddy://remote/trybot-whirlwind-test-ap-tryjob/R65-10323.15.0-c39332


4) test the image. Something like:
    B=kefka ; HOST=chromeos15-row1-rack4-host5.cros; test_that -b $B  $HOST suite:wifi_perf

5) update network_WiFi_UpdateRouter to use the new image (this will update all the routers over night):
   e.g. https://chromium-review.googlesource.com/757122
 

6) verify all the routers are running release-R65-10323.B builds:
    for h in $(cat hosts-wificell.txt); do r="$h-router.cros" ; echo "$r " $(ssh root@$r fgrep DESCRIPTION /etc/lsb-release); done > routers-DESCRIPTION.txt

    grep panther routers-DESCRIPTION.txt | sed s'/.*CHROMEOS_RELEASE_DESCRIPTION=//' | cut -d " " -f 1 | sort | uniq -c

5) $PROFIT from better testing. :D

Other bugs worth looking at for guidance:
  crbug.com/770255   "Move to new stable whirlwind testbed-ap build and deploy to lab"