Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
1,529
edits
m (Callek moved page TaskCluster/Meetings/2014-01-14 to Taskcluster/Meetings/2014-01-14: Pinged directly by :dustin to do this) |
|||
(7 intermediate revisions by 3 users not shown) | |||
Line 15: | Line 15: | ||
=== Provisioner (owner: jonas) === | === Provisioner (owner: jonas) === | ||
* jonas rewriting in node | |||
=== Worker (owner: lightsofapollo) === | === Worker (owner: lightsofapollo) === | ||
Line 26: | Line 28: | ||
* [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? | ||
** ted and jonas to help out here | |||
* [dminor] Maybe an owner for 'systems integration' / whole system testing? | * [dminor] Maybe an owner for 'systems integration' / whole system testing? | ||
** ted to own this | |||
* [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? | ||
** Something simple, maybe just AMI initially (or URL for a docker image), until we can explore the problem space a bit more | |||
* [jmaher] - are all parameters required for the json object coming into the job queue? | |||
** No, many of them are optional | |||
* [jgriffin] - For prototyping, we can use Pulse for any AMQP needs; we may switch out later to cloudamqp or other service | |||
== Action Items == | == Action Items == | ||
* [dustin] to discuss deployment strategies (heroku vs internal?) with lightsofapollo and other module owners | |||
* [jgriffin] to find a different meeting time for next week |
edits