{"id":13040,"date":"2018-06-12T13:43:01","date_gmt":"2018-06-12T12:43:01","guid":{"rendered":"http:\/\/www.devopsonline.co.uk\/?p=13040"},"modified":"2018-06-12T13:49:25","modified_gmt":"2018-06-12T12:49:25","slug":"sole-tenant-nodes-to-google-clouds-rescue","status":"publish","type":"post","link":"https:\/\/devopsnews.online\/sole-tenant-nodes-to-google-clouds-rescue\/","title":{"rendered":"Sole-tenant nodes to Google Cloud’s rescue"},"content":{"rendered":"

In a bid to put Google in line with Amazon and Microsoft, Google Cloud has announced that it’s using sole-tenant nodes in its Compute Engine to help customers run multiple instances of various sizes without sharing hardware hosts with other projects.<\/p>\n

In regards to compliance regulations, the cloud giant hopes that the sole-tenant nodes will help regulated industries separate their compute resources in the cloud.<\/p>\n

Accommodating virtual machines<\/h2>\n

The\u00a0n1-node-96-624<\/code>node type is available in multiple\u00a0zones, and has\u00a096 vCPUs and 624 GB of system memory.<\/p>\n

The node size can accommodate virtual machine (VM) instances with up to 96 vCPUs and 624 GB of system memory, and customers will be able to fill the node with multiple smaller VM instances with various sizes including\u00a0custom machine types<\/a>\u00a0and instances via\u00a0extended memory<\/a>.<\/p>\n

The instances that the nodes are run on must have at least two vCPUs, and when a node is full, customers will not be able to schedule additional instances.<\/p>\n

Compute Engine features<\/h2>\n

According to Google Cloud’s blog post, the sole-tenant nodes are compatible with the existing Compute Engine features:<\/p>\n