Opinie (Networking 102)

3882 opinie

nunzio s. · Sprawdzono ponad 7 lat temu

Good lab for concepts illustration. However, there are definitely some rooms for improvements that could make this illustration much smoother learning experience for the first timer. Currently, the disconnects throughout the lab instruction will make it a less productive experience, especially given the amount of time allocated per lab. Optional tasks are great but it does not have the proper time allocated. Please see below for itemized improvement areas. 0. The network Diagram. The network diagrams are incomplete because it didn’t include the VPC network privatenet, in addition, it didn’t indicates the two VM instances that were referenced in the procedure; private-bastion, and privatenet-us-vm. Network diagram is one of the most important key in networking, it needs to be accurate. 1. Typos and disconnects. 1.1 Confusing explanation with incorrect info at Overview section. Specifically, the sentence in “The MyProject environment includes 2 Networks with 8 auto Subnetworks each (1 for each Region) and 1 Network with 1 Custom Subnetwork.” 8 auto subnetwork is incorrect based on the network diagram, it should be 6; us-central1, europe-west1, us-west1, us-east1, asia-east1, and asia-northeast1. It may even help in explaining what those referenced networks and subnetworks are. For example, 2 networks (default and mynetwork) with 6 auto subnetwork each (1 for each Region) and 1 Network (privatenet) with 1 Custom Subnetwork (privatesubnet; 10.0.0.0/24). It was kind of confusing when reading thru this section for the first time with the network diagram that does not include the reference VPC network (privatenet) and its subnetwork(privatesubnet). Also, the inclusion of specific zone in the network diagram will significantly improves the lab, imo. Such as private-net-bastion and privatenet-us-vm are both in the us-central1- region at us-central1-c zone …etc. 1.2 Incorrect VPC network reference in the lab instruction. In the “ Create Virtual Private Cloud (VPC) Networks and Instances” section, there is an inconsistency typo; “Run the following to create the network mynet with auto subnets:” The “mynet” should be consistent with the gcloud CLI configuration below. gcloud compute networks create mynetwork --subnet-mode=auto Currently, the instruction stated mynet while the configuration CLI is configuring it as mynetwork. This is a small inconsistency here that may introduce some unnecessary confusion later, depending on which configuration used. 1.3 Unable to delete the Default network. In the “Delete the Default network” section, this step cannot be complete. I am not fully sure what’s causing it, perhaps, it’s because of the two separate ProjectIDs that were assign to this single lab; ProjectID1 and ProjectID2? The error that I received when trying to delete the default is “The network resource project ‘ProjectID1’ is already being used by ‘ProjectID1’ 1.4 Content accuracy verification 1. In “Deny/Egress Rules” section, the “Note: This rule was created with the direction EGRESS. Since ping is a bi-directional protocol, this will block ICMP as traffic leaves the VMs virtual NIC. If this rule were to be created with the INGRESS direction, the ICMP packets would be allowed to leave the VM's virtual NIC.” The Egress FW is not a nic scope concept, it’s more like a subnetwork scope. If we have created another VM say mynet-us-vm2 in different zone in us-central1-c, we still won’t be able to ping the mynet-eu-vm from mynet-us-vm2. So, the NIC inference here is not exactly correct. 1.5 Content accuracy verification 2 In the “Convert to a NAT gateway” section, “You can see that none of these commands succeeds (all needed a Ctrl +c to abort).”, is incorrect. 2 out of the 4 commands will succeed, not “none of these command will succeed.” The one that has GCP internal scope will succeed; the gustil CLIs. 1.6 “Optional: Give IAM role to a buddy” section needs improvement. projectID needs to be set in order to perform the task. It may be worth the time to mention which projectID should we use; projectID1 or ProjectID2. The ProjectID2’s purpose remains unclear to me. So, overall, good lab for concepts illustration, but a review on content accuracy and consistency will greatly improve the lab. Currently, with the time allocated, it will be quite challenging to try to go thru the whole lab and sink in all concepts while trying to identify the typos and inconsistency, with only 1 hours 25 minutes allocated.. Have a good one. Warm Regards, Kenny

Tgo168 C. · Sprawdzono ponad 7 lat temu

Sarah C. · Sprawdzono ponad 7 lat temu

laboratorio terminado

Hebert Erland C. · Sprawdzono ponad 7 lat temu

Awesome

Kyohei T. · Sprawdzono ponad 7 lat temu

Jorge L. · Sprawdzono ponad 7 lat temu

Nalin G. · Sprawdzono ponad 7 lat temu

Kiran A. · Sprawdzono ponad 7 lat temu

Sahil S. · Sprawdzono ponad 7 lat temu

David P. · Sprawdzono ponad 7 lat temu

Alessandro R. · Sprawdzono ponad 7 lat temu

Jose Carlos A. · Sprawdzono ponad 7 lat temu

sajith m. · Sprawdzono ponad 7 lat temu

Diego B. · Sprawdzono ponad 7 lat temu

Ferdinand L. · Sprawdzono ponad 7 lat temu

David P. · Sprawdzono ponad 7 lat temu

Manikandan N. · Sprawdzono ponad 7 lat temu

nice to practice

Purnachandra D. · Sprawdzono ponad 7 lat temu

Srinivasa G. · Sprawdzono ponad 7 lat temu

Patrick M. · Sprawdzono ponad 7 lat temu

First L. · Sprawdzono ponad 7 lat temu

Ravindra R. · Sprawdzono ponad 7 lat temu

Pium S. · Sprawdzono ponad 7 lat temu

Thanks.

Awadhesh P. · Sprawdzono ponad 7 lat temu

Corinna F. · Sprawdzono ponad 7 lat temu

Nie gwarantujemy, że publikowane opinie pochodzą od konsumentów, którzy dane produkty kupili lub ich używali. Google nie weryfikuje opinii.