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, I'm going to talk about instance groups. An instance group is actually a collection of VM instances. The key advantage of an instance group, however, is the ability to manage all of the instances as a single entity. Google Compute Engine offers two kinds of VM instance groups. They include managed instance groups, or MIGs, and unmanaged instance groups.
Using a managed instance group allows you to run applications on several identically configured virtual machines. Additionally, a managed instance group offers several automated services such as autoscaling, auto-healing, regional deployment, and auto updating. By leveraging the many automated services that are offered by a managed instance group, you can make workload scalable and highly available.
Typically you'd want to use a managed instance group for stateless workloads, like maybe a website frontend. Managed instance groups are also a good choice for high-performance workloads and batch workloads, such as image processing from a queue. It's important to note that each VM instance within a managed instance group is created from an instance template. If you prefer - or need - to load balance apps across a fleet of virtual machines that you need to manage yourself, you might want to consider unmanaged instance groups.
An unmanaged instance group contains multiple heterogeneous VM instances. You can, as needed, add and remove instances from the group. As you would expect, an unmanaged instance group does not offer any of the features that a managed instance group provides. You get no autoscaling, no auto-healing, and no rolling update support. As a rule of thumb, you should only consider using unmanaged instance groups if you need to apply load balancing to groups of heterogeneous instances, or if you need to manage the instances within the group yourself.
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.