Use brsvmod to shift, extend or reduce the time window horizontally; grow or shrink the size vertically.
Use brsvmod to add hosts and slots on hosts into the original advance 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 is, slots that are not already reserved by other reservations. You must specify -n along with -m or -R. The -m option can be used alone if there is no host group specified in the list. You cannot specify -R without -n.
The specified slot number must be less than or equal to the available number of job slots for the host.
You can only add hosts (-m) to a system reservation. You cannot add slots (-n) to a system reservation.
brsvadd -n 1024 -m "hostA hostB" -g groupA -t "3:0:0-3:3:0"Reservation "groupA#0" is created
brsvsRSVID TYPE USER NCPUS RSV_HOSTS TIME_WINDOWgroupA#0 user groupA 0/1024 hostA:0/256 3:3:0-3:3:0 *hostB:0/768
Use brsvmod rmhost to remove 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 the host. Removing a host without -n releases all reserved slots on the host. The slot specification must be less than or equal to the actual reserved slot number of the host.
brsvmod rmhost -n 2 -m "hostA" system#1
brsvsRSVID TYPE USER NCPUS RSV_HOSTS TIME_WINDOWuser1_1 user user1 3/4 hostA:2/2 1/24/12/2-1/24/13/0hostB:1/2
Use brsvmod disable to disable specified periods, or instances, of a recurring advance reservation.
Recurring reservations may repeat either on a daily cycle or a weekly cycle. For daily reservations, the instances of the reservation that occur on disabled days will be inactive. Jobs using the reservation are not dispatched during on those disabled days. Other reservations are permitted to use slots of the reservation on those days. For overnight reservations (active from 11 p.m. to 9 a.m. daily), if the reservation is disabled on the starting day of an instance, the reservation is disabled for the whole of that instance.
For a weekly reservation, if the reservation is disabled on the start date of an instance of the reservation then the reservation is disabled for the entire instance. For example, for a weekly reservation with time window from 9 a.m. Wednesday to 10 p.m. Friday, in one particular week, the reservation is disabled on Thursday, then the instance of the reservation remains active for that week. However, if the same reservation is disabled for the Wednesday of the week, then the reservation is disabled for the week.
Once a reservation is disabled for a period, it cannot be enabled again; 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.
Reservation "user1#0" is createdbrsvadd -n 4 -m hostA -u user1 -t "6:0-8:0"
Use brsvmod -u to change the user or brsvmod -g to change the user group that is able to submit jobs with the advance reservation.
Jobs submitted by the original user or user group to the reservation still belong to the reservation and scheduled as advance reservation jobs, but new submitted jobs from the removed user or user group cannot use the reservation any longer.
An advance reservation job dispatched with brun is still subject to run windows and suspending conditions of the advance reservation for the job. The job must finish running before the time window of a closed reservation expires. Extending or shrinking a closed advance reservation duration prolongs or shortens lifetime of a brun job.
bslots displays a snapshot of the slots currently not in use by parallel jobs or advance reservations. If the hosts or duration of an advance reservation is modified, bslots recalculates and displays the available slots and available run time accordingly.
Where: "Yes" means the modification is supported; otherwise, "No" is marked. For example, all modifications are acceptable in the case that the advance reservation is inactive (and not disabled).