The Google GCE cloud and Juju
List of supported clouds > Google GCE
This document describes details specific to using your existing Google GCE cloud with Juju.
See more: Google GCE
When using the Google GCE cloud with Juju, it is important to keep in mind that it is a (1) machine cloud and (2) not some other cloud.
See more: Cloud differences in Juju
As the differences related to (1) are already documented generically in our Tutorial, How-to guides, and Reference docs, here we record just those that follow from (2).
Juju points of variation | Notes for the Google GCE cloud |
---|---|
setup (chronological order): | |
CLOUD | |
supported versions: | |
requirements: | Permissions: Service Account Key Admin, Compute Instance Admin, and Compute Security Admin. See more: Google | Compute Engine IAM roles and permissions. |
definition: | Already known to Juju. Run juju clouds --all to confirm. (Pre-defined cloud name in Juju: google .) |
CREDENTIAL | |
definition: |
auth-type : jsonfile or oauth2 > See more: Google | Authenticate to Compute Engine, Google | Create and delete service account keys If you want to use environment variables: - - |
CONTROLLER | |
notes on bootstrap: | – |
other (alphabetical order:) | |
CONFIGURATION (model) | |
cloud-specific: |
base-image-path Sets the base path to look for machine disk images. Type: string |
CONSTRAINT | |
conflicting: |
[instance-type] vs. [arch, cores, cpu-power, mem]
|
supported? | |
- allocate-public-id
|
![]() |
- arch
|
![]() |
- container
|
![]() |
- cores
|
![]() |
- cpu-power
|
![]() |
- image-id
|
![]() |
- instance-role
|
![]() |
- instance-type
|
![]() |
- mem
|
![]() |
- root-disk
|
![]() |
- root-disk-source
|
![]() |
- spaces
|
![]() |
- tags
|
![]() |
- virt-type
|
![]() |
- zones
|
![]() |
PLACEMENT DIRECTIVE | |
<machine> |
TBA |
subnet=... |
![]() |
system-id=... |
![]() |
zone=... |
![]() |
MACHINE | |
RESOURCE (cloud) Consistent naming, tagging, and the ability to add user-controlled tags to created instances. |
![]() |
Last updated a month ago.