[[["わかりやすい","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-04-22 UTC。"],[],[],null,["# Create a stretched private cloud with Vmware Engine\n===================================================\n\nThis quickstart explains how to set up Google Cloud VMware Engine and create a\n[stretched private cloud](/vmware-engine/docs/concepts-stretched-private-cloud).\n\nBefore you begin\n----------------\n\nTo perform the steps in this quickstart, you need access to Google Cloud VMware Engine,\navailable VMware Engine node quota, and an appropriate IAM role.\n\nPrepare the following requirements before you proceed:\n\n1. [Request API access and node quota](/vmware-engine/docs/quickstart-prerequisites).\n\n2. Verify that you're familiar with the address ranges you want to use for\n VMware management appliances and the HCX deployment network. For details,\n see [Networking requirements](/vmware-engine/docs/quickstart-networking-requirements).\n\n3. Have the `VMware Engine Service Admin` IAM role.\n\n| **Note:** The **Owner** and **Editor** basic roles include the **VMware Engine\n| Service Admin** role. The **Viewer** basic role includes the **VMware Engine Service Viewer** role. For more information, see [VMware Engine IAM roles and permissions](/vmware-engine/docs/iam).\n\nLastly, the steps in this document assume that you first do the following:\n\n- Allocate a unique IP address range for vSphere or vSAN subnets of the private cloud you want to create.\n - **Minimum CIDR range prefix:** */24*\n - **Maximum CIDR range prefix:** */20*\n- If you want [global address resolution using Cloud DNS](/vmware-engine/docs/networking/howto-dns-on-premises#global-address-resolution-cloud-dns), then [enable the Cloud DNS API](/dns/docs/set-up-dns-records-domain-name#before-you-begin) and complete Cloud DNS setup before you create your private cloud.\n\nThe vSphere or vSAN subnet address space must not overlap with any network that\nwill communicate with the private cloud, such as on-premises networks and\nGoogle Cloud Virtual Private Cloud (VPC) networks. For more information about\nvSphere or vSAN subnets, see [VLANs and subnets on VMware Engine](/vmware-engine/docs/concepts-vlans-subnets).\n\nCreate a stretched private cloud\n--------------------------------\n\n1. In the Google Cloud console, go to the **Private clouds** page.\n\n [Go to Private clouds](https://console.cloud.google.com/vmwareengine/privateclouds)\n2. Click **Select a project** and then select the organization, folder, or project where\n you want to create the stretched private cloud.\n\n3. Click **Create**.\n\n4. Click **Stretched private cloud**.\n\n5. Enter your primary hosting location and select your secondary zone.\n\n6. Select the node type for your primary cluster.\n\n7. Select the number of nodes per zone for the stretched private cloud.\n Create your stretched private cloud with a minimum of 3 nodes per zone.\n\n8. Optional: Click the **Customize Cores** toggle if you want to reduce the\n number of available cores for each node in the management cluster.\n For details, see [Custom core counts](/vmware-engine/docs/concepts-private-cloud#custom-core-count).\n\n9. Enter a CIDR range for the VMware management network. Make sure that the\n CIDR range doesn't overlap with any of your on-premises or cloud subnets.\n\n10. Select **Create new network** to create a new VMware Engine network or select\n from an existing network, if applicable.\n\n11. Click **Create** to begin creating the private cloud.\n\nAs VMware Engine creates your new stretched private cloud, it deploys\na number of [VMware components](/vmware-engine/docs/concepts-vmware-components) and divides the\nprovided IP address range into subnets. Stretched private cloud creation can\ntake 30 minutes to 2 hours. After the provisioning is complete, you receive an\nemail.\n| **Note:** If the stretched cluster creation fails and you see the message `error Stretched private cloud creation is not allowed in projects without the\n| gcp.requiresPhysicalZoneSeparation organizational policy constraint`, reach out to your account or support team before creating the stretched cluster for a new organization.\n\nConnect to your private cloud\n-----------------------------\n\nTo connect to your standard or stretched private cloud vCenter server, establish\na secure connection from your network to the private cloud. You can use any of\nthe following options to create a secure connection:\n\n- [Connect an on-premises network to VMware Engine private cloud](/vmware-engine/docs/networking/howto-connect-to-onpremises)\n- [Connect using a point-to-site VPN connection](/vmware-engine/docs/concepts-vpn-gateways)\n\nWhat's next\n-----------\n\n- [Get management appliance sign-in credentials](/vmware-engine/docs/vmware-platform/howto-access-vsphere-client) for your private cloud.\n- [Configure internet access for workload VMs](/vmware-engine/docs/networking/workload-internet-access) for your private cloud."]]
