summaryrefslogtreecommitdiff
path: root/cloudinit/url_helper.py
diff options
context:
space:
mode:
authorScott Moser <smoser@ubuntu.com>2014-02-13 12:13:42 -0500
committerScott Moser <smoser@ubuntu.com>2014-02-13 12:13:42 -0500
commit87d0fa867f27f101e93006ba8dc8a395098e8df1 (patch)
tree39a81a1f9b5074fbbb681b738e13ae4c1a8238f8 /cloudinit/url_helper.py
parentf82e9552145ff468763727d7e5a53f56dc9f5b20 (diff)
downloadvyos-cloud-init-87d0fa867f27f101e93006ba8dc8a395098e8df1.tar.gz
vyos-cloud-init-87d0fa867f27f101e93006ba8dc8a395098e8df1.zip
wait less for the metadata service (by default)
Waiting around for a metadata service in a given datasource means that if its not there all the subsequent datasources have to wait, and boot is slowed down. As it is right now, EC2 is the only one that has the right to wait. In the past, we had to wait around for the EC2 metadata service. I really do not want to extend that courtesy to other cloud platforms. A network based metadata service should be up as soon as networking is up.
Diffstat (limited to 'cloudinit/url_helper.py')
-rw-r--r--cloudinit/url_helper.py1
1 files changed, 1 insertions, 0 deletions
diff --git a/cloudinit/url_helper.py b/cloudinit/url_helper.py
index c116a484..4a83169a 100644
--- a/cloudinit/url_helper.py
+++ b/cloudinit/url_helper.py
@@ -266,6 +266,7 @@ def wait_for_url(urls, max_wait=None, timeout=None,
max_wait: roughly the maximum time to wait before giving up
The max time is *actually* len(urls)*timeout as each url will
be tried once and given the timeout provided.
+ a number <= 0 will always result in only one try
timeout: the timeout provided to urlopen
status_cb: call method with string message when a url is not available
headers_cb: call method with single argument of url to get headers