vyos-cloud-init.git/upstart/cloud-init-local.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-12T17:03:44+00:00upstart: 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: #1368861cloud-init-local depends on /run. reflect that in upstart job.2014-09-11T14:50:04+00:00Scott Mosersmoser@ubuntu.com2014-09-11T14:50:04+00:00urn:sha1:26c1cf9eeeb39e9bfcc1a37743679e5c76ab97b0
With the writing of cloud-init status, cloud-init-local needs to
have /run mounted. The issue we were seeing was a race where:
cloud-init-local creates /run/cloud-init
/run is mounted
cloud-init-local tries to link a file into /run/cloud-init
that directory was no longer visisable as /run was mounted over
the top.
LP: #1353008change upstart jobs to use single 'cloud-init' binary2012-06-28T20:46:11+00:00Scott Mosersmoser@ubuntu.com2012-06-28T20:46:11+00:00urn:sha1:0b79a18679e03b300a8a607f28f8fd1c9acbf39e
This just updates upstart jobs to the new single binary approach.
initial dump of "sans-cloud" code (DataSourceNoCloud)2010-08-12T05:56:12+00:00Scott Mosersmoser@ubuntu.com2010-08-12T05:56:12+00:00urn:sha1:54346d35221fd405423dd33a2b06202f10e2aa22
The new classes 'DataSourceNoCloud' and 'DataSourceNoCloudNet'
implement a way to get data from the filesystem, or (very minimal)
data from the kernel command line. This allows the user to seed data to
these sources.
There are now 2 "cloud-init" jobs, cloud-init-local that runs on
mounted MOUNTPOINT=/
and 'cloud-init' that runs on
start on (mounted MOUNTPOINT=/ and net-device-up IFACE=eth0 and
stopped cloud-init-local )
The idea is that cloud-init-local can actually function without network.
The last thing in this commit is "uncloud-init".
This tool can be invoked as 'init=/usr/lib/cloud-init/uncloud-init'
It will "uncloudify" things in the image, generally making it easier
to use for a simpler environment, and then it will exec /sbin/init.