* ReservationTemplate(): maxSlots is only supportable with PEs (parallel environments). Same for jobs, they need a PE in order to request more than 1 slot. While in the JobTemplate this is made *very* explicit, that one might need request a job category this is not mentioned in the ReservationTemplate. Therefore I propose to add
string JobCategory;
in the ReservationTemplate in order to be consistent with the multiple slots request approach. The JobCategory in the spec could be renamed to Category if needed.
this is fine with me, but lets call it ReservationCategory or Category, not JobCategory.
I also thought on ReservationCategory but this needs to add it as a different new concept in the spec and also requires new functions (for retrieving all ReservationCategories).
Since both (ReservationCategory and JobCategory) are just strings and in Univa Grid Engine for example both categories maps to the same concept (additional resource requests, which are appended). I would rather change "JobCategory" to "Category" as a generic category name for job or reservation requests.
Since this one of the rare events were Mariusz, Daniel and me (a group majority) agrees on something, I will just do it like this. Best regards, Peter.