vyos-cloud-init.git/upstart/cloud-init-nonet.conf, branch circinus-public-unmaintained (mirror of https://github.com/vyos/vyos-cloud-init.git)
https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=circinus-public-unmaintained2014-09-12T21:59:52+00:00upstart/cloud-init-nonet.conf: only mention wait if larger than 5 seconds2014-09-12T21:59:52+00:00Scott Mosersmoser@ubuntu.com2014-09-12T21:59:52+00:00urn:sha1:f5be74dc84aac7bb9a634e5518f5aac6ae80098a
silently wait 5 seconds for networking to come up.
We started seeing the message more now, as we are now blocking
the networking from coming up until cloud-init-local is done.
Previously that would have happened in parallel, and we were less likely
to see that message.
upstart/cloud-init-nonet.conf: do not exit on existance of obj.pkl2014-09-12T21:45:20+00:00Scott Mosersmoser@ubuntu.com2014-09-12T21:45:20+00:00urn:sha1:41a52ef99a9dddd3fef9bdc883dfca55770ef2a5
not sure why this was here.
the intent must of have been to allow for a local datasource
to continue booting and not annoyingly block waiting for network information
(if ithere was no network information).
However, that seems wrong.
If the datasource wipes /etc/network/interfaces and there are no network
interfaces then we're probably breaking that use case here. However we're
fixing the other more common case.
upstart: add blocknet which blocks net until after cloud-init-local2014-09-12T17:03:44+00:00Scott Mosersmoser@ubuntu.com2014-09-12T17:03:44+00:00urn:sha1:b09b12bc0130b6787bfee0332addd055459b9629
This makes it so networking wont start to come up until after
cloud-init-local has had a chance to search local datasources
and set /etc/network/interfaces.
The changes most likely need to still be done for systemd.
LP: #1368861upstart/cloud-init-nonet.conf: fix indentation2013-09-17T16:34:25+00:00Scott Mosersmoser@ubuntu.com2013-09-17T16:34:25+00:00urn:sha1:266d12c5777d5fba97c374c33cb4f31d50e2d347cloud-init-nonet.conf: handle case where sleep died2013-03-26T19:40:29+00:00Scott Mosersmoser@ubuntu.com2013-03-26T19:40:29+00:00urn:sha1:be0041e7c7fd6ce5ffc1c9c54893b715bcab6358
In starting containers in lxc, I was seeing errors like:
/proc/self/fd/9: 24: kill: No such process
Which indicated the sleep pid had already died.
I'm not sure how or why it was dead, but this just is less annoying in that
case.
add uptime to msg output2013-03-04T19:28:34+00:00Scott Mosersmoser@ubuntu.com2013-03-04T19:28:34+00:00urn:sha1:bcf04395be323c60b013e531ef3bf32b722a780aif sigterm received, and networking is up, exit 02013-03-04T14:56:24+00:00Scott Mosersmoser@ubuntu.com2013-03-04T14:56:24+00:00urn:sha1:1a3e0fa19b6c3224ea986141b37f74d5464b7c82
LP: #1015223add cloud-init-container.conf2012-09-13T18:01:04+00:00Scott Mosersmoser@ubuntu.com2012-09-13T18:01:04+00:00urn:sha1:67bf7722398278e7089098dfd683389ef4e418c5
This changes the way that we avoid cloud-init-nonet hanging in a container.
Previously, under LP: #800824 we tried 'start networking', but that caused
issues described in LP: #1031065.
Here, we emit the net-device-added for any devices that have not yet been
seen.
LP: #1031065increase cloud-init-nonet timeout to 130 seconds from 702011-09-29T00:16:05+00:00Scott Mosersmoser@ubuntu.com2011-09-29T00:16:05+00:00urn:sha1:bad89c162e8f5be513537a1a430aa98cd1822fb7
LP: #861866cloud-init-nonet.conf: redirect 'start networking' output to /dev/null2011-09-21T14:26:23+00:00Scott Mosersmoser@ubuntu.com2011-09-21T14:26:23+00:00urn:sha1:93f41985489a31630949c92431dea01009a8e7e0