5 commits

Author	SHA1	Message	Date
catborise	13d3a16ea5	fix(instances): a clone takes a free name the form offers ... A user who is not a superuser chooses the clone's name from the free names the clone form lists, or gets the first one with automatic names, but the server took any posted name. It now refuses a name outside the list, and with automatic names it takes the first free one whatever is posted. A superuser still names a clone freely. The panel checks VM names on every compute, but a job held a name only on its compute, so two clones from VMs on two hosts could take the same free name at once; a name claim now holds the name everywhere. A clone job whose name a VM found on a host took while it was queued stops before it copies anything.	2026-10-31 00:32:39 +03:00
catborise	fbf82da5a9	feat(instances): VM clone runs as a job	2026-10-15 09:28:43 +03:00
catborise	49232c6e1d	feat(storages): volume clone runs as a job	2026-10-15 09:28:43 +03:00
catborise	68812ddbdf	refactor(computes): the lock helpers take claims instead of file locks	2026-10-14 23:27:57 +03:00
catborise	fca4a5d91c	feat(operations): admit claims atomically; redact secrets	2026-10-14 23:27:57 +03:00