Derek Higgins 97399e9bb1 Set the dhclient timeout to match DIB_DHCP_TIMEOUT ... On initial boot when networking is brought up by cloud-init this is the timeout that dhclient adheres to. Centos configures "timeout 300" (for an EC2 bug) in their cloud image, which results in a 5 minutes delay to boot in cases where no dhcp available (e.g. IPv6 SLAAC). To reduce this boot delay and to provide consistency with places where we have set other dhcp timeouts set this to DIB_DHCP_TIMEOUT. Change-Id: I119a002070501c3dfe7c6730b07ee25f422b85b0 Related-Bug: #1758324		2018-04-05 14:29:22 +01:00
..
block_device	Fix default partition type	2018-03-22 10:10:47 +11:00
elements	Set the dhclient timeout to match DIB_DHCP_TIMEOUT	2018-04-05 14:29:22 +01:00
lib	Restore tracing on exit points of block_device_create_config_file	2018-04-03 14:33:09 +10:00
tests	Fail if two elements provide the same thing	2018-02-23 10:04:26 +11:00
__init__.py	Bump hacking to 0.9.x series	2014-07-21 10:15:41 +02:00
disk_image_create.py	squash-package-install to use the correct python	2017-03-13 20:24:39 +11:00
element_dependencies.py	Fail if two elements provide the same thing	2018-02-23 10:04:26 +11:00
logging_config.py	Add timestamp output filter	2017-06-16 15:58:50 +10:00
paths.py	Move diskimage-image-create to an entry point	2016-11-02 05:12:11 +00:00
version.py	Create docs site containing element READMEs	2015-02-10 11:45:35 -08:00