summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2016-10-19Move user/group functions to new ug_util fileJoshua Harlow
The amount of code to do user and group normalization and extraction deserves its own file so move the code that does this to a new file and update references to the old location. This removes some of the funkyness done in config modules to avoid namespace and attribute clashes as well.
2016-10-18update changelogScott Moser
* debian/cloud-init.templates: enable DigitalOcean by default
2016-10-18debian/cloud-init.templates: enable DigitalOcean by defaultBen Howard
Added DigitalOcean to the default templates as enabled by default. This allows cloud-init to work out of the box on DigitalOcean droplets.
2016-10-18DigitalOcean: enable usage of data source by default.Scott Moser
Just add DigitalOcean to the list of datasources that are used if there is no 'datasource_list' provided in config.
2016-10-18update Gentoo initscripts to run in the correct orderMatthew Thode
cloud-init-local needs to be run before net (and in the boot runlevel) as it sets up networking config and adds it to the default runlevel. cloud-init-local needs to be run in the boot runlevel because it modifies services in the default runlevel. When a runlevel is started it is cached, so modifications that happen to the current runlevel while you are in it are not acted upon. cloud-init needs to run after net, it does not need net because we still want it to set up other things if it can.
2016-10-07releasing package cloud-init version 0.7.8-15-g6e45ffb-0ubuntu1Scott Moser
2016-10-07update changelog (new upstream snapshot 0.7.8-15-g6e45ffb).Scott Moser
2016-10-07merge from 6e45ffb21e9622780585b4fe15890f009ca8fa71 at 0.7.8-15-g6e45ffbScott Moser
2016-10-07MAAS: improve the main of datasource to look at kernel cmdline config.Scott Moser
This just looks in one other maas related path for a config file. The file '91_kernel_cmdline_url' is written by cloud-init when it gets a cloud-config-url parameter. Also now we read the config even if a url is specified to potentially fill in credentials.
2016-10-07tests: silence the Cheetah UserWarning about NameMapper C version.Scott Moser
This silences a warning made by Cheetah in pip installed environments: UserWarning: You don't have the C version of NameMapper installed! I'm disabling Cheetah's useStackFrames option ... The reason for the monkey patching is that the warning goes to stderr during nose and breaks up its expected output. The side affect of it is that tests would run with Cheetah's 'useStackFrames' enabled which is "painfully slow with the Python version of NameMapper".
2016-10-07systemd: Run cloud-init.service Before dbus.socket not dbus.targetDaniel Watkins
The change reported to fix bug 1629797 was incorrect. It added: Before=dbus.target and its commit message referenced dbus.service. dbus.target does not exist, and dbus.service would not solve the problem. The change did not fix the problem nor actually make any difference. The fix here is just to use Before=dbus.socket. LP: #1629797
2016-10-04releasing package cloud-init version 0.7.8-14-g94fd35e-0ubuntu1Scott Moser
2016-10-04update changelog (new upstream snapshot 0.7.8-14-g94fd35e).Scott Moser
2016-10-04merge from master at 0.7.8-14-g94fd35eScott Moser
2016-10-04systemd: run cloud-init.service Before dbus.serviceScott Moser
This is the best work around we have for an issue seen when dns is used during cloud-init.service on a system that is configured in nsswitch to use systemd-resolved. The problem is that cloud-init.service was blocking basic.target, and dbus would not be available until after cloud-init.service finished. LP: #1629797
2016-10-04unittests: fix use of mock 2.0 'assert_called' when running make checkRyan Harper
Some of the new DigitalOcean unittests were written to use 'assert_called', which is only available in mock versions 2.0. Because of this, the failure would only occur in releases less than yakkety and not in 'tox'. Add a 'xenial' entry to tox.ini with versions from xenial.
2016-10-03releasing package cloud-init version 0.7.8-1-g3705bb5-0ubuntu1~16.04.3Scott Moser
2016-10-03update changelogScott Moser
2016-10-03cherry pick 6d1edc3f5a1Scott Moser
add 6d1edc3f5a1 to debian/patches/ntp-move-to-run-after-apt-configuration.patch LP: #1628337
2016-09-30Improve module documentation and doc cleanup.Wesley Wiedenmeier
This adds lots of config module documentation in a standard format. It will greatly improve the content at readthedocs. Additionally: * Add a 'doc' env to tox.ini * Changed default highlight language for sphinx conf from python to yaml most examples in documentation are yaml configs * Updated datasource examples to highlight sh code properly
2016-09-29releasing package cloud-init version 0.7.8-11-g02f6c4b-0ubuntu1Scott Moser
2016-09-29update changelog (new upstream snapshot 0.7.8-11-g02f6c4b).Scott Moser
2016-09-29merge from master at 0.7.8-11-g02f6c4bScott Moser
2016-09-29lxd: Update network config for LXD 2.3Stéphane Graber
Prior to LXD 2.3, the bridge configuration was done through distro packaging. Thus, lxd module interacted with debconf. With 2.3 and higher, this is now done inside LXD itself, so we need to use "lxc network" there. For now, this perfectly matches what we had before with debconf and doesn't cover any of the new options. We can always add those later. A set of tests similar to what we had for debconf has been added to make sure things look good. This is tested in Yakkety container running LXD 2.3 and all options seem to be passed through as expected, giving me the bridge I defined. Signed-off-by: Stéphane Graber <stgraber@ubuntu.com>
2016-09-29DigitalOcean: use meta-data for network configruationBen Howard
On DigitalOcean, Network information is provided via Meta-data. It changes the datasource to be a local datasource, meaning it will run before fallback networking is configured. The advantage of that is that before networking is configured it can bring up a network device with ipv4 link-local and hit the metadata service that lives at 169.254.169.254 to find its networking configuration. It then takes down the link local address and lets cloud-init configure networking. The configuring of a network device to go looking for a metadata service is gated by a check of data in the smbios. This guarantees that the code will not run on another system.
2016-09-28Import version 0.7.8-1-g3705bb5-0ubuntu1~16.04.2Scott Moser
Imported using git-dsc-commit.
2016-09-28ntp: move to run after apt configurationScott Moser
since ntp module may try to install packages, it needs to run after apt is configured. LP: #1628337
2016-09-23releasing package cloud-init version 0.7.8-8-g0439d8a-0ubuntu1Scott Moser
2016-09-23update changelog (new upstream snapshot 0.7.8-8-g0439d8a).Scott Moser
2016-09-23merge from master at 0.7.8-8-g0439d8aScott Moser
2016-09-21Decode unicode types in decode_binaryRobert Schweikert
The test in decode_binary for six.text_type was incorrect as that includes unicode type in Python 2 which should actually be decoded. When the type is string_types we now properly check only for basestring and str in Python 2 and Python 3 respectively and return the given blob without making an attempt to decode.
2016-09-21systemd: Ensure that cloud-init-local happens before NetworkManagerJoshua Harlow
2016-09-21Allow ephemeral drive to be unpartitionedPaul Meyer
If device has no partition table, the first line of output from `sgdisk -p <device>` will be "Creating new GPT entries.", instead of something like "Disk /dev/sdb: 266338304 sectors, 127.0 GiB". Also, protect against localized output by adjusting subp calls that parse sgdisk output to set LANG=C.
2016-09-21subp: add 'update_env' argumentScott Moser
In order for a caller to use 'env' argument of subp, they will realistically do: env = os.environ.copy() env['FOO'] = 'BZR' subp(cmd, env=env) This shortens that to be: subp(cmd, update_env={'FOO': 'BZR'}) Add tests, and update growpart tests to use mock when playing with os.environ.
2016-09-21releasing package cloud-init version 0.7.8-4-g970dbd1-0ubuntu1Scott Moser
2016-09-21update changelog (new upstream snapshot 0.7.8-4-g970dbd1).Scott Moser
2016-09-21merge from master at 0.7.8-4-g970dbd1Scott Moser
2016-09-21net: support reading ipv6 dhcp config from initramfsLaMont Jones
This adds support for understanding 'dhcp6' as a protocol that can be written into /run/net-IFACE.cfg files by the initramfs. The end result is supporting ipv6 dhcp from initramfs boot all the way into iscsi root. LP: #1621615, #1621507
2016-09-20releasing package cloud-init version 0.7.8-3-g80f5ec4-0ubuntu1Scott Moser
2016-09-20update changelog (new upstream snapshot 0.7.8-3-g80f5ec4).Scott Moser
2016-09-20merge from master at 0.7.8-3-g80f5ec4Scott Moser
2016-09-20Adjust mounts and disk configuration for systemd.Scott Moser
The end result of all of these changes is to get mounts managed by cloud-init to occur only after cloud-init.service is done. We need to do that so that filesystems that are set up by cloud-init (in disk_setup) do not get mounted by stale entries in /etc/fstab before the setup occurs. This can occur in 2 ways: a.) new instance with old /etc/fstab b.) same instance where disk needs adjusting (Azure resize will re-format the ephemeral disk). The list of changes here is: - move mounts and disk_setup module to cloud-init.service rather than config. cloud-init.service runs earlier in boot so it can get those mount points done earlier. - on systemd add 'x-systemd.requires=cloud-init.service' to fstab options - cloud-init-local.service: add Before=basic.target - cloud-init.service: - extend After, Before, and Wants to multiple lines rather than one long line. - sort consistently with cloud-init-local.service - add DefaultDependencies=no - add Before=default.target - add Conflicts=shutdown.target LP: #1611074
2016-09-15dmidecode: run dmidecode only on i?86 or x86_64 arch.Robert Schweikert
Dmidecode is not going to run successfully on anything other than an x86 or x86_64, just avoid running it anywhere else.
2016-09-15releasing package cloud-init version 0.7.8-1-g3705bb5-0ubuntu1~16.04.1Scott Moser
2016-09-15update changelog (new upstream snapshot 0.7.8-1-g3705bb5).Scott Moser
2016-09-15merge from master at 0.7.8-1-g3705bb5Scott Moser
2016-09-15releasing package cloud-init version 0.7.8-1-g3705bb5-0ubuntu1Scott Moser
2016-09-15update changelog (new upstream snapshot 0.7.8-1-g3705bb5).Scott Moser
2016-09-15merge from master at 0.7.8-1-g3705bb5Scott Moser
2016-09-15systemd: put cloud-init.target After multi-user.targetScott Moser
When we moved cloud-final.service to run After multi-user.target it caused a dependency loop (as cloud-init.target was still implied to be Before multi-user.target). journalctl would either show: cloud-init.target: Breaking ordering cycle by deleting job cloud-final.service/start or multi-user.target: Breaking ordering cycle by deleting job cloud-init.target/start The fix here is to clearly state that cloud-init.target is also After multi-user.target LP: #1623868
generated by cgit v1.2.3 (git 2.39.1) at 2026-01-15 00:24:55 +0000