mirror of
https://github.com/kevingruesser/bootstrap-vz.git
synced 2025-12-15 14:30:23 +00:00
Up until now I didn't see the point of using spaces for indentation. However, the previous commit (a18bec3) was quite eye opening. Given that python is an indentation aware language, the amount of mistakes that went unnoticed because tabs and spaces were used at the same time (tabs for indentation and spaces for alignment) were unacceptable. E101,W191 have been re-enable in the tox flake8 checker and the documentation has been modified accordingly. The following files have been left as-is: * bootstrapvz/common/assets/extlinux/extlinux.conf * bootstrapvz/common/assets/init.d/expand-root * bootstrapvz/common/assets/init.d/generate-ssh-hostkeys * bootstrapvz/common/assets/init.d/squeeze/generate-ssh-hostkeys * bootstrapvz/plugins/docker_daemon/assets/init.d/docker * bootstrapvz/providers/ec2/assets/bin/growpart * bootstrapvz/providers/ec2/assets/grub.d/40_custom * bootstrapvz/providers/ec2/assets/init.d/ec2-get-credentials * bootstrapvz/providers/ec2/assets/init.d/ec2-run-user-data * docs/_static/taskoverview.coffee * docs/_static/taskoverview.less * tests/unit/subprocess.sh |
||
|---|---|---|
| .. | ||
| tasks | ||
| __init__.py | ||
| apiclient.py | ||
| manifest-schema.yml | ||
| README.rst | ||
Oracle
======
The `Oracle <https://cloud.oracle.com/en_US/compute>`__ provider creates RAW
images compressed in a ``.tar.gz`` tarball. Those images can be uploaded using
the web interface of the Oracle Compute Cloud Service dashboard or configured
to be automatically sent by our Oracle Storage Cloud Service API embedded
client.
Manifest settings
-----------------
Credentials
~~~~~~~~~~~
The settings described below should be placed in the ``credentials`` key under
the ``provider`` section, if the image is intended to be uploaded after
generation. They will be used to authenticate the API client.
- ``username``: the same login used to access the Oracle Compute Cloud
dashboard.
``required``
- ``password``: password for the username specified above.
``required``
- ``identity-domain``: this is auto-generated by Oracle and available in the
"New Account Information" e-mail message they send after registration.
``required``
Example:
.. code-block:: yaml
---
provider:
name: oracle
credentials:
username: user@example.com
password: qwerty123456
identity-domain: usoracle9999
Provider
~~~~~~~~
If the ``credentials`` have been specified, the following settings are
available to customize the process of uploading and verifying an image.
- ``container``: the container (folder) to which the image will be uploaded.
``required``
- ``verify``: specifies if the image should be downloaded again and have its
checksum compared against the local one.
Valid values: ``true``, ``false``.
Default: ``false``.
``optional``
.. code-block:: yaml
---
provider:
name: oracle
container: compute_images
verify: true