kevinheyer/bootstrap-vz
1
0
Fork 0
mirror of https://github.com/kevingruesser/bootstrap-vz.git synced 2025-08-24 07:26:29 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
bootstrap-vz/bootstrapvz/providers/gce
History
Zach Marano 1f747788c1 Fix missing source repo in GCE images. Add back baseline apt cache as 
well. Add in additional GCE guest package into manifests (init files
were split into their own package to make the python package adhere to
pypi standards).
2016-07-21 14:14:42 -07:00
..
tasks Fix missing source repo in GCE images. Add back baseline apt cache as 2016-07-21 14:14:42 -07:00
__init__.py Fix missing source repo in GCE images. Add back baseline apt cache as 2016-07-21 14:14:42 -07: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