VM Manager is a suite of tools that can be used to manage operating systems for large virtual machine (VM) fleets running Windows and Linux on Compute Engine.
VM Manager helps drive efficiency through automation and reduces the operational burden of maintaining these VM fleets.
VM Manager supports projects in VPC Service Controls service perimeters.
The following services are available as part of the VM Manager suite:
- OS patch management: use this service to apply on-demand and scheduled patches. You can also use OS patch management for patch compliance reporting in your environment.
- OS inventory management: use this service to collect and review operating system information.
- OS configuration management: use this service to install, remove, and auto-update software packages.
Figure 1 provides an high level overview of VM Manager.
When you set up or enable VM Manager in your Cloud project, you can access the full suite of VM Manager tools: OS patch management, OS configuration management, and OS inventory management.
VM Manager enablement
You can set VM Manager to be automatically enabled or manually enabled. Automatic enablement applies to your entire project. Manual enablement can be done per VM or for the entire project.
In summary, when you enable VM Manager, whether automatically or manually, the following setup takes place:
- OS Config service API and Container Analysis API are enabled on the Google Cloud project.
The OS Config agent, running on each selected VM, is activated by setting the required instance metadata values.
For more information about manually enabling VM Manager, see Setup overview.
Automatic enablement is done from the Google Cloud Console.
OS Config agent
When VM Manager is enabled, the OS Config agent functions as follows for each of the services:
- For OS patch management, the OS Config agent uses OS system utilities
rpmor the Windows Update Agent) to retrieve patches or updates from the OS package or update source and apply them to the VM. For more information, see How OS patch management works.
- For OS configuration management, the OS Config agent uses OS system
utilities (such as
rpmor the Windows Update Agent) to maintain the state for the VM that is specified in the guest policy. For more information, see How OS guest policies work.
- For OS inventory management, the OS Config agent collects
This inventory data that is then stored in the
instance metadata and in various
log streams. This data can then be queried using the
gcloudcommand-line tool. For more information, see How OS inventory management works.
OS packages and update source
For both OS patch management and OS configuration management, your VMs must be able to access package sources and repositories. For VMs in private networks, you can set up Private Google Access.
The entire VM Manager suite is charged as a single service at one flat rate per VM with an active OS Config agent.
You incur charges per the number of VMs that have an active OS Config agent as follows:
- To get started with testing in your environment a free tier is available. This free tier provides a monthly usage of 100 VMs per Cloud Billing account.
- Once the free tier is exhausted, for all VMs that have an active OS Config agent, each active agent is charged at a rate of $0.003 per hour per VM.
The following table summarizes the units and formulas that can be used to determine the total charges.
|Item||Cost/unit (cost in USD)|
|Hourly cost (per VM with an active agent)||$0.003|
|Monthly usage discount (per Cloud Billing account)||
Fixed number of free VMs = 100 |
Monthly usage formula = (number of hours in the month * number of free VMs)
For example, in a 31 days month = 744 * 100 = 74,400 active agent hours
The following examples are calculated in USD.
If you are running 10 VMs in a 31 day month (744 hours) that have an active OS Config agent, using the formula from the preceding table, the calculations are as follows:
Free tier = 74,400 agent hours Monthly usage = 744 * 10= 7,440 agent hours
Monthly usage is less than the free tier, so the adjusted monthly usage is 0 agent hours, and the total monthly cost is $0.
If you are running 100 VMs in a 31 day month (744 hours) that have an active OS Config agent, using the formulas from the preceding table, the calculations are as follows:
Free tier = 74,400 agent hours Monthly usage = 744 * 100 = 74,400 agent hours
Monthly usage is equal to the free tier so the adjusted monthly usage is 0 agent hours, and the total monthly cost is $0.
If you are running 700 VMs in a 31 day month (744 hours) that have an active OS Config agent, using the formulas from the preceding table, the calculations are as follows:
Free tier = 74,400 agent hours Monthly usage = 744 * 700 = 520,800 agent hours
Monthly usage is greater than the free tier so the adjusted monthly usage is (520,800 - 74,400) = 446,400 agent hours.
After the introductory period, the monthly cost is calculated as follows:
Monthly cost = $0.003 * number of active agents that exceed the free tier = $0.003 * 446,400 = $1339.20