Creating a VM instance in GCP - Try It Yourself

Creating a VM instance

📖 Scenario: You are setting up a simple virtual machine (VM) instance on Google Cloud Platform (GCP) to host a small website. This VM will run a basic Linux operating system.

🎯 Goal: Create a VM instance on GCP with a specific name, machine type, and image. Configure it to allow HTTP traffic.

📋 What You'll Learn

Create a VM instance named my-vm-instance

Use the machine type e2-micro

Use the image family debian-11 from the debian-cloud project

Allow HTTP traffic to the VM

💡 Why This Matters

🌍 Real World

Creating VM instances is a common task when deploying applications or websites on cloud platforms like GCP.

💼 Career

Cloud engineers and developers often need to configure and launch VM instances with specific settings to meet application requirements.

1

Define the VM instance name

Create a variable called instance_name and set it to the string "my-vm-instance".

GCP

# Your code here

Hint

Use a simple string assignment to create the variable.

2

Set the machine type

Create a variable called machine_type and set it to the string "e2-micro".

GCP

instance_name = "my-vm-instance"
# Your code here

Hint

Assign the machine type as a string to the variable.

3

Specify the image family and project

Create two variables: image_family set to "debian-11" and image_project set to "debian-cloud".

GCP

instance_name = "my-vm-instance"
machine_type = "e2-micro"
# Your code here

Hint

Define both variables with the exact string values.

4

Create the VM instance configuration dictionary

Create a dictionary called vm_config with keys and values: "name" set to instance_name, "machineType" set to machine_type, "imageFamily" set to image_family, "imageProject" set to image_project, and "allowHttp" set to True.

GCP

instance_name = "my-vm-instance"
machine_type = "e2-micro"
image_family = "debian-11"
image_project = "debian-cloud"
# Your code here

Hint

Use a dictionary with the exact keys and link the values to the variables you created.

Practice

1. What does creating a VM instance in Google Cloud allow you to do?

easy

A. Create a database

B. Store files permanently

C. Run a virtual computer in the cloud

D. Send emails automatically

Solution

1. Step 1: Understand VM instance purpose

   A VM instance is a virtual machine, like a computer inside the cloud.

2. Step 2: Identify correct function

   Running a virtual computer matches the VM instance role, unlike storing files or sending emails.

3. Final Answer:

   Run a virtual computer in the cloud -> Option C

4. Quick Check:

   VM instance = virtual computer [OK]

Hint: VM means virtual machine, a computer in the cloud [OK]

Common Mistakes:

• Confusing VM with storage service
• Thinking VM creates databases directly
• Assuming VM sends emails automatically

2. Which command correctly creates a VM instance named my-vm in zone us-central1-a with machine type e2-medium and image debian-11?

easy

A. gcloud create vm my-vm --zone us-central1-a --type e2-medium --image debian-11

B. gcloud compute vm create my-vm --zone=us-central1-a --machine-type=e2-medium --image debian-11

C. gcloud instances create --name my-vm --zone us-central1-a --machine e2-medium --image debian-11

D. gcloud compute instances create my-vm --zone=us-central1-a --machine-type=e2-medium --image-family=debian-11 --image-project=debian-cloud

Solution

1. Step 1: Check correct command structure

   The correct command starts with 'gcloud compute instances create' followed by the instance name.

2. Step 2: Verify flags and parameters

   Flags like '--zone', '--machine-type', '--image-family', and '--image-project' must be exact and use '=' sign.

3. Final Answer:

   gcloud compute instances create my-vm --zone=us-central1-a --machine-type=e2-medium --image-family=debian-11 --image-project=debian-cloud -> Option D

4. Quick Check:

   Correct gcloud syntax = gcloud compute instances create my-vm --zone=us-central1-a --machine-type=e2-medium --image-family=debian-11 --image-project=debian-cloud [OK]

Hint: Use 'gcloud compute instances create' with exact flags [OK]

Common Mistakes:

• Using wrong command verbs like 'create vm'
• Missing '=' in flags
• Wrong flag names like '--machine' instead of '--machine-type'

3. What will happen if you run this command?

gcloud compute instances create test-vm --zone=us-east1-b --machine-type=n1-standard-1 --image-family=ubuntu-2004-lts --image-project=ubuntu-os-cloud

medium

A. The command will fail due to missing machine type

B. A VM named test-vm will be created in zone us-east1-b with Ubuntu 20.04 OS

C. A VM will be created but with default image, not Ubuntu

D. The VM will be created in the wrong zone

Solution

1. Step 1: Analyze command parameters

   The command specifies instance name, zone, machine type, image family, and image project correctly.

2. Step 2: Understand image selection

   Using '--image-family=ubuntu-2004-lts' with '--image-project=ubuntu-os-cloud' selects Ubuntu 20.04 LTS image.

3. Final Answer:

   A VM named test-vm will be created in zone us-east1-b with Ubuntu 20.04 OS -> Option B

4. Quick Check:

   Correct flags create VM with specified OS [OK]

Hint: Image family + project picks correct OS image [OK]

Common Mistakes:

• Confusing image-family with image name
• Omitting image-project causes errors
• Wrong zone spelling

4. You tried to create a VM with:

gcloud compute instances create vm1 --zone=us-west1-c --machine-type=e2-small --image=debian-10

The command failed with an error about the image. What is the likely cause?

medium

A. The image name 'debian-10' is incorrect or deprecated

B. The zone 'us-west1-c' does not exist

C. The machine type 'e2-small' is invalid

D. You forgot to specify the project

Solution

1. Step 1: Check image parameter validity

   Using '--image=debian-10' is often invalid because images require full name or image family with project.

2. Step 2: Understand error cause

   Image errors usually mean the image name is wrong or deprecated, not zone or machine type.

3. Final Answer:

   The image name 'debian-10' is incorrect or deprecated -> Option A

4. Quick Check:

   Image errors = wrong image name [OK]

Hint: Use image family and project, not just image name [OK]

Common Mistakes:

• Assuming zone or machine type caused image error
• Not specifying image project with image family
• Using outdated image names

5. You want to create a VM instance that automatically allows HTTP traffic and uses a custom startup script to install software. Which command correctly achieves this?

hard

A. gcloud compute instances create web-vm --zone=us-central1-a --machine-type=e2-medium --image-family=debian-11 --image-project=debian-cloud --tags=http-server --metadata=startup-script='sudo apt-get update && sudo apt-get install -y nginx'

B. gcloud compute instances create web-vm --zone=us-central1-a --machine-type=e2-medium --image=debian-11 --allow-http --script='install nginx'

C. gcloud compute instances create web-vm --zone=us-central1-a --machine-type=e2-medium --image-family=debian-11 --image-project=debian-cloud --firewall=http --startup='apt-get install nginx'

D. gcloud compute instances create web-vm --zone=us-central1-a --machine-type=e2-medium --image=debian-11 --http --metadata=startup='install nginx'

Solution

1. Step 1: Enable HTTP traffic with tags

   Using '--tags=http-server' allows HTTP traffic via firewall rules.

2. Step 2: Add startup script correctly

   '--metadata=startup-script=' followed by the script installs nginx on startup.

3. Step 3: Verify image and machine type

   Using '--image-family=debian-11' and '--image-project=debian-cloud' is correct for Debian 11.

4. Final Answer:

   gcloud compute instances create web-vm --zone=us-central1-a --machine-type=e2-medium --image-family=debian-11 --image-project=debian-cloud --tags=http-server --metadata=startup-script='sudo apt-get update && sudo apt-get install -y nginx' -> Option A

5. Quick Check:

   Tags + metadata=startup-script = correct setup [OK]

Hint: Use --tags for HTTP and --metadata for startup script [OK]

Common Mistakes:

• Using wrong flags like --allow-http or --http
• Incorrect metadata key name
• Not specifying image project with image family