vSphere 또는 vSAN 서브넷 주소 공간은 온프레미스 네트워크 및 Google Cloud Virtual Private Cloud(VPC) 네트워크와 같이 프라이빗 클라우드와 통신하는 네트워크와 겹쳐서는 안 됩니다. vSphere 또는 vSAN 서브넷에 대한 자세한 내용은 VMware Engine의 VLAN 및 서브넷을 참조하세요.
확장된 프라이빗 클라우드의 영역당 노드 수를 선택합니다.
영역당 최소 3개 노드로 확장된 프라이빗 클라우드를 만듭니다.
선택사항: 관리 클러스터의 각 노드에서 사용 가능한 코어 수를 줄이려면 코어 맞춤설정 전환 버튼을 클릭합니다.
자세한 내용은 커스텀 코어 수를 참조하세요.
VMware 관리 네트워크의 CIDR 범위를 입력합니다. CIDR 범위가 온프레미스 또는 클라우드 서브넷과 겹치지 않는지 확인합니다.
새 네트워크 만들기를 선택하여 새 VMware Engine 네트워크를 만들거나 해당하는 경우 기존 네트워크에서 선택합니다.
만들기를 클릭하여 프라이빗 클라우드 만들기를 시작합니다.
VMware Engine은 새 확장된 프라이빗 클라우드를 만들 때 다양한 VMware 구성요소를 배포하고 제공된 IP 주소 범위를 서브넷으로 나눕니다. 확장된 프라이빗 클라우드를 만드는 데 30분~2시간 정도 걸릴 수 있습니다. 프로비저닝이 완료되면 이메일이 전송됩니다.
프라이빗 클라우드에 연결
표준 또는 확장된 프라이빗 클라우드 vCenter 서버에 연결하려면 네트워크에서 프라이빗 클라우드로의 보안 연결을 설정합니다. 다음 옵션을 사용해서 보안 연결을 만들 수 있습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2024-12-21(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."]]