lp://staging/~harlowja/cloud-init/no-negative-max-wait
- Get this branch:
- bzr branch lp://staging/~harlowja/cloud-init/no-negative-max-wait
Branch merges
- Server Team CI bot: Needs Fixing (continuous-integration)
- cloud-init Commiters: Pending requested
-
Diff: 33 lines (+7/-3)2 files modifiedcloudinit/sources/DataSourceOpenStack.py (+2/-2)
cloudinit/url_helper.py (+5/-1)
Branch information
Recent revisions
- 972. By Joshua Harlow
-
Fix max_wait being showed as < 0
Ensure that max_wait is always >= 0 so that
when it is displayed it doesn't show up as a
negative number (which is confusing). - 971. By Scott Moser
-
OpenNebula: support base64 encoded user-data
This change adds the possibility to have base64 encoded userdata in
OpenNebula source.OpenNebula uses a text file with shell variables for storing the
configuration variables (including user provided data). Some user data may
not be renderable into this format, so using base64 encoding alleviates
the problem.The change here allows the user to provide a second variable
USERDATA_ENCODING (or USER_DATA_ENCODING) and set that value to 'base64'
to indicate that USERDATA is base64 encoded. - 970. By Scott Moser
-
NoCloud: fix broken seedfrom on the kernel command line
This was broken in the VendorData add.
- 968. By Scott Moser
-
Azure: re-format ephemeral disk if necessary
On azure, the ephemeral disk may be destroyed and replaced with a fresh
ephemeral disk on any reboot or stop and start cycle.This makes the datasource able to detect that by presence of an unformatted
and specifically labeled NTFS filesystem with no files on it. - 967. By Scott Moser
-
final_message: allow replacement of capital name keys.
documentation of final_message in
doc/examples/cloud-config- final-message. txt
showed '$UPTIME' and '$TIMESTAMP' would be available, but
only the lower case versions of these strings were available.This change just makes all lower case and upper case keys
available here to avoid breaking anyone who used the
functional-but-not- correctly- documented lower case names. - 966. By Scott Moser
-
seed_random: do not capture command output, provide env RANDOM_SEED_FILE
call the command without capturing output, and provide RANDOM_SEED_FILE
to the environment that it is run in. - 965. By Kiril Vladimiroff
-
CloudSigma: support user-data being base64 encoded
This adds the ability to read a 'base64_fields' entry in the metadata,
and if cloud-init-userdata is listed in that, then content will be
base64 decoded first. - 964. By Scott Moser
-
write status to /run/cloud-init/ for external consumption
This populates and maintains status.json and result.json with
json formated data about cloud-init's errors and datasource.It is intended to be consumed by other programs that want to
wait until cloud-init is done, or know its success. - 963. By Dustin Kirkland
-
seed_random: support a 'command' to seed /dev/random
This extends 'random_seed' top level entry to include a 'command'
entry, that has the opportunity to then seed the random number generator.Example config:
#cloud-config
random_seed:
command: ['dd', 'if=/dev/zero', 'of=/dev/random', 'bs=1M', 'count=10']
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp://staging/~cloud-init-dev/cloud-init/trunk