~harlowja/cloud-init/fix-auto-bool : changes

~harlowja/cloud-init/fix-auto-bool » Changes from revision 963

From Revision 963 to 944

Rev	Summary	Authors	Date
963	Remove usage of bool as string Remove usage of bool as string The net_util format is that 'auto' if it exists will be a boolean so it is likely that the code that exists does not correctly work in this mode (since it tries to do a lower() call on a boolean, which will not work).	Joshua Harlow	10 years ago
962	distros/freebsd.py: fix regression due to previous pylint cl... distros/freebsd.py: fix regression due to previous pylint cleanup	Scott Moser	10 years ago
961	tools/make-tarball: add ability to include uncommited change... tools/make-tarball: add ability to include uncommited changes if you have UNCOMMITTED=1 in environment then the tree will contain uncommitted changes.	Scott Moser	10 years ago
960	test_altcloud: fix altcloud tests when running on arm test_altcloud: fix altcloud tests when running on arm Similar test-hack as the SmartOS one. Here we just pretend that we're running on x86_64 so as to avoid re-writing the tests to expect otherwise on arm.	Scott Moser	10 years ago
959	AltCloud: to not run dmidecode on arm systems. AltCloud: to not run dmidecode on arm systems. As with SmartOS change earlier, running dmidecode on arm will crash kvm. So instead of doing that, just return UNKNOWN which will cause this data source to not activate.	Scott Moser	10 years ago
958	pep8 and pylint pep8 and pylint	Scott Moser	10 years ago
957	SmartOS: do not run on arm as dmidecode causes problems SmartOS: do not run on arm as dmidecode causes problems See LP: #1243287 for more information, but the easiest thing to do here is just not run smartos on arm.	Scott Moser	10 years ago
956	netinfo.py: fix regression causing ubuntu to show 'addr:v.x.... netinfo.py: fix regression causing ubuntu to show 'addr:v.x.y.z' after freebsd merge, ubuntu shows addr:v.x.y.z instead of v.x.y.z for the ipv4 address. This should fix that by just skipping the 'inet' (or inet6) token if the next token starts with 'addr:'.	Scott Moser	10 years ago
955	ConfigDrive: trim trailing newlines in previous-instance-id ConfigDrive: trim trailing newlines in previous-instance-id When cloud-init writes previous-instance-id, it does so with a trailing '\n'. This isn't ideal, as other readers also have to know that this will have a trailing '\n' on it, but here we just trim that off.	Scott Moser	10 years ago
954	DataSourceOpenStack: debug, not warn on non-ideal version. d... DataSourceOpenStack: debug, not warn on non-ideal version. do not use latest. do not search 'latest', as that would be assuming the versioned api would never break. Also, instead of warning when we use something else, just debug.	Scott Moser	10 years ago
953	test_smartos: remove bad test case test_smartos: remove bad test case This test case isn't really valid any more as we've changed the way this works.	Scott Moser	10 years ago
952	NoCloud: fix broken seed from external image NoCloud: fix broken seed from external image	Scott Moser	10 years ago
951	CloudSigma: remove 'WARN' in not found case CloudSigma: remove 'WARN' in not found case The CloudSigma datasource would attempt to read /dev/ttyS1 and if not found would warn (which gets logged to stdout by default). Better to just debug.	Scott Moser	10 years ago
950	DataSourceGCE: fix 'is_resolvable', remove unnecessary WARN DataSourceGCE: fix 'is_resolvable', remove unnecessary WARN	Scott Moser	10 years ago
949	DataSourceOpenStack: allow vendor-data to be a dict with 'cl... DataSourceOpenStack: allow vendor-data to be a dict with 'cloud-init' inside There might be multiple things to put inside a vendor-data. So, if it is a dict and that dict has 'cloud-init', assume that the whole thing was not meant for cloud-init, and set vendordata_raw to the specific item.	Scott Moser	10 years ago
948	smartos: fix bug in previous commit smartos: fix bug in previous commit The code in the previous commit was creating /var/lib/cloud/instance/ when it should not have. This is better handled now by using /var/lib/cloud/instances/<instance-id>, and then letting the link get created by cloud-init elsewhere.	Scott Moser	10 years ago
947	re-work vendor-data and smartos re-work vendor-data and smartos This reduces how much cloud-init is explicitly involved in what "vendor-data" could accomplish. The goal of vendor-data was to provide the vendor with a channel to run arbitrary code that accomodate for their specific platform. Much of those accomodations are currently being done in cloud-init. However, this now moves some of those things to default "vendor-data", instead of cloud-init proper. Basically, now we have an 'sdc:vendor-data' key in the metadata. If that does not exist, then cloud-init will use the default. The default, provides a boothook. That boothook writes a file into /var/lib/cloud/per-boot/ . That file will be both written on every boot and then executed at rc.local time frame (by 'scripts-per-boot'). It will then execute /var/lib/cloud/instance/data/user-script and /var/lib/cloud/instance/data/operator-script if they exist. So, the things that cloud-init is now doing outside of the default vendor-data that I would rather be done in vendor-data is: * managing the population of instance/data/user-script and instance/data/operator-script. These could very easily be done from the boothook, but doing them in cloud-init removes the necessity for having a 'mdata-get' command in the image (or some other way for the boothook script to query the datasource). * managing the LEGACY things.	Scott Moser	10 years ago
946	GCE: add some tests, some small fixes GCE: add some tests, some small fixes	Scott Moser	10 years ago
945	Add a openstack specific datasource Add a openstack specific datasource Openstack has a unique derivative datasource that is gaining usage. Previously the config drive datasource provided part of this functionality as well as the ec2 datasource, but since new functionality is being added to openstack's special datasource it seems beneficial to combine the used parts into a new datasource just made for handling openstack deployments that use the openstack metadata service (possibly in combination with the ec2 metadata service). This patch factors out the common logic shared between the config drive and the openstack metadata datasource and places that in a shared helper file and then creates a new openstack datasource that readers from the openstack metadata service and refactors the config drive datasource to use this common logic.	Joshua Harlow	10 years ago
944	Add initial GCE datasource Add initial GCE datasource There are some rough edges here and its missing some test, but I want to get this pulled in.	Scott Moser	10 years ago

Older »