[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-09-04 (世界標準時間)。"],[],[],null,["# VMware Engine node types\n========================\n\nA Google Cloud VMware Engine private cloud is a collection of vSphere clusters created\nwith a set of dedicated isolated bare metal hardware nodes in a region. These\nnodes provide the compute, memory, and storage required to run VMware ESXi, and\nare the basic unit of consumption of VMware Engine. This document details the\nnode types, their resource capacity and availability in the regions.\n\nA vSphere cluster must have nodes with identical storage. Google Cloud VMware Engine\nallows creation of a cluster with a mix of hyperconverged infrastructure (HCI)\nand storage only node types. You can create a cluster with `ve2-standard-128`\nand `ve2-standard-so` node types, but not mix two different HCI node types.\n\nNode types\n----------\n\nThe following sections list node types that are available when creating a\nVMware Engine private clouds or clusters.\n\n### Hyperconverged node types\n\nThe following table lists HCI node types that are available when creating a\nVMware Engine private cloud or a cluster. \n\n### Storage-only node types\n\nThe following table lists storage-only node types that are available when\ncreating a VMware Engine private cloud or cluster. \n\n\n^\\*^ Raw storage excluding cache. \n\n^†^ Available in select regions.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nRegion availability\n-------------------\n\nThe following table lists the regional availability of Google Cloud VMware Engine node\ntypes. \n\nNode identification\n-------------------\n\nEach VMware Engine private cloud has a `nodeTypeId` that's\navailable as soon as you create a VMware Engine private cloud. Retrieve\nthe `nodeTypeId` with the\n[`projects.locations.nodeTypes.get`](/vmware-engine/docs/reference/rest/v1/projects.locations.nodeTypes/get)\nREST request.\n\nNode billing\n------------\n\nThere are two options for paying for VMware Engine nodes: On-demand and\ncommitment. When you provision a VMware Engine node, you control the\nVMs on that host. For more information about pricing, see [VMware Engine pricing](/vmware-engine/pricing).\n\n### Node commitments\n\nYou can purchase VMware Engine nodes with a one- or three-year\n[committed use discount](/vmware-engine/docs/cud) (CUD) where you make a fixed\nmonthly payment, or you can pay for nodes as you use them. Once you purchase a\nCUD, you can't cancel it. For more information about pricing, see [VMware Engine pricing](/vmware-engine/pricing).\n\n### Purchasing nodes as CAPEX or OPEX\n\nGoogle does not provide guidance about accounting. Review the details about the\nVMware Engine node product and seek guidance from your Controllership team and\nauditors before you make any accounting decisions regarding CAPEX or OPEX.\n\nNode maintenance\n----------------\n\nIf a node fails, VMware Engine immediately and automatically adds a new\nnode to the affected VMware cluster to restore service operability. VMware Engine\nalso sends an email to the primary address notifying you about the replacement of\nthe failed node and the name of the private cloud. For more information about\nmaintenance, see [Private cloud maintenance and updates](/vmware-engine/docs/concepts-maintenance-updates).\n\nWhat's next\n-----------\n\n- Learn about [bringing images with existing licenses to Google Cloud](/vmware-engine/docs/vmware-ecosystem/microsoft-licensing#bring-licenses).\n- Learn about [VLANs and subnets](/vmware-engine/docs/concepts-vlans-subnets)."]]