Automatiser le déploiement d'infrastructure avec Deployment Manager avis

Kamil O. · Examiné il y a presque 6 ans

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

Daniel A. · Examiné il y a presque 6 ans

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

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

another great lab

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

정환 승. · Examiné il y a presque 6 ans

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

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

In Cloud Shell (accessed from the GCP console), there's no reference to a "Code Editor" - you just get prompted to "Open Editor" - as I was using ChromeOS I got a warning about how the editor wouldn't "play nicely" Sure enough, as the lab progressed I found issues with indentation and cut/paste from the Lab instructions, this contributed to my failure to complete the Lab. Might need to attempt the Lab using a different device (not really a Qwiklabs issue though) I re-tried the Lab (using the same ChromeOS based device) and still encountered issues at the "deployment creation" stage - the instructions suggest trouble-shooting and it was clear enough that Deployment Manager was unable to parse either the config OR template files I'd edited. Although exactly whether it was one or both files was not clear from the console output (which I've copied below)... ERROR: (gcloud.deployment-manager.deployments.update) Error in Operation [operation-1602069902442-5b112f770be86-b3313db7-4ffef4f0]: errors: - code: MANIFEST_EXPANSION_USER_ERROR location: /deployments/dminfra/manifests/manifest-1602069902762 message: |- Manifest expansion encountered the following errors: while parsing a block mapping in "<unicode string>", line 2, column 3: - name: mynet-us-vm ^ expected <block end>, but found '<block mapping start>' in "<unicode string>", line 6, column 6: zone: us-central1-a ^ Resource: config ....so I resorted to uploading the sample files into the Lab's CloudShell VM and renamed them to configQW.yaml and instance-templateQW.jinja respectively. The deployment then worked OK using the uploaded files (as expected) so a quick browse of the uploaded files indicated blank lines between the different resource entries in the yaml file whilst the indentations in the updated template file didn't match how they were rendered by my Chrome browser in the Lab instructions

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

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

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

lilianlhli l. · Examiné il y a presque 6 ans

Harsh D. · Examiné il y a presque 6 ans

Nicholas O. · Examiné il y a presque 6 ans

Kingsley Ikechukwu O. · Examiné il y a presque 6 ans

lilianlhli l. · Examiné il y a presque 6 ans

Harsh D. · Examiné il y a presque 6 ans

Good

Ayodeji O. · Examiné il y a presque 6 ans

Jonathan E. · Examiné il y a presque 6 ans

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

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

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

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