Queues and projects

[sashabaranov]

It makes sense to introduce two new entities: queues and projects, both of which should be present in DB.

Each queue should have

• Name
• Scheduling policy - i.e. FIFO/balance between projects/something else

job.kind should be changed to job.queue — just a string, referencing foreign key in db.

Each project should have

• Name
• Any scheduling characteristics — number of jobs allocated or cputime allocated to project.

I'm guessing we can get away without CRUD for queues/projects for now, however rpc for getting length of queue might be useful.

[andreiSaw]

protobuf: policy= enum

[andreiSaw]

is it ok ? @sashabaranov