summaryrefslogtreecommitdiff
path: root/cloudinit/DataSourceNoCloud.py
AgeCommit message (Collapse)Author
2010-08-13fix 'seedfrom' in DataSourceNoCloud (LP: #617400)Scott Moser
LP: #617400
2010-08-12DataSourceNoCloud: record where seeds were read fromScott Moser
This just records in 'self.seedfrom' each of the locations that seed data was read from.
2010-08-12DataSourceNoCloud: fix issue with seeded filesScott Moser
get_data was returning True before it set self.user_data_raw and self.user_data.
2010-08-12use read_optional_seed, change 'parse_cmdline_data' to return booleanScott Moser
using read_optional_seed in DataSourceEc2 and DataSourceNoCloud. change parse_cmdline_data to fill a dictionary that is supplied by caller. It then returns strictly true or false based on whether or not it was specified in cmdline
2010-08-12initial dump of "sans-cloud" code (DataSourceNoCloud)Scott Moser
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.