Add support for Google Cloud 'us-east4' region and future regions

Bug #1690413 reported by Francis Ginther
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Andrew Wilkins
2.2
Won't Fix
High
Unassigned

Bug Description

Google cloud has enabled a new region, 'us-east4'. Can this be added to the regions supported by juju. Furthermore, google is planning on launching many more regions this year alone [1]. Please be aware of this as it might impact how you address this issue. From an Ubuntu image perspective, any region listed by the GCE api will have ubuntu images, so for GCE, there is no reason not to support every region returned.

$ gcloud compute regions list
NAME CPUS DISKS_GB ADDRESSES RESERVED_ADDRESSES STATUS TURNDOWN_DATE
asia-east1 0/600 0/102400 0/575 0/175 UP
asia-northeast1 0/24 0/20480 0/23 0/7 UP
asia-southeast1 0/24 0/20480 0/23 0/7 UP
europe-west1 0/600 0/102400 0/575 0/175 UP
us-central1 2/600 400/102400 2/575 0/175 UP
us-east1 0/600 0/102400 0/575 0/175 UP
us-east4 0/24 0/20480 0/23 0/7 UP
us-west1 0/24 0/20480 0/23 0/7 UP

$ juju show-cloud google
defined: public
type: gce
description: Google Cloud Platform
auth-types: [jsonfile, oauth2]
regions:
  us-east1:
    endpoint: https://www.googleapis.com
  us-central1:
    endpoint: https://www.googleapis.com
  us-west1:
    endpoint: https://www.googleapis.com
  europe-west1:
    endpoint: https://www.googleapis.com
  asia-east1:
    endpoint: https://www.googleapis.com
  asia-northeast1:
    endpoint: https://www.googleapis.com

[1] - https://cloud.google.com/compute/docs/regions-zones/regions-zones#announced

Changed in juju:
importance: Undecided → High
status: New → Triaged
milestone: none → 2.3-alpha1
Revision history for this message
Francis Ginther (fginther) wrote :

Google has enabled additional regions as of July 28, 2017:

$ gcloud compute regions list
NAME CPUS DISKS_GB ADDRESSES RESERVED_ADDRESSES STATUS TURNDOWN_DATE
asia-east1 0/600 0/102400 0/575 0/175 UP
asia-northeast1 0/24 0/20480 0/23 0/8 UP
asia-southeast1 0/24 0/20480 0/23 0/8 UP
australia-southeast1 0/24 0/20480 0/23 0/8 UP
europe-west1 0/600 0/102400 0/575 0/175 UP
europe-west2 0/24 0/20480 0/23 0/8 UP
us-central1 1/600 200/102400 1/575 0/175 UP
us-east1 0/600 0/102400 0/575 0/175 UP
us-east4 0/24 0/20480 0/23 0/8 UP
us-west1 0/24 0/20480 0/23 0/8 UP

With juju 2.2.2, I can see 8 of these regions:

$ juju version
2.2.2-xenial-amd64

$ juju show-cloud google
defined: public
type: gce
description: Google Cloud Platform
auth-types: [jsonfile, oauth2]
regions:
  us-east1:
    endpoint: https://www.googleapis.com
  us-central1:
    endpoint: https://www.googleapis.com
  us-west1:
    endpoint: https://www.googleapis.com
  europe-west1:
    endpoint: https://www.googleapis.com
  asia-east1:
    endpoint: https://www.googleapis.com
  asia-northeast1:
    endpoint: https://www.googleapis.com
  asia-southeast1:
    endpoint: https://www.googleapis.com
  australia-southeast1:
    endpoint: https://www.googleapis.com

Changed in juju:
milestone: 2.3-beta1 → 2.3-beta2
Andrew Wilkins (axwalk)
Changed in juju:
assignee: nobody → Andrew Wilkins (axwalk)
status: Triaged → In Progress
Revision history for this message
Andrew Wilkins (axwalk) wrote :
Changed in juju:
status: In Progress → Fix Committed
Revision history for this message
Francis Ginther (fginther) wrote :

Tested 1:2.3~rc1-0ubuntu1~16.04.1~juju1 on xenial. The regions now match up

$ gcloud compute regions list|sort
asia-east1 0/600 0/102400 0/575 0/175 UP
asia-northeast1 0/24 0/20480 0/23 0/8 UP
asia-south1 0/24 0/20480 0/23 0/8 UP
asia-southeast1 0/24 0/20480 0/23 0/8 UP
australia-southeast1 0/24 0/20480 0/23 0/8 UP
europe-west1 0/600 0/102400 0/575 0/175 UP
europe-west2 0/24 0/20480 0/23 0/8 UP
europe-west3 0/600 0/102400 0/575 0/175 UP
southamerica-east1 0/24 0/20480 0/23 0/8 UP
us-central1 1/600 200/102400 1/575 0/175 UP
us-east1 0/600 0/102400 0/575 0/175 UP
us-east4 0/24 0/20480 0/23 0/8 UP
us-west1 0/600 0/102400 0/575 0/175 UP

$ juju show-cloud google|sort
  asia-east1:
  asia-northeast1:
  asia-south1:
  asia-southeast1:
  australia-southeast1:
  europe-west1:
  europe-west2:
  europe-west3:
  southamerica-east1:
  us-central1:
  us-east1:
  us-east4:
  us-west1:

Now just waiting for this to show up in the final 2.3. Thanks!

Changed in juju:
status: Fix Committed → Fix Released
Revision history for this message
Matthew Dresden (matthew.dresden.vw.com) wrote :

This still isnt working:

Doesn't work interactively or as follows:

$ juju bootstrap google/us-east4 juju-controller-gcp-default-us-east4 \
> --config api-port=443 \
> --config auditing-enabled=true \
> --auto-upgrade=true
Creating Juju controller "juju-controller-gcp-default-us-east4" on google/us-east4
Looking for latest patch of packaged Juju agent version 2.4 for amd64
Launching controller instance(s) on google/us-east4...
ERROR failed to bootstrap model: cannot start bootstrap instance in any availability zone (us-east4-c, us-east4-b, us-east4-a)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.