6 commits

Author	SHA1	Message	Date
catborise	5a523befbd	feat(computes): a compute names the address migrations reach it on ... Migration is client-driven: libvirt sends the VM's memory to the destination's own host name unless a migration URI is given, and the app never gave one. Where the hosts cannot resolve each other's names (or the names point at a management network) every migration failed with "Unable to resolve address '<host name>' service '49152'". A compute now has an optional migration address (an IP address or a host name, no scheme or port), editable in the compute form and the API. A VM migrating to that compute is sent to tcp://<address> (bracketed for IPv6). Empty, the default for existing computes, keeps the previous behavior. The compute's host name is not reused, because for SSH computes it can be an ssh_config alias. The migration log entry names the address when one is set.	2026-10-06 15:05:40 +03:00
catborise	217e106c8b	format python code with black	2022-11-02 08:54:35 +03:00
catborise	508e3609be	lint with black python. convert f style strings to old one. some small fixes	2020-11-05 12:34:31 +03:00
Real-Gecko	1b3fd9d05e	replaced ugettext_lazy with gettext_lazy	2020-10-14 18:27:57 +06:00
catborise	e97d592e51	fix some messages, add translation for some keywords, update tr locale file	2020-06-12 14:46:17 +03:00
Real-Gecko	7103c52380	Reworked some computes forms and views	2020-05-29 19:25:36 +06:00