@vccardenas Thanks for reviewing the document. I've made some changes to document based on the comments I've got.
I've reworded it
I guess dynamic consumable resources aren't something that one can make available on server/queue/node objects. In that sense even if these resources are added to res_release_on_susp list it wouldn't make any difference because nothing will get released. This is probably applicable even today (without this change).
Well the resource can really be altered if there is a job busy on it. It is the same way as it works today.
The change is only about when a job is suspended. Suspension can only happen via a qsig command or using preemption.
I don't know what benefit we will get out of making two lists. And, then there will be cases where some resources don't exist in either of the lists then what do we do.
I thought about creating only a list of resources that would sustain on job when it is suspended, but I decided against it while writing this design proposal because in that case admins will have to mention all the consumable resources that they don't want to release. Some sites have hundreds of custom resource and changing the field for every new resource you add wasn't very user friendly in my opinion.