Opinie (Automating the Deployment of Infrastructure Using Deployment Manager)

Kamil O. · Sprawdzono prawie 6 lat temu

Jason B. · Sprawdzono prawie 6 lat temu

Daniel A. · Sprawdzono prawie 6 lat temu

Thouseefuddin M. · Sprawdzono prawie 6 lat temu

Tilak B. · Sprawdzono prawie 6 lat temu

another great lab

Ashton N. · Sprawdzono prawie 6 lat temu

정환 승. · Sprawdzono prawie 6 lat temu

Alisher B. · Sprawdzono prawie 6 lat temu

Adebiyi T. · Sprawdzono prawie 6 lat temu

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. · Sprawdzono prawie 6 lat temu

Denis P. · Sprawdzono prawie 6 lat temu

Thouseefuddin M. · Sprawdzono prawie 6 lat temu

lilianlhli l. · Sprawdzono prawie 6 lat temu

Harsh D. · Sprawdzono prawie 6 lat temu

Nicholas O. · Sprawdzono prawie 6 lat temu

Kingsley Ikechukwu O. · Sprawdzono prawie 6 lat temu

lilianlhli l. · Sprawdzono prawie 6 lat temu

Harsh D. · Sprawdzono prawie 6 lat temu

Good

Ayodeji O. · Sprawdzono prawie 6 lat temu

Jonathan E. · Sprawdzono prawie 6 lat temu

Thouseefuddin M. · Sprawdzono prawie 6 lat temu

Benoit M. · Sprawdzono prawie 6 lat temu

Ruwini S. · Sprawdzono prawie 6 lat temu

Jelena M. · Sprawdzono prawie 6 lat temu