cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nux! <>
Subject Re: [cloud-init] change on how DHCP leases are scanned to fetch VR address
Date Tue, 16 Jan 2018 13:56:05 GMT
Also interested as the CentOS project is about to patch their cloud-init with this:

Might as well save them the trouble and go directly for Marc's patch.

Sent from the Delta quadrant using Borg technology!


----- Original Message -----
> From: "Marc-Aurèle Brothier" <>
> To: "dev" <>
> Sent: Tuesday, 16 January, 2018 13:43:58
> Subject: [cloud-init] change on how DHCP leases are scanned to fetch VR address

> 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 ?
> Cheers,
> Marc-Aurèle

View raw message