modifies an advance reservation
Replaces advance reservation option values previously created, extends or reduces the reservation time window, or adds or removes reserved hosts of the advance reservation specified by reservation_ID. For a recurring reservation, can disable specified occurrences of the reservation.
Administrators and root can modify any reservations. Users listed in the ResourceReservation section of lsb.resources, can only modify reservations they created themselves.
The original value for user, user group, or time window, can be overridden with a new value by specifying the option as in brsvadd. Change a reservation from closed (the default) to open with the -o option, or from open to closed with the -on option.
Options -n, -m, and -R must be used with the subcommands addhost or rmhost. These options allow adding or removing from the original values.
The -td and -tn options are only allowed in disable subcommand.
All three subcommands are mutually exclusive. The time window options -b, -e and -t are not valid in any of the subcommands.
You cannot modify the start time of an active reservation.
brsvmod does not support the reservation_ID@cluster_name notation for advance reservations on remote clusters, or the user_name@cluster_name notation for reservations with remote users.
-n 3 -m "host1 host2"
3 slots are required. LSF tries to find as many slots as possible from host1. If 3 slots are not available on host1, then LSF tries to find the rest from host2. Hosts with no slots available are removed from the list when the request is handled.
Adds hosts and slots on hosts into the original reservation allocation. The hosts can be local to the cluster or hosts leased from remote clusters.
Adding a host without -n reserves all available slots on the host that are not already reserved by other reservations. You can specify the number of slots to be added from the host list specified with -n, but -n cannot be used alone. -m can be used alone if no host group is specified in the list. You cannot specify -R without with -n.
The specified slot number must be less than or equal to the available number of slots for the hosts.
Only hosts can be added (-m) to a system reservation. Slots cannot be added (-n) to a system reservation.
The start date must be the same as or earlier than the end date.
If a reservation is disabled for a given day, then it does not become active on that day, and remains inactive for the duration of the reservation time window. Non-recurring reservations are able to use slots of the recurring reservation for the duration of the time window.The -tn option is a shortcut that disables a reservation on the starting day of the next instance of the reservation time window; that is, the instance that starts nearest in the future. If the reservation has already been disabled for this day, the modification request is rejected.
For example, for a weekly reservation with time window from Wednesday 9 a.m. to Friday 10 p.m, if the current day is Monday, then running the command with the -tn option disables the reservation from Wednesday to Friday of the current week. However, if the current day is Thursday, then the reservation is disabled from Wednesday to Friday of the following week. If it is Wednesday, then whether to disable in the current week or following week depends on whether or not the start time of the instance has passed: if not then the reservation is disabled in the current week, otherwise the following week’s reservation is disabled.
Running the disable command with the -tn option twice on Monday tries to disable twice in the current week. The second run has no effect, but is rejected because the specified reservation instance is already disabled.
Once a reservation is disabled for a period, it cannot be enabled; that is, the disabled periods remain fixed. Before a reservation is disabled, you are prompted to confirm whether to continue disabling the reservation. Use the -f option to silently force the command to run without prompting for confirmation; for example, to allow for automating disabling reservations from a script.
Removes hosts or slots on hosts from the original reservation allocation. You must specify either -n or -m. Use -n to specify the number of slots to be released from reserved hosts. Removing a host without -n releases all reserved free slots on the host. The new slot specification must be less than or equal to the actual reserved slot number of the host.
You can only remove a whole host from a system AR.
How many slots or hosts can be removed depends on the number of slots that are free as long as the reservation is active. rmhost cannot remove more slots than are free on the host. This applies to removing hosts on both one-time and recurring reservations that are active. If you want to remove more slots from the reservation, you must wait until running jobs finish or the reservation is inactive.
Changes a closed advance reservation to open, or cancels an open reservation.
Changes the type of a reservation to be open or closed. If the reservation is open, all jobs in the reservation become normal jobs, not subject to termination when the reservation window closes. -on closes the reservation when it expires.The running jobs of an open reservation are terminated when the reservation is changed into closed. The termination times of running jobs of a closed reservation are removed if the reservation is changed to open. The termination time of running jobs is set by mbatchd but checked by sbatchd. Termination time is an absolute time based on master host, so all hosts in the cluster should be synchronized with the local time on the master host. If sbatchd and mbatchd are not synchronized, termination may not occur at the correct time.
Replaces the begin time for a one-time reservation, or gives an offset in minutes to the current begin time.
You must specify at least hour:minute. Year, month, and day are optional. Three fields are assumed to be day:hour:minute, four fields are assumed to be month:day:hour:minute, and five fields are year:month:day:hour:minute.
If you do not specify a day, LSF assumes the current day. If you do not specify a month, LSF assumes the current month. If you specify a year, you must specify a month.
The offset is in minutes, an integer with a prefix+ or -. For example, -b+5 moves the begin time 5 minutes later, and -b-5 moves the begin time 5 minutes earlier.
The modified time value for -b must use the same syntax as the time value for -e. It must be earlier than the time value for -e, and cannot be earlier than the current time.
Replaces or sets a description for the reservation. The description must be provided as a double quoted text string. The maximum length is 512 characters.
Replaces the end time for a one-time reservation, or gives an offset in minutes to the current end time.
By giving a positive offset to the end time, you extend the duration of a reservation so that the jobs in the reservation can run longer. Shrinking the reservation with a negative value terminates running jobs earlier.
You must specify at least hour:minute. Year, month, and day are optional. Three fields are assumed to be day:hour:minute, four fields are assumed to be month:day:hour:minute, and five fields are year:month:day:hour:minute.
If you do not specify a day, LSF assumes the current day. If you do not specify a month, LSF assumes the current month. If you specify a year, you must specify a month.
The time value for -e must use the same syntax as the time value for -b. It must be later than the time value for -b.
Changes the user group that is able to submit jobs to the reservation. Changing the user group does not affect the currently running jobs.
Jobs submitted by the original user group to the reservation still belong to the reservation and scheduled as advance reservation jobs, but newly submitted jobs from a user group that has been removed from the reservation cannot use the reservation any longer.
The -g group_name option does not support the @cluster notation for advance reservations on remote clusters.
Changes the list of hosts for which job slots specified with -n are reserved. At job submission, LSF considers the hosts in the specified order.
If you also specify a resource requirement string with the -R option, -m is optional.
The hosts can be local to the cluster or hosts leased from remote clusters.
Changes the number of job slots to reserve. job_slots must be less than or equal to the actual number of slots for the hosts selected by -m or -R for the reservation.
If you also specify the reservation for system use with the -s option, -n is optional.
Changes the host selection for the reservation according to the specified resource requirements. Only hosts that satisfy the resource requirement expression are reserved. -R accepts any valid resource requirement string, but only the select string takes effect.
If you also specify a host list with the -m option, -R is optional.
For more information about resource requirements, see Administering Platform LSF.
The size of the resource requirement string is limited to 512 bytes.
Replaces the time window with a new one to shift a recurring reservation. You cannot modify the start time of a recurring reservation that has current active instance.
time_window = begin_time-end_time
The default value for minute is 0 (on the hour); the default value for day is every day of the week.
You must specify at least the hour. Day of the week and minute are optional. Both the start time and end time values must use the same syntax. If you do not specify a minute, LSF assumes the first minute of the hour (:00). If you do not specify a day, LSF assumes every day of the week. If you do specify the day, you must also specify the minute.
LSF administrators can prevent running jobs from being killed when the reservation expires by changing the termination time of the job using the reservation (bmod -t) before the reservation window closes.
When the job starts running, the run limit of the reservation is set to the minimum of the job run limit (if specified), the queue run limit (if specified), or the duration of the time window.
Changes the user who is able to submit jobs to the reservation. Changing user does not affect the currently running jobs.
Jobs submitted by the original user to the reservation still belong to the reservation and scheduled as advance reservation jobs, but newly submitted jobs from users that have been removed from the reservation cannot use the reservation any longer.
The -u user_name option does not support the @cluster notation for advance reservations on remote clusters.