Propagate compute server changes to students #8609
Description
At the moment the only easy change that can be done to students servers after they are created is the spend limit. But it is quite likely that the instructor will want to tune other parameters based on feedback, e.g. timeout parameters, health check commands, disk size, perhaps even the type of machine/GPU/image. The current workaround is to create a completely new server and then distribute that to the students, which may lead to confusion and is just not very straightforward/intuitive.
So it would be nice if attaching a compute server to a course in reality attached the description of the server, i.e. its "deprovisioned record" and changes to that record propagated to the students. One may want to avoid overwriting with a new configuration those student servers, that were already changed for some reason.
Possible UI representation: edit settings of the attached compute server in the same dialog as "regular compute servers". Then have an option:
- propagate changes to those students whose configuration is exactly the same as the previous configuration (i.e. to those that were not adjusted manually)
- propagate changes to ALL students, regardless of their current state
Separate confirmation:- propagate changes even if it means that student servers have to be deprovisioned (e.g. the instructor decides to move to a different region).
In principle, one could cherry-pick which changes have to be propagated, but I think this will be confusing and error-prone. Instead some settings that cannot be the same should not propagate, such as domain names or authorization tokens.