ensure we have 6 foopies configured and up to date so we can use them in production for 6 chassis of panda boards

RESOLVED FIXED

Status

RESOLVED FIXED
6 years ago
3 months ago

People

(Reporter: jmaher, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
We are going to be turning on 6 chassis worth of panda boards (66 pandas) and we need to make sure we have foopies to run them!

This might be a dup of bug 802667.
(Reporter)

Comment 1

6 years ago
oops, I meant this might be a dup of bug 790339.
Blocks: 725544, 820824
(Reporter)

Updated

6 years ago
Depends on: 820827

Comment 2

6 years ago
Yes we have enough foopies up as per bug 790339, I'll make sure they are updated with the latest version of the tools repo and have the dirs created in the correct location once we have the pandas up in bug 820825

Comment 3

6 years ago
kmoir I wrote this script for setting up the "b2g pandas" that might be useful.
Section #2 in the script will not help until the day that we can use mozpool for the Android slaves.
This script does not setup symlinks to clientproxy.py.
(In reply to Armen Zambrano G. [:armenzg] from comment #3)
> kmoir I wrote this script ... 

You didn't link it :-P

Kim also had a work-in-progress script in https://bugzilla.mozilla.org/attachment.cgi?id=683163 that should work just fine as well ;-)

We do plan on consolidating the scripts eventually and using a single puppet magic for it all, of course.

Comment 5

6 years ago
Oh brain! Why can't you telepathically paste unto a web browser?!
https://hg.mozilla.org/build/tools/file/default/buildfarm/mobile/setup_foopy.py

Comment 6

6 years ago
Thanks for the script Armen.  

I think this can be closed, we have foopies 96-101 up for the 66 new pandas
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
(Assignee)

Updated

5 years ago
Product: mozilla.org → Release Engineering
(Assignee)

Updated

3 months ago
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.