Exploring GCP Global Infrastructure

Welcome to your third lesson in the Introduction to GCP course! In your first lesson, you learned the foundational concepts of cloud computing, including how Google Cloud Platform (GCP) organizes its infrastructure into regions and zones. In your second lesson, you discovered how to use the GCP Pricing Calculator to estimate costs and saw how region selection impacts pricing.

Now it's time to move from theory to hands-on exploration. This lesson will teach you how to discover and understand your GCP setup using the gcloud CLI, giving you practical skills to explore GCP’s global infrastructure programmatically.

Understanding GCP’s global infrastructure is crucial as you start building real applications. The region you choose affects three critical factors: reliability improves when you understand how many zones are available, latency decreases when you choose regions closer to your users, and cost varies between regions, as you discovered when comparing pricing in different locations.

By the end of this lesson, you'll know how to discover your current GCP configuration, explore available regions and zones, and save your findings for future reference.

Before exploring your GCP environment, let's clarify the key infrastructure concepts you'll encounter.

A region in GCP is a specific geographic location where Google has built multiple data centers. Each region operates independently and contains multiple zones. When you choose a region like us-central1 (Iowa) or europe-west1 (Belgium), you're selecting where your GCP resources will physically reside. Regions are isolated from each other to provide fault tolerance and independence.

A zone is a deployment area within a region, representing a single failure domain. Each GCP region contains multiple zones, typically labeled with a letter, such as us-central1-a, us-central1-b, and us-central1-c. Zones are close enough for low-latency connections but are isolated to minimize the risk of simultaneous failures.

The relationship between region choice and both price and performance becomes clearer when you understand the physical infrastructure. Some regions may have newer hardware or more features, and the distance to your users affects network latency.

Throughout this lesson, you'll use the gcloud CLI (Command Line Interface) to explore your GCP environment. The gcloud CLI provides a powerful way to interact with GCP services programmatically.

Note: In this course environment, you'll be using a mock version of the gcloud CLI that provides representative outputs without requiring GCP credentials or authentication. This allows you to practice the commands and understand the concepts without needing an active GCP account. The outputs you see are realistic examples of what you would encounter in a real GCP environment.

The gcloud CLI allows you to list, describe, and configure resources in your GCP account. You can use it to view available regions and zones, check your current configuration, and save information for future reference. The output format can be controlled with the --format flag, which supports options like json, yaml, table, and value for different display needs.

Before running commands, make sure you have the gcloud CLI installed and initialized with your GCP account. If you are working in a cloud-based environment or lab, the CLI may already be set up for you.

Every gcloud CLI configuration includes a default region and zone that determine where your commands will operate unless you explicitly specify a different location. Understanding your default region and zone is crucial because it affects which resources you can see and where new resources will be created.

To discover your current default region and zone, use:

gcloud config get-value compute/region
gcloud config get-value compute/zone

These commands query your gcloud CLI configuration and return the identifiers for your default region and zone. You’ll see output similar to this:

us-central1
us-central1-a

The region identifier follows GCP’s naming convention: geographic area (us, europe, asia), specific location (central, west, east), and number (1, 2, etc.). The zone adds a letter to the region name.

Your default region and zone matter because when you run gcloud commands without specifying a location, they operate in your default region and zone. When you create new resources through the CLI, they’ll be placed in your default region and zone unless you override these settings.

To set your default region and zone, use:

gcloud config set compute/region us-central1
gcloud config set compute/zone us-central1-a

Now let’s explore all the regions GCP makes available worldwide. GCP continuously expands its global infrastructure, so the total number changes over time.

To see all available GCP regions:

gcloud compute regions list --format="value(name)"

This command lists the names of all available regions. You’ll see output similar to this (the exact regions available may vary as GCP adds new locations):

asia-east1
asia-northeast1
asia-south1
australia-southeast1
europe-north1
europe-west1
europe-west2
europe-west3
europe-west4
northamerica-northeast1
southamerica-east1
us-central1
us-east1
us-east4
us-west1
us-west2
us-west3
us-west4

To get a count of available regions:

gcloud compute regions list --format="value(name)" | wc -l

This returns the current count of available regions. The exact number changes as GCP adds new regions globally.

Among these regions, some are considered "major" due to their age, feature availability, and cost characteristics. For example, us-central1 (Iowa) is one of GCP’s original and most widely used regions, often offering the lowest prices and broadest feature support. europe-west1 (Belgium) is a primary region for European users.

While regions provide geographic distribution, zones within your region provide the redundancy that makes cloud applications resilient. Let’s explore the zones in your current region.

To see the zones in your default region:

gcloud compute zones list --filter="region:($(gcloud config get-value compute/region))" --format="value(name)"

You’ll see output showing the specific zone identifiers (the exact number and names depend on your region):

us-central1-a
us-central1-b
us-central1-c
us-central1-f

To count how many zones are available in your region:

gcloud compute zones list --filter="region:($(gcloud config get-value compute/region))" --format="value(name)" | wc -l

The number of zones varies by region, depending on how GCP has built out infrastructure in that location over time. When you design applications for high availability, you typically deploy identical resources in multiple zones. If one zone experiences problems, your application continues running in the other zones.

Understanding how different regions compare helps you make informed decisions about where to deploy your applications. Let’s explore a few major regions and save our findings.

To compare the number of zones across different regions, specify the region explicitly:

gcloud compute zones list --filter="region:(us-central1)" --format="value(name)" | wc -l
gcloud compute zones list --filter="region:(us-east1)" --format="value(name)" | wc -l
gcloud compute zones list --filter="region:(europe-west1)" --format="value(name)" | wc -l

You’ll see different counts for each region, reflecting how GCP has built out infrastructure in different regions over time. Older, more established regions often have more zones.

Now let’s save these discoveries to a JSON file for future reference:

cat > my_gcp_setup.json << EOF
{
    "date": "$(date -I)",
    "default_region": "$(gcloud config get-value compute/region)", 
    "default_zone": "$(gcloud config get-value compute/zone)",
    "total_regions": $(gcloud compute regions list --format="value(name)" | wc -l),
    "my_region_zones": $(gcloud compute zones list --filter="region:($(gcloud config get-value compute/region))" --format="value(name)" | wc -l)
}
EOF

This command creates a JSON file containing key information about your GCP setup. The resulting file will contain current values that reflect GCP’s infrastructure at the time you run the command:

{
    "date": "2024-01-15",
    "default_region": "us-central1", 
    "default_zone": "us-central1-a",
    "total_regions": 18,
    "my_region_zones": 4
}

Saving your infrastructure discoveries becomes valuable when planning deployments, comparing options over time, or documenting your GCP environment for team members.

Understanding how to interpret the output from your GCP infrastructure exploration commands is crucial for making informed decisions about your deployments.

When you see that one region has more zones than another, this doesn’t necessarily mean the region with more zones is “better.” Most high-availability architectures work well with just a few zones. What matters is having at least two zones available for basic redundancy patterns.

The total region count represents all regions currently available to your GCP account. Some regions might have restricted access or limited feature availability. This number grows over time as GCP adds new regions.

Common pitfalls can cause confusion when exploring GCP infrastructure. The most frequent issue occurs when you don’t have a default region or zone configured. If gcloud config get-value compute/region or gcloud config get-value compute/zone returns nothing, you’ll need to set a default region and zone using:

gcloud config set compute/region us-central1
gcloud config set compute/zone us-central1-a

Permission issues can also cause problems. If you see "PERMISSION_DENIED" or similar errors, your GCP account may not have the necessary permissions to list regions or zones. In production environments, you might need to request additional permissions from your GCP administrator.

Network connectivity issues can cause commands to time out or fail. If you encounter connection errors, wait and retry. The gcloud CLI includes automatic retry logic for transient failures.

When you run the complete exploration script, validate that the generated JSON file contains reasonable values. Your default region and zone should be valid GCP identifiers, the total regions count should reflect the current number of GCP regions (which grows over time), and your region’s zone count should be at least two. If any values seem incorrect, re-run the individual commands to identify the issue.

In this lesson, you gained hands-on experience exploring GCP's global infrastructure using the gcloud CLI. You learned to discover your default region and zone with gcloud config get-value, list all available GCP regions, and examine zones within any region.

You now understand that regions are geographically distributed areas containing multiple zones, and you can use gcloud commands to filter and display output. You also learned to save your infrastructure discoveries to JSON files for future reference.

These gcloud CLI skills form the foundation for programmatically managing GCP resources and making informed decisions about region selection based on actual infrastructure availability.

Remember: In this course, you've been working with a mock gcloud CLI that simulates real GCP responses. When you work with an actual GCP account, you'll need to authenticate and configure the real gcloud CLI, but the commands and concepts you've learned here will work exactly the same way.