您可以使用 Google Cloud 控制台、Google Cloud CLI 和 VMware Engine API 创建存储空间专用节点。存储节点不会为私有云和集群提供核心或内存,也无法运行虚拟机。您可以使用 Google Cloud CLI 和 VMware Engine API 查询集群中仅存储节点的数量。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-09-04。"],[],[],null,["# Storage-only nodes\n==================\n\nA storage-only node, also known as storage node, is a VMware Engine\nnode type that does not have any customer-usable cores and only has\ncustomer-usable storage. These nodes can be added to a cluster of\nVMware Engine hyper converged nodes to increase the storage capacity of\nthe cluster without adding cores to the cluster.\n| **Note:** A cluster can consist of a maximum of **50%** storage-only nodes. A dedicated cluster made up entirely of storage-only nodes is not supported because the workload VMs can't run on storage-only nodes.\n\nStorage-only nodes can only be added to a management cluster with a minimum of\nthree HCI nodes and a workload cluster that has at least two HCI nodes.\n\nStorage-only nodes are available using the Google Cloud console, Google Cloud CLI and\nVMware Engine API. The storage nodes don't contribute cores or memory to the\nprivate cloud and cluster and can't run VMs. You can use the Google Cloud CLI and\nVMware Engine API to query the number of storage-only nodes in a cluster.\n\nBy accessing the vCenter UI, you can identify which ESXi hosts are configured as\nstorage-only nodes by looking at tags assigned to ESXi hosts. You can query for\nthe tag `storage_only_node` in vCenter and find all ESXi hosts that\nhave this tag.\n\nLimitations\n-----------\n\n- When using a cluster made up of two HCI and one storage node, if there's an\n HCI node failure, there might be only one available HCI node in the cluster\n to run VMs. This scenario can remain until the cluster adds a replacement\n node, at which time your cluster is restored back to resilience.\n\n- You won't be able to use vMotion on a VM to a storage node within a cluster.\n If you try to perform this action, you may see a vCenter error stating that\n there are insufficient resources on the storage node. Instead, you can use\n the vCenter interface to query the \"storage-only\" tag to find all ESXi hosts\n that are configured as storage nodes.\n\n- Converting a storage node to an HCI node and the other way around is not\n supported.\n\nWhat's next\n-----------\n\n- Learn how to [use storage only nodes](/vmware-engine/docs/networking/howto-use-storage-only-nodes)."]]