Deploying and Implementing Networking Resources
Deploying and Implementing Compute Engine Resources
This course has been designed to teach you how to deploy network and compute resources on Google Cloud Platform. The content in this course will help prepare you for the Associate Cloud Engineer exam.
- To understand key networking and compute resources on Google Cloud Platform
- Be able to explain different networking and compute features commonly used on GCP
- Be able to deploy key networking and compute resources on Google Cloud Platform
- Those who are preparing for the Associate Cloud Engineer exam
- Those looking to learn more about GCP networking and compute features
To get the most from this course then you should have some exposure to GCP resources, such as VPCs and Compute Instances. However, this is not essential.
When adding storage to a compute instance, you have a choice of a few different disk types. You can add zonal persistent disks, regional persistent disks or you can add local SSDs.
Zonal persistent disks are available as either standard hard disk drives or solid state drives. The compute engine actually manages the hardware underneath the zonal persistent disks so they can be added and resized without the need to deal with striping or redundancy. I should also note that unless you're creating a new zonal persistent disk from an image, the disk will start with no data or file system. That being said, you'll have to format any new disk after you attach it to an instance.
Regional persistent disks are like zonal persistent disks but different in a few ways. For example, regional persistent disks cannot be used as boot disks. In addition, regional persistent disks support force attachment to another VM instance in the event of a zonal failure. It's also important to note that you can create a regional persistent disk from snapshots but not from images. Local SSD disks, unlike persistent disks, are physically attached to the server that hosts the virtual machine instance. This configuration offers superior performance to persistent disks, higher IOPS than persistent disks, and very low latency when compared to persistent disks.
Earlier on, you learned how to deploy a compute instance. During the demonstration, I showed you how to add a second disk to the VM. The process for adding a disk to an insisting VM is essentially the same as it is when provisioning a new instance. So I'm not going to drag you through another demo just to show you how to add a disk to an existing instance. Just refer to the VM deployment demo to see how to add a disk to a VM instance.
About the Author
Tom is a 25+ year veteran of the IT industry, having worked in environments as large as 40k seats and as small as 50 seats. Throughout the course of a long an interesting career, he has built an in-depth skillset that spans numerous IT disciplines. Tom has designed and architected small, large, and global IT solutions.
In addition to the Cloud Platform and Infrastructure MCSE certification, Tom also carries several other Microsoft certifications. His ability to see things from a strategic perspective allows Tom to architect solutions that closely align with business needs.
In his spare time, Tom enjoys camping, fishing, and playing poker.