GCP Fundamentals: Primeiros passos com Deployment Manager e Cloud Monitoring avaliações

205093 avaliações

IbrahimMohamed I. · Revisado há almost 6 years

Christopher T. · Revisado há almost 6 years

Alberto G. · Revisado há almost 6 years

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. · Revisado há almost 6 years

Kyle G. · Revisado há almost 6 years

Gautham C. · Revisado há almost 6 years

Juan F. · Revisado há almost 6 years

Sindhusha G. · Revisado há almost 6 years

Lasith N. · Revisado há almost 6 years

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

Kirk R. · Revisado há almost 6 years

Shane M. · Revisado há almost 6 years

Jani T. · Revisado há almost 6 years

Jagdeep S. · Revisado há almost 6 years

Sreenivas V. · Revisado há almost 6 years

Werner Oscar T. · Revisado há almost 6 years

Fernando Ignacio P. · Revisado há almost 6 years

Srinivasa P. · Revisado há almost 6 years

Rick K. · Revisado há almost 6 years

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. · Revisado há almost 6 years

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. · Revisado há almost 6 years

James B. · Revisado há almost 6 years

Anthony G. · Revisado há almost 6 years

Yuriy P. · Revisado há almost 6 years

Rohan K. · Revisado há almost 6 years

Danilov S. · Revisado há almost 6 years

Não garantimos que as avaliações publicadas sejam de consumidores que compraram ou usaram os produtos. As avaliações não são verificadas pelo Google.