You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now we watch for DHCP leases to be assigned to the domains, so even if the VM is configured with a static IP address there's not really a way to use it without also provisioning a DHCP address. This would not be an especially important use case except for #66, which prevents a machine from restarting and having the same IP.
The text was updated successfully, but these errors were encountered:
tgross
changed the title
support static IPs
support IPs from CNI
Oct 6, 2024
Does Nomad Virt driver only support libvirt provided DHCP addresses? I'm currently facing an issue where an external DHCP server is successfully replying to the DHCP requests from Nomad managed VMs, however the task fails because Nomad is unable to determine the IP address of the VM.
It of course works via the libvirt managed bridge virbr0 which handle DNS via dnsmasq
Would it be possible to fall back to using the VM-tools commands to get the IP from the VMs? It would also be nice if we could assign static IPs to the VMs, which means there's no DHCP to intercept
Hi @ocient-cliimatta; in its current state the driver only supports IPs provided by libvirt managed DHCP. We are open to other possibilities on the networking side, but this issue is focussed on CNI integration rather than external DHCP or fallback mechanisms. Could you open a new issue to detail your feature request please?
Right now we watch for DHCP leases to be assigned to the domains, so even if the VM is configured with a static IP address there's not really a way to use it without also provisioning a DHCP address. This would not be an especially important use case except for #66, which prevents a machine from restarting and having the same IP.
The text was updated successfully, but these errors were encountered: