Taskcluster/Meetings/2014-01-14: Difference between revisions
< Taskcluster | Meetings
Jump to navigation
Jump to search
| Line 26: | Line 26: | ||
* [jgriffin] Bare-bones project page at [[Auto-tools/Projects/TaskCluster]] | * [jgriffin] Bare-bones project page at [[Auto-tools/Projects/TaskCluster]] | ||
* [jgriffin] Additional co-owner needed for the Worker component? | * [jgriffin] Additional co-owner needed for the Worker component? | ||
* [dminor] Maybe an owner for 'systems integration' / whole system testing? | |||
* [dminor] Can we agree upon a limited set of tags/parameters/? for matching jobs to workers for Q1? | * [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? | ** Is maybe just os, cpu sufficient for now? | ||
== Action Items == | == Action Items == | ||
Revision as of 19:50, 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
- Current implementation is in memory, changing to use a database (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)
Task Graph (owner: aki)
Treeherder Integration (owner: jeads)
Round Table
- [jgriffin] Bare-bones project page at Auto-tools/Projects/TaskCluster
- [jgriffin] Additional co-owner needed for the Worker component?
- [dminor] Maybe an owner for 'systems integration' / whole system testing?
- [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?