A new reservation confirmation hook event shall be introduced when the reservation(standing or advanced or degraded) gets confirmation from the scheduler.
The hook shall be able to reject or accept the confirmation of the reservation.
Usecases :
Admin shall be able to read the reservation attributes and server attributes by enabling and importing the hook at this event.
Admin shall be able to use the reservation attributes and invoke external API's. On the basis of the results returned from the API, the hook can accept or reject the confirmation request.
Admin can use this hook event to accept or reject the reservation confirmation.
Reservation end hook event
Requirements :
A new reservation end hook event shall be introduced when a confirmed/running reservation(standing or advanced) ends successfully or there is a user request for deleting either of the same.
Usecases:
Admin shall be able to read the reservation attributes and server attributes by enabling and importing a hook at this event.
Admin shall be able to to use the reservation attributes in real time.
End job hook event
Requirements :
A new end job hook event shall be introduced when the job ends(successfully or failed) or there is a user request for deleting the same.
Usecases:
Admin shall be able to read the job, server, node and queue attributes by enabling and importing a hook at this event.
Admin shall be able to use the job attributes in real time.
Considering allocation management, admin shall be able to run the endjob hook event regardless of whether the job started.