S3 images can now be bootstrapped outside EC2.
However, this fix adds the requirement of a "region" setting.
At some point we could make "region" optional and fail when bootstrap-vz
is run outside EC2 and no "region" is set.
* force kpartx to use synchronous mode, removing sleep(10)
* get image configuration, use it during tarball creation and registration
* add (non-working, path problems) image registration
* add cleaning of image from Google keys and repositories
* add NTP server address in manifest
* add preference for backport kernels in manifest
* disable IPv6
* correctly set host name
Added GenerateLocale as SetMetadataSource predecessor, to avoid any
potential locale warnings. Also fixed a space indentation flaw and a
string which was being formatted with a non-existent key-argument.
This closes#75.
The tarball bootstrap method now uses an existing tarball if it is
found, regardless of its settings on the manifest, although it will
create a new one only if `"tarball"` is `true`.
This closes#24.
DETAILS:
- Apparently a potential security issue with yaml.load vs yaml.safe_load.
Like pickling, yaml.load could result in arbitrary code being run.
- tox.ini file includes the flake8 settings for this project, build spec for 2.7
and line for eventually testing the project.
Specify the version in the manifest (system/waagent section)
Add possibility to specify waagent conf file in manifest (system/waagent section)
Update documentation to match changes
Use log_check_call instead of log_call
refactor test on dictionary key
- Manifest format parsing is now checked by the file extension ie: .json, .yml or .yaml.
- load_yaml in common/tools is the same as the json version.
- schema checking of manifest still passes (and fails appropriately) like the json manifests.
- I've also included a sample yaml config based off of the debian test json manifest.
