Closed Bug 876795 Opened 11 years ago Closed 11 years ago

Terminate 3 B2G VM's

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

Product:
Infrastructure & Operations Graveyard
Component:
CIDuty
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jgriffin, Unassigned)

Details

We no longer need the following 3 Amazon AWS VM's, which were previously used for running B2G unit tests on Jenkins:

ec2-23-23-13-8.compute-1.amazonaws.com
ec2-107-22-114-223.compute-1.amazonaws.com
ec2-23-20-232-76.compute-1.amazonaws.com 

These may all be terminated.
These are named b2g-jenkins{5,6,7} and are in us-east-1. I've stopped them for now, pending catlee looking to see if we can also remove any keys or security groups.
Found in triage.
Component: Release Engineering: Automation (General) → Release Engineering: Machine Management
QA Contact: catlee → armenzg
Product: mozilla.org → Release Engineering
Flags: needinfo?(catlee)
I don't know how to answer that question. Look through all the other instances and see what ssh keys / security groups they're using?
Flags: needinfo?(catlee)
Which keys are we talking about?
The VMs must have been terminated, I can't find them anywhere. There is a left over key and security group nothing else is using, which I've left in place.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
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.