Awesome. Any GCP folks here have an ETA on the new California region? Can't wait until we can provision clusters across two regions (California <=> Oregon) while keeping the speed of light latency low.
The ETA for all of California (United States), Frankfurt (Germany), Hamina (Finland), Montreal (Canada), Mumbai (India), Netherlands and Sao Paulo (Brazil) is "2017".
This is incorrect. We happily share a transparent and very open view into 3+ quarters ahead with customers and partners under NDA! We just publish for broader public when its open for the broader public.
(Source: me, the GCP roadmap Program Manager. Who also appreciates how consistently our NDA is upheld internally and externally.)
GCP support here. We're aware of some users hitting this, it's an artifact of how the new regions are published to existing projects. This should be resolved for all users by the end of the day (Sydney time).
In the meantime, try these workarounds:
* Create a new project, it should work off the bat
* Create a manual network and explicitly add the subnetworks you want
AWS in contrast likes to spread things out more, like in Northern Virginia where they have 5 different AZs that are supplied from different electrical substations and confer some 'more than one block down the street' geographic separation. While a bunch of them are in the usual Ashburn-Sterling-Dulles triangle on north of Dulles Airport, there's also ones in Chantilly on the south side of the airport, and past Manassas another 15 miles out.
When AWS rolled out in Ohio, they did the same thing [1], locating two of them in the suburbs northwest of Columbus and one northeast, or in Sweden where they're in Västerås and Eskilstuna on opposite sides of a large lake, and a third in Katerineholm another 50 km out.