we should be able to tell slavealloc to send a specific number of slaves of a given pool to a specifc master

RESOLVED WONTFIX

Status

P4
minor
RESOLVED WONTFIX
7 years ago
2 years ago

People

(Reporter: jhford, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2556] [slavealloc])

When doing a time-critical release, its really frustrating to see a bunch of jobs pending on 1 of 2 slaves.  We should have a knob that says "I am doing a release and I want X of this type of slave without having to specify specific slaves to push around

Comment 1

7 years ago
IMHO the right way is to allow release jobs to happen in any master rather than lock them to a specific master where we really have a silo rather than the whole pool.
I think this is a great idea. Let's be sure to avoid calling turning this into "release mode" when we build it, though. Having the generic ability to say "gimme more slaves" could be useful elsewhere.
Summary: we should be able to tell slavealloc a master is doing a release and it should throw slaves at the master → we should be able to tell slavealloc to send a specific number of slaves of a given pool to a specifc master
(In reply to Armen Zambrano G. [:armenzg] - Release Engineer from comment #1)
> IMHO the right way is to allow release jobs to happen in any master rather
> than lock them to a specific master where we really have a silo rather than
> the whole pool.

actually, I'd rather have masters that *only* did releases.
(In reply to Chris AtLee [:catlee] from comment #3)
> (In reply to Armen Zambrano G. [:armenzg] - Release Engineer from comment #1)
> > IMHO the right way is to allow release jobs to happen in any master rather
> > than lock them to a specific master where we really have a silo rather than
> > the whole pool.
> 
> actually, I'd rather have masters that *only* did releases.

Yes.  There are other advantages to having masters that only do releases, like being able to use a snapshot of releng infra that has been vetted by a staging release + manual testing.
(In reply to Chris AtLee [:catlee] from comment #3)
> (In reply to Armen Zambrano G. [:armenzg] - Release Engineer from comment #1)
> > IMHO the right way is to allow release jobs to happen in any master rather
> > than lock them to a specific master where we really have a silo rather than
> > the whole pool.
> 
> actually, I'd rather have masters that *only* did releases.

Yeah, this is good to have, too. I'm having trouble coming up with a specific use case, but I still feel like this feature could be useful.
Found in triage.

Unclear from the back-forth in this bug as to what the actual objective is here, but regardless, I *think* this is the correct component.
Component: Release Engineering → Release Engineering: Developer Tools
QA Contact: hwine
(Assignee)

Updated

5 years ago
Product: mozilla.org → Release Engineering

Updated

4 years ago
Whiteboard: [slavealloc] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2556] [slavealloc]
WONTFIX in favor of bug 1135818.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WONTFIX
(Assignee)

Updated

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