Taskcluster/Meetings/2014-01-14: Difference between revisions
< Taskcluster | Meetings
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
** Using sqlite for Q1 | ** Using sqlite for Q1 | ||
* Writing correctness tests | * Writing correctness tests | ||
** will be useful | ** will be useful even if we end up throwing this prototype away | ||
* Stress testing | * Stress testing | ||
** Notional goal is to simulate 250000 jobs for 10 minutes | ** Notional goal is to simulate 250000 jobs for 10 minutes | ||
Revision as of 14:54, 14 January 2014
Previous Action Items
Status Updates
Job Queue (owner: dminor/ted)
- Have prototype implementation using Python 3.3
- https://github.com/dminor/taskcluster-jobqueue
- implemented REST interfaces discussed last week for Q1, but some of the JSON passed in is not fully defined yet
- Using sqlite for Q1
- Writing correctness tests
- will be useful even if we end up throwing this prototype away
- Stress testing
- Notional goal is to simulate 250000 jobs for 10 minutes
- See how far we can get with Python
Provisioner (owner: jonas)
Worker (owner: lightsofapollo)
Round Table
- [jgriffin] Bare-bones project page at Auto-tools/Projects/TaskCluster
- [jgriffin] Additional co-owner needed for the Worker component?
- [dminor] Can we agree upon a limited set of tags/parameters/? for matching jobs to workers for Q1?
- Is maybe just os, cpu sufficient for now?