Attendance: Daniel, Dan, Mariusz, Roger, Peter
1. Meeting secretary for this meeting?
Peter
2. Discussion of advanced reservation idea by Mariusz: http://tinyurl.com/yhcqww6
- Comparison to SGE solution (see mail from Daniel G.) - SGE works with AR ID, proposal from Poznan relies on DRMAA2 interface concept - Lot of similarities resp. mappable concepts (e.g. start time / duration vs. start time / end time) - SGE has more of a dictionary approach - 'everything is requestable' - Restricting this through a portable 'reservation template' would be ok - Slot concept in both proposals - Configured per host, usually express number of concurrent processes - Available slots often map to core count, but ultimately it is a administrator decision - SGE has slots per queue / host / ..., depends only on configuration - Overall agreement that advanced reservation happens before job template creation - Both rely on similar resource allocation attributes (e.g. candidate hosts, OS type) - User submits advanced reservation and then submits jobs to it - Separate DRMAA AR data structure beside job template needed - needs to become part of the session persistence concept - needs to have separate nativeOptions attribute (e.g. for qrsub) - Donation of reservation to other users not widely supported, left out in DRMAA Best, Peter.