Closed
Bug 807415
Opened 12 years ago
Closed 9 years ago
puppet should setup directory structure on foopies
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: kmoir, Unassigned)
Details
Attachments
(1 file)
2.56 KB,
patch
|
Callek
:
feedback+
|
Details | Diff | Splinter Review |
Right now we just run a script after the foopies have been puppetized to create the dirs for the pandas, would be nice if this was puppetized.
Reporter | ||
Comment 1•12 years ago
|
||
This is just a better shell script than the one that currently exists. For example
./create_dirs.sh 687 697 buildbot-master41 panda
Still working out the details to run this through puppet.
Attachment #683163 -
Flags: review?(bugspam.Callek)
Comment 2•12 years ago
|
||
Comment on attachment 683163 [details] [diff] [review]
patch
>diff --git a/buildfarm/mobile/create_dirs.sh.in b/buildfarm/mobile/create_dirs.sh.in
>--- a/buildfarm/mobile/create_dirs.sh.in
>+++ b/buildfarm/mobile/create_dirs.sh.in
>@@ -1,33 +1,59 @@
> #!/bin/bash
>
>-tegras="sedTEGRALISTsed"
>+#script to run as root on the foopies to setup device dirs
>
>-echo "setting up tegra directories"
>+if [ $# != 4 ]; then
>+ echo "usage: create_dirs.sh start end master [panda|tegra]"
>+ exit
>+fi
Suggestion, use python+json.tool+devices.json to extract a useable list based on the foopy?
Reporter | ||
Comment 3•12 years ago
|
||
Also, puppet should configure logrotate on the foopies to only store a fixed number of log files, right now their are too many
Comment 4•12 years ago
|
||
Comment on attachment 683163 [details] [diff] [review]
patch
Review of attachment 683163 [details] [diff] [review]:
-----------------------------------------------------------------
f+, which for this, is enough to land it. However see my comment earlier about using devices.json to get the list of devices to create. Since always assuming a contiguous number will prove flawed (especially with tegras)
Attachment #683163 -
Flags: review?(bugspam.Callek) → feedback+
Reporter | ||
Comment 5•12 years ago
|
||
Yes, I'm going to look at parsing devices.json and using puppet to set this up, but I have to fix some other bugs first.
Comment 6•11 years ago
|
||
Callek: did your (or Pete's) recent work with the foopies already fix this?
Flags: needinfo?(bugspam.Callek)
Comment 7•11 years ago
|
||
(In reply to Chris Cooper [:coop] from comment #6)
> Callek: did your (or Pete's) recent work with the foopies already fix this?
No its still a todo, just not urgent at this point
Flags: needinfo?(bugspam.Callek)
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Reporter | ||
Comment 8•11 years ago
|
||
This should be easier now that mobile devices are managed by slavealloc. We just need to create the directory name, not additional files in this dir.
Comment 9•11 years ago
|
||
I've talked to Callek about this recently, but I'm still not sure how exactly we want this to work.
I think we want to add foopies to slavealloc, and then periodically poll slavealloc to see which mobile devices a particular foopy should have attached, possibly moving old devices aside, and setting up new device dirs as required.
Since foopies *should* have long uptimes, we should treat puppet-on-foopies the same way we do puppet-on-masters and run it on some regular cadence. Under that model, there's no reason to implement another periodic check for which mobile devices should be attached to a given foopy, we should just do it from puppet.
Lots of intervening steps to get to that model though.
Updated•11 years ago
|
Assignee: nobody → armenzg
Updated•11 years ago
|
Assignee: armenzg → nobody
Reporter | ||
Comment 10•9 years ago
|
||
Think this can be closed since pandas are on there way out in bug 1186615
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Assignee | ||
Updated•7 years ago
|
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•