Closed
Bug 702747
Opened 14 years ago
Closed 13 years ago
Set up distributed / clustered JMeter nodes in the SeaMicro cluster in PHX
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task)
Infrastructure & Operations Graveyard
WebOps: Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: stephend, Assigned: cturra)
References
()
Details
Attachments
(1 file)
|
130.56 KB,
application/pdf
|
Details |
The WebQA team has been talking with Corey + others about installing a bunch of JMeter nodes on the SeaMicro cluster in PHX (hope I got that right; Corey will correct me).
This bug is to track the _setup/configuration_work, not any actual performance/load-testing -- that'll be handled jointly with the AMO team, etc.
I've also attached a PDF guide on how to run distributed JMeter, in the hopes it makes the remote setup process smoother.
Comment 1•14 years ago
|
||
we won't be able to get this done in a "major" time frame so I'm dropping that.
Will organize dep bugs and nodes today.
Assignee: server-ops → cshields
Severity: major → normal
Comment 3•14 years ago
|
||
(In reply to Corey Shields [:cshields] from comment #1)
> Will organize dep bugs and nodes today.
That day was a wash.. stuff came up. Filing these today. :|
| Reporter | ||
Comment 4•13 years ago
|
||
Will this be usable in Q4, or Q1, more realistically? If the latter, can we investigate using a commercial service in the meantime, to augment?
Comment 5•13 years ago
|
||
(In reply to Stephen Donner [:stephend] from comment #4)
> Will this be usable in Q4, or Q1, more realistically? If the latter, can we
> investigate using a commercial service in the meantime, to augment?
heh, no, sorry, it didn't happen then.. This was a casualty of our data center move.
Will see if we can fit it in quickly.
Updated•13 years ago
|
Assignee: cshields → cturra
Component: Server Operations: Projects → Server Operations: Web Operations
| Assignee | ||
Comment 6•13 years ago
|
||
jmeter workers are in place and some testing has been done with them. we're waiting on some network routes to be put in place so we can complete basic remote testing. stay tuned for more updates soon :)
| Assignee | ||
Comment 7•13 years ago
|
||
good news! the master & workers are now in place.
:stephend - i have added you and all your direct reports that have postfix accounts and ssh keys setup to the master so they can remotely run their jmx tests. the following users have ssh access: sdonner, mbrandt, zcampbell, retornam and kraj. if ajalgaonkar and rbillings need access, we'll need ssh keys from them for their ldap accounts.
now onto the good stuff! you can access the jmeter master (client) at: master.jmeter.dmz.phx1.mozilla.com. and to run a test...
1. upload your jmeter test (jmx) to the jmeter master. you can do this by secure copying (scp) the the jmx to your home directly.
$ scp my_awesome_test.jmx master.jmeter.dmz.phx1.mozilla.com:
2. login to the jmeter master and run the test you uploaded in step 1.
$ ssh -A master.jmeter.dmz.phx1.mozilla.com
$ jmeter -n -t my_awesome_test.jmx -l my_awesome_test.log -R worker1,worker2,worker3,worker4,worker5
3. profit++
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Updated•6 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•