Please loan jgriffin an ubuntu64 AWS VM with g2.2xlarge instance type

RESOLVED FIXED

Status

Release Engineering
Loan Requests
RESOLVED FIXED
3 years ago
2 years ago

People

(Reporter: jgriffin, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
I'll verify whether the media mochitests on a B2G emulator can be run successfully in this environment.

Updated

3 years ago
Assignee: nobody → sbruno

Updated

3 years ago
Assignee: sbruno → pmoore
(Reporter)

Comment 1

3 years ago
Coop, any chance you could handle this while pmoore is PTO?
Flags: needinfo?(coop)

Comment 2

3 years ago
jgriffin: sorry for the delay here. If someone assigns a loan request bug to themselves, it drops out of the buildduty queue and we don't see it.

I'll get this set up for you tonight.
Flags: needinfo?(coop)

Updated

3 years ago
Assignee: pmoore → nobody

Comment 3

3 years ago
Looking at this more closely, our current tst-linux64-spot instances are all para-virtualized (PV) instead of hardware virtualized (HVM). The g2.2xlarge instance type is only available with HVM nodes. I've found scripts to convert HVM->PV, but not the other way around. This could explain why this loan didn't get resolved immediately before.

I've cc-ed Rail as our resident AWS expert to see whether we need to create a new AMI here from scratch, or whether we can use the existing process and simply convert some how.

See also: https://bugzilla.mozilla.org/show_bug.cgi?id=1053800
Flags: needinfo?(rail)
See Also: → bug 1053800
There is no straight forward way to reuse or convert PV to HVM. The major differences are how they boot and the partitioning.

Let me look and figure out what's left to make bug 1053800 happen.
Depends on: 1053800
Flags: needinfo?(rail)

Updated

3 years ago
Assignee: nobody → coop

Comment 5

3 years ago
Setting this up now.
Status: NEW → ASSIGNED

Comment 6

3 years ago
Email sent to :jgriffin for further instructions. 

Loaning slaves: 
- tst-linux64-hvm-ec2-jgriffin

Hi Jonathan, 

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 really fast turnaround, ping #releng (look for nick with 'buildduty')
Assignee: coop → jgriffin
(Reporter)

Comment 7

3 years ago
You can stop this instance for now, but let's not destroy it until bug 1090612 is done, in case we need it again.

Comment 8

3 years ago
(In reply to Jonathan Griffin (:jgriffin) from comment #7)
> You can stop this instance for now, but let's not destroy it until bug
> 1090612 is done, in case we need it again.

OK, I've stopped it.

Comment 9

2 years ago
It's 2015, so I'd like to check-in to see if you still need your loaned slave.

If yes, great, just let buildduty know when you are done.

If you no longer need the slave, comment here and then un-assign yourself from the bug. buildduty will take care of it from there.
(Reporter)

Comment 10

2 years ago
I think you can destroy the slave.  I had been keeping it around (but inactive) in case it was useful for bug 1090612, but it doesn't look like that's a big priority right now.
Assignee: jgriffin → nobody
OK, thanks Jonathan. I've terminated the instance.
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.