...
- New functional tests for resv_begin hook events.
- New PBS batch request event "rq_resresvbegin" to enable hook processing.
- New event type:
HOOK_EVENT_RESV_BEGIN - A new batch request to allow for hook handling, the PBS_BATCH_BeginResv dummy request, has been added.
- A call to process_hooks() has been added to Time4resv.
- This hook reuses the reservation information structure that resv_end uses. No new data is being added at this time.
- This hook will run from the server when the server processes the reservation beginning. This will not be affected by the scheduler starting the reservation in it's own internal loop.
- This hook runs after the scheduler has been informed of the reservation that is beginning and occurs immediately after an email may be sent to the owner and the B-accounting record is written.
RESV_CONFIRM
- New functional tests for resv_confirm hook events.
- New event type:
HOOK_EVENT_RESV_CONFIRM - process_hooks has been extended to run resv_confirm hooks when run with the PBS_BATCH_ConfirmResv event.
- This hook reuses the reservation information structure that resv_end uses. No new data is being added at this time.
- A handler for HOOK_EVENT_RESV_CONFIRM has been added to _pbs_python_event_set to retrieve data from the correct reservation id as the event passed to process_hooks is a rq_runjob structure and not an rq_manage structure with the correct data, unlike the handler for resv_begin and resv_end events.
- A call to process_hooks() has been added to req_confirmresv.
- This hook runs whenever a reservation has been confirmed and a Y-accounting record would have been written. This should run on every confirmation and re-confirmation of a reservation.
...