TestEngineering/Services/LoopTestEnvironments

Loop Server Production Environments

• Loop-Server:
• MSISDN Gateway:

• Monitoring
  • NOTE: TBD

• QA Access: not allowed

• Pointing Fx Nightly to Production
  • NOTE: Fx Nightly is already set to point to Production by default
  • Loop-Server - TBD
  • MSISDN Gateway - TBD

Loop Server Stage Environment

• URLs
  • Loop-Server: https://loop.stage.mozaws.net
  • Loop-Client: https://call.stage.mozaws.net
  • Loop-Redis-Stage: still need the details
  • Mock: https://loop-delayed-response.stage.mozaws.net
  • MSISDN Gateway: http://msisdn.stage.mozaws.net

Loop Server Stage Details

• URL

• Versions

• AWS
  • Loop-Server
  • MSISDN Gateway
  • Shared: TBD

• Files

• Processes

• Logs

• Heka

• Setting Stage configuration:
  • Toggling the config setting to use either a mock server or a third-party server
  • File: /data/loop-server/config/settings.json

Loop Client Stage Details

• URL

• Versions

• AWS
  • Loop-Server
  • MSISDN Gateway
  • Shared: TBD

• Files

• Processes

• Logs

• Heka

Mock Server Stage Details

• URL

• Versions

• AWS
  • Loop-Server
  • MSISDN Gateway
  • Shared: TBD

• Files

• Processes

• Logs

• Heka

MSISDN Gateway Server Stage Details

• URL

• Versions

• AWS
  • Loop-Server
  • MSISDN Gateway
  • Shared: TBD

• Files

• Processes

• Logs

• Heka

QA Access via a Bastion Host

• SSH with AWS keys to the Stage bastion host in US East 1. From there SSH directly into any instance.

Stage Monitoring

• NOTE: TBD
• Sentry: https://sentry.shared.us-east-1.stage.mozaws.net

Loads Services Cluster Environment

• URLs
  • http://loads.services.mozilla.com/
  • or http://ec2-54-212-44-143.us-west-2.compute.amazonaws.com/

• Versions

Loads Cluster/Broker/Agents:
$ cd /home/ubuntu/loads/bin
$ ./loads-runner --version

• AWS in US West
  • loads-master (broker and agent processes)
  • loads-slave-1 (agent processes)
  • loads-slave-2 (agent processes)
  • NOTE: there is no stack or ELB for this cluster

• Files
  • /home/ubuntu
    • loads
    • loads-aws
    • loads-web
• Processes
  • Search for processes owned by ubuntu, loads, nginx, circus
• Logs
  • /var/log/redis
  • /var/log/nginx
• QA access
  • You need special access to be able to SSH into these devices
  • You need to make some changes to your .ssh/config file
• Monitoring
  • Web Interface: http://loads.services.mozilla.com/
  • StackDriver: https://app.stackdriver.com/groups/6664/stage-loads-cluster
• Cluster status
  • Check from any loadtest folder or loads install:

../bin/loads-runner --ping-broker --ssh=ubuntu@loads.services.mozilla.com
../bin/loads-runner --check-cluster --ssh=ubuntu@loads.services.mozilla.com
(or similar)

• Links
  • http://loads.readthedocs.org/en/latest/
  • https://github.com/mozilla-services/loads
  • https://github.com/mozilla-services/loads-aws

References

• GitHub Repos
  • https://github.com/mozilla-services/loop-server
  • https://github.com/mozilla-services/loop-client
  • https://github.com/mozilla-services/msisdn-gateway
  • https://github.com/mozilla-services/svcops
  • https://github.com/mozilla-services/puppet-config

OPs Mana and GitHub Pages

• NOTE: Talk to OPs for the links to Mana.
• Puppet Config: https://github.com/mozilla-services/puppet-config
• Cloud Formation: https://github.com/mozilla-services/svcops
• Loop-specific: TBD