Creating reservation out of a job

hey @bhroam,

[root@d_server /]# qmgr -c “p q workq” | grep foo
set queue workq resources_default.foo = 5
[root@d_server /]# qsub – /bin/sleep 25320
1012.d_server
[root@d_server /]# qstat -f | grep foo
Resource_List.foo = 5
Resource_List.select = 1:foo=5:ncpus=1
schedselect = 1:foo=5:ncpus=1
[root@d_server /]# pbs_rsub --job 1012
R1013.d_server CONFIRMED
[root@d_server /]# pbs_rstat -f | grep foo
Resource_List.select = 1:foo=5:ncpus=1
schedselect = 1:foo=5:ncpus=1

[root@d_server /]#

The resource foo is not there in Resource_List.*, and any jobs that are submitted to the reservation later will not have the resource foo.
I believe we should go ahead and document this behaviour.

Thanks,
Prakash

@prakashcv13
Thanks for testing this. Did the resulting reservation queue have a resources_max.foo? If it doesn’t, I’m somewhat surprised. If I were to submit pbs_rsub -lfoo=5, the resulting reservation queue should have resources_max.foo = 5. We are creating a reservation based on the job resources. At the time we query the resources, the job has Resource_List.foo. It isn’t until after we create the reservation and move the job that it loses it. If a queue has a resources_max, a job should pick it up as a default.

Bhroam

Hi @bhroam, @scc, All,

I have updated the design to say that we will copy Resource_List.* of the job to the Resource_List.* of the reservation being created out of it.

Thanks,
Prakash

I made some slight modifications to the design document to clarify when create_resv_from_job can be set and what can set it.

Bhroam