{"id":382,"date":"2018-06-03T17:38:50","date_gmt":"2018-06-03T15:38:50","guid":{"rendered":"https:\/\/virtualguru.cz\/?p=382"},"modified":"2018-06-05T09:57:31","modified_gmt":"2018-06-05T07:57:31","slug":"2-node-direct-connect-vsan-networking-best-practices","status":"publish","type":"post","link":"https:\/\/virtualguru.cz\/en\/2018\/06\/03\/2-node-direct-connect-vsan-networking-best-practices\/","title":{"rendered":"2-node Direct Connect vSAN networking best practices"},"content":{"rendered":"<p>Dvounodov\u00fd cluster je nejmen\u0161\u00ed mo\u017en\u00e1 konfigurace vSAN. Tato konfigurace je prim\u00e1rn\u011b ur\u010dena pro pobo\u010dky firem, kter\u00e9 pot\u0159ebuj\u00ed \u010d\u00e1st v\u00fdpo\u010detn\u00edho v\u00fdkonu lok\u00e1ln\u011b (navrhnuto pro americk\u00fd trh). V \u010cesk\u00e9 republice je v\u0161ak takov\u00fdto cluster pou\u017eiteln\u00fd jako prim\u00e1rn\u00ed serverov\u00e1 infrastruktura pro men\u0161\u00ed firmy. Poskytuje redundanci v\u0161ech hlavn\u00edch komponent (v\u00fdpo\u010detn\u00ed a diskov\u00fd v\u00fdkon). Cel\u00e1 konfigurace se skl\u00e1d\u00e1 ze dvou server\u016f a m\u00edsta, kde je um\u00edst\u011bno witness VM (to m\u016f\u017ee b\u00fdt n\u011bjak\u00fd serv\u0159\u00edk s minimem prost\u0159edk\u016f, stejn\u011b tak ale m\u016f\u017ee b\u00fdt um\u00edst\u011bno n\u011bkde v datov\u00e9m centru).<\/p>\n<p><a href=\"https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/vSAN-lokality.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-386\" src=\"https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/vSAN-lokality.png\" alt=\"\" width=\"1333\" height=\"1051\" srcset=\"https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/vSAN-lokality.png 1333w, https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/vSAN-lokality-300x237.png 300w, https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/vSAN-lokality-768x606.png 768w, https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/vSAN-lokality-1024x807.png 1024w\" sizes=\"auto, (max-width: 1333px) 100vw, 1333px\" \/><\/a>My se dnes budeme bavit o tom, jak takov\u00fd cluster s\u00ed\u0165ov\u011b spojit a jak\u00e1 jsou \u00faskal\u00ed n\u011bkter\u00fdch voleb. Nebudu zde popisovat z\u00e1klady vSphere networkingu, ty jsou detailn\u011b pops\u00e1ny <a href=\"https:\/\/docs.vmware.com\/en\/VMware-vSphere\/6.5\/com.vmware.vsphere.networking.doc\/GUID-35B40B0B-0C13-43B2-BC85-18C9C91BE2D4.html\">zde<\/a>, stejn\u011b tak v\u0161eobecn\u00e1 doporu\u010den\u00ed vSAN networkignu jsou pops\u00e1na <a href=\"https:\/\/storagehub.vmware.com\/t\/vmware-vsan\/vmware-r-vsan-tm-network-design\/\">zde<\/a>.<\/p>\n<h4>Propojen\u00ed nod\u016f<\/h4>\n<p>Jedna z v\u00fdhod dvounodov\u00e9ho \u0159e\u0161en\u00ed je, \u017ee pro vSAN a vMotion traffic lze pou\u017e\u00edt pouze pasivn\u00ed p\u0159enosov\u00e9 m\u00e9dium. Nen\u00ed tak pot\u0159eba \u017e\u00e1dn\u00fdch switch\u016f. Sta\u010d\u00ed m\u00edt dva voln\u00e9 porty a ty propojit proti sob\u011b. Samoz\u0159ejm\u011b porty vol\u00edme dle zam\u00fd\u0161len\u00e9 konfigurace. Pokud zam\u00fd\u0161l\u00edte hybridn\u00ed \u0159e\u0161en\u00ed (SSD pro cache a rota\u010dn\u00ed disky jako storage), sta\u010d\u00ed v\u00e1m 1Gb porty, v All-flash variant\u011b jsou ji\u017e po\u017eadov\u00e1ny 10Gb porty. V\u0161eobecn\u011b v\u017edy doporu\u010duji pou\u017e\u00edt 10Gb porty, ide\u00e1ln\u011b dv\u011b dvouportov\u00e9 karty. M\u00e1te tak redundanci proti chyb\u011b jedn\u00e9 z nich a zb\u00fdvaj\u00edc\u00ed porty se daj\u00ed pou\u017e\u00edt pr\u00e1v\u011b nap\u0159. pro vMotion. Jeliko\u017e u tohoto \u0159e\u0161en\u00ed nepot\u0159ebujeme dal\u0161\u00ed networing, tak 10Gb NIC nejsou z\u00e1sadn\u00edm prodra\u017een\u00edm \u0159e\u0161en\u00ed.<\/p>\n<h4>Propojen\u00ed witness<\/h4>\n<p>Jak jsem psal v \u00favodu, witness VM m\u016f\u017ee b\u011b\u017eet teoreticky kdekoliv. Mus\u00ed b\u00fdt pouze zachov\u00e1ny minim\u00e1ln\u00ed po\u017eadavky konektivity, 1,5 Mbps \u0161\u00ed\u0159ka p\u00e1sma a latence ni\u017e\u0161\u00ed ne\u017e 500ms. Doporu\u010den\u00e9 hodnoty bych ale zva\u017eoval p\u0159ed samotn\u00fdm nasazen\u00edm s ohledem na zam\u00fd\u0161len\u00fd po\u010det a velikost VM (rozhoduj\u00edc\u00ed je po\u010det objekt\u016f). P\u0159esn\u00fd v\u00fdpo\u010det je pops\u00e1n <a href=\"https:\/\/storagehub.vmware.com\/t\/vmware-vsan\/vsan-stretched-cluster-bandwidth-sizing\/bandwidth-requirements-between-witness-data-site\/\">zde<\/a>.<\/p>\n<h4>Z\u00e1kladn\u00ed vlastnosti<\/h4>\n<p>&#8211; pro vSAN traffic se pou\u017e\u00edv\u00e1 VMkernel port<br \/>\n&#8211; vSAN nepodporuje multipath<br \/>\n&#8211; jumbo frames je doporu\u010den (MTU 9000)<\/p>\n<h2>Sc\u00e9n\u00e1\u0159e<\/h2>\n<h3>1) Pou\u017eit\u00ed dvou VMkernel port\u016f<\/h3>\n<p><a href=\"https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/1.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-388\" src=\"https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/1.png\" alt=\"\" width=\"1042\" height=\"974\" srcset=\"https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/1.png 1042w, https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/1-300x280.png 300w, https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/1-768x718.png 768w, https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/1-1024x957.png 1024w\" sizes=\"auto, (max-width: 1042px) 100vw, 1042px\" \/><\/a><\/p>\n<p>Tento sc\u00e9n\u00e1\u0159 je podporovan\u00fd, ale nedoporu\u010dovan\u00fd. Existuj\u00ed sice dv\u011b na sob\u011b naprosto nez\u00e1visl\u00e9 cesty, a tak je sc\u00e9n\u00e1\u0159 podobn\u00fd klasick\u00fdm SAN s\u00edt\u00edm, nicm\u00e9n\u011b m\u00e1 mnoho nev\u00fdhod dan\u00fdch vlastnostmi vSAN nap\u0159.:<\/p>\n<ul>\n<li>vSphere ani vSAN nepodporuj\u00ed v\u00edce VMkernel adapt\u00e9r\u016f ve stejn\u00e9m subnetu, ka\u017ed\u00fd vmkX tak mus\u00ed m\u00edt IP z jin\u00e9ho rozsahu, viz. VMware KB <a href=\"https:\/\/kb.vmware.com\/s\/article\/2010877\">2010877<\/a><\/li>\n<li>ka\u017ed\u00fd VMkernel port mus\u00ed m\u00edt p\u0159i\u0159azeny dva fyzick\u00e9 uplinky, v opa\u010dn\u00e9m p\u0159\u00edpad\u011b vSphere hl\u00e1s\u00ed chybu &#8222;network uplink redundancy lost&#8220;<\/li>\n<li>vzhledem k tomu, \u017ee vSAN nepodporuje multipath, tento sc\u00e9n\u00e1\u0159 nep\u0159in\u00e1\u0161\u00ed benefit rozkladu z\u00e1t\u011b\u017ee<\/li>\n<li>p\u0159i selh\u00e1n\u00ed aktivn\u00ed cesty m\u016f\u017ee v n\u011bkter\u00fd konfigurac\u00edch trvat p\u0159echod na dal\u0161\u00ed cestu a\u017e 90 sekund, toto je zp\u016fsobeno ESXi TCP connection timeoutem<\/li>\n<\/ul>\n<h3>2) Pou\u017e\u00edt\u00ed jednoho VMkernel portu<\/h3>\n<p><a href=\"https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/2.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-389\" src=\"https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/2.png\" alt=\"\" width=\"962\" height=\"771\" srcset=\"https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/2.png 962w, https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/2-300x240.png 300w, https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/2-768x616.png 768w\" sizes=\"auto, (max-width: 962px) 100vw, 962px\" \/><\/a>Tento sc\u00e9n\u00e1\u0159 minimalizuje konfiguraci, zjednodu\u0161uje troubleshooting, a pokud se spr\u00e1vn\u011b nastav\u00ed teaming a failover, tak v\u00e1s ne\u010dekaj\u00ed \u017e\u00e1dn\u00e1 nep\u0159\u00edjemn\u00e1 p\u0159ekvapen\u00ed. Uk\u00e1\u017eeme si tedy, jak\u00e9 volby m\u00e1me k dispozici.<\/p>\n<p><a href=\"https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/3.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-390\" src=\"https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/3.png\" alt=\"\" width=\"993\" height=\"271\" srcset=\"https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/3.png 993w, https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/3-300x82.png 300w, https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/3-768x210.png 768w\" sizes=\"auto, (max-width: 993px) 100vw, 993px\" \/><\/a><strong>Load balancing<\/strong> &#8211; jedin\u00e9 smyslupln\u00e9 varianty jsou &#8222;Route Based on Physical NIC&#8220; a &#8222;Route Based on Originating Virtual Port&#8220;, z\u00e1le\u017e\u00ed sp\u00ed\u0161 na tom, jak\u00fd typ virtu\u00e1ln\u00edho switche pou\u017eijete, jestli VSS nebo VDS.<br \/>\n<strong>Network failure detection a Notify switches<\/strong> &#8211; tyto parametry ponech\u00e1me v defaultu, jejich dal\u0161\u00ed volby nemaj\u00ed u direct connect \u0159e\u0161en\u00ed smysl.<br \/>\n<strong>Failback<\/strong> &#8211; je volba, kter\u00e1 m\u016f\u017ee mnoh\u00e9 ovlivnit. Z\u00e1le\u017e\u00ed v\u0161ak na nastaven\u00ed &#8222;Failover Order&#8220;, viz. d\u00e1le.<\/p>\n<h4>Failover Order Active\/Active<\/h4>\n<p><a href=\"https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/Active-Active.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-393\" src=\"https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/Active-Active.png\" alt=\"\" width=\"175\" height=\"152\" \/><\/a>Tato volba na prvn\u00ed pohled vypad\u00e1 p\u011bkn\u011b, ale to, co se za n\u00ed skr\u00fdv\u00e1, u\u017e tak p\u011bkn\u00e9 nen\u00ed. P\u0159ipome\u0148me si, \u017ee vSAN nepodporuje multipath a vSAN traffic nem\u016f\u017ee pou\u017e\u00edt dvou cest z\u00e1rove\u0148. Nastaven\u00ed &#8222;Failback&#8220; v tomto p\u0159\u00edpad\u011b nehraje roli, ob\u011b linky jsou ve stavu &#8222;Active&#8220;, a tak i kdy\u017e jedna vypadne a traffic p\u0159ejde na druhou, tak dokud ta bude aktivn\u00ed, nikdy se nevr\u00e1t\u00ed zp\u011bt, viz. VMware KB <a href=\"https:\/\/kb.vmware.com\/s\/article\/2072928\">2072928<\/a>. Tato volba ale m\u016f\u017ee m\u00edt je\u0161t\u011b hor\u0161\u00ed dopad. Pokud v takto nakonfigurovan\u00e9m clusteru budete cht\u00edt prov\u00e9st b\u011b\u017en\u00fd vSphere update nebo prost\u011b jen restartovat server, tak se vSAN na s\u00ed\u0165ov\u00e9 vrstv\u011b ji\u017e z vysokou pravd\u011bpodobnost\u00ed nespoj\u00ed. Je to zp\u016fsobeno t\u00edm, \u017ee node, kter\u00fd z\u016fstal v provozu,\u00a0 p\u0159e\u0161el na druh\u00fd uplink, a node, kter\u00fd se pr\u00e1v\u011b vr\u00e1til po restartu, vid\u00ed oba uplinky v po\u0159\u00e1dku, tak se zkou\u0161\u00ed spojit po prvn\u00edm uplinku, kde ji\u017e druh\u00fd node nenaslouch\u00e1. Existuj\u00ed dv\u011b varianty, jak tento stav opravit:<\/p>\n<ol>\n<li>jeden z link\u016f fyzicky rozpojit, pak oba nody p\u0159ejdou na jeden zb\u00fdvaj\u00edc\u00ed a v\u0161e se vr\u00e1t\u00ed do funk\u010dn\u00edho stavu<\/li>\n<li>zm\u011bnit\u00a0 &#8222;Failover Order&#8220; nastaven\u00ed<\/li>\n<\/ol>\n<h4>Failover Order Active\/Standby<\/h4>\n<p><a href=\"https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/Active-Standby.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-395\" src=\"https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/Active-Standby.png\" alt=\"\" width=\"173\" height=\"147\" \/><\/a>Dle m\u00e9ho n\u00e1zoru nejvhodn\u011bj\u0161\u00ed mo\u017en\u00e1 varianta. Oba nody maj\u00ed v\u017edy aktivn\u00ed pouze jeden uplink a nedoch\u00e1z\u00ed ke k\u0159\u00ed\u017een\u00ed a p\u0159\u00edpadn\u00e9 nefunk\u010dnosti. V t\u00e9to variant\u011b takt\u00e9\u017e je mo\u017en\u00e9 efektivn\u011b uplatnit volbu &#8222;Failback&#8220;. V t\u00e9to konfiguraci pokud je &#8222;Failback&#8220; nastaven na &#8222;No&#8220; p\u0159i poru\u0161e Uplink 1 p\u0159ejde provoz na Uplink 2, po znovuobnoven\u00ed Uplink 1 v\u0161ak z\u016fst\u00e1v\u00e1 provoz na Uplink2. Pokud je &#8222;Failback&#8220; nastaven na &#8222;Yes&#8220;, tak p\u0159i poru\u0161e Uplink 1 dojde k p\u0159epnut\u00ed na Uplink 2 a po znovuobnoven\u00ed Uplink 1 p\u0159ech\u00e1z\u00ed provoz zp\u011bt na n\u011bj. Toto ale v p\u0159\u00edpad\u011b chyby, kter\u00e1 zp\u016fsobuje flapov\u00e1n\u00ed, m\u016f\u017ee m\u00edt negativn\u00ed vliv na v\u00fdkon. Osobn\u011b si mysl\u00edm, \u017ee nen\u00ed d\u016fvod, aby se p\u0159ech\u00e1zelo zp\u011bt, dokud je cesta, kterou proud\u00ed data, funk\u010dn\u00ed.<\/p>\n<h2>Nastaven\u00ed vSAN a Witness trafficu<\/h2>\n<p>U 2-node Direct Connect clusteru je nutn\u00e9 p\u0159esm\u011brovat witness traffic proti witness VM. T\u00edm, \u017ee jsou nody p\u0159ipojeny proti sob\u011b na p\u0159\u00edmo, nen\u00ed tak witness VM, kam p\u0159ipojit. I vzhledem k tomu, \u017ee witness VM m\u016f\u017ee b\u00fdt mimo lokalitu a komunikace ji\u017e m\u016f\u017ee prob\u00edhat za pomoc\u00ed routingu, je witness traffic odd\u011blen a sm\u011brov\u00e1n ide\u00e1ln\u011b p\u0159es management VMkernel port.<\/p>\n<p><a href=\"https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/vsan-vmkX.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-399\" src=\"https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/vsan-vmkX.png\" alt=\"\" width=\"1240\" height=\"716\" srcset=\"https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/vsan-vmkX.png 1240w, https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/vsan-vmkX-300x173.png 300w, https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/vsan-vmkX-768x443.png 768w, https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/vsan-vmkX-1024x591.png 1024w\" sizes=\"auto, (max-width: 1240px) 100vw, 1240px\" \/><\/a><\/p>\n<h3>Nastaven\u00ed vSAN trafficu<\/h3>\n<p>Lze prov\u00e9st dv\u011bma zp\u016fsoby, z GUI:<\/p>\n<p><a href=\"https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/vSAN-traffic.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-400\" src=\"https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/vSAN-traffic.png\" alt=\"\" width=\"947\" height=\"404\" srcset=\"https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/vSAN-traffic.png 947w, https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/vSAN-traffic-300x128.png 300w, https:\/\/virtualguru.cz\/wp-content\/uploads\/2018\/06\/vSAN-traffic-768x328.png 768w\" sizes=\"auto, (max-width: 947px) 100vw, 947px\" \/><\/a>co\u017e je asi nejrychlej\u0161\u00ed i vzhledem k tomu, \u017ee je nutno VMkernel vytvo\u0159it. Druh\u00e1 varianta je pomoc\u00ed p\u0159\u00edkazu:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\">esxcli vsan network ipv4 add -i vmk1 -T=vsan<\/pre>\n<h3>Nastaven\u00ed Witness trafficu<\/h3>\n<p>Witness traffic lze nastavit pouze z p\u0159\u00edkazov\u00e9 \u0159\u00e1dky pomoc\u00ed p\u0159\u00edkazu:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\">esxcli vsan network ipv4 add -i vmk0 -T=witness<\/pre>\n<h3>Kontrola nastaven\u00ed<\/h3>\n<p>pomoc\u00ed p\u0159\u00edkazu <em>esxcli vsan network list<\/em> zkontrolujeme, \u017ee m\u00e1me spr\u00e1vn\u011b nastaveno<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"no-highlight\">[root@esxi:~] esxcli vsan network list\r\nInterface\r\n   VmkNic Name: vmk1\r\n   IP Protocol: IP\r\n   Interface UUID: 654e125b-4700-e7c1-bf1c-e0071b66d180\r\n   Agent Group Multicast Address: 224.2.3.4\r\n   Agent Group IPv6 Multicast Address: ff19::2:3:4\r\n   Agent Group Multicast Port: 23451\r\n   Master Group Multicast Address: 224.1.2.3\r\n   Master Group IPv6 Multicast Address: ff19::1:2:3\r\n   Master Group Multicast Port: 12345\r\n   Host Unicast Channel Bound Port: 12321\r\n   Multicast TTL: 5\r\n   Traffic Type: vsan\r\n\r\nInterface\r\n   VmkNic Name: vmk0\r\n   IP Protocol: IP\r\n   Interface UUID: 5b50125b-5001-b359-e3da-e0071b66d180\r\n   Agent Group Multicast Address: 224.2.3.4\r\n   Agent Group IPv6 Multicast Address: ff19::2:3:4\r\n   Agent Group Multicast Port: 23451\r\n   Master Group Multicast Address: 224.1.2.3\r\n   Master Group IPv6 Multicast Address: ff19::1:2:3\r\n   Master Group Multicast Port: 12345\r\n   Host Unicast Channel Bound Port: 12321\r\n   Multicast TTL: 5\r\n   Traffic Type: witness<\/pre>\n<p>&nbsp;<\/p>","protected":false},"excerpt":{"rendered":"<p>Dvounodov\u00fd cluster je nejmen\u0161\u00ed mo\u017en\u00e1 konfigurace vSAN. Tato konfigurace je prim\u00e1rn\u011b ur\u010dena pro pobo\u010dky firem, kter\u00e9 pot\u0159ebuj\u00ed \u010d\u00e1st v\u00fdpo\u010detn\u00edho v\u00fdkonu lok\u00e1ln\u011b (navrhnuto pro americk\u00fd trh).&#8230;<\/p>\n<div class=\"more-link-wrapper\"><a class=\"more-link\" href=\"https:\/\/virtualguru.cz\/en\/2018\/06\/03\/2-node-direct-connect-vsan-networking-best-practices\/\">Continue Reading<span class=\"screen-reader-text\">2-node Direct Connect vSAN networking best practices<\/span> <i class=\"fas fa-angle-right\"><\/i><\/a><\/div>","protected":false},"author":3,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"iawp_total_views":25,"footnotes":""},"categories":[5],"tags":[21,13],"class_list":["post-382","post","type-post","status-publish","format-standard","hentry","category-vsan","tag-2-node","tag-vsan","entry"],"_links":{"self":[{"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/posts\/382","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/comments?post=382"}],"version-history":[{"count":13,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/posts\/382\/revisions"}],"predecessor-version":[{"id":580,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/posts\/382\/revisions\/580"}],"wp:attachment":[{"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/media?parent=382"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/categories?post=382"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/tags?post=382"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}