mirror of
https://github.com/retspen/webvirtcloud
synced 2026-11-09 11:46:49 +00:00
cf991adad5
Without a migration address libvirt sends a migrating VM to the
destination's own host name, which the source host often cannot resolve:
a live migration to a host added without one failed ("Unable to resolve
address ..."), also when the other host had one. The destination's
address on the Computes page, which the panel reaches it at, is now the
default; the migration address stays for another network. A host the
panel reaches on its loopback keeps libvirt's default.
19 lines
663 B
Python
19 lines
663 B
Python
# Generated by Django 5.2.18 on 2026-11-01 14:52
|
|
|
|
import computes.validators
|
|
from django.db import migrations, models
|
|
|
|
|
|
class Migration(migrations.Migration):
|
|
|
|
dependencies = [
|
|
('computes', '0007_gstfsd_key'),
|
|
]
|
|
|
|
operations = [
|
|
migrations.AlterField(
|
|
model_name='compute',
|
|
name='migration_address',
|
|
field=models.CharField(blank=True, default='', help_text='IP address or host name the other hosts send migrating VMs to; empty: the address the panel reaches the host at', max_length=64, validators=[computes.validators.validate_migration_address], verbose_name='migration address'),
|
|
),
|
|
]
|