| Age | Commit message (Collapse) | Author |
|---|
|
cloud-init expands $RELEASE in a source so it can easily be used.
|
|
|
|
|
|
Also added some comments and captured the output
|
|
In order to allow an ephemeral, or otherwise pristine image to
receive some configuration, cloud-init will read a url directed by
the kernel command line and proceed as if its data had previously existed.
For more information, see doc/kernel-cmdline.txt
|
|
|
|
|
|
|
|
|
|
The reason for moving this from cloudinit/__init__.py was that it
was running too late there.
The cloudinit.parsed_cfgs variable was already filled by cloud-init.py's
reading of cloud config. I'm sure I had done this so that it would not have to
re-parse configs.
I think the right way to handle this is to move that logic back to
cloudinit/__init__.py and add some function like 'reread_configs()'
that would re-read all releavent cofnigs and re-setup logging.
That seemed more error prone at the moment, with limited time.
|
|
|
|
What this does is provide an second DataSource that could use the
kernel command line url=. For example:
ro root=/dev/vda url=http://example.com/i-abcdefg/
http://example.com/i-abcdefg/ would contain:
datasource:
NoCloud:
# default seedfrom is None
# if found, then it should contain a url with:
# <url>/user-data and <url>/meta-data
# seedfrom: http://my.example.com/i-abcde
seedfrom: http://example.com/i-abcdefg/
Then, the NoCloudNet DataSource would find that seedfrom config
and consume data at
http://example.com/i-abcdefg/user-data
and
http://example.com/i-abcdefg/meta-data
|
|
|
|
On the users's first login with a locale that is not supported (where 'locale'
would give errors), inform the user on how they can generate the locales
or install language support packages.
LP: #859814
|
|
* remove unused 'line' variable
* fix bug where multiple errant locales were not working correctly
* only output each bad locale once in the list
* you only need to run the apt-get install of the package *or* localegen
|
|
|
|
Just to avoid an entry in top level directory, get rid of profile.d there
and instead move Z99-cloud-locale-test.sh -> tools/Z99-cloud-locale-test.sh
|
|
|
|
|
|
This fixes a bug in chef handling if the config contained the 'validation_key'
key, but not the 'validation_cert' key.
LP: #960547
|
|
|
|
|
|
LP: #961226
|
|
Previously, we were returning an array with a single item, which could
have contained newlines in it.
This does limit the potential content of a ssh public key, but it
seems unlikely that in the future a valid public key would contain a newline.
|
|
|
|
instead of MaaS or Maas, use MAAS consistently.
The only non 'MAAS' left are all lower case.
|
|
|
|
LP: #953915
|
|
If user-data is supplied that is not multipart, and is unhandled, then
log a warning. A warning by default will get to the console, so the user
can see it even if they cannot get into the instance. If they don't see
it there, it would still be available in the cloud-init log.
|
|
|
|
|
|
|
|
Per Cosmin in personal mail:
> I didn't change any of the copyright/license information, as I'm not
> sure what should be there (feel free to adjust it as you please, I don't
> even care for my name to appear in the file).
I've added Canonical to copyright (as the file was originally copied and modified
from the DataSourceEc2). And also added Cosmin's name to Authors and Copyright
for the portions that he contributed.
|
|
most types
|
|
|
|
|
|
of ca-certificates from adding new trusted certs.
|
|
|
|
Thanks to Ben Howard.
|
|
|
|
* removed the 'CLOUD-INIT-IGNORE' section, as we're just blindly writing
the file now. removed the now-unnecessary import of 're' and 'os'
* removed try/except block around write_apt_snippet. This will bubble
up and cloud-init will let it through even to the console. Catching
it and turning it into a debug would just hide it.
* removed 'default' as a synonym for 'whatever cloud-init thinks is best'
If people are going to change this, I'd rather they be specific.
* supported value of "0"
* fixed some complaints from
./tools/run-pylint cloudinit/CloudConfig/cc_apt_pipelining.py
|
|
- Changed values to be more simplistic and intuitive
- Only allow pipelining values up to 5
- Changed to per_instance over per_always to remove need
for tracking the values
- Fixed Python style
|
|
|
|
LP: #942061
|
|
|
|
|
|
|
|
|
|
|
|
|
