cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc-Aurèle Brothier <>
Subject [cloud-init] change on how DHCP leases are scanned to fetch VR address
Date Tue, 16 Jan 2018 13:43:58 GMT
Hi all,

I pushed a PR for cloud-init to change the way the DHCP leases are scanned
to retrieve the VR ip address. Currently it does scan the lease files in
reverse time order (newest file first) to get the VR address and if that
address does not work, it falls back on the default gateway address.

My change is to scan the DHCP lease in alphabetical order of the iterface
names, retrieving all potential address from those file and iterating among
them in the same order to find the VR address, with the latest entry on the
default gateway address.
This is to overcomes issue when additional interfaces are added to the VM
which are also configured with a DHCP server which is not part of
cloudstack. In the current situtation, cloud-init would try to use the
address from that newest interface.

Does that sound like a good change to everyone? Or would it break, slow
down, your current VM boot process ?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message