| Age | Commit message (Collapse) | Author |
|---|
|
Use the --quiet switch when running apt-get to get output suitable for
logging, rather than with pretty progress updates designed for interactive
use. This makes the log, as returned by GetConsoleOutput for instance, a
little shorter and easier to read. Some action completion notices are also
missed, but it's pretty clear still as no error output appears before
cloud-init goes on to the next thing.
Mer apt-get man page:
Quiet; produces output suitable for logging, omitting progress indicators.
LP: #1012613
|
|
LP: #1012613
|
|
in order to work on python 2.6, replace usage of check_output with util.subp.
|
|
LP: #970071
|
|
LP: #978329
|
|
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
|
|
|
|
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.
|
|
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
|
|
|
|
|
|
|
|
|
|
main now is more useful for debugging. now it does:
* get: just dump contents of a url provided after oauth
* crawl: walk through using indexes, dumping content
* check-seed: validate the seed is good
uses MD_VERSION in the url, and appends that to the metadata url
in the config file. (previously it assumed the url in the config
was the full url)
does not require user-data in the http seed. if the user did not
specify user-data, it wont be there, so do not fail on that case.
|
|
|
|
- cloud-config option of "apt-pipelining"
- Address LP: 948461
|
|
|
|
This adds to the 'main' in cloudinit/DataSourceMaaS.py a method for
testing oauth_headers.
|
|
|
|
|
|
|
|
This commits a generally functional read_maas_seed_url, and re-works how
the content is checked, to share between read_maas_seed{url,dir}.
|
|
|
|
Also, add in the headers_cb which will be required for oauth.
|
|
Tests at this point seem to indicate that seed-dir would work.
|
|
Because Fedora's run-parts does not accept '--regex' and debian's
run-parts skips files with a '.' in the *without* '--regex=.*', we're
forced to include our own version of run-parts.
LP: #933553
|
|
|
|
|
|
|
