Bucket tasks per project; add tags to TaskRequest.

[GoogleCodeExporter]

To get accountability, we currently have --user. This is not sufficient.

We need tags, basically assigning arbitrary values to the tasks so it is easier 
to search for them.

Action items:

- New entity property to store this new data:
https://code.google.com/p/swarming/source/browse/services/swarming/server/task_r
equest.py#221
tags = ndb.StringProperty(repeated=True)

- New swarming.py client code to accept tags at CLI, e.g.
https://code.google.com/p/swarming/source/browse/swarming.py?repo=client#872
parser..add_option('--tag', action='append', default=[]

- New swarming client API to accept this value. Likely blocked on issue 118.

- New task presentation to show these tags
https://code.google.com/p/swarming/source/browse/services/swarming/templates/use
r_task.html

- New search functionality to search for tasks with a tag
https://code.google.com/p/swarming/source/browse/services/swarming/templates/use
r_tasks.html
https://code.google.com/p/swarming/source/browse/services/swarming/handlers_fron
tend.py#380

Original issue reported on code.google.com by maruel@chromium.org on 6 Aug 2014 at 4:12

• Blocking: #144, #149

[GoogleCodeExporter]

Original comment by maruel@chromium.org on 6 Aug 2014 at 4:15

[GoogleCodeExporter]

Original comment by maruel@chromium.org on 6 Aug 2014 at 4:21

[GoogleCodeExporter]

we should also add tag for project, i.e. chromium, QO etc...

Original comment by jam@chromium.org on 7 Aug 2014 at 3:10

[GoogleCodeExporter]

jam@ - I think what you really want is a resource economy?

Original comment by kmg@chromium.org on 7 Aug 2014 at 3:17

[GoogleCodeExporter]

yes, chrome infra is perpetually reinventing internal Google best practices 
because we can't reuse it :)

Original comment by jabdelmalek@google.com on 7 Aug 2014 at 3:22

[GoogleCodeExporter]

Original comment by maruel@chromium.org on 15 Aug 2014 at 4:24

• Now blocking: #144

[GoogleCodeExporter]

I'd like to work on that if you don't mind. I'll also slap ACLs to tags. Each 
tag may have a list of groups that can read it, and a list of groups that can 
set it.

Swarming task is visible in UI for current user if all its tags are readable by 
current user.

Wdyt?

Original comment by vadimsh@chromium.org on 25 Aug 2014 at 6:30

• Changed state: Accepted

[GoogleCodeExporter]

Fine with me! As long as performance wise it's doing well.

The main problem I foresee is /user/tasks. As long as you have an idea how to 
handle this plus the list of tasks in /restricted/bots/<bot>, it's fine with me.

Original comment by maruel@chromium.org on 26 Aug 2014 at 2:06

[GoogleCodeExporter]

Original comment by maruel@chromium.org on 27 Aug 2014 at 2:04

• Now blocking: #149

[GoogleCodeExporter]

Original comment by maruel@chromium.org on 30 Oct 2014 at 12:02

• Changed state: Fixed