1305391 - Slave loan request for a bld-linux64-ec2 vm

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: CIDuty, task)

Description

[Mihai Tabara [:mtabara]⌚️GMT]

Need a testing environment to test my puppet patches in order to deploy balrogworker with scriptworker. 

Thanks!

Comment 1

[Andrei Obreja [:aobreja NOT AVAILABLE][:buildduty]]

Email sent to mtabara for further instructions. 

Loaning machines: 
- dev-linux64-ec2-mtabara

Hi Mihai, 

As a note, linux and mac build machine do not provide vnc connection.
I am going to assign this to you to keep track of the loan. 

When you are finished with the loan forever, please comment stating so here in the bug, and mark the 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 faster turnaround, ping #releng (look for nick with 'buildduty')

Comment 2

[Mihai Tabara [:mtabara]⌚️GMT]

Thanks again, works like a charm, all good.

Comment 3

[Andrei Obreja [:aobreja NOT AVAILABLE][:buildduty]]

Hi Mihai,

New machine was created, dev-linux64-ec2-mtabara2 as you requested,on the new machine the cleaning was not done.
FQDN is dev-linux64-ec2-mtabara2.dev.releng.use1.mozilla.com.

Comment 4

[Mihai Tabara [:mtabara]⌚️GMT]

Machine works well and am able to play with puppet from it. Thanks again.

Comment 5

[Mihai Tabara [:mtabara]⌚️GMT]

@aobreja: found this bug in triaging. Afaik, I switched off the machines from aws console to not waste $$$. However, is there anything left to do to close this bug? Decommissioning, leaving the machine go back to the pool? Feel free to close the bug if not.

Comment 6

[Andrei Obreja [:aobreja NOT AVAILABLE][:buildduty]]

Machine was terminated and credentials removed from Ldap and Inventory.