{"id":39249,"date":"2019-10-31T22:28:41","date_gmt":"2019-10-31T19:28:41","guid":{"rendered":"https:\/\/prohoster.info\/blog\/cse-kubernetes-dlya-teh-kto-v-vcloud-e\/"},"modified":"2019-10-31T22:28:41","modified_gmt":"2019-10-31T19:28:41","slug":"cse-kubernetes-dlya-teh-kto-v-vcloud-e","status":"publish","type":"post","link":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/cse-kubernetes-dlya-teh-kto-v-vcloud-e","title":{"rendered":"CSE: Kubernetes neile, kes on vCloudis","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"CSE:
\nTere k\u00f5igile!<\/b><\/p>\n

Nii on juhtunud, et meie v\u00e4ike meeskond, mitte just hiljuti ja kindlasti mitte ootamatult, on j\u00f5udnud faasi, kus kolime m\u00f5ned (ja tulevikus isegi k\u00f5ik) tooted Kubernetesesse. <\/p>\n

Selleks oli palju p\u00f5hjuseid, kuid meie lugu ei ole konfliktide ja vaidluste kohta.<\/p>\n

Infrastruktuuri alusena oli meie valik v\u00e4ike. vCloud Director ja vCloud Director. Valisime uuema ja otsustasime alustada. <\/p>\n

J\u00e4llegi sirvides \u201eThe Hard Way\u201d, j\u00f5udsin v\u00e4ga kiiresti j\u00e4reldusele, et t\u00f6\u00f6riist, mis automatiseriks v\u00e4hemalt p\u00f5hiprotsessid, nagu juurutamine ja suuruse m\u00e4\u00e4ramine, on vajalik juba eilsest. S\u00fcgav sukeldumine Google'i avas teed sellisele tootearendusele nagu VMware Container Service Extension (CSE) \u2014 avatud l\u00e4htekoodiga toode, mis v\u00f5imaldab automatiseerida k8s klastrite loomist ja suuruse m\u00e4\u00e4ramist neile, kes on vCloudis.
\n<\/a><\/noindex><\/p>\n

M\u00e4rkus: CSE-l on oma piirangud, kuid meie eesm\u00e4rkide jaoks sobis see ideaalselt. Samuti peaks lahendust toetama pilveteenuse pakkuja, kuid kuna serveripool on samuti avatud l\u00e4htekoodiga, k\u00fcsige selle olemasolu kohalikult haldurilt \ud83d\ude42<\/p><\/blockquote>\n

Kasutamiseks on vajalik administraatori konto olemasolu vCloudis ja eelnevalt loomine suunatud v\u00f5rgustik klastrile (deploeerimise ajal on vajalik interneti\u00fchendus sellest v\u00f5rgustikust, \u00e4rge unustage seadistada tulem\u00fc\u00fcr\/NAT). Aadressimisest ei ole see s\u00f5ltuv. Antud n\u00e4ites kasutame 10.0.240.0\/24.<\/p>\n

\"CSE:<\/p>\n

Kuna p\u00e4rast loomist vajab klaster haldamist, on soovitatav VPN, mis suunab loodud v\u00f5rgustikule. Kasutame standardset SSL-VPN-i, mis on seadistatud meie organisatsiooni Edge Gateway'le.<\/p><\/blockquote>\n

Seej\u00e4rel tuleb installida CSE klient sinna, kust klastreid k8s-i hakatakse haldama. Minu puhul on see t\u00f6\u00f6laual ja paar h\u00e4sti peidetud konteinerit, mis haldavad automatiseerimist. <\/p>\n

Klient n\u00f5uab paigaldatud Python versiooni 3.7.3 v\u00f5i uuemat ja paigaldatud moodulit vcd-cli<\/a><\/noindex>, seega installime need m\u00f5lemad.<\/p>\n

pip3 install vcd-cli\n\npip3 install container-service-extension\n<\/code><\/pre>\n
\nP\u00e4rast paigaldamist kontrollime CSE versiooni ja saame j\u00e4rgmist:<\/p>\n
# vcd cse version\nError: No such command \"cse\".\n<\/code><\/pre>\n
\n\u00dcllatav, aga parandatav. Selgus, et CSE tuleb vcd-cli-le moodulina lisada.
\nSelleks tuleb esmalt sisse logida vcd-cli meie organisatsiooni:<\/p>\n
# vcd login MyCloud.provider.com org-dev admin\nPassword: \nadmin logged in, org: 'org-dev', vdc: 'org-dev_vDC01'\n<\/code><\/pre>\n
\nP\u00e4rast seda loob vcd-cli konfigureerimisfaili. ~\/.vcd-cli\/profiles.yaml<\/i>
\nSelle l\u00f5ppu tuleb lisada j\u00e4rgnev:<\/p>\n
laiendused:\n  - container_service_extension.client.cse\n<\/code><\/pre>\n
\nSeej\u00e4rel kontrollime uuesti:<\/p>\n
# vcd cse version\nCSE, Container Service Extension for VMware vCloud Director, version 2.5.0\n<\/code><\/pre>\n
\nKlientide installimise etapp on l\u00f5petatud. Proovime rakendada esimest klastri.
\nCSE-l on mitu kasutamisparameetrite komplekti, k\u00f5ik need on n\u00e4htavad. siit.<\/a><\/noindex><\/p>\n
Alustuseks loome v\u00f5tmed, et saada paroolivaba juurdep\u00e4\u00e4s tulevatele klastritele. See on oluline, kuna vaikimisi on juurdep\u00e4\u00e4s s\u00f5lmedele parooliga keelatud, ja kui v\u00f5tmeid ei seadistata, v\u00f5ib palju t\u00f6\u00f6d vaja minna virtuaalsete masinate kaudu, mis ei ole just mugav.<\/p>\n
# ssh-keygen\nGenerating public\/private rsa key pair.\nEnter file in which to save the key (\/root\/.ssh\/id_rsa): \nCreated directory '\/root\/.ssh'.\nEnter passphrase (empty for no passphrase): \nEnter same passphrase again: \nYour identification has been saved in \/root\/.ssh\/id_rsa.\nYour public key has been saved in \/root\/.ssh\/id_rsa.pub.\n<\/code><\/pre>\n
\nProovime klastri loomist:<\/p>\n
vcd cse cluster create MyCluster --network k8s_cluster_net --ssh-key ~\/.ssh\/id_rsa.pub --nodes 3 --enable-nfs<\/code><\/pre>\n
\nKui saame vea Error: Session has expired or user not logged in. Please re-login.<\/i> \u2014 siis logime vcd-cli j\u00e4lle vCloudi sisse, nagu eespool kirjeldatud, ja proovime uuesti.<\/p>\n
Seekord l\u00e4ks k\u00f5ik h\u00e4sti ja klastri loomise \u00fclesanne k\u00e4ivitati.<\/p>\n
klastri operatsioon: Loome klastri vApp 'MyCluster' (38959587-54f4-4a49-8f2e-61c3a3e879e0) mallist 'photon-v2_k8-1.12_weave-2.3.0' (redaktsioon 1)\n<\/code><\/pre>\n
\n\u00dclesande l\u00f5petamiseks kulub umbes 20 minutit; sellega samal ajal vaatame l\u00e4bi peamised k\u00e4ivitamisparameetrid.<\/p>\n
—network \u2014 \u0441\u043e\u0437\u0434\u0430\u043d\u043d\u0430\u044f \u043d\u0430\u043c\u0438 \u0440\u0430\u043d\u0435\u0435 \u0441\u0435\u0442\u044c.
\n—ssh-key \u2014 \u0441\u043e\u0437\u0434\u0430\u043d\u043d\u044b\u0435 \u043d\u0430\u043c\u0438 \u043a\u043b\u044e\u0447\u0438, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0431\u0443\u0434\u0443\u0442 \u0437\u0430\u043f\u0438\u0441\u0430\u043d\u044b \u043d\u0430 \u043d\u043e\u0434\u044b \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0430
\n—nodes n \u2014 \u041a\u043e\u043b\u0438\u0447\u0435\u0441\u0442\u0432\u043e Worker \u043d\u043e\u0434 \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0430. \u041c\u0430\u0441\u0442\u0435\u0440 \u0431\u0443\u0434\u0435\u0442 \u0432\u0441\u0435\u0433\u0434\u0430 \u043e\u0434\u0438\u043d, \u044d\u0442\u043e \u043e\u0433\u0440\u0430\u043d\u0438\u0447\u0435\u043d\u0438\u0435 CSE
\n—enable-nfs \u2014 \u0441\u043e\u0437\u0434\u0430\u0442\u044c \u0434\u043e\u043f\u043e\u043b\u043d\u0438\u0442\u0435\u043b\u044c\u043d\u0443\u044e \u043d\u043e\u0434\u0443 \u0434\u043b\u044f NFS \u0448\u0430\u0440\u044b \u043f\u043e\u0434 persistent volumes. \u041d\u0435\u043c\u043d\u043e\u0433\u043e \u043f\u0435\u0434\u0430\u043b\u044c\u043d\u0430\u044f \u043e\u043f\u0446\u0438\u044f, \u043a \u0434\u043e\u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0435 \u0442\u043e\u0433\u043e, \u0447\u0442\u043e \u043e\u043d\u0430 \u0434\u0435\u043b\u0430\u0435\u0442, \u043c\u044b \u0432\u0435\u0440\u043d\u0451\u043c\u0441\u044f \u0447\u0443\u0442\u044c \u043f\u043e\u0437\u0436\u0435.\n<\/p><\/blockquote>\n
 Samal ajal saab vCloud'is visuaalselt j\u00e4lgida klastrite loomist.
\n\"CSE:
\n
\nNiipea kui klastrite loomise \u00fclesanne on l\u00f5petatud, on see t\u00f6\u00f6ks valmis.<\/p>\n
Kontrollime juurutuse \u00f5iget toimimist k\u00e4suga vcd cse cluster info MyCluster<\/i><\/p>\n
\"CSE:
\n
\nJ\u00e4rgmiseks peame saama klastri konfiguratsiooni kasutamiseks. kubectl<\/i><\/p>\n
# vcd cse cluster config MyCluster > .\/.kube\/config\n<\/code><\/pre>\n
\nJa selle abil saab juba kontrollida klastri seisundit:<\/p>\n
\"CSE:
\n
\nSel hetkel v\u00f5ib klastri pidada tinglikult t\u00f6\u00f6korras, kui mitte arvestada persistent volumes probleemiga. Kuna oleme vCloudis, ei saa kasutada vSphere Provider'i. Valik —enable-nfs<\/i> on m\u00f5eldud selle ebamugavuse leevendamiseks, kuid see ei \u00f5nnestunud t\u00e4ielikult. Vajalik on k\u00e4sitsi seadistamine.<\/p>\n
Kuna meie node peab looma eraldi Independent ketta vCloudis. See garanteerib, et meie andmed ei kao koos klastriga, kui see kustutatakse. Samuti \u00fchendame ketta NFS-iga. <\/p>\n
# vcd disk create nfs-shares-1 100g --description 'Kubernetes NFS shares'\n# vcd vapp attach mycluster nfsd-9604 nfs-shares-1\n<\/code><\/pre>\n
\nSeej\u00e4rel \u00fchendame ssh kaudu (te t\u00f5esti l\u00f5ite v\u00f5tmed, eks?) meie NFS s\u00f5lmega ja liidame kettad l\u00f5puks:<\/p>\n
root@nfsd-9604:~# parted \/dev\/sdb\n(parted) mklabel gpt\nHoiatus: Juba olemasolev ketasild peal \/dev\/sdb kustutatakse ja k\u00f5ik andmed\nsellel kettal kaovad. Kas soovite j\u00e4tkata?\nJah\/Ei? jah\n(parted) unit GB\n(parted) mkpart primary 0 100\n(parted) print\nMudeli: VMware Virtuaalne ketas (scsi)\nKetas \/dev\/sdb: 100GB\nSector size (logical\/physical): 512B\/512B\nPartition Table: gpt\nDisk Flags:\n\nNumber  Start   End    Size   File system  Name     Flags\n 1      0.00GB  100GB  100GB               primary\n\n(parted) quit\nroot@nfsd-9604:~# mkfs -t ext4 \/dev\/sdb1\nLoome failis\u00fcsteemi 24413696 4k blokiga ja 6111232 inode'iga\nFailis\u00fcsteemi UUID: 8622c0f5-4044-4ebf-95a5-0372256b34f0\nSuperbloki varukoopiad on salvestatud plokkides:\n\t32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,\n\t4096000, 7962624, 11239424, 20480000, 23887872\n\nGrupi tabelid eraldatud: tehtud\nInode tabelite kirjutamine: tehtud\nK\u00e4imasolev ajakiri (32768 plokki): tehtud\nSuperplokkide ja failis\u00fcsteemi arvutustehnika teabe kirjutamine: tehtud\n<\/code><\/pre>\n
\nLoome andmete jaoks kausta ja mountime sinna uue partitsiooni:<\/p>\n
mkdir \/export\necho '\/dev\/sdb1  \/export   ext4  defaults   0 0' >> \/etc\/fstab\nmount -a\n<\/code><\/pre>\n
\nLoome viis testpartitsiooni ja jagame need klastrile:<\/p>\n
>cd \/export\n>mkdir vol1 vol2 vol3 vol4 vol5\n>vi \/etc\/exports\n# Lisame selle faili l\u00f5ppu\n\/export\/vol1 *(rw,sync,no_root_squash,no_subtree_check)\n\/export\/vol2 *(rw,sync,no_root_squash,no_subtree_check)\n\/export\/vol3 *(rw,sync,no_root_squash,no_subtree_check)\n\/export\/vol4 *(rw,sync,no_root_squash,no_subtree_check)\n\/export\/vol5 *(rw,sync,no_root_squash,no_subtree_check)\n#:wq! ;)\n# J\u00e4rgmiseks - ekspordime partitsioonid\n>exportfs -r\n<\/code><\/pre>\n
\nKogu selle maagia j\u00e4rel saab meie klastris luua PV ja PVC umbes nii:
\nPV:<\/p>\n
cat <<EOF | kubectl apply -f -\napiVersion: v1\nkind: PersistentVolume\nmetadata:\n  name: nfs-vol1\nspec:\n  capacity:\n    storage: 10Gi\n  accessModes:\n    - ReadWriteMany\n  nfs:\n    # Sama IP nagu meie NFS hostil, kuhu me SSH'de l\u00e4bi l\u00e4ksime.\n    server: 10.150.200.22\n    path: "\/export\/vol1"\nEOF\n<\/code><\/pre>\n
\nPVC:<\/p>\n
cat <<EOF | kubectl apply -f -\napiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\n  name: nfs-pvc\nspec:\n  accessModes:\n    - ReadWriteMany\n  storageClassName: ""\n  resources:\n    requests:\n      storage: 10Gi\nEOF\n<\/code><\/pre>\n
\nSellega l\u00f5peb \u00fche klastrite loo loomine ja algab tema eluts\u00fckli lugu. Boonusena \u2014 veel kaks kasulikku CSE k\u00e4sku, mis aitavad aeg-ajalt ressursse s\u00e4\u00e4sta v\u00f5i mitte:<\/p>\n
#\u0423\u0432\u0435\u043b\u0438\u0447\u0438\u0432\u0430\u0435\u043c \u0440\u0430\u0437\u043c\u0435\u0440 \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0430 \u0434\u043e 8 \u0432\u043e\u0440\u043a\u0435\u0440 \u043d\u043e\u0434\n>cse cluster resize MyCluster --network k8s_cluster_net --nodes 8\n\n#\u0412\u044b\u0432\u043e\u0434\u0438\u043c \u043d\u0435\u043d\u0443\u0436\u043d\u044b\u0435 \u043d\u043e\u0434\u044b \u0438\u0437 \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0430 \u0441 \u0438\u0445 \u043f\u043e\u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0438\u043c \u0443\u0434\u0430\u043b\u0435\u043d\u0438\u0435\u043c\n>vcd cse node delete MyCluster node-1a2v node-6685 --yes\n<\/code><\/pre>\n
\nAit\u00e4h k\u00f5igile aja eest, kui on k\u00fcsimusi \u2014 k\u00fcsige kommentaarides.
\n
Allikas: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
\u0412\u0441\u0435\u043c \u043f\u0440\u0438\u0432\u0435\u0442! \u0422\u0430\u043a \u0441\u043b\u043e\u0436\u0438\u043b\u043e\u0441\u044c, \u0447\u0442\u043e \u043d\u0430\u0448\u0430 \u043d\u0435\u0431\u043e\u043b\u044c\u0448\u0430\u044f \u043a\u043e\u043c\u0430\u043d\u0434\u0430, \u043d\u0435 \u0441\u043a\u0430\u0437\u0430\u0442\u044c, \u0447\u0442\u043e\u0431\u044b \u043d\u0435\u0434\u0430\u0432\u043d\u043e, \u0438 \u0443\u0436 \u0442\u043e\u0447\u043d\u043e \u043d\u0435 \u0432\u043d\u0435\u0437\u0430\u043f\u043d\u043e, \u0434\u043e\u0440\u043e\u0441\u043b\u0430 \u0434\u043e \u043f\u0435\u0440\u0435\u043d\u043e\u0441\u0430 \u043d\u0435\u043a\u043e\u0442\u043e\u0440\u044b\u0445 (\u0430 \u0432 \u043f\u0435\u0440\u0441\u043f\u0435\u043a\u0442\u0438\u0432\u0435 \u0438 \u0432\u0441\u0435\u0445) \u043f\u0440\u043e\u0434\u0443\u043a\u0442\u043e\u0432 \u0432 Kubernetes. \u041f\u0440\u0438\u0447\u0438\u043d \u0442\u043e\u043c\u0443 \u0431\u044b\u043b\u043e \u043c\u043d\u043e\u0436\u0435\u0441\u0442\u0432\u043e, \u043d\u043e \u043d\u0430\u0448\u0430 \u0438\u0441\u0442\u043e\u0440\u0438\u044f \u043d\u0435 \u043f\u0440\u043e \u0445\u043e\u043b\u0438\u0432\u0430\u0440. \u0418\u0437 \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u043d\u043e\u0439 \u043e\u0441\u043d\u043e\u0432\u044b \u0432\u044b\u0431\u043e\u0440 \u0443 \u043d\u0430\u0441 \u0431\u044b\u043b \u043d\u0435\u0431\u043e\u043b\u044c\u0448\u043e\u0439. vCloud Director \u0438 vCloud Director. \u0412\u044b\u0431\u0440\u0430\u043b\u0438 \u0442\u043e\u0442, \u0447\u0442\u043e […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":29455,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-39249","post","type-post","status-publish","format-standard","has-post-thumbnail","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\udd47CSE: Kubernetes neile, kes on vCloud-is | ProHoster","description":"Tere k\u00f5igile! Nii on kujunenud, et meie v\u00e4ike meeskond, mitte just hiljuti ja kindlasti mitte ootamatult, kasvas suureks m\u00f5tteks viia m\u00f5ned (ja tulevikus k\u00f5ik) tooted Kubernetesesse. P\u00f5hjusi oli mitmeid, kuid meie lugu ei ole vaidluste teemal. Meie infrastruktuuri aluseks valik oli v\u00e4ike. vCloud Director ja vCloud Director. Valisime selle, mis","canonical_url":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/cse-kubernetes-dlya-teh-kto-v-vcloud-e","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"et_EE","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\udd47CSE: Kubernetes \u0434\u043b\u044f \u0442\u0435\u0445 \u043a\u0442\u043e \u0432 vCloud-\u0435 | ProHoster","og:description":"\u0412\u0441\u0435\u043c \u043f\u0440\u0438\u0432\u0435\u0442! \u0422\u0430\u043a \u0441\u043b\u043e\u0436\u0438\u043b\u043e\u0441\u044c, \u0447\u0442\u043e \u043d\u0430\u0448\u0430 \u043d\u0435\u0431\u043e\u043b\u044c\u0448\u0430\u044f \u043a\u043e\u043c\u0430\u043d\u0434\u0430, \u043d\u0435 \u0441\u043a\u0430\u0437\u0430\u0442\u044c, \u0447\u0442\u043e\u0431\u044b \u043d\u0435\u0434\u0430\u0432\u043d\u043e, \u0438 \u0443\u0436 \u0442\u043e\u0447\u043d\u043e \u043d\u0435 \u0432\u043d\u0435\u0437\u0430\u043f\u043d\u043e, \u0434\u043e\u0440\u043e\u0441\u043b\u0430 \u0434\u043e \u043f\u0435\u0440\u0435\u043d\u043e\u0441\u0430 \u043d\u0435\u043a\u043e\u0442\u043e\u0440\u044b\u0445 (\u0430 \u0432 \u043f\u0435\u0440\u0441\u043f\u0435\u043a\u0442\u0438\u0432\u0435 \u0438 \u0432\u0441\u0435\u0445) \u043f\u0440\u043e\u0434\u0443\u043a\u0442\u043e\u0432 \u0432 Kubernetes. \u041f\u0440\u0438\u0447\u0438\u043d \u0442\u043e\u043c\u0443 \u0431\u044b\u043b\u043e \u043c\u043d\u043e\u0436\u0435\u0441\u0442\u0432\u043e, \u043d\u043e \u043d\u0430\u0448\u0430 \u0438\u0441\u0442\u043e\u0440\u0438\u044f \u043d\u0435 \u043f\u0440\u043e \u0445\u043e\u043b\u0438\u0432\u0430\u0440. \u0418\u0437 \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u043d\u043e\u0439 \u043e\u0441\u043d\u043e\u0432\u044b \u0432\u044b\u0431\u043e\u0440 \u0443 \u043d\u0430\u0441 \u0431\u044b\u043b \u043d\u0435\u0431\u043e\u043b\u044c\u0448\u043e\u0439. vCloud Director \u0438 vCloud Director. \u0412\u044b\u0431\u0440\u0430\u043b\u0438 \u0442\u043e\u0442, \u0447\u0442\u043e","og:url":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/cse-kubernetes-dlya-teh-kto-v-vcloud-e","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-31T19:28:41+00:00","article:modified_time":"2019-10-31T19:28:41+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"39249","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-24 01:28:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 00:53:37","updated":"2026-01-24 01:28:19"},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/39249","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/comments?post=39249"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/39249\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media\/29455"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media?parent=39249"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/categories?post=39249"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/tags?post=39249"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}