Age | Commit message (Collapse) | Author |
|
|
|
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
|
|
|
|
|
|
|
|
|
|
seems CloudStack doesn't need that.
|
|
|
|
if public-keys in metadata are a list (rather than a dict), then
return them as such.
This allows populating NoCloud keys with:
public-keys:
- ssh-rsa .... myname.mylabel
- ssh-dsa .... myname.mylabel2
Or:
cat <<EOF
public-keys:
$(ssh-add -L | sed 's,^\(.*\), - "\1",')
EOF
|
|
|
|
The purely local non-device (vfat/iso9660) sources were broken by the
last set of changes here. This restores them to functional.
If the seed is from a device, then the default behavior is to be 'net' mode.
For seed via cmdline, the user can specify 'ds=nocloud-net' and for
seed via filesystem seed dir, they can just populate the other directory.
To make it easier, when attaching a seed device, the user does not need
to specify 'dsmode' of 'net' in the metadata file. They still can, but that is
the default. It seems that that is more likely to be what is desired.
LP: #942695
|
|
Also improves the logic in is_container following ubuntu's
/etc/init/container-detect.conf .
LP: #941955
|
|
This branch also adds tests for part-handler registration and part-handler
handling.
|
|
ca-certificates package upgrades.
|
|
|
|
|
|
|
|
This makes the user able to pass in multi-line input to the public-key flag,
and it will be handled correctly (just as if it came from the authorized_keys
file)
|
|
document usage of DataSourceNoCloud from vfat or iso disk.
|