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
..
0001_initial.py	Python3 & Django 2.2 Migration - Fix & Updates	2020-03-16 16:59:45 +03:00
0002_auto_20200529_1320.py	Reworked some computes forms and views	2020-05-29 19:25:36 +06:00
0003_auto_20200615_0637.py	Added missing migrations	2020-06-15 12:38:44 +06:00
0004_compute_migration_address.py	feat(computes): a compute names the address migrations reach it on	2026-10-06 15:05:40 +03:00
__init__.py	Initial commit	2015-02-27 10:53:51 +02:00