GCP Fundamentals : Premiers pas avec Deployment Manager et Cloud Monitoring avis

IbrahimMohamed I. · Examiné il y a presque 6 ans

Christopher T. · Examiné il y a presque 6 ans

Alberto G. · Examiné il y a presque 6 ans

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. · Examiné il y a presque 6 ans

Kyle G. · Examiné il y a presque 6 ans

Gautham C. · Examiné il y a presque 6 ans

Juan F. · Examiné il y a presque 6 ans

Sindhusha G. · Examiné il y a presque 6 ans

Lasith N. · Examiné il y a presque 6 ans

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

Kirk R. · Examiné il y a presque 6 ans

Shane M. · Examiné il y a presque 6 ans

Jani T. · Examiné il y a presque 6 ans

Jagdeep S. · Examiné il y a presque 6 ans

Sreenivas V. · Examiné il y a presque 6 ans

Werner Oscar T. · Examiné il y a presque 6 ans

Fernando Ignacio P. · Examiné il y a presque 6 ans

Srinivasa P. · Examiné il y a presque 6 ans

Rick K. · Examiné il y a presque 6 ans

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. · Examiné il y a presque 6 ans

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. · Examiné il y a presque 6 ans

James B. · Examiné il y a presque 6 ans

Anthony G. · Examiné il y a presque 6 ans

Yuriy P. · Examiné il y a presque 6 ans

Rohan K. · Examiné il y a presque 6 ans

Danilov S. · Examiné il y a presque 6 ans