{"id":22680,"date":"2018-01-16T09:00:15","date_gmt":"2018-01-16T08:00:15","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=22680"},"modified":"2023-07-16T11:27:57","modified_gmt":"2023-07-16T09:27:57","slug":"vmware-vcenter-high-availability-setup-pt-1","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/vmware-vcenter-high-availability-setup-pt-1\/","title":{"rendered":"VMware vCenter High Availability: setup - pt.1"},"content":{"rendered":"<p><img decoding=\"async\" class=\"aligncenter wp-image-23048 size-full\" title=\"vcha-setup-01\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-01.jpg\" alt=\"vcha-setup-01\" width=\"602\" height=\"202\" \/><\/p>\n<p>vCenter High Availability (VCHA) is a features introduced in <a href=\"https:\/\/nolabnoparty.com\/en\/mastering-vmware-vsphere-6-5-book-2\/\">VMware vSphere 6.5<\/a> that <strong>eliminates the single point of failure<\/strong> of vCenter and is available for the VCSA 6.5 only.<\/p>\n<p>To implement a VCHA cluster, only a <strong>single vCenter license<\/strong> (standard license is sufficient) is required. VCHA supports both <strong>external PSC<\/strong> (vCenter Server and PSC resides on different VMs) and <strong>embedded PSC<\/strong> (vCenter Server and PSC are on the same VM) deployment models.<!--more--><\/p>\n<p>&nbsp;<\/p>\n<h2>Blog Series<\/h2>\n<p>VMware vCenter High Availability: setup - pt.1<br \/>\n<a href=\"https:\/\/nolabnoparty.com\/en\/vmware-vcenter-high-availability-maintenance-test-failover-pt-2\/\">VMware vCenter High Availability: maintenance and test failover - pt.2<\/a><\/p>\n<p>&nbsp;<\/p>\n<h2>vCenter Server HA architecture<\/h2>\n<p>The vCenter HA architecture includes three nodes:<\/p>\n<ul>\n<li><strong>Active Node<\/strong> - runs the\u00a0active instance of vCenter Server serving the client requests.<\/li>\n<li><strong>Passive Node<\/strong> -\u00a0runs as the passive instance of vCenter Server and constantly receives state updates from the Active node in synchronous mode. Take the role of Active node in the event of failure.<\/li>\n<li><strong>Witness Node<\/strong> - is a light-weight VM that serves as a quorum node and does not take over of Active\/Passive nodes.<\/li>\n<\/ul>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23049 size-large\" title=\"vcha-setup-02\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-02-600x473.jpg\" alt=\"vcha-setup-02\" width=\"600\" height=\"473\" \/><\/p>\n<p>Although traditional architectures uses shared storage to solve the <strong>split-brain problem<\/strong>, that is data\/availability inconsistencies due to network failures within distributed systems maintaining replicated data, the VCHA design <strong>does not assume the use of a shared storage\u2013based deployment<\/strong> in order to support VCHA cluster spanning multiple datacenters. <strong>Three different datastores<\/strong> must be used to store the three VMs and each node should reside on a different host as well. <strong>At least 3 hosts<\/strong> are required to complete the deployment.<\/p>\n<p>A <strong>good network\u00a0connectivity<\/strong> is required between Active and Passive node to guarantee <strong>zero RPO<\/strong> then a <strong>dedicated network<\/strong> separated from the management network must be configured. Clients have access to the VCSA via the management network interface.<\/p>\n<p>In the event of the Active vCenter Server failing, the VCSA works as follow:<\/p>\n<ul>\n<li><strong>Active node fails<\/strong>: until Passive and Witness node can communicate with each other, the Passive node will take over the Active role and starts serving client requests.<\/li>\n<li><strong>Passive node fails<\/strong>: if Active and Witness node can communicate with each other, the Active node will\u00a0continue to server client requests.<\/li>\n<li><strong>Witness node fails<\/strong>: as long as the Active and Passive node can communicate with each other, the Active node will\u00a0continue to serve client requests.<\/li>\n<li><strong>More than one node fails<\/strong>: all three nodes cannot communicate with each other, the cluster is assumed non-functional causing the vCenter Server services disruption.<\/li>\n<li><strong>Isolated node behavior<\/strong>: if a node gets isolated from the cluster, it is automatically taken out of the cluster and all\u00a0services are stopped. For example, if an Active node is isolated, all services are stopped to ensure that the\u00a0Passive node can take over as long as it is connected to the Witness node.<\/li>\n<\/ul>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23050 size-large\" title=\"vcha-setup-03\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-03-600x268.jpg\" alt=\"vcha-setup-03\" width=\"600\" height=\"268\" \/><\/p>\n<p>&nbsp;<\/p>\n<h2>Configure the HA network<\/h2>\n<p>Before proceeding with the VCHA deployment, we need to create a new network since the VCHA cluster <strong>requires an isolated network<\/strong> for the nodes communication.<\/p>\n<p>From vSphere Web Client, select the first host in the cluster then go to <strong>Configure<\/strong> tab. Select <strong>Virtual switches<\/strong> section in order to configure network settings.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23051 size-large\" title=\"vcha-setup-04\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-04-600x275.jpg\" alt=\"vcha-setup-04\" width=\"600\" height=\"275\" \/><\/p>\n<p>Click <strong>Add host network<\/strong> icon to configure the HA network.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23052 size-large\" title=\"vcha-setup-05\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-05-600x389.jpg\" alt=\"vcha-setup-05\" width=\"600\" height=\"389\" \/><\/p>\n<p>Select <strong>Virtual Port Group for a Standard Switch<\/strong>\u00a0as connection type then click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23053 size-large\" title=\"vcha-setup-06\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-06-600x351.jpg\" alt=\"vcha-setup-06\" width=\"600\" height=\"351\" \/><\/p>\n<p>Thick <strong>Select an existing standard switch<\/strong> option\u00a0and click <strong>Browse<\/strong> to select the vSwicth to use. Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23055 size-large\" title=\"vcha-setup-07\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-07-600x351.jpg\" alt=\"vcha-setup-07\" width=\"600\" height=\"351\" \/><\/p>\n<p>Enter a <strong>Network label\u00a0<\/strong>and optionally a <strong>VLAN ID<\/strong>. Click <strong>Next<\/strong> to continue.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23056 size-large\" title=\"vcha-setup-08\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-08-600x351.jpg\" alt=\"vcha-setup-08\" width=\"600\" height=\"351\" \/><\/p>\n<p>Click <strong>Finish<\/strong> to create the new Port Group.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23057 size-large\" title=\"vcha-setup-09\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-09-600x351.jpg\" alt=\"vcha-setup-09\" width=\"600\" height=\"351\" \/><\/p>\n<p>The HA Port Group has been created.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23058 size-large\" title=\"vcha-setup-10\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-10-600x291.jpg\" alt=\"vcha-setup-10\" width=\"600\" height=\"291\" \/><\/p>\n<p>Now <strong>repeat same steps<\/strong> for all other hosts members of the cluster.<\/p>\n<p>&nbsp;<\/p>\n<h2>Deploy vCenter HA with the embedded PSC<\/h2>\n<p>Once the HA network is ready, we can proceed with the vCenter High Availability configuration.<\/p>\n<p>The VCHA cluster can be deployed in two ways:<\/p>\n<ul>\n<li><strong>Basic<\/strong>\u00a0\u2013 suitable for medium small businesses, the wizard takes care of active\/passive\/witness nodes creation as well as vNIC interfaces. Minimum info are requested by the system, such as IP address. If you have a DRS cluster, VMs placement is done automatically. Keep in mind this deployment method requires an already configured HA network.<\/li>\n<li><strong>Advanced<\/strong>\u00a0\u2013 a more complex setup is needed but provides flexibility to the design (a VM can be placed in a different datacenter or SSO domain for example). The three nodes active\/passive\/witness must be manually created\u00a0providing the required network information.<\/li>\n<\/ul>\n<p>From vSphere Web Client, right click the vCenter Server and select <strong>vCenter HA Settings<\/strong> option.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23059 size-large\" title=\"vcha-setup-11\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-11-600x442.jpg\" alt=\"vcha-setup-11\" width=\"600\" height=\"442\" \/><\/p>\n<p>In the <strong>vCenter HA<\/strong> section click <strong>Configure<\/strong> button to begin the VCHA deployment.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23060 size-large\" title=\"vcha-setup-12\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-12-600x286.jpg\" alt=\"vcha-setup-12\" width=\"600\" height=\"286\" \/><\/p>\n<p>Select <strong>Basic<\/strong> deployment method and click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23061 size-large\" title=\"vcha-setup-13\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-13-600x351.jpg\" alt=\"vcha-setup-13\" width=\"600\" height=\"351\" \/><\/p>\n<p>Specify the <strong>IP address<\/strong> and <strong>subnet mask<\/strong>\u00a0for the Active node, click <strong>Browse<\/strong> and select the <strong>vCenter HA network<\/strong> previously configured. Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23062 size-large\" title=\"vcha-setup-14\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-14-600x351.jpg\" alt=\"vcha-setup-14\" width=\"600\" height=\"351\" \/><\/p>\n<p>Specify the <strong>IP address<\/strong> for the Passive and Witness nodes then click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23063 size-large\" title=\"vcha-setup-15\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-15-600x351.jpg\" alt=\"vcha-setup-15\" width=\"600\" height=\"351\" \/><\/p>\n<p>In the deployment configuration window if\u00a0<strong>VCHA requisites are not met<\/strong>, Passive and Witness nodes may display an error. Click the\u00a0<strong>Compatibility errors<\/strong>\u00a0link to check what's wrong.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23064 size-large\" title=\"vcha-setup-16\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-16-600x351.jpg\" alt=\"vcha-setup-16\" width=\"600\" height=\"351\" \/><\/p>\n<p>The error occurs because Passive and Witness nodes must be <strong>located on different hosts and storage<\/strong> devices. Click <strong>Close<\/strong> to close the window.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23065 size-full\" title=\"vcha-setup-17\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-17.jpg\" alt=\"vcha-setup-17\" width=\"500\" height=\"250\" \/><\/p>\n<p>To fix the problem, click <strong>Edit<\/strong> next to the Passive node's error message.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23066 size-large\" title=\"vcha-setup-18\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-18-600x351.jpg\" alt=\"vcha-setup-18\" width=\"600\" height=\"351\" \/><\/p>\n<p>Enter a name for the virtual machine or leave the default, select the location and click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23067 size-large\" title=\"vcha-setup-19\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-19-600x351.jpg\" alt=\"vcha-setup-19\" width=\"600\" height=\"351\" \/><\/p>\n<p>Select the ESXi host to use and click <strong>Next<\/strong> once the compatibility checks succeed.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23068 size-large\" title=\"vcha-setup-20\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-20-600x351.jpg\" alt=\"vcha-setup-20\" width=\"600\" height=\"351\" \/><\/p>\n<p>Since\u00a0<strong>Datastore clusters are not supported<\/strong>\u00a0by vCenter HA deployment, select a standalone storage not member of any cluster and click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23069 size-large\" title=\"vcha-setup-21\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-21-600x351.jpg\" alt=\"vcha-setup-21\" width=\"600\" height=\"351\" \/><\/p>\n<p>Specify networks used for the management and HA then click <strong>Next<\/strong> to continue.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23070 size-large\" title=\"vcha-setup-22\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-22-600x352.jpg\" alt=\"vcha-setup-22\" width=\"600\" height=\"352\" \/><\/p>\n<p>In the configuration summary, click <strong>Finish<\/strong> to complete the configuration of the <strong>Passive node<\/strong>. Note that the procedure to create the Passive node will perform a\u00a0<strong>clone of the current VM<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23071 size-large\" title=\"vcha-setup-23\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-23-600x351.jpg\" alt=\"vcha-setup-23\" width=\"600\" height=\"351\" \/><\/p>\n<p>The Passive\u00a0node is now marked as compatible. Proceed with the\u00a0<strong>Witness node<\/strong> by clicking the corrisponding <strong>Edit<\/strong> link.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23072 size-large\" title=\"vcha-setup-24\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-24-600x351.jpg\" alt=\"vcha-setup-24\" width=\"600\" height=\"351\" \/><\/p>\n<p>Repeat same procedure as done for the Passive node. Note that you have to specify\u00a0<strong>only the HA network<\/strong>\u00a0for the Witness node.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23073 size-large\" title=\"vcha-setup-25\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-25-600x352.jpg\" alt=\"vcha-setup-25\" width=\"600\" height=\"352\" \/><\/p>\n<p>When the configuration has completed, also the Witness node is marked as compatible. Click <strong>Next<\/strong> to complete the deployment.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23074 size-large\" title=\"vcha-setup-26\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-26-600x351.jpg\" alt=\"vcha-setup-26\" width=\"600\" height=\"351\" \/><\/p>\n<p>When the configuration settings have been verified, click <strong>Finish<\/strong> to proceed with the deployment.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23075 size-large\" title=\"vcha-setup-27\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-27-600x351.jpg\" alt=\"vcha-setup-27\" width=\"600\" height=\"351\" \/><\/p>\n<p>If you are deploying the VCHA nodes in less than three hosts you receive an error. As pre-requisite you <strong>must have at least three hosts<\/strong> to deploy VCHA.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23081 size-full\" title=\"vcha-setup-28\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-28.jpg\" alt=\"vcha-setup-28\" width=\"400\" height=\"166\" \/><\/p>\n<p>As a workaround, this\u00a0<a href=\"https:\/\/www.virtuallyghetto.com\/2016\/11\/how-to-enable-vcenter-server-high-availability-vcha-in-vsphere-6-5-wsingle-esxi-host.html\" target=\"_blank\" rel=\"noopener noreferrer\">post<\/a> published on <em>virtuallyGhetto.com <\/em>blog explains you can <strong>disable the DRS Anti affinity rule<\/strong>\u00a0that blocks the deployment by editing a parameter in the vCenter Server.<\/p>\n<p>From the vCenter Server go to <strong>Configure<\/strong> tab and select <strong>Advanced Settings<\/strong>. Click the <strong>Edit<\/strong> button to modify the requested parameter. In the search box, type the word\u00a0<em>vcha<\/em> to <strong>quickly locate the parameter<\/strong> to modify.<\/p>\n<p>Select the parameter\u00a0<strong>config.vpxd.vcha.drsAntiAffinity<\/strong>\u00a0and replace the <strong>value <em>true<\/em> with <em>false<\/em><\/strong> then click <strong>OK<\/strong> to confirm. Although this setup allows the deployment of the VCHA nodes in two hosts, this configuration should be used in LAB environment only and not in production.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23082 size-large\" title=\"vcha-setup-29\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-29-600x442.jpg\" alt=\"vcha-setup-29\" width=\"600\" height=\"442\" \/><\/p>\n<p>After disabling the DRS Anti-Affinity rule, the deployment of the VCHA nodes succeed.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23083 size-large\" title=\"vcha-setup-30\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-30-600x181.jpg\" alt=\"vcha-setup-30\" width=\"600\" height=\"181\" \/><\/p>\n<p>After some minutes, the deployment of the Passive and Witness nodes is complete. In the <strong>Summary<\/strong>\u00a0tab you can find the <strong>vCenter HA widget<\/strong>\u00a0which indicates the status of the cluster.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23084 size-large\" title=\"vcha-setup-31\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-31-600x399.jpg\" alt=\"vcha-setup-31\" width=\"600\" height=\"399\" \/><\/p>\n<p>In <strong>Configure<\/strong> tab selecting the item<strong> vCenter HA<\/strong> you can see the status of the three nodes.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23085 size-large\" title=\"vcha-setup-32\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-32-600x331.jpg\" alt=\"vcha-setup-32\" width=\"600\" height=\"331\" \/><\/p>\n<p>&nbsp;<\/p>\n<h2>Deploy vCenter HA with an external PSC<\/h2>\n<p>To deploy an HA cluster with an external PSC, you will need at least <strong>two PSC instances behind a load balancer<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-23088 size-large\" title=\"vcha-setup-33\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2017\/12\/vcha-setup-33-600x555.jpg\" alt=\"vcha-setup-33\" width=\"600\" height=\"555\" \/><\/p>\n<p>The configuration of the <strong>HA network<\/strong> and the <strong>deployment of VCHA nodes<\/strong>\u00a0have been completed successfully. <a href=\"https:\/\/nolabnoparty.com\/en\/vmware-vcenter-high-availability-maintenance-test-failover-pt-2\/\">Part 2<\/a> will show how to <strong>manage the VCHA nodes<\/strong> testing the <strong>failover<\/strong>.<\/p>\n<p><img decoding=\"async\" title=\"signature\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/images\/firma.jpg\" alt=\"signature\" \/><\/p>\n","protected":false},"excerpt":{"rendered":"<p>vCenter High Availability (VCHA) is a features introduced in VMware vSphere 6.5 that eliminates the single point of failure of vCenter and is available for the VCSA 6.5 only. To implement a VCHA cluster, only a single vCenter license (standard license is sufficient) is required. VCHA supports both external PSC (vCenter Server and PSC resides on different VMs) and embedded PSC (vCenter Server and PSC are on the same VM) deployment models.<\/p>\n","protected":false},"author":3,"featured_media":23048,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[903,2701],"tags":[1825,1824,583],"class_list":["post-22680","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware-en","category-vsphere-en","tag-availability","tag-high","tag-vcenter-en","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/22680","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=22680"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/22680\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/23048"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=22680"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=22680"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=22680"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}