Lines Matching full:machine

34 Each machine is labeled with its hostname and the number or letter used to
38 associated with. Each device connects to a host machine, either directly or
41 **Disclaimer: Please ONLY make changes on a lab machine as a last resort, as it
45 made on the machine (such as a driver update), please contact an infra team
52 ### Locating the host machine for a failing bot
56 machine where a failing bot is running in order to debug the failure.
62    builder and buildslave. Click the "Lookup" link next to "Host machine". This
65    select the machine which runs the buildslave in question.
66 3. The information box will display the hostname of the machine as well as the
67    KVM switch and number used to access the machine, if the machine is in the
72    the machine up.
73 5. Log in to the machine if necessary. The password is stored in
82 2. Click the "Lookup" link for the host machine. Remember the name of the
84 3. The hosts page will display the information used to access the host machine
90 5. Access the host machine for the device, per the above instructions. Use the
100 ### Bringing up a new buildbot host machine
102 This assumes that we're just adding a host machine for a new buildbot slave,
106 1. Obtain the machine itself and place it on the racks in the lab. Connect
108 2. If we already have a disk image appropriate for this machine, follow the
109    instructions for flashing a disk image to a machine below. Otherwise, follow
110    the instructions for bringing up a new machine from scratch.
111 3. Power on the machine. Be sure to kill any buildbot processes that start up,
114 4. Set the hostname for the machine.
115 5. Ensure that the machine is labeled with its hostname and KVM number.
119 7. Add an entry for the new host machine to the slave_hosts_cfg.py file in the
126 10. Reboot the machine and monitor the build master to ensure that it connects.
132 1. Locate or add a host machine. We generally want to keep the number of
133    devices attached to each host below 5 or so. If a new host machine is
135    host machine, with the exception that the slave corresponds to the Android
136    device, not the host machine itself.
143    attaching to the host machine.
144 4. Connect the device to the host machine, either through a powered USB hub or
145    directly to the machine.
148 6. Authorize the device for USB debugging on the host machine by checking the
156 8. Reboot the machine to start the buildslave.
159 ### Bringing up a new machine from scratch
167 ### Flashing a disk image to a machine
170    machine.
171 2. Turn on the machine and load the boot menu. For Shuttle machines, press
190 15. Select the image to use. Make sure that it's compatible with this machine.
191 16. Choose the hard drive in the machine. It should be the only option.
193 18. Choose "reboot" after flashing the image to the machine.
194 19. Set the hostname of the machine so that it doesn't conflict with any
199 1. Make sure that the machine is in a clean state: no pre-existing buildslave
202    machine.
203 3. Turn on the machine and load the boot menu. For Shuttle machines, press
223 12. Choose the hard drive in the machine. It should be the only option.