TestEngineering/Services/LoopTestEnvironments
< TestEngineering | Services
Jump to navigation
Jump to search
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
- 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.
- Monitoring
- NOTE: TBD
Loads Services Cluster Environment
- URLs
- 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
- /home/ubuntu
- 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
References
- GitHub Repos
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