TestEngineering/Services/FxALoadTesting: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 70: Line 70:


== Running the Loads tool against FxA Stage ==
== Running the Loads tool against FxA Stage ==
* Note: the following value can stay fixed in loadsrunner.sh.
** BROKER=broker.loads.lcip.org
* This will allow the current loads tool install to make use of the broker and agents in the Loads environment.
* The basic load test can be run as follows
$ make test SERVER_URL=https://api-accounts.stage.mozaws.net
* The full, default load test can be run as follows
$ make bench SERVER_URL=https://api-accounts.stage.mozaws.net
* Configuring the load test:


== Monitoring FxA Stage ==
== Monitoring FxA Stage ==

Revision as of 19:58, 4 February 2014

Load Test Tool Client

Creating a RHEL AWS instance

  • Pick a Region then Create Instance > Launch Instance
  • Follow the prompts to create a basic, RHEL-flavored instance
  • Use of the QA/Dev key pairs that have been set up for this:
    • US East Key Pair: QA-Dev-Share (created by jbonacci) for general use
    • US West Key Pair: QA-dev-share (created by RaFromBRC) for general use
  • Once the instance is running, log in as "ec2-user"
  • The following apps, tools, and libs will need to be installed for use with various Services applications:
    • gcc, gcc-c++
    • hg
    • git
    • python-devel
    • automake, autoconf, and libtool (required for libzmq, for easy_install)
    • pip
    • virtualenv
  • Install node/npm
  • Install zeromq 3.X
  • Install gmp, gmp-devel
  • Also, general rhel updates:
$ sudo yum -y update
and/or
$ sudo yum -y upgrade
  • Now, the instance should be ready for installing and using the Loads tool.

Creating an Ubuntu AWS instance

  • Pick a Region then Create Instance > Launch Instance
  • Follow the prompts to create a basic, Ubuntu-flavored instance
  • Use of the QA/Dev key pairs that have been set up for this:
    • US East Key Pair: QA-Dev-Share (created by jbonacci) for general use
    • US West Key Pair: QA-dev-share (created by RaFromBRC) for general use
  • Once the instance is running, log in as "ubuntu"
  • The following apps, tools, and libs will need to be installed for use with various Services applications:
    • gcc, g++
    • mercurial
    • git
    • python-setuptools, python-virtualenv, and python-dev
    • automake, autoconf, libtool
    • m4
  • Install node/npm
  • Install libzmq and zeromq 3.X
  • Install gmp-5.1.3 or newer
  • Also, general rhel updates:
$ sudo apt-get update
and/or
$ sudo apt-get upgrade
  • Now, the instance should be ready for installing and using the Loads tool.

Installing the Loads tool on the AWS instance via FxA-Auth-Server

Installation:
$ git clone https://github.com/mozilla/fxa-auth-server.git
$ cd ./fxa-auth-server
$ npm install
$ node ./scripts/gen_keys.js
$ npm test
$ cd ./loadtest
$ make build
  • Note: This will install a local copy of the Loads tool for use with FxA-Auth-Server.

Running the Loads tool against FxA Stage

  • Note: the following value can stay fixed in loadsrunner.sh.
    • BROKER=broker.loads.lcip.org
  • This will allow the current loads tool install to make use of the broker and agents in the Loads environment.
  • The basic load test can be run as follows
$ make test SERVER_URL=https://api-accounts.stage.mozaws.net
  • The full, default load test can be run as follows
$ make bench SERVER_URL=https://api-accounts.stage.mozaws.net
  • Configuring the load test:

Monitoring FxA Stage