Beberapa atau semua informasi di halaman ini mungkin tidak berlaku untuk Trusted Cloud oleh S3NS.
FAQ akuntansi sole-tenancy
FAQ ini dapat membantu Anda mengevaluasi apakah Anda dapat mengelompokkan pembayaran sole-tenant node Anda sebagai belanja modal (CAPEX) atau belanja operasional (OPEX). Meskipun Google menyediakan FAQ ini, Google menganjurkan agar Anda berkonsultasi dengan akuntan mengenai cara mengelompokkan pembayaran untuk sole-tenant node.
Apa yang dimaksud dengan sole-tenant node?
Lazimnya, VM berjalan di host fisik yang mungkin digunakan bersama oleh banyak pelanggan. Dengan sole-tenant node, Anda memiliki akses eksklusif ke VM di host fisik.
Setiap sole-tenant node dikaitkan dengan satu server fisik. Dalam setiap node, satu pelanggan dapat sepenuhnya mengontrol VM mana yang berjalan di node tersebut, tanpa berbagi hardware host dengan pelanggan lainnya.
Sebaiknya saya menganggap pembelian sole-tenant node sebagai CAPEX atau OPEX?
Google tidak memberikan panduan tentang akuntansi. Silakan pelajari detail produk sole-tenant node sebelum Anda membuat keputusan akuntansi terkait CAPEX atau OPEX.
Dapatkah saya mengidentifikasi sole-tenant node secara unik?
Ya, setiap sole-tenant node memiliki ID unik: server_id.
server_id bersifat unik di semua Trusted Cloud by S3NS hardware, dan tersedia segera setelah Anda membuat node tenant tunggal. Ambil server_id dengan permintaan REST nodeGroups.listNodes.
Apa itu server_id?
server_id adalah ID unik yang digunakan untuk menandai setiap server fisik. Saat sole-tenant node dialokasikan ke akun Anda, terjadi hubungan one-to-one antara server_id dan server fisik.
Apakah Trusted Cloud by S3NS akan menggunakan kembali server_id yang sama untuk server fisik yang berbeda?
Tidak, Trusted Cloud tidak akan menggunakan kembali server_id yang sama untuk server fisik yang berbeda. Jika host fisik dihentikan karena peristiwa terkait pemeliharaan, Anda akan menerima server pengganti beserta server_id-nya, dan VM Anda akan dipindahkan ke server pengganti tersebut.
Peristiwa terkait pemeliharaan dicatat di Cloud Audit Logs, dan Anda dapat menggunakan log ini untuk melacak silsilah server fisik Anda.
Jika host fisik saya dihentikan, dapatkah saya melacak silsilah server_id-nya?
Ya, setiap kali host dihentikan dan Anda diberi host pengganti, server_id baru akan tersedia di Cloud Audit Logs. Gunakan log ini untuk melacak histori server_id host VM Anda.
Bagaimana metode penagihan sole-tenant node?
Anda membayar untuk seluruh sole-tenant node berdasarkan detik penggunaan, terlepas dari berapa banyak VM yang berjalan di node tersebut. Saat menyediakan sole-tenant node, Anda mengontrol VM di host tersebut.
Langkah berikutnya
Kecuali dinyatakan lain, konten di halaman ini dilisensikan berdasarkan Lisensi Creative Commons Attribution 4.0, sedangkan contoh kode dilisensikan berdasarkan Lisensi Apache 2.0. Untuk mengetahui informasi selengkapnya, lihat Kebijakan Situs Google Developers. Java adalah merek dagang terdaftar dari Oracle dan/atau afiliasinya.
Terakhir diperbarui pada 2025-08-19 UTC.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Informasi yang saya butuhkan tidak ada","missingTheInformationINeed","thumb-down"],["Terlalu rumit/langkahnya terlalu banyak","tooComplicatedTooManySteps","thumb-down"],["Sudah usang","outOfDate","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Masalah kode / contoh","samplesCodeIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-19 UTC."],[[["\u003cp\u003eSole-tenant nodes provide exclusive access to VMs on a physical host, ensuring that no other customers share the hardware.\u003c/p\u003e\n"],["\u003cp\u003eEach sole-tenant node has a unique \u003ccode\u003eserver_id\u003c/code\u003e that identifies the physical server, allowing for tracking and management.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Cloud does not reuse \u003ccode\u003eserver_id\u003c/code\u003e values for different physical servers, and in case of maintenance, you are given a new \u003ccode\u003eserver_id\u003c/code\u003e that can be tracked through Cloud Audit Logs.\u003c/p\u003e\n"],["\u003cp\u003eBilling for sole-tenant nodes is on a per-second basis for the entire node, regardless of VM usage, and committed use discounts are available for 1 or 3-year terms.\u003c/p\u003e\n"],["\u003cp\u003eGoogle doesn't provide guidance about how you should classify the cost of sole-tenant nodes as either CAPEX or OPEX, and you should consult an accountant.\u003c/p\u003e\n"]]],[],null,["*** ** * ** ***\n\nThis FAQ can help you evaluate whether you can classify your [sole-tenant\nnode](/compute/docs/nodes) payments as capital expenditures (CAPEX) or\noperational expenditures (OPEX). Although Google provides this FAQ, Google\nrecommends that you consult with your accountants about how to classify your\npayments for sole-tenant nodes.\n\nWhat are sole-tenant nodes?\n\nNormally, VMs run on physical hosts that might be shared by many customers. With\nsole-tenant nodes, you have exclusive access to the VMs on the physical host.\nEach sole-tenant node is associated with one physical server. Within each node,\na single customer can fully control which VMs are running on that node, without\nsharing the host hardware with other customers.\n\nShould I consider the purchase of a sole-tenant node as CAPEX or OPEX?\n\nGoogle does not provide guidance about accounting. Please review the details\nabout the sole-tenant node product before you make any accounting decisions\nregarding CAPEX or OPEX.\n\nCan I uniquely identify a sole-tenant node?\n\nYes, each sole-tenant node has a unique identifier: the `server_id`.\nThe `server_id` is unique across all of Google Cloud hardware, and is\navailable as soon as you create a sole-tenant node. Retrieve the\n`server_id` with the\n[`nodeGroups.listNodes`](/compute/docs/reference/rest/v1/nodeGroups/listNodes)\nREST request.\n\nWhat is the server_id?\n\nThe `server_id` is a unique identifier that is used to mark each\nphysical server. When a sole-tenant node is allocated to your account, there\nis a one-to-one relationship between the `server_id` and the physical\nserver.\n\nWill Google Cloud reuse the same server_id for different physical servers?\n\nNo, Google Cloud does not reuse the same `server_id` for\ndifferent physical servers. If the physical host is retired due to maintenance-related events, you receive a replacement server along with its\n`server_id`, and your VMs are moved to the replacement server.\nMaintenance-related events are logged in the Cloud Audit Logs, and you can use\nthese logs to help you trace the lineage of your physical server.\n\nIn the event that my physical host is retired, can I trace the server_id lineage?\n\nYes, each time a host is retired and you are provided a replacement host, the\nnew `server_id` is available in Cloud Audit Logs. Use these logs to\ntrace the `server_id` history of your VM's hosts.\n\nHow am I billed for a sole-tenant node?\n\nYou pay for the entire sole-tenant node on a per-second basis, regardless of how\nmany VMs are running on the node. When you provision a sole-tenant node, you\ncontrol the VMs on that host.\n\nCan I pay for a commitment of longer than one year?\n\nYou can purchase sole-tenant nodes with a 1- or 3-year [committed use\ndiscount](/compute/docs/instances/signing-up-committed-use-discounts), or you\ncan pay for them as you use them. For more information about pricing, see\n[sole-tenant node pricing](/compute/sole-tenant-pricing).\n\nWhat's next\n\n- Learn about [bringing images with existing licenses to\n Google Cloud](/compute/docs/instances/windows/bring-your-own-license).\n- Learn more about [sole-tenant nodes](/compute/docs/nodes)."]]
