Now, you could repartition the cluster nodes between a "normal" partition and a "testing" partition, but for most pbs/maui clusters (which don't have anything but the 'ALL' partition set), this involves changing configuration for all the nodes, rather than simply the nodes we care about. (And then changing it back when you're finished.)
You might also consider doing this with reservations - indeed, the maui manual suggests that a reservation locked to a user specified with an & prefix will force precisely the behaviour we want - locking the reservation and the user together. This appears not to work under empirical testing.
Instead, the solution we've found to work is (all in
- Create a reservation for the user only.
SRCFG[ssdnodes] STARTTIME=00:00:00 ENDTIME=24:00:00
- Create a quality of service class with the property that it only runs on that reservation.
- Make the user a member of that quality of service class only.
USERCFG[ssp001] QDEF=ssd QLIST=ssd
(In this case, the configuration mutually restricts the user
ssp001and the nodes
node309to each other.)
This has the benefit that it also generalises to any number of users, as long as you add them to the reservation and the QoS class.