Google Cloud Fundamentals: Getting Started with Deployment Manager and Cloud Monitoring Reviews

IbrahimMohamed I. · Reviewed almost 6 years ago

Christopher T. · Reviewed almost 6 years ago

Alberto G. · Reviewed almost 6 years ago

There were two issues with this lab. Initially the project ID was not set up in the $DEVSHELL_PROJECT_ID variable so I had to set it and do that section over. Secondly the instructions for setting up the CPU monitoring does not match the current UI.

James P. · Reviewed almost 6 years ago

Kyle G. · Reviewed almost 6 years ago

Gautham C. · Reviewed almost 6 years ago

Juan F. · Reviewed almost 6 years ago

Sindhusha G. · Reviewed almost 6 years ago

Lasith N. · Reviewed almost 6 years ago

some errors again at the vary last step of launching the cpu monitoring, but the lab completed anyway.

Kirk R. · Reviewed almost 6 years ago

Shane M. · Reviewed almost 6 years ago

Jani T. · Reviewed almost 6 years ago

Jagdeep S. · Reviewed almost 6 years ago

Sreenivas V. · Reviewed almost 6 years ago

Werner Oscar T. · Reviewed almost 6 years ago

Fernando Ignacio P. · Reviewed almost 6 years ago

Srinivasa P. · Reviewed almost 6 years ago

Rick K. · Reviewed almost 6 years ago

This lab is broken. Despite entering the sed command to declare the zone, it is being overwritten and not applying on the YAML file which causes the lab to fail as you can see from the code below. student_00_1e3c0da0253c@cloudshell:~ (qwiklabs-gcp-00-589e997e1ca0)$ sed -i -e "s/qwiklabs-gcp-00-589e997e1ca0/$DEVSHELL_PROJECT_ID/" mydeploy.yaml student_00_1e3c0da0253c@cloudshell:~ (qwiklabs-gcp-00-589e997e1ca0)$ sed -i -e "s/us-central1-a/$MY_ZONE/" mydeploy.yaml student_00_1e3c0da0253c@cloudshell:~ (qwiklabs-gcp-00-589e997e1ca0)$ cat mydeploy.yaml resources: - name: my-vm type: compute.v1.instance properties: zone: ZONE machineType: zones/ZONE/machineTypes/n1-standard-1 metadata: items: - key: startup-script value: "apt-get update" disks: - deviceName: boot type: PERSISTENT boot: true autoDelete: true initializeParams: sourceImage: https://www.googleapis.com/compute/v1/projects/debian-cloud/global/images/debian-9-stretch-v20180814 networkInterfaces: - network: https://www.googleapis.com/compute/v1/projects/PROJECT_ID/global/networks/default accessConfigs: - name: External NAT type: ONE_TO_ONE_NAT

Eric S. · Reviewed almost 6 years ago

Had issues with SSH'ing into my vm as part of the lab. It complained and suggested to connected direct without IAP. It worked after using that option.

Joey W. · Reviewed almost 6 years ago

James B. · Reviewed almost 6 years ago

Anthony G. · Reviewed almost 6 years ago

Yuriy P. · Reviewed almost 6 years ago

Rohan K. · Reviewed almost 6 years ago

Danilov S. · Reviewed almost 6 years ago