[PVE-User] Matching VM-id and routed IP

Alexandre DERUMIER aderumier at odiso.com
Tue Jul 25 14:31:46 CEST 2017


they are no hook script for vm stop/start,

but maybe can you try to hack

this is the script that qemu is executing when vm stop/start, or nic is hotplugged.
(I'm not sure about live migration, as you need to announce ip only when the vm is resumed on target host, and I think network script is launch before)

I'm still working on cloudinit support, where we'll be able to put ip address for qemu machine in vm config.
But for now, you can write config in /etc/pve/ if you want.

I'm interested to see if it's working fine, as in the future, I would like to test this kind of setup, to eliminate layer2 on my network.

(BTW, you can contact me directly if you want, in french ;)

----- Mail original -----
De: "Alarig Le Lay" <alarig at grifon.fr>
À: "proxmoxve" <pve-user at pve.proxmox.com>
Envoyé: Lundi 24 Juillet 2017 00:52:31
Objet: [PVE-User] Matching VM-id and routed IP


I’m wondering if there is a way to do some matching between the id of 
a VM and it’s routed IP. 

The plan is to announce the IPv4’s /32 and IPv6’s /48 of each VM running 
on an hypervisor to edge routers with iBGP or OSPF. 
Of course, a cluster will be set up, so ID will be unique in the 
cluster’s scope. 

My basic idea is to have something like dev tap101i0 
2a00:5884:8218::/48 dev tap101i0 
on the host where VM 101 is running, and doing 'redistribute kernel' 
with quagga or bird. 

If this feature is not included in promox, is it possible to use the 
pmxcfs to achieve this (by example by writing the routed IP in 
/etc/pve/nodes/${node}/priv/101-routes.conf) and having some hooks at 
the startup/shutdown that will read that file? 


pve-user mailing list 
pve-user at pve.proxmox.com 

More information about the pve-user mailing list