Page Comparison

...

1.  It shall be possible to move the start time of a reservation.

   1. It shall be possible to push the start time into the future.

      1. The request should be allowed if the reservation is empty.
      2. The request should be allowed if the reservation has not already started.

   2. It shall be possible to move the start time of a confirmed reservation sooner if resources are available.

      1. If the new start time would interfere with an existing high priority calendared event (i.e. another reservation or dedicated time), PBS should try to reconfirm the reservation on another set of nodes (vnodes). If that is not possible, the request shall fail.

2. For an already running reservation it shall be possible to extend the end time of a reservation.

   1. If the new end time would interfere with an existing high priority calendared event (i.e. another reservation or dedicated time) the request shall fail.

3. For a reservation that has not started, it shall be possible to extend the end time of a reservation.
   1. If the new end time would interfere with an existing high priority calendared event (i.e. another reservation or dedicated time), PBS should try to reconfirm the reservation on another set of nodes (vnodes). If that is not possible, the request shall fail.
4. It shall be possible to move the end time of a reservation so that it ends sooner.
5. A new CLI viz. pbs_ralter to be provided so alter the reservation.

6. The new capabilities should be applicable on advance reservations.

7. The new capabilities should be applicable on standing reservations.

   1. The instances of the standing reservation that need to be modifiable are the current and next one.

   2. If the requested times cause an overlap of shadowing of a later instance of the standing reservation being modified, the request will be denied.
8. A scheduling cycle should also be triggered by the end of an advance reservation.

...