This page provides an overview of bringing your own license (BYOL) to Compute Engine using sole-tenant nodes and the in-place restart feature. Before getting started, please review your licensing terms and conditions to confirm that you meet the licensing requirements to bring your own license to Compute Engine. For step-by-step instructions, read the how-to guide to bringing your own license.
If you have existing operating system licenses, you can bring them to Compute Engine using sole-tenant nodes and the in-place restart feature. Sole-tenant nodes are physical Compute Engine servers that are dedicated to hosting VM instances only for your specific project; that is, these servers are dedicated to just your workloads. When you enable the in-place restart feature on sole-tenant nodes, Compute Engine will also restart your node VMs on the same physical server instead of live migrating to a new physical server during host maintenance events. If that is not possible (for example, if the physical server is no longer available), then the VM is restarted on another server and Compute Engine reports the new physical server ID.
By using sole-tenant nodes with in-place restarts, you expose your VMs to a minimal number of physical servers to support potential hardware requirements for licenses. Please note that VMs on your server will experience outages while maintenance is applied.
Hosting instances on sole-tenant nodes provides the following benefits:
- Ensures your VMs run on hardware that is exclusively dedicated to your project.
- Minimizes the number of physical servers your VM instances will touch during maintenance events.
- Allows you to track per-socket and per-core usage that might be required for license reporting purposes.
- Gives you control over node placement so that your VMs can be scheduled on a specific sole-tenant node or scheduled across a set of matching nodes.
- Supports server usage reporting, where Compute Engine will report when instances are created or deleted on a specific server using a server ID. This information can be combined with the server's physical characteristics to determine information for license usage.
- Bring your own licenses for Windows Server and Windows Client.
For Windows applications such as SharePoint Server, MS Exchange Server, and so on, existing application licenses can be deployed on Google Cloud Platform using License Mobility instead. See the Frequently Asked Questions for details.
Compatible OS versions
Compute Engine's current image import workflow has been tested for compatibility with the following OS versions.
- Windows Server 2008 R2 SP1, 2012, 2012 R2, 2016
- Windows 7 SP1 x64, 10 Enterprise x64
If you are looking to use Windows 7 SP1 or Windows 2008 R2, your image must support SHA2 signing as Compute Engine drivers are signed with SHA2. Additionally, certain agents from 3rd party cloud providers might interfere with the Compute Engine driver installation workflow and should be removed prior to import.
Pricing and availability
During Beta, this feature is available only in the following regions:
You will not be charged extra for bringing your own licenses to Compute Engine.
Licensing and activation
Before getting started with BYOL with sole-tenant nodes, please make sure that you understand your product licensing terms.
You must also prepare your guest image for BYOL according to your agreements. If you use Compute Engine public images, Google Cloud Platform's (GCP) pay-as-you-go licenses will be attached to VM instances that use these images and you cannot update the VM to use your own licenses later.
Unlike premium images where Compute Engine will take care of license activation, imported images require that you own the license activation process. It is not possible to activate licenses against Compute Engine's license server. As such, you are responsible for preparing infrastructure for activation, such as a KMS server and network connection, and activating your licenses.
During Beta, we strongly recommend reviewing the following information to help you determine the best workload for this feature.
This feature adds the ability to enable in-place restarts for your VM instances running on sole-tenant nodes. This means that, during maintenance events, instead of live migrating a running instance to another machine and exposing your license to another physical server, the instance is terminated and restarted on the same physical server whenever possible. If that server is no longer available, Google restarts your VMs on a new dedicated server and reports the server ID.
Google performs an average of one maintenance event a month, which means the VMs on your server will experience an outage while maintenance is applied. Each event lasts about 60 minutes each, though this could vary depending on the situation, such as type of maintenance, whether it is a patching event, and so on.
Because of this expected downtime, Google recommends using workloads that are tolerant of the downtime associated with these maintenance events.
Physical server migration
From time to time, Compute Engine might need to retire a physical server
and move your VMs to a new underlying server. During these situations,
Compute Engine will restart your VMs on a new physical server and
assign a new sole-tenant physical server ID. The VMs will be restarted on the
newly-provisioned physical server if the user sets the following VM property
--restart-on-failure) for it. Once this happens, the previous sole tenant
physical server ID will not be reused.