Closed Bug 1017303 Opened 7 years ago Closed 7 years ago

Slave loan request for a bld-linux64-ec2 vm


(Infrastructure & Operations Graveyard :: CIDuty, task)

Not set


(Not tracked)



(Reporter: ianconnolly, Assigned: ianconnolly)


(Whiteboard: [buildduty][capacity][buildslaves][loaner])

Loan :ianconnolly a AWS Linux build slave for working on :catlee's runner and runner puppet module.
Email sent to Ian with further instructions. 

Loaning slaves: 

Hi Ian, I am going to assign this to you to keep track of the loan(s). 

When you are finished with the loan(s) forever, please comment stating so and mark this bug as resolved.

By the way, now that this aws instance has been created, starting and stopping it can happen in a flash!
If you are not going to be using this machine for multiple hours, let us know in this bug and we can stop it.

Comment again when you want it started back up.
*For really fast turnaround, ping #releng (look for nick with 'buildduty')
Assignee: nobody → iconnolly
this slave has been added to slavealloc.
Assignee: iconnolly → jlund
Requested a re-creation of the instance, with the re-created instance being added to slavealloc. is back and fresher than ever.

I think slavealloc goes by hostname only but, to be safe, I didn't remove the DNS records so you should have the same ip as before.

to enable, click the checkbox in slavealloc and reboot your instance, that should start up all the buildbots shtuff.
Assignee: jlund → iconnolly
Still needed?
Flags: needinfo?(iconnolly)
(In reply to Pete Moore [:pete][:pmoore] from comment #5)
> Still needed?

Yep, definitely for another week, possibly for a second.
Flags: needinfo?(iconnolly)
Done forever ;_;
Closed: 7 years ago
Resolution: --- → INVALID
Component: Loan Requests → Buildduty
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.