bootstrap-vz/bootstrapvz/providers/gce
Justin Santa Barbara 4b34cb2615 GCE: Documentation improvements
Small tweaks
* Add note that gce_project only works with gcs_destination
* Google's storage is called "Google Cloud Storage"
* Minor grammar tweaks
2016-04-19 11:34:53 -04:00
..
assets/initramfs-tools/scripts/local-premount Fix a problem with Debian 8 on GCE with >2TB disks 2015-09-23 16:55:16 -07:00
tasks GCE: Allow templating of image description 2016-04-19 11:34:53 -04:00
__init__.py Again fix the expand-root script for GCE. The volume is not /dev/loop0 2016-03-03 13:59:01 -08: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

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