Auto-tools/Projects/WebRTC Cloud Automation: Difference between revisions

Line 1: Line 1:
This is our project page for the WebRTC/Services Automation system that we're building in the cloud. Our first target is to build something in AWS and then to build out into hardware since we can't test everything we'd like to test in AWS. However, we should be able to use the same configuration, tests, and set-up for both types of testing.
This is our project page for the WebRTC/Services Automation system that we're building in the cloud. Our first target is to build something in AWS and then to build out into hardware since we can't test everything we'd like to test in AWS. However, we should be able to use the same configuration, tests, and set-up for both types of testing.


=== Design ===
== Design ==
Coming....
=== Phase 1 ===
* Prototype system in AWS, using VPC, NAT, TURN and STUN servers
* Create test runner (ted)
* Create execution environment on client (dminor)
* Define test format, get test running (adam)
** Support both C++ as well as web page tests?
* ''Milestone 1'': test runner + tests coordinating, running tests on separate machines
 
=== Phase 2 ===
* Automatically being able to specify a network configuration in the test and create/remove components before test
** Perhaps borrow from Releng's existing items:
*** RelEng is using Boto to communicate with AWS instances (https://github.com/boto/boto)
*** Start script: http://hg.mozilla.org/build/cloud-tools/file/5e627ea3e624/aws/aws_watch_pending.py
*** Stop script: http://hg.mozilla.org/build/cloud-tools/file/5e627ea3e624/aws/aws_stop_idle.py
*** Rail says Boto is working well for them, other than the fact it is a synchronous interface


=== Meetings ===
=== Meetings ===
Confirmed users
3,816

edits