lp:~smoser/cloud-init/trunk.disable_pollinate
- Get this branch:
- bzr branch lp:~smoser/cloud-init/trunk.disable_pollinate
Branch merges
- Ryan Harper: Approve
- Dustin Kirkland : Pending requested
-
Diff: 102 lines (+42/-7)4 files modifiedChangeLog (+1/-0)
cloudinit/config/cc_seed_random.py (+1/-1)
doc/examples/cloud-config-seed-random.txt (+32/-0)
tests/unittests/test_handler/test_handler_seed_random.py (+8/-6)
Related bugs
Related blueprints
Branch information
Recent revisions
- 1177. By Scott Moser
-
No longer run pollinate by default in seed_random
The user can still choose to run pollinate here to seed their
random data. And in an environment with network datasource, that
would be expected to work. However, we do not want to run it any
more from cloud-init because
a.) pollinate's own init system jobs should get it ran before ssh,
which is the primary purpose of wanting cloud-init to run it.
b.) with a local datasource, there is no network guarantee when
init_modules run, so pollinate -q would often cause issues then.
c.) cloud-init would run pollinate and log the failure causing
many cloud-init specific failures that it could do nothing about. - 1176. By Scott Moser
-
pep8: update formatting to pass pep8 1.4.6 (trusty) and 1.6.2 (xenial)
make check fails in a trusty sbuild due to different rules on older pep8.
Fix formatting to pass in older and newer pep8. - 1173. By Scott Moser
-
Add a kill switch for customization on VMware platform.
The customization is set to False by default and is triggered only
when the option disable_vmware_ customization is set to false in
/etc/cloud/cloud.cfg. - 1172. By Scott Moser
-
Apply pep8, pyflakes fixes for python2 and 3
Update make check target to run pep8 and run pyflakes or pyflakes3
depending on the value of 'PYVER'. This way the python3 build
environment does not need python2 and vice versa.Also have make check run the 'yaml' test.
tox: have tox run pep8 in the pyflakes
- 1171. By Scott Moser
-
systemd: support disabling cloud-init via file or kernel cmdline
This adds a systemd generator for a 'cloud-
init.target' . That target will
be WantedBy multi-user.target in the default case. If there is a file
/etc/cloud/cloud-init. disabled or the kernel command line contains
'cloud-init=disabled' then cloud-init will not affect boot at all. There are some packages/debian changes to affect this:
* postinst, preinst: these are necessary to remove some
old target files for multi-user.target (LP: #1552999)
* changes to include these files in the debian source package.
* rules.in: supports DEB_BUILD_OPTIONS= nocheck to not run check setup.py: mostly changes to support installing the generator
but also pep8 fixes along the waysystemd/*: make each of the services 'WantedBy=
cloud-init. target'
rather than being wanted by multi-user.target - 1170. By Scott Moser
-
packages/debian: make trunk packaging closer to ubuntu
The big difference is using:
${python3:Depends} or ${python:Depends}
rather than explicitly listing the dependencies (via template ${requires}).which means we get paths of
/usr/lib/python3/ dist-packages/ ..
rather than
/usr/lib/python3. 5/dist- packages/ ..
when built on xenial.Additionally it seems we no longer need this strange line.
# Because setup tools didn't copy data... - 1169. By Scott Moser
-
lxd fix bug and only run if enabled.
The lxd module would run lxd init even if no lxd/init config was provided.
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp:~cloud-init-dev/cloud-init/trunk