Managing Network Resources
Managing Compute Engine Resources
This course has been designed to teach you how to manage networking and compute resources on Google Cloud Platform. The content in this course will help prepare you for the Associate Cloud Engineer exam.
The topics covered within this course include:
- Adding subnets to a VPC
- Expanding existing subnets
- Reserving static addresses via the console and Cloud Shell
- Managing, configuring, and connecting to VM instances
- Adding GPUs and installing CUDA libraries
- Creating and deploying from snapshots and images
- Working with instance groups
- Learn how to manage networking and compute resources on Google Cloud Platform
- Prepare for the Google Associate Cloud Engineer Exam
- Those who are preparing for the Associate Cloud Engineer exam
- Those looking to learn more about managing GCP networking and compute features
To get the most from this course, you should have some exposure to GCP resources, such as VCPs, VM Instances, Cloud Console, and Cloud Shell. However, this is not essential.
Hi, everyone, and welcome to this lecture. In this lecture, we're going to cover instance templates. Instance templates are used to create VM instances and manage instance groups. When you create an instance template, what you're really doing is defining the machine type, the boot disk image, the container image, if necessary, any labels, and any other properties that will be used to deploy your instance or instance group.
Once the instance template settings are defined, you can use the template to create either a managed instance group or to create individual VM instances. The purpose of an instance template is to facilitate the creation of identically configured instances. That being the case, it's not possible to update or change an existing instance template once it's been created. If you need to make changes to a configuration, you need to create a new instance template.
It's important to note that instance templates are global resources; they are not bound to a specific zone nor to a specific region. However, when you create an instance template, you may need to specify some zonal resources. This, in essence, restricts the template to whatever zone in which those zonal resources reside. For example, if an instance template includes a persistent disk from the US-Central-1A zone, you won't be able to use that instance template in any other zone since the disk exists only in zone US-Central-1A.
Join me in the next lesson where I'll show you how to create and assign an instance template.
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.