kevinheyer/bootstrap-vz
1
0
Fork 0
mirror of https://github.com/kevingruesser/bootstrap-vz.git synced 2025-12-16 23:00:23 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
bootstrap-vz/bootstrapvz/providers/gce
History
Anders Ingemann f62c8ade99 Convert indentation from tabs to spaces (4) 
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
2016-06-04 11:38:16 +02:00
..
tasks Convert indentation from tabs to spaces (4) 2016-06-04 11:38:16 +02:00
__init__.py Convert indentation from tabs to spaces (4) 2016-06-04 11:38:16 +02:00
manifest-schema.yml Remove image section in manifest 2015-12-13 19:41:18 +01:00
README.rst GCE: Documentation improvements 2016-04-19 11:34:53 -04:00

README.rst 

Google Compute Engine
=====================

The `GCE <https://cloud.google.com/products/compute-engine/>`__ provider
can creates image as expected by GCE - i.e. raw disk image in \*.tar.gz
file. It can upload created images to Google Cloud Storage (to a URI
provided in the manifest by ``gcs_destination``) and can register images to
be used by Google Compute Engine to a project provided in the manifest by
``gce_project``. Both of those functionalities are not fully tested yet.

Note that to register an image, it must first be uploaded to GCS, so you must
specify ``gcs_destination`` (upload to GCS) to use ``gce_project`` (register
with GCE)

Manifest settings
-----------------

Provider
~~~~~~~~

-  ``description``: Description of the image.
-  ``gcs_destination``: Image destination in GCS.
-  ``gce_project``: GCE project in which to register the image.


Example:

.. code-block:: yaml

    ---
    provider:
      name: gce
      description: Debian {system.release} {system.architecture}
      gcs_destination: gs://my-bucket
      gce_project: my-project