{"id":71895,"date":"2020-02-29T08:54:01","date_gmt":"2020-02-29T05:54:01","guid":{"rendered":"https:\/\/prohoster.info\/blog\/klasterizacziya-v-proxmox-ve"},"modified":"2020-03-03T16:14:07","modified_gmt":"2020-03-03T13:14:07","slug":"klasterizacziya-v-proxmox-ve","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/klasterizacziya-v-proxmox-ve","title":{"rendered":"Clustering in Proxmox VE","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Clustering in Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/041268b9d5304cdae5a984f07a2fa029.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nIn previous articles, we began to discuss what Proxmox VE is and how it works. Today, we will talk about how to use the clustering feature and demonstrate the advantages it provides.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nWhat is a cluster and why is it needed? A cluster is a group of servers connected by high-speed communication paths, functioning and presenting itself to the user as a single entity. There are several main scenarios for using a cluster:<\/p>\n<ul>\n<li><b>Ensuring Fault Tolerance<\/b> (High-availability).<\/li>\n<li><b>Load balancing<\/b> (Load Balancing).<\/li>\n<li><b>Increasing Performance<\/b> (High Performance).<\/li>\n<li><b>Performing Distributed Computing<\/b> (Distributed computing).<\/li>\n<\/ul>\n<p>\nEach scenario imposes its own requirements on the components of the cluster. For example, a cluster performing distributed computing primarily requires high floating-point operation speed and low network latency. Such clusters are often used for research purposes.<\/p>\n<p>Since we've touched on the topic of distributed computing, it\u2019s worth noting that there\u2019s also a concept known as <b>grid system<\/b> (from English grid \u2014 mesh, network). Despite their general similarity, a grid system should not be confused with a cluster. A grid is not a cluster in the conventional sense. Unlike a cluster, nodes in a grid are often heterogeneous and have low availability. This approach simplifies solving distributed computing tasks but does not allow for creating a unified entity from the nodes.<\/p>\n<blockquote><p>A prime example of a grid system is the popular computing platform <noindex><a rel=\"nofollow\" href=\"https:\/\/boinc.berkeley.edu\/\">BOINC<\/a><\/noindex> (Berkeley Open Infrastructure for Network Computing). This platform was originally created for the project <noindex><a rel=\"nofollow\" href=\"https:\/\/setiathome.ssl.berkeley.edu\/\">SETI@home<\/a><\/noindex> (Search for Extra-Terrestrial Intelligence at Home), which deals with the problem of searching for extraterrestrial intelligence through the analysis of radio signals.<\/p><\/blockquote>\n<p><b class=\"spoiler_title\">How it works<\/b>A massive amount of data obtained from radio telescopes is broken into many small pieces and sent to the nodes of the grid system (in the SETI@home project, such nodes are volunteer computers). The data is processed at the nodes, and once processing is complete, it is sent back to the project's central server. In this way, the project addresses a complex global challenge without possessing the required computational power.<\/p>\n<p>Now that we have a clear understanding of what a cluster is, let's consider how to create and implement it. We will use an open-source virtualization system. <noindex><a rel=\"nofollow\" href=\"http:\/\/www.proxmox.com\/en\/proxmox-ve\">Proxmox VE<\/a><\/noindex>.<\/p>\n<p>It is especially important to clearly understand the limitations and system requirements of Proxmox before starting to create a cluster, namely:<\/p>\n<ul>\n<li>the maximum number of nodes in the cluster \u2014 <b>32<\/b>;<\/li>\n<li>all nodes must have <b>the same version of Proxmox<\/b> (there are exceptions, but they are not recommended for production);<\/li>\n<li>if High Availability functionality is planned to be implemented further, the cluster must have <b>at least 3 nodes<\/b>;<\/li>\n<li>for the nodes to interact with each other, the ports must be open <b>UDP\/5404<\/b>, <b>UDP\/5405<\/b> for corosync and <b>TCP\/22<\/b> for SSH;<\/li>\n<li>the network latency between nodes must not exceed <b>2 ms<\/b>.<\/li>\n<\/ul>\n<p><\/p>\n<h2>Creating a cluster<\/h2>\n<p>\n<b>Important! The configuration described below is for testing purposes. Be sure to check with <noindex><a rel=\"nofollow\" href=\"https:\/\/pve.proxmox.com\/pve-docs\/pve-admin-guide.pdf\">official documentation<\/a><\/noindex> Proxmox VE.<\/b><\/p>\n<p>To launch a test cluster, we took three servers with the Proxmox hypervisor installed, all with the same configuration (2 cores, 2 GB of RAM).<\/p>\n<blockquote><p>If you want to know how to install Proxmox, we recommend reading our previous article \u2014 <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/selectel\/blog\/483236\/\">The Magic of Virtualization: An Introductory Course on Proxmox VE<\/a><\/noindex>.<\/p><\/blockquote>\n<p>Initially, after the OS installation, a single server operates in <b>Standalone-mode<\/b>.<\/p>\n<p><img decoding=\"async\" alt=\"Clustering in Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/07bb2294b5ccd096c868786e20c14200.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nLet's create a cluster by clicking the button <b>Create Cluster<\/b> in the appropriate section.<\/p>\n<p><img decoding=\"async\" alt=\"Clustering in Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/a816a86de93a5f97b388490b92e122df.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nWe set a name for the future cluster and choose the active network connection.<\/p>\n<p><img decoding=\"async\" alt=\"Clustering in Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/0b37004b271fccd14917190589081a6c.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nWe click the Create button. The server will generate a 2048-bit key and save it along with the parameters of the new cluster in the configuration files.<\/p>\n<p><img decoding=\"async\" alt=\"Clustering in Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/3c6aeaf5b175c2246ba2dea0dcbeb795.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nThe message <b>TASK OK<\/b> indicates the successful completion of the operation. Now, looking at the overall system information, it is evident that the server has switched to cluster mode. For now, the cluster consists of only one node, meaning it lacks the capabilities that require a cluster.<\/p>\n<p><img decoding=\"async\" alt=\"Clustering in Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/b5d1ed1e09f055bc1ed82dfdde3e2e62.png\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h2>Joining the cluster<\/h2>\n<p>\nBefore connecting to the created cluster, we need to obtain the information necessary for the connection. For this, we go to the section <b>Cluster<\/b> and click the button <b>Join Information<\/b>.<\/p>\n<p><img decoding=\"async\" alt=\"Clustering in Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/ff7bb8a493d26cb28d475fe0624f784f.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nIn the window that opens, we are interested in the contents of the same-named field. It needs to be copied.<\/p>\n<p><img decoding=\"async\" alt=\"Clustering in Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/bc26af19c074ba8b4f7b359d7bd65301.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nAll necessary connection parameters are encoded here: the server address for connection and the digital fingerprint. We proceed to the server that needs to be included in the cluster. Click the button <b>Join Cluster<\/b> and in the opened window, paste the copied content.<\/p>\n<p><img decoding=\"async\" alt=\"Clustering in Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/4670181c99cc1f1446c418fc0702c583.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nFields <b>Peer Address<\/b> and <b>Fingerprint<\/b> will be filled in automatically. Enter the root password for node number 1, select the network connection, and click the button <b>Join<\/b>.<\/p>\n<p><img decoding=\"async\" alt=\"Clustering in Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/e9c3e2c255332422ad27b52634fef2fe.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nDuring the process of joining the cluster, the GUI web page may stop updating. This is normal; just refresh the page. In the same way, we add another node, resulting in a fully functional cluster of 3 working nodes.<\/p>\n<p><img decoding=\"async\" alt=\"Clustering in Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/94727cbe4f161213505e8f197c1382aa.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nNow we can control all cluster nodes from a single GUI.<\/p>\n<p><img decoding=\"async\" alt=\"Clustering in Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/faed8fc852de04fbfb465a66bf2c4e52.png\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h2>High Availability Organization<\/h2>\n<p>\nProxmox \"out of the box\" supports HA functionality for both virtual machines and LXC containers. The tool <b>ha-manager<\/b> detects and handles errors and failures, performing failover from the failed node to the operational one. For the mechanism to work correctly, it is necessary for the virtual machines and containers to share a common storage.<\/p>\n<p>After activating the High Availability functionality, the ha-manager software stack will continuously monitor the status of the virtual machine or container and asynchronously interact with other nodes in the cluster.<\/p>\n<h3>Join shared storage<\/h3>\n<p>\nFor example, we deployed a small NFS file storage at the address 192.168.88.18. In order for all cluster nodes to use it, the following steps need to be taken.<\/p>\n<p>Select in the web interface menu <b>Datacenter \u2014 Storage \u2014 Add \u2014 NFS<\/b>.<\/p>\n<p><img decoding=\"async\" alt=\"Clustering in Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/47719648825a22894088c313fefc4a7d.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nFill in the fields <b>ID<\/b> and <b>Server<\/b>. In the dropdown list <b>Export<\/b> select the desired directory from the available ones, and in the list <b>Content<\/b> \u2014 the necessary data types. After clicking the button <b>Add<\/b> , the storage will be connected to all nodes in the cluster.<\/p>\n<p><img decoding=\"async\" alt=\"Clustering in Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/aff4b32a586b83c7bdb7d5618e1bbc19.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nWhen creating virtual machines and containers on any of the nodes, specify our <b>storage<\/b> as the storage.<\/p>\n<h3>Configure HA<\/h3>\n<p>\nAs an example, we will create a container with Ubuntu 18.04 and configure High Availability for it. After creating and starting the container, go to the section <b>Datacenter \u2014 HA \u2014 Add<\/b>. In the opened field, specify the ID of the virtual machine\/container and the maximum number of restart and migration attempts between nodes.<\/p>\n<blockquote><p>If this limit is exceeded, the hypervisor will mark the VM as failed and transition it to an Error state, after which no further actions will be taken with it.<\/p><\/blockquote>\n<p><img decoding=\"async\" alt=\"Clustering in Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/2b3b06b6db91e9db333e2b08473b5578.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nAfter clicking the button <b>Add<\/b> utility <b>ha-manager<\/b> will notify all nodes in the cluster that the VM with the specified ID is now under control and must be restarted on another node in case of a crash.<\/p>\n<p><img decoding=\"async\" alt=\"Clustering in Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/19a96ff579a921a3171a904bb3ec35eb.png\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Let's simulate a failure<\/h3>\n<p>\nTo see how the failover mechanism works, let's unexpectedly power off node1. We'll observe from another node what happens to the cluster. We see that the system has recorded the failure.<\/p>\n<p><img decoding=\"async\" alt=\"Clustering in Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/ff1bd10589325413bf9914c2a73bf0ed.png\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<blockquote><p>The operation of the HA mechanism does not guarantee continuous operation of the VM. As soon as a node 'fails', the VM's operation is temporarily halted until it is automatically restarted on another node.<\/p><\/blockquote>\n<p>And here\u2019s where the 'magic' begins \u2014 the cluster automatically reassigned a node for our VM's operation, and within 120 seconds, the operation was automatically restored.<\/p>\n<p><img decoding=\"async\" alt=\"Clustering in Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/3174e1df06f57092e05825fa1302592f.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nWe power off node2. Let\u2019s see if the cluster can handle it and if the VM will automatically return to operational status.<\/p>\n<p><img decoding=\"async\" alt=\"Clustering in Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/771d4e629c75e6b895d0c11348a66a8e.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nUnfortunately, as we can see, we have encountered an issue where there is no quorum left on the only surviving node, which automatically disables HA operation. We give the command to force quorum in the console.<\/p>\n<pre><code class=\"plaintext\">pvecm expected 1<\/code><\/pre>\n<p>\n<img decoding=\"async\" alt=\"Clustering in Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/00a573876894377304084d5eeed6275c.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nAfter 2 minutes, the HA mechanism worked correctly and, not finding node2, started our VM on node3.<\/p>\n<p><img decoding=\"async\" alt=\"Clustering in Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/dda03dbc36955eba356ad1e902ddd5ef.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nOnce we turned node1 and node2 back on, the cluster's operation was fully restored. Note that the VM does not automatically migrate back to node1, but this can be done manually.<\/p>\n<h2>Summing up<\/h2>\n<p>\nWe have explained how the clustering mechanism works in Proxmox and demonstrated how HA is set up for virtual machines and containers. Proper use of clustering and HA significantly increases infrastructure reliability and ensures recovery after failures.<\/p>\n<p>Before creating a cluster, it is essential to plan from the start for what purposes it will be used and how much it will need to be scaled in the future. It\u2019s also necessary to check the network infrastructure for readiness to operate with minimal latency, so that the future cluster operates flawlessly.<\/p>\n<p>Tell us \u2014 do you utilize clustering capabilities in Proxmox? We look forward to your comments.<\/p>\n<p><i>Previous articles on the topic of the Proxmox VE hypervisor:<\/i><\/p>\n<ul>\n<li><i><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/selectel\/blog\/483236\/\">The Magic of Virtualization: An Introductory Course on Proxmox VE<\/a><\/noindex><\/i><\/li>\n<li><i><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/selectel\/blog\/486194\/\">About backups in Proxmox VE<\/a><\/noindex><\/i><\/li>\n<\/ul>\n<p>Source: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/selectel\/blog\/489914\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0412 \u043f\u0440\u043e\u0448\u043b\u044b\u0445 \u0441\u0442\u0430\u0442\u044c\u044f\u0445 \u043c\u044b \u043d\u0430\u0447\u0430\u043b\u0438 \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u044b\u0432\u0430\u0442\u044c \u043e \u0442\u043e\u043c, \u0447\u0442\u043e \u0442\u0430\u043a\u043e\u0435 Proxmox VE \u0438 \u043a\u0430\u043a \u043e\u043d \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442. \u0421\u0435\u0433\u043e\u0434\u043d\u044f \u043c\u044b \u0440\u0430\u0441\u0441\u043a\u0430\u0436\u0435\u043c \u043e \u0442\u043e\u043c, \u043a\u0430\u043a \u043c\u043e\u0436\u043d\u043e \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u044c \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0438\u0437\u0430\u0446\u0438\u0438 \u0438 \u043f\u043e\u043a\u0430\u0436\u0435\u043c \u043a\u0430\u043a\u0438\u0435 \u043f\u0440\u0435\u0438\u043c\u0443\u0449\u0435\u0441\u0442\u0432\u0430 \u044d\u0442\u043e \u0434\u0430\u0435\u0442. \u0427\u0442\u043e \u0436\u0435 \u0442\u0430\u043a\u043e\u0435 \u043a\u043b\u0430\u0441\u0442\u0435\u0440 \u0438 \u0437\u0430\u0447\u0435\u043c \u043e\u043d \u043d\u0443\u0436\u0435\u043d? \u041a\u043b\u0430\u0441\u0442\u0435\u0440 (\u043e\u0442 \u0430\u043d\u0433\u043b. cluster) \u2014 \u044d\u0442\u043e \u0433\u0440\u0443\u043f\u043f\u0430 \u0441\u0435\u0440\u0432\u0435\u0440\u043e\u0432, \u043e\u0431\u044a\u0435\u0434\u0438\u043d\u0435\u043d\u043d\u044b\u0445 \u0441\u043a\u043e\u0440\u043e\u0441\u0442\u043d\u044b\u043c\u0438 \u043a\u0430\u043d\u0430\u043b\u0430\u043c\u0438 \u0441\u0432\u044f\u0437\u0438, \u0440\u0430\u0431\u043e\u0442\u0430\u044e\u0449\u0430\u044f \u0438 \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u044f\u044e\u0449\u0430\u044f\u0441\u044f [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":71896,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-71895","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.2 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0412 \u043f\u0440\u043e\u0448\u043b\u044b\u0445 \u0441\u0442\u0430\u0442\u044c\u044f\u0445 \u043c\u044b \u043d\u0430\u0447\u0430\u043b\u0438 \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u044b\u0432\u0430\u0442\u044c \u043e \u0442\u043e\u043c, \u0447\u0442\u043e \u0442\u0430\u043a\u043e\u0435.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/klasterizacziya-v-proxmox-ve\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2\" \/>\n\t\t<meta property=\"og:locale\" content=\"en_US\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u041a\u043b\u0430\u0441\u0442\u0435\u0440\u0438\u0437\u0430\u0446\u0438\u044f \u0432 Proxmox VE | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0412 \u043f\u0440\u043e\u0448\u043b\u044b\u0445 \u0441\u0442\u0430\u0442\u044c\u044f\u0445 \u043c\u044b \u043d\u0430\u0447\u0430\u043b\u0438 \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u044b\u0432\u0430\u0442\u044c \u043e \u0442\u043e\u043c, \u0447\u0442\u043e \u0442\u0430\u043a\u043e\u0435.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/klasterizacziya-v-proxmox-ve\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2020-02-29T05:54:01+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-03-03T13:14:07+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Clustering in Proxmox VE | ProHoster","description":"In previous articles, we began discussing what this is.","canonical_url":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/klasterizacziya-v-proxmox-ve","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"en_US","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u041a\u043b\u0430\u0441\u0442\u0435\u0440\u0438\u0437\u0430\u0446\u0438\u044f \u0432 Proxmox VE | ProHoster","og:description":"\u0412 \u043f\u0440\u043e\u0448\u043b\u044b\u0445 \u0441\u0442\u0430\u0442\u044c\u044f\u0445 \u043c\u044b \u043d\u0430\u0447\u0430\u043b\u0438 \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u044b\u0432\u0430\u0442\u044c \u043e \u0442\u043e\u043c, \u0447\u0442\u043e \u0442\u0430\u043a\u043e\u0435.","og:url":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/klasterizacziya-v-proxmox-ve","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-02-29T05:54:01+00:00","article:modified_time":"2020-03-03T13:14:07+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"71895","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 18:54:25","updated":"2022-09-28 06:41:05","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/71895","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/comments?post=71895"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/71895\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/media\/71896"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/media?parent=71895"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/categories?post=71895"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/tags?post=71895"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}