{"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\/ro\/blog\/administrirovanie\/klasterizacziya-v-proxmox-ve","title":{"rendered":"Clusterizarea \u00een Proxmox VE","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Clusterizarea \u00een Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/041268b9d5304cdae5a984f07a2fa029.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n\u00cen articolele anterioare, am \u00eenceput s\u0103 discut\u0103m despre ce este Proxmox VE \u0219i cum func\u021bioneaz\u0103 acesta. Ast\u0103zi, vom vorbi despre cum putem folosi capacitatea de clustering \u0219i vom ar\u0103ta care sunt avantajele oferite.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nCe este un cluster \u0219i de ce este necesar? Clusterul (din englez\u0103: cluster) este un grup de servere, unite prin canale de comunicare rapide, care func\u021bioneaz\u0103 \u0219i se prezint\u0103 utilizatorului ca un \u00eentreg.<\/p>\n<ul>\n<li><b>Asigurarea redundan\u021bei<\/b> (High-availability).<\/li>\n<li><b>\u00cenc\u0103rcarea echilibrat\u0103<\/b> (Load Balancing).<\/li>\n<li><b>Cre\u0219terea performan\u021bei<\/b> (High Performance).<\/li>\n<li><b>Realizarea calculelor distribuite<\/b> (Distributed computing).<\/li>\n<\/ul>\n<p>\nFiecare scenariu impune propriile cerin\u021be pentru componentele clusterului. De exemplu, pentru un cluster care efectueaz\u0103 calcule distribuite, principala cerin\u021b\u0103 este o vitez\u0103 ridicat\u0103 de execu\u021bie a opera\u021biunilor cu virgul\u0103 mobil\u0103 \u0219i o laten\u021b\u0103 redus\u0103 a re\u021belei. Astfel de clustere sunt adesea utilizate \u00een scopuri de cercetare \u0219tiin\u021bific\u0103.<\/p>\n<p>\u00centruc\u00e2t am abordat subiectul calculelor distribuite, este important s\u0103 men\u021bion\u0103m \u0219i conceptul de <b>sistem grid<\/b> (din englez\u0103: grid \u2014 plas\u0103, re\u021bea). De\u0219i exist\u0103 asem\u0103n\u0103ri, nu trebuie s\u0103 confund\u0103m sistemul grid cu un cluster. Gridul nu este un cluster \u00een sensul obi\u0219nuit. Spre deosebire de cluster, nodurile dintr-un grid sunt adesea eterogene \u0219i prezint\u0103 o disponibilitate redus\u0103. Aceast\u0103 abordare simplific\u0103 rezolvarea sarcinilor de calcul distribuit, dar nu permite crearea unui \u00eentreg unificat din noduri.<\/p>\n<blockquote><p>Un exemplu elocvent de sistem grid este platforma de calcul popular\u0103 <noindex><a rel=\"nofollow\" href=\"https:\/\/boinc.berkeley.edu\/\">BOINC<\/a><\/noindex> (Berkeley Open Infrastructure for Network Computing). Aceast\u0103 platform\u0103 a fost creat\u0103 ini\u021bial pentru proiectul <noindex><a rel=\"nofollow\" href=\"https:\/\/setiathome.ssl.berkeley.edu\/\">SETI@home<\/a><\/noindex> (Search for Extra-Terrestrial Intelligence at Home), care se ocup\u0103 cu problema c\u0103ut\u0103rii inteligen\u021bei extraterestre prin analiza semnalelor radio.<\/p><\/blockquote>\n<p><b class=\"spoiler_title\">Cum func\u021bioneaz\u0103<\/b>Marele volum de date ob\u021binute de la radiotelescopuri este \u00eemp\u0103r\u021bit \u00een multe buc\u0103\u021bi mici, care sunt trimise c\u0103tre nodurile sistemului grid (\u00een cadrul proiectului SETI@home, rolul acestor noduri este jucat de computerele voluntarilor). Datele sunt procesate pe noduri \u0219i, dup\u0103 finalizarea proces\u0103rii, sunt trimise la serverul central al proiectului SETI. Astfel, proiectul rezolv\u0103 o sarcin\u0103 global\u0103 complex\u0103, f\u0103r\u0103 a dispune de puterea de calcul necesar\u0103.<\/p>\n<p>Acum, c\u00e2nd avem o \u00een\u021belegere clar\u0103 despre ce este un cluster, s\u0103 examin\u0103m cum poate fi creat \u0219i utilizat. Vom folosi un sistem de virtualizare cu surs\u0103 deschis\u0103. <noindex><a rel=\"nofollow\" href=\"http:\/\/www.proxmox.com\/en\/proxmox-ve\">Proxmox VE<\/a><\/noindex>.<\/p>\n<p>Este deosebit de important, \u00eenainte de a \u00eencepe crearea clusterului, s\u0103 \u00een\u021belegem clar limit\u0103rile \u0219i cerin\u021bele sistemice ale Proxmox, \u0219i anume:<\/p>\n<ul>\n<li>num\u0103rul maxim de noduri \u00een cluster - <b>32<\/b>;<\/li>\n<li>toate nodurile trebuie s\u0103 aib\u0103 <b>aceea\u0219i versiune Proxmox<\/b> (exist\u0103 excep\u021bii, dar acestea nu sunt recomandate pentru produc\u021bie);<\/li>\n<li>dac\u0103 se preconizeaz\u0103 utilizarea func\u021bionalit\u0103\u021bii de High Availability, atunci \u00een cluster ar trebui s\u0103 fie <b>cel pu\u021bin 3 noduri<\/b>;<\/li>\n<li>pentru interac\u021biunea dintre noduri, trebuie s\u0103 fie deschise porturile <b>UDP\/5404<\/b>, <b>UDP\/5405<\/b> pentru corosync \u0219i <b>TCP\/22<\/b> pentru SSH;<\/li>\n<li>\u00eent\u00e2rzierea \u00een re\u021bea \u00eentre noduri nu trebuie s\u0103 dep\u0103\u0219easc\u0103 <b>2 ms<\/b>.<\/li>\n<\/ul>\n<p><\/p>\n<h2>Crearea clusterului<\/h2>\n<p>\n<b>Important! Configura\u021bia de mai jos este una de test. Nu uita\u021bi s\u0103 verifica\u021bi cu <noindex><a rel=\"nofollow\" href=\"https:\/\/pve.proxmox.com\/pve-docs\/pve-admin-guide.pdf\">documenta\u021bia oficial\u0103<\/a><\/noindex> Proxmox VE.<\/b><\/p>\n<p>Pentru a lansa un cluster de test, am folosit trei servere cu hypervisor Proxmox instalat, cu aceea\u0219i configura\u021bie (2 nuclee, 2 GB de RAM).<\/p>\n<blockquote><p>Dac\u0103 dori\u021bi s\u0103 afla\u021bi cum poate fi instalat Proxmox, v\u0103 recomand\u0103m s\u0103 citi\u021bi articolul nostru anterior - <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/selectel\/blog\/483236\/\">Magia virtualiz\u0103rii: curs introductiv \u00een Proxmox VE<\/a><\/noindex>.<\/p><\/blockquote>\n<p>Ini\u021bial, dup\u0103 instalarea sistemului de operare, un server singular func\u021bioneaz\u0103 \u00een <b>Standalone-mode<\/b>.<\/p>\n<p><img decoding=\"async\" alt=\"Clusterizarea \u00een Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/07bb2294b5ccd096c868786e20c14200.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nS\u0103 cre\u0103m un cluster, ap\u0103s\u00e2nd butonul <b>Create Cluster<\/b> \u00een sec\u021biunea corespunz\u0103toare.<\/p>\n<p><img decoding=\"async\" alt=\"Clusterizarea \u00een Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/a816a86de93a5f97b388490b92e122df.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nAtribuim un nume viitorului cluster \u0219i alegem conexiunea de re\u021bea activ\u0103.<\/p>\n<p><img decoding=\"async\" alt=\"Clusterizarea \u00een Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/0b37004b271fccd14917190589081a6c.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nAp\u0103s\u0103m butonul Create. Serverul va genera o cheie de 2048 de bi\u021bi \u0219i o va \u00eenregistra \u00eempreun\u0103 cu parametrii noului cluster \u00een fi\u0219ierele de configurare.<\/p>\n<p><img decoding=\"async\" alt=\"Clusterizarea \u00een Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/3c6aeaf5b175c2246ba2dea0dcbeb795.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nInscrip\u021bia <b>TASK OK<\/b> atest\u0103 finalizarea cu succes a opera\u021biunii. Acum, privind informa\u021biile generale despre sistem, se poate observa c\u0103 serverul a trecut \u00een modul cluster. Deocamdat\u0103, clusterul const\u0103 doar dintr-un singur nod, adic\u0103 nu are \u00eenc\u0103 capacit\u0103\u021bile pentru care este necesar un cluster.<\/p>\n<p><img decoding=\"async\" alt=\"Clusterizarea \u00een Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/b5d1ed1e09f055bc1ed82dfdde3e2e62.png\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h2>Conectare la cluster<\/h2>\n<p>\n\u00cenainte de a ne conecta la clusterul creat, trebuie s\u0103 ob\u021binem informa\u021biile necesare pentru a efectua conexiunea. Pentru aceasta, acces\u0103m sec\u021biunea <b>Cluster<\/b> \u0219i facem clic pe butonul <b>Join Information<\/b>.<\/p>\n<p><img decoding=\"async\" alt=\"Clusterizarea \u00een Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/ff7bb8a493d26cb28d475fe0624f784f.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n\u00cen fereastra deschis\u0103, ne intereseaz\u0103 con\u021binutul c\u00e2mpului cu acela\u0219i nume. Acesta trebuie copiat.<\/p>\n<p><img decoding=\"async\" alt=\"Clusterizarea \u00een Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/bc26af19c074ba8b4f7b359d7bd65301.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nAici sunt codificate toate parametrii necesari pentru conexiune: adresa serverului pentru conectare \u0219i amprenta digital\u0103. Trecem pe serverul care trebuie inclus \u00een cluster. Ap\u0103s\u0103m butonul <b>Join Cluster<\/b> \u0219i \u00een fereastra care se deschide, inser\u0103m con\u021binutul copiat.<\/p>\n<p><img decoding=\"async\" alt=\"Clusterizarea \u00een Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/4670181c99cc1f1446c418fc0702c583.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nC\u00e2mpuri <b>Adresa Peer<\/b> \u0219i <b>Fingerprint<\/b> va fi completat\u0103 automat. Introducem parola root pentru nodul num\u0103rul 1, alegem conexiunea de re\u021bea \u0219i facem clic pe butonul <b>Al\u0103turare<\/b>.<\/p>\n<p><img decoding=\"async\" alt=\"Clusterizarea \u00een Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/e9c3e2c255332422ad27b52634fef2fe.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n\u00cen timpul procesului de al\u0103turare la cluster, pagina web GUI poate \u00eenceta s\u0103 se actualizeze. Acest lucru este normal, doar re\u00eenc\u0103rca\u021bi pagina. \u00cen acela\u0219i mod ad\u0103ug\u0103m un alt nod \u0219i, \u00een cele din urm\u0103, ob\u021binem un cluster complet format din 3 noduri func\u021bionale.<\/p>\n<p><img decoding=\"async\" alt=\"Clusterizarea \u00een Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/94727cbe4f161213505e8f197c1382aa.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nAcum putem monitoriza toate nodurile clusterului dintr-un singur GUI.<\/p>\n<p><img decoding=\"async\" alt=\"Clusterizarea \u00een Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/faed8fc852de04fbfb465a66bf2c4e52.png\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h2>Organizarea High Availability<\/h2>\n<p>\nProxmox \u201edin cutie\u201d suport\u0103 func\u021bionalitatea de organizare HA at\u00e2t pentru ma\u0219ini virtuale c\u00e2t \u0219i pentru containere LXC. Utilitarul <b>ha-manager<\/b> detecteaz\u0103 \u0219i rezolv\u0103 erorile \u0219i defectele, efectu\u00e2nd comutarea de urgen\u021b\u0103 de la nodul defect la cel func\u021bional. Pentru ca mecanismul s\u0103 func\u021bioneze corect, este necesar ca ma\u0219inile virtuale \u0219i containerele s\u0103 aib\u0103 un spa\u021biu de stocare comun.<\/p>\n<p>Dup\u0103 activarea func\u021bionalit\u0103\u021bii High Availability, stiva software ha-manager va \u00eencepe s\u0103 monitorizeze continuu starea de func\u021bionare a ma\u0219inii virtuale sau a containerului \u0219i s\u0103 interac\u021bioneze asincron cu celelalte noduri ale clusterului.<\/p>\n<h3>Al\u0103tur\u0103m spa\u021biul de stocare comun<\/h3>\n<p>\nDe exemplu, am desf\u0103\u0219urat un mic spa\u021biu de stocare NFS la adresa 192.168.88.18. Pentru ca toate nodurile clusterului s\u0103 poat\u0103 utiliza acest lucru, trebuie s\u0103 facem urm\u0103toarele manevre.<\/p>\n<p>Alegem \u00een meniul interfe\u021bei web <b>Datacenter \u2014 Storage \u2014 Add \u2014 NFS<\/b>.<\/p>\n<p><img decoding=\"async\" alt=\"Clusterizarea \u00een Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/47719648825a22894088c313fefc4a7d.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nUmplem c\u00e2mpurile <b>ID<\/b> \u0219i <b>Server<\/b>. \u00cen lista derulant\u0103 <b>Export<\/b> alegem directorul dorit din cele disponibile \u0219i \u00een lista <b>Con\u021binut<\/b> \u2014 tipurile de date necesare. Dup\u0103 ap\u0103sarea butonului <b>Adaug\u0103<\/b> spa\u021biul de stocare va fi conectat la toate nodurile clusterului.<\/p>\n<p><img decoding=\"async\" alt=\"Clusterizarea \u00een Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/aff4b32a586b83c7bdb7d5618e1bbc19.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nAtunci c\u00e2nd cre\u0103m ma\u0219ini virtuale \u0219i containere pe oricare dintre noduri, specific\u0103m <b>storage<\/b> ca spa\u021biu de stocare.<\/p>\n<h3>Configur\u0103m HA<\/h3>\n<p>\nDe exemplu, vom crea un container cu Ubuntu 18.04 \u0219i vom configura High Availability pentru acesta. Dup\u0103 ce amendem \u0219i lans\u0103m containerul, intr\u0103m \u00een sec\u021biunea <b>Datacenter \u2014 HA \u2014 Add<\/b>. \u00cen c\u00e2mpul deschis, indic\u0103m ID-ul ma\u0219inii virtuale\/containerului \u0219i num\u0103rul maxim de \u00eencerc\u0103ri de repornire \u0219i migrare \u00eentre noduri.<\/p>\n<blockquote><p>Dac\u0103 acest num\u0103r este dep\u0103\u0219it, hipervizorul va marca VM-ul ca fiind defect \u0219i \u00eel va transfera \u00een stare de Eroare, dup\u0103 care va \u00eenceta s\u0103 mai efectueze orice ac\u021biuni cu acesta.<\/p><\/blockquote>\n<p><img decoding=\"async\" alt=\"Clusterizarea \u00een Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/2b3b06b6db91e9db333e2b08473b5578.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nDup\u0103 ce a\u021bi ap\u0103sat butonul <b>Adaug\u0103<\/b> utilitate <b>ha-manager<\/b> va informa toate nodurile clusterului c\u0103 acum VM-ul cu ID-ul specificat este sub control \u0219i, \u00een cazul unei c\u0103deri, trebuie repornit pe un alt nod.<\/p>\n<p><img decoding=\"async\" alt=\"Clusterizarea \u00een Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/19a96ff579a921a3171a904bb3ec35eb.png\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Vom organiza o defectiune<\/h3>\n<p>\nPentru a vedea cum func\u021bioneaz\u0103 mecanismul de comutare, vom opri neprogramat node1 prin alimentare. Ne uit\u0103m dintr-un alt nod pentru a observa ce se \u00eent\u00e2mpl\u0103 cu clusterul. Vedem c\u0103 sistemul a detectat defectiunea.<\/p>\n<p><img decoding=\"async\" alt=\"Clusterizarea \u00een Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/ff1bd10589325413bf9914c2a73bf0ed.png\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<blockquote><p>Func\u021bionarea mecanismului HA nu garanteaz\u0103 continuitatea activit\u0103\u021bii VM-ului. De \u00eendat\u0103 ce nodul \"a c\u0103zut\", activitatea VM-ului se opre\u0219te temporar p\u00e2n\u0103 la reluarea automat\u0103 pe un alt nod.<\/p><\/blockquote>\n<p>\u0218i aici \u00eencepe \"magia\" \u2014 clusterul a realocat automat nodul pentru a executa VM-ul nostru \u0219i \u00een decurs de 120 de secunde activitatea a fost restaurat\u0103 automat.<\/p>\n<p><img decoding=\"async\" alt=\"Clusterizarea \u00een Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/3174e1df06f57092e05825fa1302592f.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nOprim node2 prin alimentare. S\u0103 vedem dac\u0103 clusterul va rezista \u0219i dac\u0103 VM-ul se va \u00eentoarce \u00een stare de func\u021bionare automat.<\/p>\n<p><img decoding=\"async\" alt=\"Clusterizarea \u00een Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/771d4e629c75e6b895d0c11348a66a8e.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nDin p\u0103cate, dup\u0103 cum vedem, avem o problem\u0103 cu faptul c\u0103 la singurul nod r\u0103mas \u00een via\u021b\u0103 nu mai exist\u0103 cvorum, ceea ce opre\u0219te automat func\u021bionarea HA. D\u0103m \u00een consol\u0103 comanda pentru a for\u021ba stabilirea cvorumului.<\/p>\n<pre><code class=\"plaintext\">pvecm expected 1<\/code><\/pre>\n<p>\n<img decoding=\"async\" alt=\"Clusterizarea \u00een Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/00a573876894377304084d5eeed6275c.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nDup\u0103 2 minute, mecanismul HA a func\u021bionat corect \u0219i, ner\u0103spunz\u00e2nd la node2, a pornit VM-ul nostru pe node3.<\/p>\n<p><img decoding=\"async\" alt=\"Clusterizarea \u00een Proxmox VE\" src=\"\/wp-content\/uploads\/2020\/02\/dda03dbc36955eba356ad1e902ddd5ef.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nImediat ce am repornit node1 \u0219i node2, func\u021bionarea clusterului a fost complet restaurat\u0103. Re\u021bine\u021bi c\u0103 VM-ul nu migreaz\u0103 automat \u00eenapoi pe node1, dar acest lucru se poate face manual.<\/p>\n<h2>\u00cencheiem<\/h2>\n<p>\nV-am vorbit despre cum este organizat mecanismul de clustering \u00een Proxmox, precum \u0219i despre cum se configureaz\u0103 HA pentru ma\u0219inile virtuale \u0219i containere. Utilizarea corect\u0103 a clustering-ului \u0219i HA cre\u0219te semnificativ fiabilitatea infrastructurii \u0219i asigur\u0103 recuperarea dup\u0103 defectiuni.<\/p>\n<p>\u00cenainte de a crea un cluster, trebuie s\u0103 planifica\u021bi de la \u00eenceput pentru ce scopuri va fi utilizat \u0219i c\u00e2t de mult va trebui s\u0103 fie scalat \u00een viitor. De asemenea, trebuie s\u0103 verifica\u021bi infrastructura de re\u021bea pentru preg\u0103tirea de a func\u021biona cu \u00eent\u00e2rzieri minime, astfel \u00eenc\u00e2t viitorul cluster s\u0103 func\u021bioneze f\u0103r\u0103 defec\u021biuni.<\/p>\n<p>Spune\u021bi-ne \u2014 folosi\u021bi posibilit\u0103\u021bile de clustering \u00een Proxmox? V\u0103 a\u0219tept\u0103m \u00een comentarii.<\/p>\n<p><i>Articolele anterioare despre hypervisorul Proxmox VE:<\/i><\/p>\n<ul>\n<li><i><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/selectel\/blog\/483236\/\">Magia virtualiz\u0103rii: curs introductiv \u00een Proxmox VE<\/a><\/noindex><\/i><\/li>\n<li><i><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/selectel\/blog\/486194\/\">Despre backup-uri \u00een Proxmox VE<\/a><\/noindex><\/i><\/li>\n<\/ul>\n<p>Sursa: <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.1 - 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\/ro\/blog\/administrirovanie\/klasterizacziya-v-proxmox-ve\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"ro_RO\" \/>\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\/ro\/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 \u00een Proxmox VE | ProHoster","description":"\u00cen articolele anterioare, am \u00eenceput s\u0103 discut\u0103m despre ce este.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/klasterizacziya-v-proxmox-ve","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","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\/ro\/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\/ro\/wp-json\/wp\/v2\/posts\/71895","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=71895"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/71895\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/71896"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=71895"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=71895"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=71895"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}