Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Menghubungkan VM workload ke Google Cloud NetApp Volumes
Google Cloud NetApp Volumes mempercepat deployment
aplikasi berbasis cloud melalui penyediaan layanan file bersama dan
fitur pengelolaan penyimpanan yang cepat. Dengan menghubungkan NetApp Volumes ke VMware Engine, Anda dapat memasang volume NetApp Volumes dari dalam OS tamu virtual machine (VM) workload.
Berikut beberapa kasus penggunaan umum untuk menggunakan Volume NetApp dengan
VMware Engine:
Infrastruktur desktop virtual (VDI)
Membuat direktori utama VM
Menyiapkan layanan file
Penyimpanan file bersama untuk aplikasi dan database
Selain itu, VM di Compute Engine dan Google Cloud VMware Engine dapat memasang
volume yang sama. Berikut adalah diagram yang menunjukkan Google Cloud NetApp Volumes yang
digunakan dengan VMware Engine dan Compute Engine:
Sebelum memulai
Langkah-langkah dalam dokumen ini mengasumsikan bahwa Anda telah melakukan hal berikut:
Membuat Storage Pool dengan lokasi, tingkat layanan, kapasitas, enkripsi data, dan kebijakan AD yang dipilih.
Membuat Volume di kumpulan penyimpanan yang sudah ada dengan parameter yang dipilih (seperti kapasitas yang dialokasikan dan jenis protokol) di region tertentu. Anda dapat menggunakan volume NFSv3, NFSv4, atau SMB untuk koneksi
yang dijelaskan dalam dokumen ini.
Saat membuat koneksi peering antara VMware Engine dan
NetApp Volumes, Anda memerlukan beberapa detail tentang jaringan VPC
yang digunakan oleh NetApp Volumes. Untuk mendapatkan detail ini, lakukan hal berikut:
Di Google Cloud konsol, buka halaman Peering Jaringan VPC.
Klik Select a project, lalu pilih organisasi, folder, atau project yang
berisi koneksi peering.
Pilih koneksi peering yang dibuat di NetApp Volumes untuk
project Anda.
Koneksi diberi nama sn-netapp-prod.
Anda mungkin melihat beberapa koneksi peering dengan nama yang sama jika memiliki lebih dari satu jaringan VPC yang di-peering. Orang yang menyiapkan
koneksi Peering Jaringan VPC dapat membantu Anda menentukan koneksi mana
yang akan digunakan untuk VMware Engine.
Salin kolom Peered VPC network dan Peered project ID, yang masing-masing dimulai dengan netapp dan diakhiri dengan -tp.
Membuat koneksi peering
Jika project VMware Engine dan cloud pribadi Anda dibuat setelah
12 November 2023, lakukan hal berikut. Untuk mengetahui informasi selengkapnya tentang cara membuat peering VPC
untuk lingkungan tersebut, lihat Melakukan peering jaringan VPC.
Di Google Cloud konsol, buka halaman Peering Jaringan VPC.
Klik Select a project, lalu pilih organisasi, folder, atau project tempat
Anda ingin membuat koneksi peering.
Klik Create.
Di kolom Nama, berikan nama untuk peering jaringan Anda. Contoh,
peering-2-netapp-volumes.
Di bagian VMware Engine network, biarkan "In current project" dipilih. Tentukan jaringan VMware Engine yang ingin Anda
hubungkan, misalnya ven1.
Untuk Peering, pilih Google Cloud NetApp Volumes.
Di kolom Service tenant project ID, masukkan project ID peer dari
Google Cloud project yang berisi volume Anda.
Di kolom Service tenant VPC name, masukkan nama jaringan VPC peer tempat volume Anda berada.
Di bagian Pertukaran rute, biarkan setelan default.
Klik Create.
Memasang volume
Setelah status peering tercantum sebagai Aktif, Anda dapat memasang volume NetApp Volumes.
Lakukan proses pemasangan dari dalam OS tamu VM VMware Anda.
Untuk memasang volume NFS, lakukan hal berikut:
Di konsol Google Cloud , buka NetApp Volumes >
Volumes.
Klik Select a project, lalu pilih organisasi, folder, atau project yang
berisi volume.
Klik volume NFS yang ingin Anda pasang ekspor NFS-nya.
Di sebelah kanan, klik Lainnyamore_vert, lalu klik
Petunjuk Penyambungan.
Ikuti petunjuk di jendela Mount Instructions for NFS yang
muncul. Petunjuk pemasangan mungkin sedikit berbeda, bergantung pada protokol NFS yang telah Anda konfigurasikan untuk volume.
Untuk memasang volume SMB, lakukan hal berikut:
Di konsol Google Cloud , buka NetApp Volumes >
Volumes.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[],[],null,["# Connecting workload VMs to Google Cloud NetApp Volumes\n======================================================\n\n[Google Cloud NetApp Volumes](/architecture/partners/netapp-cloud-volumes) speeds up the deployment of\ncloud-based applications through rapid provisioning of shared file services and\nstorage management features. Connecting NetApp Volumes to\nVMware Engine lets you mount NetApp Volumes volumes\nfrom within the guest OS of your workload virtual machines (VMs).\n\nHere are some common use cases for using NetApp Volumes with\nVMware Engine:\n\n- Virtual desktop infrastructure (VDI)\n- Creating VM home directories\n- Setting up file services\n- Shared file storage for applications and databases\n\nAdditionally, VMs in Compute Engine and Google Cloud VMware Engine can both mount\nthe same volumes. Here's a diagram that shows Google Cloud NetApp Volumes being\nused with VMware Engine and Compute Engine:\n\nBefore you begin\n----------------\n\nThe steps in this document assume that you have done the following:\n\n- [Created a Storage Pool](/netapp/volumes/docs/configure-and-use/storage-pools/create-storage-pool) with the chosen location, service level, capacity, data encryption, and AD policy.\n- [Created a Volume](/netapp/volumes/docs/configure-and-use/volumes/create-volume) in a pre-existing storage pool with the selected parameters (like allocated capacity and protocol type) in a given region. You can use NFSv3, NFSv4, or SMB volumes for the connection described in this document.\n- [Created a private cloud](/vmware-engine/docs/private-clouds/howto-create-private-cloud) in the same region as your volume.\n\nGet VPC network details\n-----------------------\n\nWhen creating a peering connection between VMware Engine and\nNetApp Volumes, you need some details about the VPC network\nused by NetApp Volumes. To get these details, do the following:\n\n1. In the Google Cloud console, go to the **VPC Network peerings** page.\n\n [Go to VPC Network peerings](https://console.cloud.google.com/vmwareengine/network-peerings)\n2. Click **Select a project** and then select the organization, folder, or project that\n contains the peering connection.\n\n3. Select the peering connection created in NetApp Volumes for\n your project.\n The connection is named `sn-netapp-prod`.\n\n You might see multiple peering connections with the same name if you\n have more than one peered VPC network. The person who set up the\n VPC Network Peering connections can help you determine which connection\n to use for VMware Engine.\n4. Copy the **Peered VPC network** and **Peered project ID** fields, which\n begin with *netapp* and end with *-tp*, respectively.\n\nCreate a peering connection\n---------------------------\n\nIf your VMware Engine project and private clouds were created after\nNov 12, 2023, do the following. For more information on how to create VPC\npeerings for such environments, see [Peer a VPC network](/vmware-engine/docs/networking/peer-vpc-network).\n\n1. In the Google Cloud console, go to the **VPC Network peerings** page.\n\n [Go to VPC Network peerings](https://console.cloud.google.com/vmwareengine/network-peerings)\n2. Click **Select a project** and then select the organization, folder, or project where\n you want to create the peering connection.\n\n3. Click **Create**.\n\n4. In the **Name** field, provide a name for your networking peering. For\n example, `peering-2-netapp-volumes`.\n\n5. In the **VMware Engine network** section, keep the default **\"In current\n project\"** selected. Specify the VMware Engine network you want to\n peer, for example `ven1`.\n\n6. For **Peering** , select **Google Cloud NetApp Volumes**.\n\n7. In the **Service tenant project ID** field, enter the *peered project ID* of\n the Google Cloud project containing your volume.\n\n8. In the **Service tenant VPC name** field, enter the name of the *peered VPC\n network* your volume is in.\n\n9. In the **Route exchange** section, keep the default settings.\n\n10. Click **Create**.\n\nMount a volume\n--------------\n\nOnce the peering status is listed as *Active*, you can mount your NetApp Volumes\nvolume.\nPerform the mounting process from within the guest OS of your VMware VM.\n\nTo mount an NFS volume, do the following:\n\n1. In the Google Cloud console, go to **NetApp Volumes \\\u003e\n Volumes**.\n\n [Go to the Volumes page](https://console.cloud.google.com/netapp/cloud-volumes/volumes)\n2. Click **Select a project** and then select the organization, folder, or project that\n contains the volume.\n\n3. Click the NFS volume for which you want to mount NFS exports.\n\n4. Go to the right, click **More**\n *more_vert* , and then click\n **Mount Instructions**.\n\n5. Follow the instructions in the **Mount Instructions for NFS** window that\n appears. The mounting instructions might be slightly different depending on\n which NFS protocol you have configured for the volume.\n\nTo mount an SMB volume, do the following:\n\n1. In the Google Cloud console, go to **NetApp Volumes \\\u003e\n Volumes**.\n\n [Go to the Volumes page](https://console.cloud.google.com/netapp/cloud-volumes/volumes)\n2. Click **Select a project** and then select the organization, folder, or project that\n contains the volume.\n\n3. Click the SMB volume for which you want to map an SMB share.\n\n4. Go to the right, click **More**\n *more_vert* , and then click\n **Mount Instructions**.\n\n5. Follow the instructions in the **Mount Instructions for SMB** window that\n appears.\n\nAfter you mount your volume, you can manage the volume using the standard\ninterfaces described by [Edit a volume](/netapp/volumes/docs/configure-and-use/volumes/edit-volume)."]]
