Closed
Bug 778260
Opened 12 years ago
Closed 12 years ago
Need 4 Ubuntu 12.04 Amazon AWS VM's for B2G Jenkins instance
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jgriffin, Assigned: catlee)
Details
We need 4 new VM's for the B2G Jenkins instance. These need to be very specifically configured:
- Ubuntu 12.04, 64-bit, instance type m1.large, 50GB volume, and port 22 open in the firewall
These will be used to run tests on B2G emulators using the existing B2G jenkins instance at http://ec2-107-20-108-245.compute-1.amazonaws.com/jenkins/.
There is some additional configuration needed; it would be easiest to clone the VM I already have setup. If you give me the AWS id of your AWS account, I can create an ABI and give you access to it. Otherwise, I can start with a clean Ubuntu 12.04 image and configure manually.
These VM's do not need to live in the build network, and in fact I'd prefer they didn't. The Jenkins master we're using does not, and will need to communicate with these, and we don't want to move the Jenkins master into the build network since we'd lose public visibility (as far as I understand).
We may need to expand this pool of VM's in the future, to accomodate a greater number of tests, depending on how fast B2G panda testing comes online.
Reporter | ||
Comment 1•12 years ago
|
||
I should add that the need for these VM's will go away once B2G panda testing is in production.
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → catlee
Priority: -- → P2
Reporter | ||
Comment 2•12 years ago
|
||
I've created an AMI based on my current image, Source: 032503845367/b2g-qemu-ci-ubuntu. I've given launch permissions to the AWS_ID provided to me by catlee. Can you see if you can find this AMI (under "private images") and launch a single instance of it? I can then verify it works correctly before we launch additional instances.
Priority: P2 → --
Assignee | ||
Comment 3•12 years ago
|
||
ec2-50-112-70-10.us-west-2.compute.amazonaws.com in us-west-2 (oregon) created
Priority: -- → P2
(In reply to Jonathan Griffin (:jgriffin) from comment #1)
> I should add that the need for these VM's will go away once B2G panda
> testing is in production.
I thought these were needed on an ongoing basis in order to run emulator web api tests which cannot be run on panda boards. Is that not correct?
Reporter | ||
Comment 5•12 years ago
|
||
(In reply to Clint Talbert ( :ctalbert ) from comment #4)
> (In reply to Jonathan Griffin (:jgriffin) from comment #1)
> > I should add that the need for these VM's will go away once B2G panda
> > testing is in production.
>
> I thought these were needed on an ongoing basis in order to run emulator web
> api tests which cannot be run on panda boards. Is that not correct?
We will only need 1 VM to run ongoing WebAPI tests on emulators (unless and until we run them on buildbot); the rest of these will be used to run mochitests, etc, and will only be needed until we transition these to panda boards.
(In reply to Jonathan Griffin (:jgriffin) from comment #5)
> (In reply to Clint Talbert ( :ctalbert ) from comment #4)
> > (In reply to Jonathan Griffin (:jgriffin) from comment #1)
> > > I should add that the need for these VM's will go away once B2G panda
> > > testing is in production.
> >
> > I thought these were needed on an ongoing basis in order to run emulator web
> > api tests which cannot be run on panda boards. Is that not correct?
>
> We will only need 1 VM to run ongoing WebAPI tests on emulators (unless and
> until we run them on buildbot); the rest of these will be used to run
> mochitests, etc, and will only be needed until we transition these to panda
> boards.
Thanks for the clarification. :)
Reporter | ||
Comment 7•12 years ago
|
||
(In reply to Chris AtLee [:catlee] from comment #3)
> ec2-50-112-70-10.us-west-2.compute.amazonaws.com in us-west-2 (oregon)
> created
Thanks! This instance is working fine with CI; can you create three additional instances?
Priority: P2 → --
Assignee | ||
Comment 8•12 years ago
|
||
ec2-50-112-238-88.us-west-2.compute.amazonaws.com
ec2-50-112-78-101.us-west-2.compute.amazonaws.com
ec2-54-245-10-12.us-west-2.compute.amazonaws.com
Reporter | ||
Comment 9•12 years ago
|
||
All of these are working well, thanks!
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•