{"id":31230,"date":"2019-10-31T21:40:10","date_gmt":"2019-10-31T18:40:10","guid":{"rendered":"https:\/\/prohoster.info\/blog\/rekomendatsii-po-nastrojke-afa-accelstor-pri-rabote-s-vmware-vsphere\/"},"modified":"2019-10-31T21:40:10","modified_gmt":"2019-10-31T18:40:10","slug":"rekomendatsii-po-nastrojke-afa-accelstor-pri-rabote-s-vmware-vsphere","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/rekomendatsii-po-nastrojke-afa-accelstor-pri-rabote-s-vmware-vsphere","title":{"rendered":"Recomand\u0103ri pentru configurarea AFA AccelStor \u00een lucrul cu VMware vSphere","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>\u00cen aceast\u0103 articol, dorim s\u0103 discut\u0103m despre particularit\u0103\u021bile func\u021bion\u0103rii aranjamentelor All Flash AccelStor cu una dintre cele mai populare platforme de virtualizare \u2013 VMware vSphere. \u00cen special, ne vom concentra asupra parametrilor care pot ajuta la ob\u021binerea unui efect maxim din utilizarea unui instrument at\u00e2t de puternic precum All Flash. <\/p>\n<p><\/p>\n<p><img decoding=\"async\" alt=\"Recomand\u0103ri pentru configurarea AFA AccelStor \u00een lucrul cu VMware vSphere\" src=\"\/wp-content\/uploads\/2019\/04\/177f44f7e1c5f30c8c072af86b4f9999.jpg\" style=\"display:block;margin: 0 auto;\" \/><noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<p>Aranjamentele All Flash AccelStor NeoSapphire\u2122 reprezint\u0103 <noindex><a rel=\"nofollow\" href=\"http:\/\/accelstor.ru\/page\/professional-models\">un<\/a><\/noindex> sau <noindex><a rel=\"nofollow\" href=\"http:\/\/accelstor.ru\/page\/modeli-vysokoj-dostupnosti-ha\">dou\u0103<\/a><\/noindex> dispozitiv nodular bazat pe unit\u0103\u021bi SSD, cu o abordare total diferit\u0103 \u00een realizarea conceptului de stocare a datelor \u0219i organizarea accesului la acesta, folosind tehnologia proprie <noindex><a rel=\"nofollow\" href=\"http:\/\/accelstor.ru\/page\/flexiremap-technology\">FlexiRemap\u00ae<\/a><\/noindex> \u00een locul algoritmilor RAID destul de populari. Aranjamentele ofer\u0103 acces bloc pentru gazde prin interfe\u021bele Fibre Channel sau iSCSI. Merit\u0103 men\u021bionat c\u0103 modelele cu interfa\u021b\u0103 ISCSI au de asemenea acces prin fi\u0219iere ca un bonus pl\u0103cut. Totu\u0219i, \u00een cadrul acestui articol ne vom concentra pe utilizarea protocoalelor bloc ca fiind cele mai productive pentru All Flash.<\/p>\n<p><\/p>\n<p>\u00centregul proces de desf\u0103\u0219urare \u0219i configurare ulterioar\u0103 a colabor\u0103rii dintre aranjamentele AccelStor \u0219i sistemul de virtualizare VMware vSphere poate fi \u00eemp\u0103r\u021bit \u00een mai multe etape:<\/p>\n<p><\/p>\n<ul>\n<li>Implementarea topologiei de conectare \u0219i configurarea re\u021belei SAN;<\/li>\n<li>Configurarea aranjamentului All Flash;<\/li>\n<li>Configurarea gazdelor ESXi;<\/li>\n<li>Configurarea ma\u0219inilor virtuale.<\/li>\n<\/ul>\n<p><\/p>\n<p>Pentru exemplele utilizate, s-au folosit aranjamente AccelStor NeoSapphire\u2122 cu interfa\u021b\u0103 Fibre Channel \u0219i cu interfa\u021b\u0103 iSCSI. Software-ul de baz\u0103 utilizat a fost VMware vSphere 6.7U1.<\/p>\n<p><\/p>\n<p>\u00cenainte de desf\u0103\u0219urarea sistemelor descrise \u00een articol, este extrem de recomandat s\u0103 se revizuiasc\u0103 documenta\u021bia de la VMware referitoare la aspectele de performan\u021b\u0103 (<noindex><a rel=\"nofollow\" href=\"https:\/\/www.vmware.com\/content\/dam\/digitalmarketing\/vmware\/en\/pdf\/techpaper\/performance\/vsphere-esxi-vcenter-server-67-performance-best-practices.pdf\">Performance Best Practices for VMware vSphere 6.7<\/a><\/noindex> ) \u0219i set\u0103rile iSCSI (<noindex>Best Practices For Running VMware vSphere On iSCSI<\/noindex>)<\/p>\n<p><\/p>\n<h3><i><b>Topologia de conectare \u0219i configurarea re\u021belei SAN<\/b><\/i><\/h3>\n<p><\/p>\n<p>Principalele componente ale re\u021belei SAN sunt adaptorii HBA din gazdele ESXi, comutatoarele SAN \u0219i nodurile aranjamentului. O topologie tipic\u0103 a acestei re\u021bele va ar\u0103ta astfel:<\/p>\n<p><\/p>\n<p><img decoding=\"async\" alt=\"Recomand\u0103ri pentru configurarea AFA AccelStor \u00een lucrul cu VMware vSphere\" src=\"\/wp-content\/uploads\/2019\/04\/0fa8f428d3120b551747e21d43d9095d.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>Prin termenul Switch, ne referim at\u00e2t la un comutator fizic separat sau la un set de comutatoare (Fabric), c\u00e2t \u0219i la un dispozitiv partajat \u00eentre diferite servicii (VSAN \u00een cazul Fibre Channel \u0219i VLAN \u00een cazul iSCSI). Utilizarea a dou\u0103 comutatoare\/Fabric independente va elimina o posibil\u0103 punct de e\u0219ec.<\/p>\n<p><\/p>\n<p>Conectarea direct\u0103 a gazdelor la matrice este posibil\u0103, dar nu este recomandat\u0103. Performan\u021ba matricei All Flash este suficient de ridicat\u0103 \u0219i, pentru vitez\u0103 maxim\u0103, este necesar s\u0103 se utilizeze toate porturile matricei. Prin urmare, este obligatorie prezen\u021ba cel pu\u021bin unui switch \u00eentre gazde \u0219i NeoSapphire\u2122.<\/p>\n<p><\/p>\n<p>Prezen\u021ba a dou\u0103 porturi pe HBA-ul gazdei este, de asemenea, o cerin\u021b\u0103 esen\u021bial\u0103 pentru a atinge performan\u021ba maxim\u0103 \u0219i pentru a asigura redundan\u021ba.<\/p>\n<p><\/p>\n<p>\u00cen cazul utiliz\u0103rii interfe\u021bei Fibre Channel, este necesar\u0103 configurarea zon\u0103rii pentru a exclude coliziunile \u00eentre ini\u021biatori \u0219i \u021binte. Zonele sunt construite pe principiul \u201eun port al ini\u021biatorului \u2013 unul sau mai multe porturi ale matricei\u201d.<\/p>\n<p><\/p>\n<p>Dac\u0103 se utilizeaz\u0103 conexiunea prin iSCSI, \u00een cazul utiliz\u0103rii unui switch partajat cu alte servicii, este obligatorie izolarea traficului iSCSI \u00eentr-un VLAN separat. Este, de asemenea, foarte recomandat s\u0103 se activeze suportul pentru Jumbo Frames (MTU = 9000) pentru a cre\u0219te dimensiunea pachetelor \u00een re\u021bea \u0219i, astfel, a reduce cantitatea de informa\u021bii administrative \u00een timpul transmisiei. Totu\u0219i, este important s\u0103 ne amintim c\u0103 pentru o func\u021bionare corect\u0103, trebuie schimbat parameterul MTU pe toate componentele re\u021belei pe lan\u021bul \u201eini\u021biator-switch-\u021bint\u0103\u201d.<\/p>\n<p><\/p>\n<h3><i><b>Configurarea matricei All Flash<\/b><\/i><\/h3>\n<p><\/p>\n<p>Matricea este livrat\u0103 clien\u021bilor cu grupuri deja formate <noindex><a rel=\"nofollow\" href=\"http:\/\/accelstor.ru\/page\/flexiremap-technology\">FlexiRemap\u00ae<\/a><\/noindex>. Prin urmare, nu este necesar s\u0103 se efectueze ac\u021biuni pentru a combina suporturile \u00eentr-o singur\u0103 structur\u0103. Este suficient s\u0103 crea\u021bi volume de dimensiunea necesar\u0103 \u0219i \u00een num\u0103rul dorit.<\/p>\n<p><\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habrastorage.org\/webt\/zn\/x9\/nc\/znx9ncuyd2rgm8-jfvwf620zaqg.png\"><img decoding=\"async\" alt=\"Recomand\u0103ri pentru configurarea AFA AccelStor \u00een lucrul cu VMware vSphere\" src=\"\/wp-content\/uploads\/2019\/04\/d09f9847203773280bc605be1c8fbc67.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habrastorage.org\/webt\/wx\/8l\/ua\/wx8lualewtdkixfwg0petpxbsre.png\"><img decoding=\"async\" alt=\"Recomand\u0103ri pentru configurarea AFA AccelStor \u00een lucrul cu VMware vSphere\" src=\"\/wp-content\/uploads\/2019\/04\/ddcdaeb16263f79536db68f9c6ae2cff.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/p>\n<p><\/p>\n<p>Pentru comoditate, exist\u0103 func\u021bionalitatea de creare \u00een bloc a mai multor volume de dimensiune specificat\u0103. Implicit, se creeaz\u0103 volume \"sub\u021biri\", deoarece acest lucru permite utilizarea mai eficient\u0103 a spa\u021biului de stocare disponibil (inclusiv datorit\u0103 suportului pentru Space Reclamation). Din punctul de vedere al performan\u021bei, diferen\u021ba \u00eentre volumele \"sub\u021biri\" \u0219i cele \"groase\" nu dep\u0103\u0219e\u0219te 1%. Totu\u0219i, dac\u0103 se dore\u0219te \u201escoaterea tuturor sucurilor\u201d din matrice, se poate oric\u00e2nd converti orice volum \"sub\u021bire\" \u00eentr-un volum \"gros\". Dar trebuie s\u0103 ne amintim c\u0103 aceast\u0103 opera\u021biune este ireversibil\u0103.<\/p>\n<p><\/p>\n<p>Apoi, r\u0103m\u00e2ne s\u0103 \u201epublica\u021bi\u201d volumele create \u0219i s\u0103 stabili\u021bi permisiunile de acces de c\u0103tre gazde prin intermediul ACL (adrese IP pentru iSCSI \u0219i WWPN pentru FC) \u0219i separarea fizic\u0103 pe porturile array-ului. Pentru modelele iSCSI, acest lucru se face prin crearea unui Target.<\/p>\n<p><\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habrastorage.org\/webt\/mw\/8y\/cg\/mw8ycgqngghoyuelortgysofswi.png\"><img decoding=\"async\" alt=\"Recomand\u0103ri pentru configurarea AFA AccelStor \u00een lucrul cu VMware vSphere\" src=\"\/wp-content\/uploads\/2019\/04\/942d7ec437ad802ef828afa91bcde1f8.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habrastorage.org\/webt\/py\/xe\/28\/pyxe28gnrsxh_cx4ltjleogwsmw.png\"><img decoding=\"async\" alt=\"Recomand\u0103ri pentru configurarea AFA AccelStor \u00een lucrul cu VMware vSphere\" src=\"\/wp-content\/uploads\/2019\/04\/f92d329b691d7b17380974253c8572ce.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/p>\n<p><\/p>\n<p>Pentru modelele FC, publicarea se realizeaz\u0103 prin crearea unui LUN pentru fiecare port al array-ului.<\/p>\n<p><\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habrastorage.org\/webt\/qh\/u3\/bx\/qhu3bxhm-kqinygguz298izbw7e.png\"><img decoding=\"async\" alt=\"Recomand\u0103ri pentru configurarea AFA AccelStor \u00een lucrul cu VMware vSphere\" src=\"\/wp-content\/uploads\/2019\/04\/554aef268d6b18069edd3531b2429db5.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habrastorage.org\/webt\/oh\/al\/ey\/ohaleyllpb-0bmot9kawc4-ssyg.png\"><img decoding=\"async\" alt=\"Recomand\u0103ri pentru configurarea AFA AccelStor \u00een lucrul cu VMware vSphere\" src=\"\/wp-content\/uploads\/2019\/04\/a770a4d3e6090c5bfaab3dad5487ee5a.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/p>\n<p><\/p>\n<p>Pentru accelerarea procesului de configurare, gazdele pot fi grupate. De fapt, dac\u0103 pe gazd\u0103 este folosit un FC HBA multiport (ceea ce se \u00eent\u00e2mpl\u0103 cel mai frecvent \u00een practic\u0103), sistemul determin\u0103 automat c\u0103 porturile unui astfel de HBA apar\u021bin acelea\u0219i gazde datorit\u0103 WWPN-ului, care se diferen\u021biaz\u0103 cu o unitate. De asemenea, pentru ambele interfe\u021be se suport\u0103 crearea \u00een mas\u0103 de Target\/LUN.<\/p>\n<p><\/p>\n<p>O observa\u021bie important\u0103 \u00een cazul utiliz\u0103rii interfe\u021bei iSCSI este crearea pentru volume a mai multor target-uri simultan pentru a cre\u0219te performan\u021ba, deoarece coada pe target nu poate fi modificat\u0103 \u0219i va fi, de fapt, un punct de congestie.<\/p>\n<p><\/p>\n<p><b><i><\/p>\n<h3>Configurarea gazdelor ESXi<\/h3>\n<p><\/i><\/b><\/p>\n<p><\/p>\n<p>Din partea gazdelor ESXi, configurarea de baz\u0103 se realizeaz\u0103 conform unui scenariu destul de a\u0219teptat. Pa\u0219ii pentru conexiunea iSCSI sunt:<\/p>\n<p><\/p>\n<ol>\n<li>Ad\u0103uga\u021bi Software iSCSI Adapter (nu este necesar dac\u0103 acesta a fost deja ad\u0103ugat, sau \u00een cazul utiliz\u0103rii Hardware iSCSI Adapter);<\/li>\n<li>Crearea unui vSwitch, prin care va circula traficul iSCSI, \u0219i ad\u0103ugarea linkurilor fizice \u0219i VMkernel \u00een acesta;<\/li>\n<li>Ad\u0103ugarea adreselor array-ului \u00een Dynamic Discovery;<\/li>\n<li>Crearea unui Datastore<\/li>\n<\/ol>\n<p><\/p>\n<p><b>C\u00e2teva observa\u021bii importante:<\/b><\/p>\n<p><\/p>\n<blockquote>\n<ul>\n<li>\u00cen general, bine\u00een\u021beles, se poate folosi \u0219i un vSwitch existent, dar \u00een cazul unui vSwitch separat, gestionarea set\u0103rilor gazdei va fi semnificativ mai simpl\u0103.<\/li>\n<li>Este necesar s\u0103 separa\u021bi traficul de Management \u0219i iSCSI pe linkuri fizice \u0219i\/sau VLAN-uri separate pentru a evita problemele de performan\u021b\u0103.<\/li>\n<li>Adresele IP ale VMkernel \u0219i ale porturilor corespunz\u0103toare ale array-ului All Flash trebuie s\u0103 fie \u00een aceea\u0219i subre\u021bea din nou din motive de performan\u021b\u0103.<\/li>\n<li>Pentru a asigura redundan\u021ba conform regulilor VMware, vSwitch-ul trebuie s\u0103 aib\u0103 cel pu\u021bin dou\u0103 uplink-uri fizice.<\/li>\n<li>Dac\u0103 se utilizeaz\u0103 Jumbo Frames, este necesar s\u0103 schimba\u021bi MTU at\u00e2t la vSwitch, c\u00e2t \u0219i la VMkernel.<\/li>\n<li>Nu stric\u0103 s\u0103 amintim c\u0103, conform recomand\u0103rilor VMware pentru adaptoarele fizice care vor fi utilizate pentru a lucra cu traficul iSCSI, este absolut necesar s\u0103 se efectueze configurarea Teaming and Failover. \u00cen special, fiecare VMkernel trebuie s\u0103 func\u021bioneze doar printr-un singur uplink, iar al doilea uplink trebuie s\u0103 fie setat pe mod unused. Pentru redundan\u021b\u0103, este necesar s\u0103 se adauge dou\u0103 VMkernel-uri, fiecare dintre ele func\u021bion\u00e2nd prin propriul s\u0103u uplink.<\/li>\n<\/ul>\n<p>\n<\/p><\/blockquote>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habrastorage.org\/webt\/_h\/jb\/va\/_hjbvatnuhjwts4duy2epgb7bbi.png\"><img decoding=\"async\" alt=\"Recomand\u0103ri pentru configurarea AFA AccelStor \u00een lucrul cu VMware vSphere\" src=\"\/wp-content\/uploads\/2019\/04\/b769fa87aa8552ed6dd775f9f9dcb1b5.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/p>\n<p><\/p>\n<p>VMkernel Adapter (vmk#)<br \/>\nPhysical Network Adapter (vmnic#)<\/p>\n<p>vmk1 (Storage01)<br \/>\nAdaptoare active<br \/>\nvmnic2<br \/>\nAdaptoare neutilizate<br \/>\nvmnic3<\/p>\n<p>vmk2 (Storage02)<br \/>\nAdaptoare active<br \/>\nvmnic3<br \/>\nAdaptoare neutilizate<br \/>\nvmnic2<\/p>\n<p>Pentru conexiunea prin Fibre Channel, nu sunt necesare ac\u021biuni preliminare. Se poate crea imediat un Datastore.<\/p>\n<p><\/p>\n<p>Dup\u0103 crearea Datastore-ului, trebuie s\u0103 ne asigur\u0103m c\u0103 se folose\u0219te politica Round Robin pentru c\u0103ile c\u0103tre Target\/LUN, deoarece aceasta este cea mai performant\u0103.<\/p>\n<p><\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habrastorage.org\/webt\/zh\/zr\/t1\/zhzrt15baoc1qlp0w6ds-mys3hu.png\"><img decoding=\"async\" alt=\"Recomand\u0103ri pentru configurarea AFA AccelStor \u00een lucrul cu VMware vSphere\" src=\"\/wp-content\/uploads\/2019\/04\/621474aa13123cd44518b263f222e6b5.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/p>\n<p><\/p>\n<p>\u00cen mod implicit, set\u0103rile VMware prev\u0103d utilizarea acestei politici conform schemei: 1000 de solicit\u0103ri prin prima cale, urm\u0103toarele 1000 de solicit\u0103ri prin a doua cale etc. Aceast\u0103 interac\u021biune a gazdelor cu un array cu dou\u0103 controle nu va fi echilibrat\u0103. De aceea, recomand\u0103m setarea parametrului Round Robin policy = 1 prin Esxcli\/PowerCLI.<\/p>\n<p>\n<b class=\"spoiler_title\">Set\u0103ri<\/b><\/p>\n<p>Pentru Esxcli:<\/p>\n<p><\/p>\n<ul>\n<li>Afi\u0219a\u021bi LUN-urile disponibile<\/li>\n<\/ul>\n<p><\/p>\n<p><b>esxcli storage nmp device list<\/b><\/p>\n<p><\/p>\n<ul>\n<li>Copia\u021bi Device Name<\/li>\n<li>Modifica\u021bi Round Robin Policy<\/li>\n<\/ul>\n<p><\/p>\n<p><b>esxcli storage nmp psp roundrobin deviceconfig set --type=iops --iops=1 --device=\"Device_ID\"<\/b><\/p>\n<p><\/p>\n<p>Majoritatea aplica\u021biilor moderne sunt proiectate pentru a schimba pachete de date de dimensiuni mari, cu scopul de a maximiza utilizarea l\u0103\u021bimii de band\u0103 \u0219i de a reduce sarcina pe procesorul central. De aceea, ESXi \u00een mod implicit trimite solicit\u0103rile de intrare\/ie\u0219ire c\u0103tre dispozitivul de stocare \u00een por\u021bii de p\u00e2n\u0103 la 32767KB. Totu\u0219i, pentru anumite scenarii, schimbul \u00een por\u021bii mai mici va fi mai performant. \u00cen leg\u0103tur\u0103 cu array-urile AccelStor, acestea sunt urm\u0103toarele scenarii:<\/p>\n<p><\/p>\n<ul>\n<li>Ma\u0219ina virtual\u0103 folose\u0219te UEFI \u00een loc de Legacy BIOS<\/li>\n<li>Se folose\u0219te vSphere Replication<\/li>\n<\/ul>\n<p><\/p>\n<p>Pentru astfel de scenarii, se recomand\u0103 modificarea valorii parametrului Disk.DiskMaxIOSize la 4096.<\/p>\n<p><\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habrastorage.org\/webt\/1g\/et\/3g\/1get3g8odkem1onrpkwjdilbnsi.png\"><img decoding=\"async\" alt=\"Recomand\u0103ri pentru configurarea AFA AccelStor \u00een lucrul cu VMware vSphere\" src=\"\/wp-content\/uploads\/2019\/04\/f7072bb572580d9bd6077afab8c272ba.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/p>\n<p><\/p>\n<p>Pentru conexiunile iSCSI, se recomand\u0103 modificarea parametrului Login Timeout la 30 (de la 5 \u00een mod implicit) pentru a \u00eembun\u0103t\u0103\u021bi stabilitatea conexiunii \u0219i dezactivarea \u00eent\u00e2rzierii confirm\u0103rilor pachetelor retransmise DelayedAck. Ambele op\u021biuni se g\u0103sesc \u00een vSphere Client: Host \u2192 Configure \u2192 Storage \u2192 Storage Adapters \u2192 Advanced Options pentru adaptorul iSCSI.<\/p>\n<p><\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habrastorage.org\/webt\/1y\/5_\/c8\/1y5_c80zsijgqtngo-9vt2zbbo8.png\"><img decoding=\"async\" alt=\"Recomand\u0103ri pentru configurarea AFA AccelStor \u00een lucrul cu VMware vSphere\" src=\"\/wp-content\/uploads\/2019\/04\/e9700594d0074b5439dbb397c081dd48.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habrastorage.org\/webt\/bh\/yi\/tv\/bhyitvuujofnioaunwhzypx3fe0.png\"><img decoding=\"async\" alt=\"Recomand\u0103ri pentru configurarea AFA AccelStor \u00een lucrul cu VMware vSphere\" src=\"\/wp-content\/uploads\/2019\/04\/c2dd6f3aaa6c0648763f66a94af2c251.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/p>\n<p><\/p>\n<p>Un aspect important este num\u0103rul de volume utilizate pentru datastore. Este evident c\u0103, pentru a simplifica gestionarea, exist\u0103 dorin\u021ba de a crea un singur volum mare pentru \u00eentreaga capacitate a array-ului. Totu\u0219i, faptul de a avea mai multe volume \u0219i, prin urmare, datastores, afecteaz\u0103 pozitiv performan\u021ba general\u0103 (mai multe detalii despre cozi mai jos). De aceea, recomand\u0103m crearea a cel pu\u021bin dou\u0103 volume.<\/p>\n<p><\/p>\n<p>Cu c\u00e2teva vreme \u00een urm\u0103, VMware recomanda limitarea num\u0103rului de ma\u0219ini virtuale pe un singur datastore din acela\u0219i motiv de a ob\u021bine o performan\u021b\u0103 maxim\u0103. Totu\u0219i, acum, \u00een special odat\u0103 cu r\u0103sp\u00e2ndirea VDI, aceast\u0103 problem\u0103 nu mai este at\u00e2t de stringent\u0103. Dar acest lucru nu anuleaz\u0103 regula veche \u2013 distribuirea ma\u0219inilor virtuale care necesit\u0103 un IO intens pe diferite datastores. Pentru a determina num\u0103rul optim de VM-uri pe un volum, nu exist\u0103 nimic mai bun dec\u00e2t a efectua <noindex><a rel=\"nofollow\" href=\"http:\/\/accelstor.ru\/page\/zaprosit-demo\">testare de \u00eenc\u0103rcare a array-ului All Flash AccelStor <\/a><\/noindex>\u00een cadrul infrastructurii proprii.<\/p>\n<p><\/p>\n<h3><i><b>Configurarea ma\u0219inilor virtuale<\/b><\/i><\/h3>\n<p><\/p>\n<p>La configurarea ma\u0219inilor virtuale nu exist\u0103 cerin\u021be speciale, adic\u0103 acestea sunt destul de obi\u0219nuite:<\/p>\n<p><\/p>\n<ul>\n<li>Folosirea celei mai recente versiuni posibile a VM (compatibility)<\/li>\n<li>Acorda\u021bi mai mult\u0103 aten\u021bie dimensiunii RAM-ului atunci c\u00e2nd plasa\u021bi dens ma\u0219inile virtuale, de exemplu, \u00een VDI (deoarece, \u00een mod implicit, la pornire se creeaz\u0103 un fi\u0219ier de swap de dimensiuni similar cu RAM-ul, ceea ce consum\u0103 capacitatea util\u0103 \u0219i afecteaz\u0103 performan\u021ba final\u0103)<\/li>\n<li>Utiliza\u021bi cele mai performante versiuni de adaptori \u00een ceea ce prive\u0219te IO: tipul de re\u021bea VMXNET 3 \u0219i SCSI de tip PVSCSI<\/li>\n<li>Utiliza\u021bi tipul de disc Thick Provision Eager Zeroed pentru performan\u021b\u0103 maxim\u0103 \u0219i Thin Provisioning pentru utilizarea eficient\u0103 a spa\u021biului de stocare<\/li>\n<li>Dac\u0103 este posibil, limita\u021bi activitatea ma\u0219inilor necritice la IO prin intermediul Virtual Disk Limit<\/li>\n<li>Asigura\u021bi-v\u0103 c\u0103 VMware Tools sunt instalate <\/li>\n<\/ul>\n<p><\/p>\n<h3><i><b>Observa\u021bii despre cozi<\/b><\/i><\/h3>\n<p><\/p>\n<p>Coada (sau I\/O-uri outstanding) se refer\u0103 la num\u0103rul de cereri de intrare\/ie\u0219ire (comenzi SCSI) care a\u0219teapt\u0103 procesarea \u00een fiecare moment pentru un anumit dispozitiv\/aplica\u021bie. \u00cen cazul \u00een care coada este suprasaturat\u0103, se emit erori QFULL, ceea ce duce \u00een final la cre\u0219terea parametrului de laten\u021b\u0103. Atunci c\u00e2nd sunt utilizate sisteme de stocare pe disc (spindle), teoretic, cu c\u00e2t coada este mai mare, cu at\u00e2t performan\u021ba acestora este mai ridicat\u0103. Totu\u0219i, nu trebuie s\u0103 se abuzeze, deoarece risca\u021bi s\u0103 \u00eent\u00e2lni\u021bi QFULL. \u00cen cazul sistemelor All Flash, pe de o parte, lucrurile sunt pu\u021bin mai simple: deoarece matricea are \u00eent\u00e2rzieri cu ordine de m\u0103rime mai mici, \u00een cele mai multe cazuri nu este necesar\u0103 ajustarea separat\u0103 a dimensiunilor cozilor. Pe de alt\u0103 parte, \u00een unele scenarii de utilizare (un dezechilibru puternic \u00een cerin\u021bele de I\/O pentru anumite ma\u0219ini virtuale, teste de performan\u021b\u0103 maxim\u0103 etc.) este necesar, dac\u0103 nu s\u0103 modifica\u021bi parametrii cozilor, m\u0103car s\u0103 \u00een\u021belege\u021bi ce valori pot fi atinse \u0219i, cel mai important, prin ce metode.<\/p>\n<p><\/p>\n<p>Pe matricea All Flash AccelStor nu exist\u0103 limite \u00een ceea ce prive\u0219te volumele sau porturile de intrare\/ie\u0219ire. Dac\u0103 este necesar, chiar \u0219i un singur volum poate beneficia de toate resursele matricei. Singura limitare a cozilor se afl\u0103 la \u021bintele iSCSI. Din acest motiv, a fost men\u021bionat\u0103 anterior necesitatea de a crea mai multe (ideal p\u00e2n\u0103 la 8) \u021binte pentru fiecare volum pentru a dep\u0103\u0219i aceast\u0103 limit\u0103. De asemenea, repet\u0103m c\u0103 matricele AccelStor sunt solu\u021bii de \u00eenalt\u0103 performan\u021b\u0103. Prin urmare, trebuie folosite toate porturile de interfa\u021b\u0103 ale sistemului pentru a atinge viteza maxim\u0103.<\/p>\n<p><\/p>\n<p>Din perspectiva gazdelor ESXi, situa\u021bia este complet diferit\u0103. Gazda aplic\u0103 practica accesului egal la resurse pentru to\u021bi participan\u021bii. Prin urmare, exist\u0103 cozi IO separate pentru sistemul de operare guest \u0219i HBA. Cozile pentru sistemul de operare guest sunt combinate din cozile c\u0103tre adaptorul SCSI virtual \u0219i discul virtual:<\/p>\n<p><\/p>\n<p><img decoding=\"async\" alt=\"Recomand\u0103ri pentru configurarea AFA AccelStor \u00een lucrul cu VMware vSphere\" src=\"\/wp-content\/uploads\/2019\/04\/e6033427e6f554490c9a6460574b7f6e.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>Coada HBA depinde de tipul\/v\u00e2nz\u0103torul specific:<\/p>\n<p><\/p>\n<p><img decoding=\"async\" alt=\"Recomand\u0103ri pentru configurarea AFA AccelStor \u00een lucrul cu VMware vSphere\" src=\"\/wp-content\/uploads\/2019\/04\/a0b078e63bdf8f306a25bfecd1310cb0.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>Performan\u021ba final\u0103 a ma\u0219inii virtuale va fi determinat\u0103 de cea mai mic\u0103 valoare a limitelor cozii (Queue Depth limit) dintre componentele gazdei. <\/p>\n<p><\/p>\n<p>Datorit\u0103 acestor valori, putem evalua indicatorii de performan\u021b\u0103 pe care \u00eei putem ob\u021bine \u00een diferite configura\u021bii. De exemplu, dorim s\u0103 cunoa\u0219tem performan\u021ba teoretic\u0103 a unei ma\u0219ini virtuale (f\u0103r\u0103 legare la un bloc) cu o laten\u021b\u0103 de 0,5 ms. Atunci IOPS-ul s\u0103u = (1,000\/latency) * Outstanding I\/Os (Limit\u0103 de ad\u00e2ncime a cozii)<\/p>\n<p>\n<b class=\"spoiler_title\">Exemple<\/b><\/p>\n<p><b>Exemplu 1<\/b><\/p>\n<p><\/p>\n<ul>\n<li>FC Emulex HBA Adapter<\/li>\n<li>O VM pe datastore<\/li>\n<li>VMware Paravirtual SCSI Adapter<\/li>\n<\/ul>\n<p><\/p>\n<p>Aici, limita de ad\u00e2ncime a cozii este determinat\u0103 de Emulex HBA. Prin urmare, IOPS = (1000\/0.5)*32 = 64K<\/p>\n<p><\/p>\n<p><b>Exemplu 2<\/b><\/p>\n<p><\/p>\n<ul>\n<li>VMware iSCSI Software Adapter<\/li>\n<li>O VM pe datastore<\/li>\n<li>VMware Paravirtual SCSI Adapter<\/li>\n<\/ul>\n<p><\/p>\n<p>Aici, limita de ad\u00e2ncime a cozii este determinat\u0103 de Paravirtual SCSI Adapter. Prin urmare, IOPS = (1000\/0.5)*64 = 128K<\/p>\n<p><\/p>\n<p>Modelele de top ale sistemelor All Flash AccelStor (de exemplu, <noindex><a rel=\"nofollow\" href=\"http:\/\/accelstor.ru\/product\/neosapphire-p710\">P710<\/a><\/noindex>) sunt capabile s\u0103 ofere o performan\u021b\u0103 de 700K IOPS la scriere cu un bloc de 4K. La acest dimensiune a blocului, este evident c\u0103 o singur\u0103 ma\u0219in\u0103 virtual\u0103 nu poate solicita un astfel de sistem. Pentru aceasta va fi nevoie de 11 (pentru exemplul 1) sau 6 (pentru exemplul 2) ma\u0219ini virtuale.<\/p>\n<p><\/p>\n<p>\u00cen final, cu o configurare corect\u0103 a tuturor componentelor descrise ale centrului de date virtual, se pot ob\u021bine rezultate foarte impresionate \u00een ceea ce prive\u0219te performan\u021ba.<\/p>\n<p><\/p>\n<p><img decoding=\"async\" alt=\"Recomand\u0103ri pentru configurarea AFA AccelStor \u00een lucrul cu VMware vSphere\" src=\"\/wp-content\/uploads\/2019\/04\/eee93cccf16539410695c6f79d94deda.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><i>4K Random, 70% Citire\/30% Scriere<\/i><\/p>\n<p><\/p>\n<p>\u00cen realitate, lumea este mult mai complex\u0103 pentru a fi descris\u0103 printr-o formul\u0103 simpl\u0103. Pe un singur host, exist\u0103 \u00eentotdeauna mai multe ma\u0219ini virtuale cu configura\u021bii \u0219i cerin\u021be IO diferite. De asemenea, procesorul host-ului gestioneaz\u0103 opera\u021biunile de intrare\/ie\u0219ire, cu puterea sa care nu este infinit\u0103. Astfel, pentru a valorifica poten\u021bialul complet al acelea\u0219i <noindex><a rel=\"nofollow\" href=\"http:\/\/accelstor.ru\/product\/neosapphire-p710\">modele P710<\/a><\/noindex> \u00een realitate, sunt necesare cel pu\u021bin trei hosts. \u00cen plus, aplica\u021biile care func\u021bioneaz\u0103 \u00een interiorul ma\u0219inilor virtuale aduc propriile lor ajust\u0103ri. Prin urmare, pentru un dimensionare precis\u0103, v\u0103 recomand\u0103m <noindex><a rel=\"nofollow\" href=\"http:\/\/accelstor.ru\/page\/zaprosit-demo\">s\u0103 utiliza\u021bi testarea modelului \u00een practic\u0103<\/a><\/noindex> sistemelor All Flash <noindex><a rel=\"nofollow\" href=\"http:\/\/accelstor.ru\/\">AccelStor<\/a><\/noindex> \u00een cadrul infrastructurii clientului pe sarcini reale.<\/p>\n<p>Sursa: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/accelstor\/blog\/447390\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0412 \u0440\u0430\u043c\u043a\u0430\u0445 \u0434\u0430\u043d\u043d\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0438 \u0445\u043e\u0442\u0435\u043b\u043e\u0441\u044c \u0431\u044b \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u0430\u0442\u044c \u043e\u0431 \u043e\u0441\u043e\u0431\u0435\u043d\u043d\u043e\u0441\u0442\u044f\u0445 \u0440\u0430\u0431\u043e\u0442\u044b All Flash \u043c\u0430\u0441\u0441\u0438\u0432\u043e\u0432 AccelStor \u0441 \u043e\u0434\u043d\u043e\u0439 \u0438\u0437 \u043f\u043e\u043f\u0443\u043b\u044f\u0440\u043d\u0435\u0439\u0448\u0438\u0445 \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u0438 \u2013 VMware vSphere. \u0412 \u0447\u0430\u0441\u0442\u043d\u043e\u0441\u0442\u0438, \u0430\u043a\u0446\u0435\u043d\u0442\u0438\u0440\u043e\u0432\u0430\u0442\u044c \u0432\u043d\u0438\u043c\u0430\u043d\u0438\u0435 \u043d\u0430 \u0442\u0435\u0445 \u043f\u0430\u0440\u0430\u043c\u0435\u0442\u0440\u0430\u0445, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043f\u043e\u043c\u043e\u0433\u0443\u0442 \u043f\u043e\u043b\u0443\u0447\u0438\u0442\u044c \u043c\u0430\u043a\u0441\u0438\u043c\u0430\u043b\u044c\u043d\u044b\u0439 \u044d\u0444\u0444\u0435\u043a\u0442 \u043e\u0442 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u044f \u0442\u0430\u043a\u043e\u0433\u043e \u043c\u043e\u0449\u043d\u043e\u0433\u043e \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u0430, \u043a\u0430\u043a All Flash. All Flash \u043c\u0430\u0441\u0441\u0438\u0432\u044b AccelStor NeoSapphire\u2122 \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u044f\u044e\u0442 \u0441\u043e\u0431\u043e\u0439 \u043e\u0434\u043d\u043e \u0438\u043b\u0438 \u0434\u0432\u0443\u0445 \u043d\u043e\u0434\u043e\u0432\u044b\u0435 \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0430 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":23196,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-31230","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 \u0440\u0430\u043c\u043a\u0430\u0445 \u0434\u0430\u043d\u043d\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0438 \u0445\u043e\u0442\u0435\u043b\u043e\u0441\u044c \u0431\u044b \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u0430\u0442\u044c \u043e\u0431 \u043e\u0441\u043e\u0431\u0435\u043d\u043d\u043e\u0441\u0442\u044f\u0445 \u0440\u0430\u0431\u043e\u0442\u044b All Flash \u043c\u0430\u0441\u0441\u0438\u0432\u043e\u0432 AccelStor \u0441 \u043e\u0434\u043d\u043e\u0439 \u0438\u0437 \u043f\u043e\u043f\u0443\u043b\u044f\u0440\u043d\u0435\u0439\u0448\u0438\u0445 \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u0438 \u2013 VMware vSphere.\" \/>\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\/rekomendatsii-po-nastrojke-afa-accelstor-pri-rabote-s-vmware-vsphere\" \/>\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\u0420\u0435\u043a\u043e\u043c\u0435\u043d\u0434\u0430\u0446\u0438\u0438 \u043f\u043e \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0435 AFA AccelStor \u043f\u0440\u0438 \u0440\u0430\u0431\u043e\u0442\u0435 \u0441 VMware vSphere | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0412 \u0440\u0430\u043c\u043a\u0430\u0445 \u0434\u0430\u043d\u043d\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0438 \u0445\u043e\u0442\u0435\u043b\u043e\u0441\u044c \u0431\u044b \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u0430\u0442\u044c \u043e\u0431 \u043e\u0441\u043e\u0431\u0435\u043d\u043d\u043e\u0441\u0442\u044f\u0445 \u0440\u0430\u0431\u043e\u0442\u044b All Flash \u043c\u0430\u0441\u0441\u0438\u0432\u043e\u0432 AccelStor \u0441 \u043e\u0434\u043d\u043e\u0439 \u0438\u0437 \u043f\u043e\u043f\u0443\u043b\u044f\u0440\u043d\u0435\u0439\u0448\u0438\u0445 \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u0438 \u2013 VMware vSphere.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/rekomendatsii-po-nastrojke-afa-accelstor-pri-rabote-s-vmware-vsphere\" \/>\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=\"2019-10-31T18:40:10+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T18:40:10+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\udd47Recomand\u0103ri pentru configurarea AFA AccelStor \u00een colaborare cu VMware vSphere | ProHoster","description":"\u00cen cadrul acestui articol, ne propunem s\u0103 discut\u0103m despre particularit\u0103\u021bile func\u021bion\u0103rii sistemelor All Flash AccelStor cu una dintre cele mai populare platforme de virtualizare - VMware vSphere.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/rekomendatsii-po-nastrojke-afa-accelstor-pri-rabote-s-vmware-vsphere","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\u0420\u0435\u043a\u043e\u043c\u0435\u043d\u0434\u0430\u0446\u0438\u0438 \u043f\u043e \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0435 AFA AccelStor \u043f\u0440\u0438 \u0440\u0430\u0431\u043e\u0442\u0435 \u0441 VMware vSphere | ProHoster","og:description":"\u0412 \u0440\u0430\u043c\u043a\u0430\u0445 \u0434\u0430\u043d\u043d\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0438 \u0445\u043e\u0442\u0435\u043b\u043e\u0441\u044c \u0431\u044b \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u0430\u0442\u044c \u043e\u0431 \u043e\u0441\u043e\u0431\u0435\u043d\u043d\u043e\u0441\u0442\u044f\u0445 \u0440\u0430\u0431\u043e\u0442\u044b All Flash \u043c\u0430\u0441\u0441\u0438\u0432\u043e\u0432 AccelStor \u0441 \u043e\u0434\u043d\u043e\u0439 \u0438\u0437 \u043f\u043e\u043f\u0443\u043b\u044f\u0440\u043d\u0435\u0439\u0448\u0438\u0445 \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u0438 \u2013 VMware vSphere.","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/rekomendatsii-po-nastrojke-afa-accelstor-pri-rabote-s-vmware-vsphere","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":"2019-10-31T18:40:10+00:00","article:modified_time":"2019-10-31T18:40:10+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"31230","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":"2026-01-21 05:09:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 03:20:31","updated":"2026-01-21 05:09:19","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\/31230","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=31230"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/31230\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/23196"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=31230"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=31230"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=31230"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}