{"id":82494,"date":"2020-05-22T01:42:24","date_gmt":"2020-05-21T23:42:24","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/ovirt-za-2-chasa-chast-2-ustanovka-menedzhera-i-hostov"},"modified":"2020-05-22T01:42:24","modified_gmt":"2020-05-21T23:42:24","slug":"ovirt-za-2-chasa-chast-2-ustanovka-menedzhera-i-hostov","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/ovirt-za-2-chasa-chast-2-ustanovka-menedzhera-i-hostov","title":{"rendered":"oVirt in 2 Hours. Part 2. Installing the Manager and Hosts","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

This article is the next in the oVirt series, part one here<\/a><\/noindex>.<\/p>\n

Articles<\/h2>\n

<\/p>\n

    \n
  1. Introduction<\/a><\/noindex><\/li>\n
  2. Installing the Manager (ovirt-engine) and Hypervisors (hosts) \u2014 Here We Are<\/li>\n
  3. Additional Settings<\/a><\/noindex><\/li>\n<\/ol>\n

    \nSo, let's discuss the initial installation of the ovirt-engine and ovirt-host components.
    \n    <\/a><\/noindex>
    \nMore details about the installation processes can always be found in     the documentation<\/a><\/noindex>.<\/p>\n

    Content<\/h2>\n

    <\/p>\n

      \n
    1. Installing ovirt-engine<\/a><\/noindex><\/li>\n
    2. Installing ovirt-host<\/a><\/noindex><\/li>\n
    3. Adding a Node to oVirt<\/a><\/noindex><\/li>\n
    4. Configuring the Network Interface<\/a><\/noindex><\/li>\n
    5. Configuring FC<\/a><\/noindex><\/li>\n
    6. Configuring FCoE<\/a><\/noindex><\/li>\n
    7. ISO Image Storage<\/a><\/noindex><\/li>\n
    8. First VM<\/a><\/noindex><\/li>\n<\/ol>\n

      \n<\/a><\/noindex><\/p>\n

      Installing ovirt-engine<\/h2>\n

      \nFor the Engine, the minimum requirements are 2 cores\/4 GiB RAM\/25 GiB storage. Recommended \u2014 at least 4 cores\/16 GiB RAM\/50 GiB storage. We will use the Standalone Manager option, where the engine runs on a dedicated physical or virtual machine outside of the managed cluster. For our installation, we will take a virtual machine, for example, on a standalone ESXi*. It is convenient to use deployment automation tools or cloning from a previously prepared template or using kickstart installation.<\/p>\n

      *Note: For a production system, this is a bad idea, as the manager operates without redundancy and becomes a bottleneck. In this case, it\u2019s better to consider the Self-hosted Engine option.<\/i><\/p>\n

      If necessary, the procedure for converting from Standalone to Self-hosted is described in detail in the documentation<\/a><\/noindex>. In particular, the host needs to execute the reinstall command with Hosted Engine support.<\/p>\n

      On the VM, install CentOS 7 in minimal configuration, then update and reboot the system:<\/p>\n

      $ sudo yum update -y && sudo reboot<\/code><\/pre>\n
      \nFor the virtual machine, it is useful to install the guest agent:<\/p>\n
      $ sudo yum install open-vm-tools<\/code><\/pre>\n
      \nfor VMware ESXi hosts, or for oVirt:<\/p>\n
      $ sudo yum install ovirt-guest-agent<\/code><\/pre>\n
      \nConnect the repository and install the manager:<\/p>\n
      $ sudo yum install https:\/\/resources.ovirt.org\/pub\/yum-repo\/ovirt-release43.rpm\n$ sudo yum install ovirt-engine\n<\/code><\/pre>\n
      \nBasic Setup:<\/p>\n
      $ sudo engine-setup<\/code><\/pre>\n
      \nIn most cases, the default settings are sufficient; to use them automatically, you can run the configuration with the flag:<\/p>\n
      $ sudo engine-setup --accept-defaults<\/code><\/pre>\n
      \nNow we can connect to our new engine at the address ovirt.lab.example.com<\/a><\/noindex>. It's still empty here, so we move on to installing hypervisors.
      \n      <\/a><\/noindex><\/p>\n
      Installing ovirt-host<\/h2>\n
      \nOn the physical host, install CentOS 7 in minimal configuration, then connect the repository, update, and reboot the system:<\/p>\n
      $ sudo yum install https:\/\/resources.ovirt.org\/pub\/yum-repo\/ovirt-release43.rpm\n$ sudo yum update -y && sudo reboot\n<\/code><\/pre>\n
      \nNote: It is convenient to use deployment automation tools or kickstart installation for setup.<\/i><\/p>\n
                              Example kickstart file<\/b>
      \n                        Attention! Existing partitions are automatically deleted!<\/b> Be careful!<\/p>\n
      # System authorization information\nauth --enableshadow --passalgo=sha512\n# Use CDROM installation media\ncdrom\n# Use graphical install\ngraphical\n# Run the Setup Agent on first boot\nfirstboot --enable\nignoredisk --only-use=sda\n# Keyboard layouts\nkeyboard --vckeymap=us --xlayouts='us','ru' --switch='grp:alt_shift_toggle'\n# System language\nlang ru_RU.UTF-8\n\n# Network information\nnetwork  --bootproto=dhcp --device=ens192 --ipv6=auto --activate\nnetwork  --hostname=kvm01.lab.example.com\n\n# Root password 'monteV1DE0'\nrootpw --iscrypted $6$6oPcf0GW9VdmJe5w$6WBucrUPRdCAP.aBVnUfvaEu9ozkXq9M1TXiwOm41Y58DEerG8b3Ulme2YtxAgNHr6DGIJ02eFgVuEmYsOo7.\/\n# User password 'metroP0!is'\nuser --name=mgmt --groups=wheel --iscrypted --password=$6$883g2lyXdkDLbKYR$B3yWx1aQZmYYi.aO10W2Bvw0Jpkl1upzgjhZr6lmITTrGaPupa5iC3kZAOvwDonZ\/6ogNJe\/59GN5U8Okp.qx.\n# System services\nservices --enabled="chronyd"\n# System timezone\ntimezone Europe\/Moscow --isUtc\n# System bootloader configuration\nbootloader --append=" crashkernel=auto" --location=mbr --boot-drive=sda\n# Partition clearing information\nclearpart --all\n# Disk partitioning information\npart \/boot --fstype xfs --size=1024 --ondisk=sda  --label=boot\npart pv.01 --size=45056 --grow\nvolgroup HostVG pv.01 --reserved-percent=20\nlogvol swap --vgname=HostVG --name=lv_swap --fstype=swap --recommended\nlogvol none --vgname=HostVG --name=HostPool --thinpool --size=40960 --grow\nlogvol \/ --vgname=HostVG --name=lv_root --thin --fstype=ext4 --label="root" --poolname=HostPool --fsoptions="defaults,discard" --size=6144 --grow\nlogvol \/var --vgname=HostVG --name=lv_var --thin --fstype=ext4 --poolname=HostPool --fsoptions="defaults,discard" --size=16536\nlogvol \/var\/crash --vgname=HostVG --name=lv_var_crash --thin --fstype=ext4 --poolname=HostPool --fsoptions="defaults,discard" --size=10240\nlogvol \/var\/log --vgname=HostVG --name=lv_var_log --thin --fstype=ext4 --poolname=HostPool --fsoptions="defaults,discard" --size=8192\nlogvol \/var\/log\/audit --vgname=HostVG --name=lv_var_audit --thin --fstype=ext4 --poolname=HostPool --fsoptions="defaults,discard" --size=2048\nlogvol \/home --vgname=HostVG --name=lv_home --thin --fstype=ext4 --poolname=HostPool --fsoptions="defaults,discard" --size=1024\nlogvol \/tmp --vgname=HostVG --name=lv_tmp --thin --fstype=ext4 --poolname=HostPool --fsoptions="defaults,discard" --size=1024\n\n%packages\n@^minimal\n@core\nchrony\nkexec-tools\n\n%end\n\n%addon com_redhat_kdump --enable --reserve-mb='auto'\n\n%end\n\n%anaconda\npwpolicy root --minlen=6 --minquality=1 --notstrict --nochanges --notempty\npwpolicy user --minlen=6 --minquality=1 --notstrict --nochanges --emptyok\npwpolicy luks --minlen=6 --minquality=1 --notstrict --nochanges --notempty\n%end\n# Reboot when the install is finished.\nreboot --eject\n<\/code><\/pre>\n
      \nSave this file, e.g., at ftp.example.com\/pub\/labkvm.cfg<\/a><\/noindex>To use the script when launching the OS installation, select the 'Install CentOS 7' option, enable the editing mode (Tab key), and at the end (with a space, without quotes) add <\/p>\n
      ' inst.ks=ftp:\/\/ftp.example.com\/pub\/labkvm.cfg'<\/code><\/pre>\n
      .
      \nThe installation script deletes existing partitions on \/dev\/sda, creates new ones based on       the developer's recommendations<\/a><\/noindex> (you can view them after installation using the lsblk command). The hostname is set to kvm01.lab.example.com (this can be changed later with the command hostnamectl set-hostname kvm03.lab.example.com), IP address acquisition is automatic, the timezone is Moscow, Russian language support is added.<\/p>\n
      Root user password: monteV1DE0, mgmt user password: metroP0!is.
      \nWarning! Existing partitions are automatically deleted! Be careful!<\/b><\/p>\n
      Repeat (or perform concurrently) on all hosts. From turning on an 'empty' server to its ready state, with 2 long boot cycles, takes about 20 minutes.
      \n      <\/a><\/noindex><\/p>\n
      Adding a node to oVirt<\/h2>\n
      \nIt is done very simply:<\/p>\n
      Compute \u2192 Hosts \u2192 New \u2192\u2026<\/p>\n
      In the wizard, the required fields are Name (display name, e.g., kvm03), Hostname (FQDN, e.g., kvm03.lab.example.com), and the Authentication section\u2014 root user (unchangeable)<\/i> \u2014 password or SSH Public Key.<\/p>\n
      After clicking the button Ok<\/b> You will receive the message \"You haven't configured Power Management for this Host. Are you sure you want to continue?\"<\/i>. This is normal\u2014power management will be covered later, after the host has successfully connected. However, if the machines on which the hosts are installed do not support management (IPMI, iLO, DRAC, etc.), I recommend disabling it: Compute \u2192 Clusters \u2192 Default \u2192 Edit \u2192 Fencing Policy \u2192 Enable fencing, uncheck the box.<\/p>\n
      If the oVirt repository was not connected on the host, the installation will fail, but this is not a big deal\u2014you need to add it, then click Install -> Reinstall.<\/p>\n
      Connecting the host takes no more than 5-10 minutes.
      \n      <\/a><\/noindex><\/p>\n
      Configuring the Network Interface<\/h3>\n
      \nSince we are building a fault-tolerant system, the network connection should also provide a redundant connection, which is done on the Compute \u2192 Hosts \u2192 HOST<\/i> \u2192 Network Interfaces \u2014 Setup Host Networks tab.<\/p>\n
      Depending on the capabilities of your networking equipment and architectural approaches, there are various options. The most optimal connection is to a top-of-rack switch stack, ensuring that the network availability does not break in the event of a failure. Let's consider the example of an LACP aggregated channel. To set up the aggregated channel, 'grab' the 2nd unused adapter with the mouse and 'move' it to the 1st one. A window will open Create New Bond<\/b>, where LACP (Mode 4, Dynamic link aggregation, 802.3ad) is chosen by default. On the switch side, the standard configuration of the LACP group is performed. If it's not possible to build a switch stack, the Active-Backup mode (Mode 1) can be utilized. We will cover VLAN settings in the next article, and more detailed recommendations for network configuration can be found in the document Planning and Prerequisites Guide<\/a><\/noindex>.
      \n      <\/a><\/noindex><\/p>\n
      Configuring FC<\/h2>\n
      \nFibre Channel (FC) is supported 'out of the box' and does not pose any difficulties in use. We will not cover the setup of the storage network, including storage system configuration and zoning fabric switches within the oVirt setup.
      \n      <\/a><\/noindex><\/p>\n
      Configuring FCoE<\/h2>\n
      \nIn my opinion, FCoE has not gained widespread adoption in storage networks, but it is often used on servers as a 'last mile', for example, in HPE Virtual Connect.<\/p>\n
                              Configuring FCoE requires a few additional straightforward steps.<\/b><\/p>\n
      Setup FCoE Engine<\/h4>\n
      \nArticle on the Red Hat website B.3. How to Set Up Red Hat Virtualization Manager to Use FCoE
      \nOn the Manager<\/a><\/noindex>, we add the key to the manager with the following command and restart it:<\/p>\n
      \n$ sudo engine-config -s UserDefinedNetworkCustomProperties='fcoe=^((enable|dcb|auto_vlan)=(yes|no),?)*$'\n$ sudo systemctl restart ovirt-engine.service\n<\/code><\/pre>\n
      <\/p>\n
      Setup Node FCoE<\/h4>\n
      \nYou need to install on oVirt Hosts <\/p>\n
      $ sudo yum install vdsm-hook-fcoe<\/code><\/pre>\n
      \nNext, the standard FCoE configuration, as per the article on Red Hat: 25.5. Configuring a Fibre Channel over Ethernet Interface<\/a><\/noindex>.<\/p>\n
      For Broadcom CNA, we look additionally at User Guide FCoE Configuration for Broadcom-Based Adapters<\/a><\/noindex>.<\/p>\n
      Ensure that the necessary packages (already included in minimal) are installed:<\/p>\n
      $ sudo yum install fcoe-utils lldpad<\/code><\/pre>\n
      \nNext, the actual configuration (replace ens3f2 and ens3f3 with the names of the CNAs connected to the storage network):<\/p>\n
      $ sudo cp \/etc\/fcoe\/cfg-ethx \/etc\/fcoe\/cfg-ens3f2\n$ sudo cp \/etc\/fcoe\/cfg-ethx \/etc\/fcoe\/cfg-ens3f3\n$ sudo vim \/etc\/fcoe\/cfg-ens3f2\n$ sudo vim \/etc\/fcoe\/cfg-ens3f3\n<\/code><\/pre>\n
      \nImportant<\/b>: if the network interface supports DCB\/DCBX hardware, the DCB_REQUIRED parameter must be set to no.<\/p>\n
      DCB_REQUIRED='yes' \u2192 #<\/b>DCB_REQUIRED='yes'<\/p>\n
      Next, ensure that adminStatus is disabled on all interfaces, including those without FCoE enabled:<\/p>\n
      $ sudo lldptool set-lldp -i ens3f0 adminStatus=disabled\n...\n$ sudo lldptool set-lldp -i ens3f3 adminStatus=disabled\n<\/code><\/pre>\n
      \nIf there are other network interfaces, LLDP can be enabled:<\/p>\n
      $ sudo systemctl start lldpad\n$ sudo systemctl enable lldpad\n<\/code><\/pre>\n
      \nAs mentioned earlier, if hardware DCB\/DCBX is used, the DCB_REQUIRED setting must be enabled in no<\/b> and this step can be skipped.<\/p>\n
      $ sudo dcbtool sc ens3f2 dcb on\n$ sudo dcbtool sc ens3f3 dcb on\n$ sudo dcbtool sc ens3f2 app:fcoe e:1\n$ sudo dcbtool sc ens3f3 app:fcoe e:1\n$ sudo ip link set dev ens3f2 up\n$ sudo ip link set dev ens3f3 up\n$ sudo systemctl start fcoe\n$ sudo systemctl enable fcoe\n<\/code><\/pre>\n
      \nTo check if auto-start is enabled for network interfaces:<\/p>\n
      $ sudo vim \/etc\/sysconfig\/network-scripts\/ifcfg-ens3f2\n$ sudo vim \/etc\/sysconfig\/network-scripts\/ifcfg-ens3f3\n<\/code><\/pre>\n
      <\/p>\n
      ONBOOT=yes<\/code><\/pre>\n
      \nView the configured FCoE interfaces; the command output should not be empty.<\/p>\n
      $ sudo fcoeadm -i<\/code><\/pre>\n
      \nThe subsequent configuration of FCoE is performed as for regular FC.<\/p>\n
      Next is the configuration of storage systems and networks \u2014 zoning, SAN hosts, creating and presenting volumes\/LUNs, after which the storage can be connected to oVirt hosts: Storage \u2192 Domains \u2192 New Domain.<\/p>\n
      Leave Domain Function as Data, Storage Type as Fibre Channel, Host as any, name as, for example, storNN-volMM.<\/p>\n
      Surely your storage system allows not just path redundancy but also load balancing. Many modern systems can transfer data equally optimally across all paths (ALUA active\/active).<\/p>\n
      To enable all paths to an active state, you need to configure multipathing, which will be explained in the following articles.<\/p>\n
      Configuring NFS and iSCSI is done similarly.
      \n<\/a><\/noindex><\/p>\n
      ISO Image Storage<\/h3>\n
      \nFor the OS installation, their installation files are required, most often available as ISO images. You can use the built-in path, but for working with images in oVirt, a special storage type \u2014 ISO \u2014 has been designed, which can be targeted to an NFS server. Add it:<\/p>\n
      Storage \u2192 Domains \u2192 New Domain,
      \nDomain Function \u2192 ISO, 
      \nExport Path \u2014 for example, mynfs01.example.com:\/exports\/ovirt-iso (at the time of connection, the folder must be empty, and the manager must have write access to it),
      \nName \u2014 for example, mynfs01-iso.<\/p>\n
      To store images, the manager will create a structure. 
      \n\/exports\/ovirt-iso\/<some UUID>\/images\/11111111-1111-1111-1111-111111111111\/<\/b><\/p>\n
      If ISO images already exist on our NFS server, to save space, it is convenient to link them instead of copying files into this folder.
      \n      <\/a><\/noindex><\/p>\n
      First VM<\/h2>\n
      \nAt this stage, you can already create the first virtual machine, install the OS and application software on it.<\/p>\n
      Compute \u2192 Virtual Machines \u2192 New<\/p>\n
      For the new machine, specify the name (Name), create a disk (Instance Images \u2192 Create), and attach a network interface (Instantiate VM network interfaces by picking a vNIC profile \u2192 select from the list the currently only ovirtmgmt).<\/p>\n
      On the client side, a modern browser and SPICE client<\/a><\/noindex> will be needed to interact with the console.<\/p>\n
      The first machine has been successfully launched. However, to fully operate the system, several additional configurations are required, which we will continue discussing in the following articles.
      \n
      Source:       habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
      \u042d\u0442\u0430 \u0441\u0442\u0430\u0442\u044c\u044f \u2014 \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0430\u044f \u0432 \u0446\u0438\u043a\u043b\u0435 \u043f\u043e oVirt, \u043d\u0430\u0447\u0430\u043b\u043e \u0437\u0434\u0435\u0441\u044c. \u0421\u0442\u0430\u0442\u044c\u0438 \u0412\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u0423\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0430 \u043c\u0435\u043d\u0435\u0434\u0436\u0435\u0440\u0430 (ovirt-engine) \u0438 \u0433\u0438\u043f\u0435\u0440\u0432\u0438\u0437\u043e\u0440\u043e\u0432 (hosts) \u2014 \u041c\u044b \u0437\u0434\u0435\u0441\u044c \u0414\u043e\u043f\u043e\u043b\u043d\u0438\u0442\u0435\u043b\u044c\u043d\u044b\u0435 \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0438 \u0418\u0442\u0430\u043a, \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0438\u043c \u0432\u043e\u043f\u0440\u043e\u0441\u044b \u043f\u0435\u0440\u0432\u0438\u0447\u043d\u043e\u0439 \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0438 \u043a\u043e\u043c\u043f\u043e\u043d\u0435\u043d\u0442\u043e\u0432 ovirt-engine \u0438 ovirt-host. \u0411\u043e\u043b\u0435\u0435 \u043f\u043e\u0434\u0440\u043e\u0431\u043d\u043e \u043f\u0440\u043e\u0446\u0435\u0441\u0441\u044b \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0438 \u0432\u0441\u0435\u0433\u0434\u0430 \u043c\u043e\u0436\u043d\u043e \u043f\u043e\u0441\u043c\u043e\u0442\u0440\u0435\u0442\u044c \u0432 \u0434\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0430\u0446\u0438\u0438. \u0421\u043e\u0434\u0435\u0440\u0436\u0430\u043d\u0438\u0435 \u0423\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0430 ovirt-engine \u0423\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0430 ovirt-host \u0414\u043e\u0431\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u0443\u0437\u043b\u0430 \u0432 oVirtN \u041d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 \u0441\u0435\u0442\u0435\u0432\u043e\u0433\u043e \u0438\u043d\u0442\u0435\u0440\u0444\u0435\u0439\u0441\u0430 \u041d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 FC […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-82494","post","type-post","status-publish","format-standard","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47oVirt in 2 hours. Part 2. Installing the manager and hosts | ProHoster","description":"This article is the next in the oVirt series, starting here. Articles","canonical_url":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/ovirt-za-2-chasa-chast-2-ustanovka-menedzhera-i-hostov","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"en_US","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47oVirt \u0437\u0430 2 \u0447\u0430\u0441\u0430. \u0427\u0430\u0441\u0442\u044c 2. \u0423\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0430 \u043c\u0435\u043d\u0435\u0434\u0436\u0435\u0440\u0430 \u0438 \u0445\u043e\u0441\u0442\u043e\u0432 | ProHoster","og:description":"\u042d\u0442\u0430 \u0441\u0442\u0430\u0442\u044c\u044f \u2014 \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0430\u044f \u0432 \u0446\u0438\u043a\u043b\u0435 \u043f\u043e oVirt, \u043d\u0430\u0447\u0430\u043b\u043e \u0437\u0434\u0435\u0441\u044c. \u0421\u0442\u0430\u0442\u044c\u0438","og:url":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/ovirt-za-2-chasa-chast-2-ustanovka-menedzhera-i-hostov","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-05-21T23:42:24+00:00","article:modified_time":"2020-05-21T23:42:24+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"82494","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 15:36:26","updated":"2022-09-28 08:12:22","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/82494","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/comments?post=82494"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/82494\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/media?parent=82494"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/categories?post=82494"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/tags?post=82494"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}