Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Jira Legacy
serverJIRA (pbspro.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId32008a99-7831-3ff8-9638-3db0cd01164d
keyPP-663
Jira Legacy
serverJIRA (pbspro.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId32008a99-7831-3ff8-9638-3db0cd01164d
keyPP-703

Interface 1: A new CLI pbs_ralter.

  1. Visibility - Public
  2. Change Control - Stable
  3. Synopsis - A new command that will be used for altering reservation attributes.
  4. Details - 
    1. The pbs_ralter command will be used to alter an already submitted advance or standing reservation.
    2. In particular, it can be used to change the start time, end time, mail points, mail_list and the reservation's name.
    3. This command can be used to change an advance reservation or the next/current instance of a standing reservation.
    4. After the change is requested, the change is either confirmed or denied.
    5. On denial of the change, the reservation is left as is.
    6. If the user changes only one of the times (start time or end time) of the reservation, the duration of the reservation will change.
    7. This command can be used by the owner of the reservation or the admin to alter any reservation.
    8. If the reservation has not started and if it cannot be reconfirmed on the same nodes, PBS will attempt to look for another set of nodes before denying the request.
    9. Following options will be supported:
      1. Start time modifier: '-R' <start_time>

        1. Specifies reservation's new start time.

        2. This option can be used only when the reservation is not running or is empty i.e. no jobs are submitted to the reservation.

        3. If the change is allowed, reservation will start at the new time specified with this option to pbs_ralter.

        4. The specifications of providing the time are same as pbs_rsub.

      2. End time modifier: '-E' <end_time>

        1. Specifies reservation's new end time.

        2. This option can be used even when the reservation is running and has jobs that are submitted to the reservation.

        3. If the change is confirmed, reservation will end at the new time specified with this option to pbs_ralter.

        4. The specifications of providing the time are same as pbs_rsub.

      3. Interactive option: '-I' <+block_time>.

        1. Specifies interactive mode.

        2. The pbs_ralter command will block, up to <block_time> seconds, while waiting for the reservation's change request to be confirmed.

        3. <block_time> should be positive.

        4. If the change is allowed, pbs_ralter returns with the status “CONFIRMED”, otherwise it returns with the status “UNCONFIRMED”.

        5. Format: Integer.

        6. Default: Not interactive.

      4. -m <mail_points> 

        1. Works same as pbs_rsub. 

      5. -N reservation_name

        1. Works same as pbs_rsub.

      6. -M mail_list

        1. Works same as pbs_rsub.

...

  1. Visibility - Public
  2. Change Control - Stable
  3. Synopsis - The 'Y' accounting record does not have any useful information, so it needs to be improved.
  4. Details - .
    1. When an advance reservation request is confirmed for the first time, 'Y' record will have the format: "Y; <resvID> requestor=Scheduler@<server> start=<requested start time> end=<requested end time> nodes=(<allotted nodes>)".
      1. example - "Y; R123.server requestor=Scheduler@svr start=1497264531 end=1497264651 nodes=(node1:ncpus=3)"
    2. When a standing reservation request is confirmed for the first time, 'Y' record will have the format: "Y; <resvID> requestor=Scheduler@<server> start=<requested start time> end=<requested end time> nodes=(<allotted nodes>) count=<count>". The nodes field will be specific for the first instance.
      1. example - "Y; R123.server requestor=Scheduler@svr start=1497264531 end=1497264651 nodes=(node1:ncpus=3) count=3"
    3. This record will be written when an advance reservation alter request is confirmed. The log will have the same format as in point 'a' above, but the requested field(s) will be updated with new value(s): "Y; <resvID> requestor=Scheduler@<server> start=<(new/original) start time> end=<(new/original) end time> nodes=(<allotted nodes>)".
      1. example - "Y; R123.server requestor=root@hostname start=1497264471 end=1497264651 nodes=(node1:ncpus=3)"
    4. This record will be written when a standing reservation alter request is confirmed. The log will have the same format as in point 'b' above, but the requested field(s) will be updated with the new value(s) and index of the next instance will be appended. The nodes field will be specific for the instance altered: "Y; <resvID> requestor=Scheduler@<server> start=<(new/original) start time> end=<(new/original) end time>  nodes=(<allotted nodes>) count=<count> index=<index of the altered instance>".
      1. example - "Y; R123.server requestor=root@hostname start=1497264471 end=1497264651 nodes=(node1:ncpus=3) count=3 index=1"

Interface 9: A  Improvement to the 'U' accounting log.

  1. Visibility - Public
  2. Change Control - Stable
  3. Synopsis - The 'U' accounting record will now have recurrence rule and timezone information for a standing reservation. 'U' record for advance reservation remains unchanged.
  4. Details - .
    1. When a standing reservation is submitted, the 'U' record will now have the format: "U;S56.d_server;requestor=pbsuser@d_server recurrence_rrule=FREQ=HOURLY;COUNT=2 timezone=Asia/Kolkata".
      1. example - "U;S56.d_server;requestor=pbsuser@d_server recurrence_rrule=FREQ=HOURLY;COUNT=2 timezone=Asia/Kolkata"

Interface 10: A new server log denoting that a reservation alter is being attempted.

  1. Visibility - Public
  2. Change Control - Stable
  3. Synopsis - Event type - Reservation, log level - Info.
  4. Details - When a reservation alter is being requested, the PBS server attempts to get a confirmation from the PBS scheduler.
    1. If only start time is being changed, this log will have the format: "Resv;<ResvID>;Attempting to modify reservation start=<requested start time>".
      1. example: "Attempting to modify reservation <resvID> start=1497264471"
    2. If only end time is being changed, this log will have the format: "Resv;<ResvID>;Attempting to modify reservation end=<requested end time>".
      1. example: "Attempting to modify reservation <resvID> end=1497264711"
    3. If both times are being changed, this log will have the format: "Resv;<ResvID>;Attempting to modify reservation start=<requested start time> end=<requested end time>".
      1. example: "Attempting to modify reservation <resvID> start=1497264471 end=1497264711"

Interface 10 11: A new server log denoting that a reservation alter request is denied/confirmed.

  1. Visibility - Public
  2. Change Control - Stable
  3. Synopsis - Event type - Reservation, log level - Info.
  4. Details - 
    1. When a reservation alter request is rejected, server logs this event.
      1. This log will have the format: "Resv;<ResvID>;Reservation alter denied.".
    2. When a reservation alter request is confirmed, server logs this event.
      1. This log will have the format: "Resv;<ResvID>;Reservation alter confirmed.".

Interface 11 12: A new server log providing information on a newly submitted reservation.

  1. Visibility - Public
  2. Change Control - Stable
  3. Synopsis - Event type - Reservation, log level - Info.
  4. Details - 
    1. When an advance reservation is submitted, server logs this event.
      1. This log will have the format: "Resv;<ResvID>;New reservation submitted start=<requested start time> end=<requested end time>".
    2. When a standing reservation is submitted, server logs this event.
      1. This log will have the format: "Resv;<ResvID>;New reservation submitted start=<requested start time> end=<requested end time> recurrence_rrule=<rrule> timezone=<timezone>".

Interface 12 13: A new server log when a reservation is confirmed/denied.

  1. Visibility - Public
  2. Change Control - Stable
  3. Synopsis - Event type - Reservation, log level - Info.
  4. Details - 
    1. When an advance reservation is confirmed, server logs this event.
      1. This log will have the format: "Resv;<ResvID>;Reservation confirmed.".
    2. When a standing reservation is confirmed, server logs this event.
      1. This log will have the format: "Resv;<ResvID>;Reservation denied.".

Interface 13 14: A new PBS IFL API for modifying a reservation.

...