{"id":32318,"date":"2019-10-31T21:46:20","date_gmt":"2019-10-31T18:46:20","guid":{"rendered":"https:\/\/prohoster.info\/blog\/flexiant-cloud-orchestrator-s-chem-ego-edyat\/"},"modified":"2019-10-31T21:46:20","modified_gmt":"2019-10-31T18:46:20","slug":"flexiant-cloud-orchestrator-s-chem-ego-edyat","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/news\/flexiant-cloud-orchestrator-s-chem-ego-edyat","title":{"rendered":"Flexiant Cloud Orchestrator: \u00e7far\u00eb \u00ebsht\u00eb dhe si e p\u00ebrdorim","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Flexiant Cloud Orchestrator: \u00e7far\u00eb \u00ebsht\u00eb dhe si e p\u00ebrdorim\" src=\"\/wp-content\/uploads\/2019\/04\/0a0325fe5c71eaac391afdcabee225b7.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nP\u00ebr ofrimin e sh\u00ebrbimit IaaS (Qendra e t\u00eb Dh\u00ebnave Virtuale), ne n\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/www.rusonyx.ru\/\">Rusonyx<\/a><\/noindex> p\u00ebrdorim orkestratorin komercial <noindex><a rel=\"nofollow\" href=\"https:\/\/www.flexiant.com\/flexiant-cloud-orchestrator\/\">Flexiant Cloud Orchestrator<\/a><\/noindex> (FCO). Ky zgjidhje ka nj\u00eb arkitektur\u00eb mjaft unike, q\u00eb e ndan at\u00eb nga platforma t\u00eb njohura si Openstack dhe CloudStack.<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex> <\/p>\n<p>Si hypervisors p\u00ebr nodet compute mb\u00ebshteten KVM, VmWare, Xen, Virtuozzo6\/7, si dhe kontejner\u00ebt e t\u00eb nj\u00ebjtit Virtuozzo. Nga ruajtjet e mb\u00ebshtetura, jan\u00eb lokale, NFS, Ceph dhe Virtuozzo Storage.<\/p>\n<p>FCO mb\u00ebshtet krijimin e disa klaster\u00ebve dhe menaxhimin e tyre nga nj\u00eb nd\u00ebrfaqe e vetme. Pra, \u00ebsht\u00eb e mundur t\u00eb menaxhohet nj\u00eb klaster Virtuozzo dhe nj\u00eb klaster KVM + Ceph duke kaluar nd\u00ebrmjet tyre me nj\u00eb klik t\u00eb miut.<\/p>\n<p>N\u00eb thelb, FCO \u00ebsht\u00eb nj\u00eb zgjidhje e plot\u00eb p\u00ebr ofruesit e cloud, e cila p\u00ebrve\u00e7 orkestrimit p\u00ebrfshin edhe faturimin, me t\u00eb gjitha konfigurimet, shtesat p\u00ebr pagesa, faturat, njoftimet, risellet, tarifat dhe k\u00ebshtu me radh\u00eb. Megjithat\u00eb, pjesa e faturimit nuk \u00ebsht\u00eb n\u00eb gjendje t\u00eb pokrij\u00eb t\u00eb gjitha nuancat ruse, prandaj ne u dor\u00ebzuam nga p\u00ebrdorimi i saj n\u00eb favor t\u00eb nj\u00eb zgjidhjeje tjet\u00ebr.<\/p>\n<p>Na g\u00ebzon shum\u00eb sistemi fleksib\u00ebl i shp\u00ebrndarjes s\u00eb t\u00eb drejtave p\u00ebr t\u00eb gjitha burimet e cloud-it: imazhet, disk\u00ebt, produktet, server\u00ebt, firewall-at \u2013 t\u00eb gjitha k\u00ebto mund t\u00eb 'ndahen' dhe t\u00eb jepen t\u00eb drejta midis p\u00ebrdoruesve, madje edhe midis p\u00ebrdoruesve t\u00eb klient\u00ebve t\u00eb ndrysh\u00ebm. \u00c7do klient mund t\u00eb krijoj\u00eb n\u00eb cloud-in e tij disa qendra t\u00eb dh\u00ebnash t\u00eb pavarura dhe t'i menaxhoj\u00eb ato nga nj\u00eb panel i vet\u00ebm.<\/p>\n<p><img decoding=\"async\" alt=\"Flexiant Cloud Orchestrator: \u00e7far\u00eb \u00ebsht\u00eb dhe si e p\u00ebrdorim\" src=\"\/wp-content\/uploads\/2019\/04\/11e93aef20dcd4a1bffb9ee988950658.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nArkitekturorisht, FCO p\u00ebrb\u00ebhet nga disa pjes\u00eb, secila prej t\u00eb cilave ka kodin e saj t\u00eb pavarur, dhe disa edhe baz\u00ebn e t\u00eb dh\u00ebnave t\u00eb saj.<\/p>\n<p><b>Skyline<\/b> \u2013 nd\u00ebrfaqja administrative dhe p\u00ebr p\u00ebrdoruesit<br \/>\n<b>Jade<\/b> \u2013 logjika biznesore, faturimi, menaxhimi i detyrave<br \/>\n<b>Tigerlily<\/b> \u2013 koordinator i sh\u00ebrbimit, menaxhon dhe koordon informacionin midis logjik\u00ebs biznesore dhe klaster\u00ebve.<br \/>\n<b>XVPManager<\/b> \u2013 menaxhimi i elementeve t\u00eb klasterit: nodet, ruajtja, rrjeti dhe makinat virtuale.<br \/>\n<b>XVPAgent <\/b>\u2013 agenti q\u00eb instalohet n\u00eb nodet p\u00ebr t\u00eb bashk\u00ebpunuar me XVPManager<\/p>\n<p><img decoding=\"async\" alt=\"Flexiant Cloud Orchestrator: \u00e7far\u00eb \u00ebsht\u00eb dhe si e p\u00ebrdorim\" src=\"\/wp-content\/uploads\/2019\/04\/f810d1624b8bcdc53144dc05e86b2e59.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nNj\u00eb rr\u00ebfim i detajuar mbi arkitektur\u00ebn e \u00e7do komponente planifikojm\u00eb ta p\u00ebrfshijm\u00eb n\u00eb nj\u00eb cik\u00ebl artikujsh, n\u00ebse sigurisht, tema do t\u00eb t\u00ebrheq\u00eb interes.<\/p>\n<p>Avantazhi kryesor i FCO rrjedh nga \"paketizimi\" i tij. Ju ofrohet thjesht\u00ebsia dhe minimalizmi. Nj\u00eb makin\u00eb virtuale n\u00eb Ubuntu i dedikohet nod\u00ebs menaxhuese, ku instalohen t\u00eb gjitha paketat e nevojshme. T\u00eb gjitha konfigurimet vendosen n\u00eb skedar\u00ebt e konfigurimit n\u00eb form\u00ebn variab\u00ebl-vler\u00eb:<\/p>\n<pre><code class=\"plaintext\"># cat \/etc\/extility\/config\/vars\n\u2026\nexport LIMIT_MAX_LIST_ADMIN_DEFAULT=\"30000\"\nexport LIMIT_MAX_LIST_USER_DEFAULT=\"200\"\nexport LOGDIR=\"\/var\/log\/extility\"\nexport LOG_FILE=\"misc.log\"\nexport LOG_FILE_LOG4JHOSTBILLMODULE=\"hostbillmodule.log\"\nexport LOG_FILE_LOG4JJADE=\"jade.log\"\nexport LOG_FILE_LOG4JTL=\"tigerlily.log\"\nexport LOG_FILE_LOG4JXVP=\"xvpmanager.log\"\nexport LOG_FILE_VARS=\"misc.log\"\n\u2026\n<\/code><\/pre>\n<p>E gjith\u00eb konfigurimi modifikohet fillimisht n\u00eb t\u00eb shpallurat, pastaj aktivizohet gjeneruesi<br \/>\n#build-config \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u0441\u0444\u043e\u0440\u043c\u0438\u0440\u0443\u0435\u0442 \u0444\u0430\u0439\u043b vars \u0438 \u0434\u0430\u0441\u0442 \u043a\u043e\u043c\u0430\u043d\u0434\u0443 \u0441\u0435\u0440\u0432\u0438\u0441\u0430\u043c \u043f\u0435\u0440\u0435\u0447\u0438\u0442\u0430\u0442\u044c \u043a\u043e\u043d\u0444\u0438\u0433. \u041f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u044c\u0441\u043a\u0438\u0439 \u0438\u043d\u0442\u0435\u0440\u0444\u0435\u0439\u0441 \u043f\u0440\u0438\u044f\u0442\u043d\u044b\u0439 \u0438 \u043c\u043e\u0436\u0435\u0442 \u0431\u044b\u0442\u044c \u043b\u0435\u0433\u043a\u043e \u0437\u0430\u0431\u0440\u0435\u043d\u0434\u0438\u0440\u043e\u0432\u0430\u043d.<\/p>\n<p><img decoding=\"async\" alt=\"Flexiant Cloud Orchestrator: \u00e7far\u00eb \u00ebsht\u00eb dhe si e p\u00ebrdorim\" src=\"\/wp-content\/uploads\/2019\/04\/bb9bd922497394f0fdbe9345fe67ee62.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nSi\u00e7 shihet, interfejsi p\u00ebrb\u00ebhet nga widget-e, menaxhimi i t\u00eb cil\u00ebve \u00ebsht\u00eb i qassh\u00ebm p\u00ebr p\u00ebrdoruesin. Ai mund t\u00eb shtoj\u00eb\/hiqet leht\u00ebsisht widget-e nga faqja, duke formuar k\u00ebshtu dashboard-in e tij t\u00eb d\u00ebshiruar.<\/p>\n<p>Pavar\u00ebsisht nga mbyllja e tij, FCO \u00ebsht\u00eb nj\u00eb sistem shum\u00eb i personalizuesh\u00ebm. Ai ka nj\u00eb num\u00ebr t\u00eb madh konfigurimesh dhe pikash hyr\u00ebse p\u00ebr t\u00eb ndryshuar rrjedh\u00ebn e pun\u00ebs:<\/p>\n<ol>\n<li>P\u00ebrkrahjen e plugin-eve t\u00eb personalizuara, p\u00ebr shembull, mund t\u00eb shkruani nj\u00eb metod\u00eb t\u00eb vet\u00eb-bilancit ose nj\u00eb burim t\u00eb jasht\u00ebm p\u00ebr t'i ofruar p\u00ebrdoruesit<\/li>\n<li>P\u00ebrkrahjen e trigger-eve t\u00eb personalizuara p\u00ebr ngjarje t\u00eb caktuara, p\u00ebr shembull, shtimi i makin\u00ebs virtuale t\u00eb par\u00eb p\u00ebr klientin gjat\u00eb krijimit t\u00eb tij<\/li>\n<li>P\u00ebrkrahjen e widget-eve t\u00eb personalizuara n\u00eb interfejs, p\u00ebr shembull, p\u00ebr t\u00eb integruar nj\u00eb video nga youtube direkt n\u00eb nd\u00ebrfaqen e p\u00ebrdoruesit.<\/li>\n<\/ol>\n<p>\nE gjith\u00eb personalizimi shkruhet n\u00eb gjuh\u00ebn FDL, e cila \u00ebsht\u00eb e bazuar n\u00eb Lua. N\u00ebse e dini Lua-n, nuk do keni asnj\u00eb problem me FDL.<\/p>\n<p>Ja nj\u00eb shembull i nj\u00eb prej trigger-eve m\u00eb t\u00eb thjeshta q\u00eb ne p\u00ebrdorim. Ky trigger nuk lejon p\u00ebrdoruesit t\u00eb ndajn\u00eb imazhet e tyre me klient\u00eb t\u00eb tjer\u00eb. Ne e b\u00ebjm\u00eb k\u00ebt\u00eb q\u00eb nj\u00eb p\u00ebrdorues t\u00eb mos mund t\u00eb krijoj\u00eb nj\u00eb imazh keqdash\u00ebs p\u00ebr p\u00ebrdoruesit e tjer\u00eb.<\/p>\n<pre><code class=\"plaintext\">function register()\n    return {\"pre_user_api_publish\"}\nend\n   \nfunction pre_user_api_publish(p)  \n    if(p==nil) then\n        return{\n            ref = \"cancelPublishImage\",\n            name = \"Cancel publishing\",\n            description = \"Cancel all user\u2019s images publishing\",\n            triggerType = \"PRE_USER_API_CALL\",\n            triggerOptions = {\"publishResource\", \"publishImage\"},\n            api = \"TRIGGER\",\n            version = 1,\n        }\n    end\n\n    -- Turn publishing off\n    return {exitState = \"CANCEL\"}\n   \nend\n<\/code><\/pre>\n<p>Funksioni register do t\u00eb thirret nga b\u00ebrthama e FCO. Ai do t\u00eb kthej\u00eb emrin e funksionit q\u00eb duhet t\u00eb thirret. Parametri \u201cp\u201d i k\u00ebtij funksioni ruan kontekstin e thirrjes, dhe gjat\u00eb thirrjes s\u00eb par\u00eb ai do t\u00eb jet\u00eb bosh (nil). Kjo do t\u00eb na lejoj\u00eb t\u00eb regjistrojm\u00eb trigger-in ton\u00eb. N\u00eb triggerType tregonim se trigger-i thirret PARA operacionit t\u00eb publikimit dhe p\u00ebrhapet vet\u00ebm p\u00ebr p\u00ebrdoruesit. Administrator\u00ebt e sistemit, natyrisht, lejohet t'i publikojn\u00eb t\u00eb gjitha. N\u00eb triggerOptions ne detajojm\u00eb operacionet p\u00ebr t\u00eb cilat trigger-i do t\u00eb aktivizohet.<\/p>\n<p>Dhe m\u00eb kryesorja \u2013 return {exitState = \u201cCANCEL\u201d}, p\u00ebr t\u00eb cilin trigger-i u zhvillua. Ai do t\u00eb kthej\u00eb d\u00ebshtim kur nj\u00eb p\u00ebrdorues p\u00ebrpiqet t\u00eb ndaj\u00eb imazhin e tij n\u00eb panelin e menaxhimit.<\/p>\n<p>N\u00eb arkitektur\u00ebn FCO \u2013 \u00e7do objekt (disku, serveri, imazhi, rrjeti, adapteri rrjetit, etj.) paraqitet n\u00eb form\u00ebn e nj\u00eb entiteti Resource, i cili ka parametrat e p\u00ebrbashk\u00ebt:<\/p>\n<ul>\n<li>UUID i burimit<\/li>\n<li>emri i burimit<\/li>\n<li>tipi i burimit<\/li>\n<li>UUID i pronarit t\u00eb burimit<\/li>\n<li>statusi i burimit (aktiv, joaktiv)<\/li>\n<li>metadatata e burimit<\/li>\n<li>\u00e7el\u00ebsat e burimit <\/li>\n<li>UUID i produktit, t\u00eb cilit i p\u00ebrket burimi<\/li>\n<li>VDC i burimit<\/li>\n<\/ul>\n<p>\nKjo \u00ebsht\u00eb shum\u00eb e p\u00ebrshtatshme kur punoni me API, kur me t\u00eb gjitha burimet puna b\u00ebhet sipas nj\u00eb principi. Produktet konfigurohen nga ofruesi, nd\u00ebrsa i k\u00ebrkon klienti. Duke qen\u00eb se faturimi yn\u00eb \u00ebsht\u00eb nga jasht\u00eb, klienti mund t\u00eb porosis\u00eb \u00e7do produkt nga paneli pa pages\u00eb. Ai do t\u00eb llogaritet m\u00eb von\u00eb n\u00eb faturim. Produkti mund t\u00eb jet\u00eb \u2013 adresa ip p\u00ebr or\u00eb, nj\u00eb GB shtes\u00eb disku p\u00ebr or\u00eb ose thjesht serveri.<\/p>\n<p>\u00c7el\u00ebsat mund t\u00eb sh\u00ebnojn\u00eb burime t\u00eb caktuara p\u00ebr t\u00eb ndryshuar logjik\u00ebn e pun\u00ebs me to. P\u00ebr shembull, ne mund t\u00eb sh\u00ebnojm\u00eb tri node fizike me \u00e7el\u00ebsin Weight dhe t\u00eb sh\u00ebnojm\u00eb disa klient\u00eb me k\u00ebt\u00eb \u00e7el\u00ebs t\u00eb nj\u00ebjt\u00eb, duke i ve\u00e7uar k\u00ebto node p\u00ebr k\u00ebta klient\u00eb. Ky mekaniz\u00ebm ne e p\u00ebrdorim p\u00ebr klient\u00ebt VIP, t\u00eb cil\u00ebt nuk duan fqinj\u00eb af\u00ebr VM-ve t\u00eb tyre. Funksionaliteti mund t\u00eb aplikohet shum\u00eb m\u00eb gjer\u00eb. <\/p>\n<p>Modeli i licencimit parashikon pages\u00ebn p\u00ebr \u00e7do b\u00ebrtham\u00eb procesori t\u00eb nodit fizik. Gjithashtu, \u00e7mimi ndikohen nga numri i tipave t\u00eb klaster\u00ebve. N\u00ebse planifikohet t\u00eb p\u00ebrdoren bashk\u00eb, p\u00ebr shembull, KVM dhe VMware, at\u00ebher\u00eb \u00e7mimi i licenc\u00ebs do t\u00eb rritet.<\/p>\n<p>FCO \u00ebsht\u00eb nj\u00eb produkt i plot\u00eb, funksionaliteti i tij \u00ebsht\u00eb shum\u00eb i pasur, prandaj ne planifikojm\u00eb t\u00eb p\u00ebrgatisim disa artikuj me p\u00ebrshkrimin e detajuar t\u00eb funksionimit t\u00eb pjes\u00ebs rrjetore.<\/p>\n<p>Pas disa vitesh pun\u00eb me k\u00ebt\u00eb orkestrator, mund t\u00eb theksojm\u00eb se \u00ebsht\u00eb shum\u00eb i besuesh\u00ebm. Fatkeq\u00ebsisht, produkti nuk \u00ebsht\u00eb i liruar nga t\u00eb metat:<\/p>\n<ul>\n<li>na ka ndodhur t\u00eb optimizojm\u00eb DB-n\u00eb, pasi k\u00ebrkesat filluan t\u00eb ngadal\u00ebsohen me rritjen e numrit t\u00eb t\u00eb dh\u00ebnave n\u00eb to;<\/li>\n<li>pas nj\u00eb aksidenti p\u00ebr shkak t\u00eb nj\u00eb defekti, mekanizmi i rikuperimit nuk funksionoi, dhe na duhej t\u00eb ngjallnim makinat e klient\u00ebve t\u00eb pafat me nj\u00eb grup skriptesh;<\/li>\n<li>mekanizmi i detektimit t\u00eb papashtyrshm\u00ebris\u00eb s\u00eb nodit \u00ebsht\u00eb i koduar dhe nuk mund t\u00eb personalizohet. Pra, ne nuk mund t\u00eb krijojm\u00eb politikat tona p\u00ebr p\u00ebrcaktimin e papashtyrshm\u00ebris\u00eb s\u00eb nodit.<\/li>\n<li>D\u00ebrgimi i skedar\u00ebve nuk \u00ebsht\u00eb gjithmon\u00eb i detajuar. Ndonj\u00ebher\u00eb, kur duhet t\u00eb zbresim n\u00eb nj\u00eb nivel shum\u00eb t\u00eb ul\u00ebt p\u00ebr t\u00eb analizuar nj\u00eb problem t\u00eb caktuar, mungojn\u00eb kodet burimore t\u00eb disa komponent\u00ebve p\u00ebr t\u00eb kuptuar arsyet;<\/li>\n<\/ul>\n<p>\n<b>TOTAL: <\/b>N\u00eb p\u00ebrgjith\u00ebsi, p\u00ebrshtypjet p\u00ebr produktin jan\u00eb t\u00eb mira. Jemi n\u00eb kontakt t\u00eb vazhduesh\u00ebm me zhvilluesit e orkestratorit. Djemt\u00eb jan\u00eb t\u00eb hapur p\u00ebr bashk\u00ebpunim konstruktiv.<\/p>\n<p>Pavar\u00ebsisht thjesht\u00ebsis\u00eb s\u00eb FCO,\u00a0ka funksionalitete t\u00eb gjera. N\u00eb artikujt e ardhshme planifikojm\u00eb t\u00eb thellohemi n\u00eb temat e m\u00ebposhtme:<\/p>\n<ul>\n<li>organizimi i rrjetit n\u00eb FCO<\/li>\n<li>sigurimi i rikuperimit t\u00eb menj\u00ebhersh\u00ebm dhe protokollit FQP<\/li>\n<li>shkrimi i plug-in-eve dhe widget-eve t\u00eb vetat<\/li>\n<li>lidha sh\u00ebrbime t\u00eb tjera, si Load Balancer dhe Acronis<\/li>\n<li>kopje rezerv\u00eb<\/li>\n<li>mekanizmi i unifikuar p\u00ebr konfigurimin dhe p\u00ebrshtatjen e nodave<\/li>\n<li>p\u00ebrpunimi i metadatas s\u00eb makinave virtuale<\/li>\n<\/ul>\n<p>\n<b>P.S. <\/b>Shkruani n\u00eb komente n\u00ebse jeni t\u00eb interesuar p\u00ebr aspekte t\u00eb tjera. Q\u00ebndroni t\u00eb lidhur!<br \/>\n<br \/>Burimi: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/rusonyx\/blog\/449196\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0414\u043b\u044f \u043f\u0440\u0435\u0434\u043e\u0441\u0442\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u0443\u0441\u043b\u0443\u0433\u0438 IaaS (\u0412\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u044b\u0439 \u0434\u0430\u0442\u0430-\u0446\u0435\u043d\u0442\u0440) \u043c\u044b \u0432 Rusonyx \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u043c \u043a\u043e\u043c\u043c\u0435\u0440\u0447\u0435\u0441\u043a\u0438\u0439 \u043e\u0440\u043a\u0435\u0441\u0442\u0440\u0430\u0442\u043e\u0440 Flexiant Cloud Orchestrator (FCO). \u042d\u0442\u043e \u0440\u0435\u0448\u0435\u043d\u0438\u0435 \u0438\u043c\u0435\u0435\u0442 \u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u043e \u0443\u043d\u0438\u043a\u0430\u043b\u044c\u043d\u0443\u044e \u0430\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u0443\u0440\u0443, \u0447\u0442\u043e \u043e\u0442\u043b\u0438\u0447\u0430\u0435\u0442 \u0435\u0433\u043e \u043e\u0442 \u0438\u0437\u0432\u0435\u0441\u0442\u043d\u044b\u0445 \u0448\u0438\u0440\u043e\u043a\u043e\u0439 \u043f\u0443\u0431\u043b\u0438\u043a\u0435 Openstack \u0438 CloudStack. \u0412 \u043a\u0430\u0447\u0435\u0441\u0442\u0432\u0435 \u0433\u0438\u043f\u0435\u0440\u0432\u0438\u0437\u043e\u0440\u043e\u0432 compute \u043d\u043e\u0434 \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u0438\u0432\u0430\u044e\u0442\u0441\u044f KVM, VmWare, Xen, Virtuozzo6\/7, \u0430 \u0442\u0430\u043a\u0436\u0435 \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u044b \u043e\u0442 \u0442\u043e\u0433\u043e \u0436\u0435 Virtuozzo. \u0418\u0437 \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u0438\u0432\u0430\u0435\u043c\u044b\u0445 \u0445\u0440\u0430\u043d\u0438\u043b\u0438\u0449 \u2013 \u043b\u043e\u043a\u0430\u043b\u044c\u043d\u043e\u0435, NFS, [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":24135,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[702],"tags":[],"class_list":["post-32318","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.2 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0414\u043b\u044f \u043f\u0440\u0435\u0434\u043e\u0441\u0442\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u0443\u0441\u043b\u0443\u0433\u0438 IaaS (\u0412\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u044b\u0439.\" \/>\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\/sq\/blog\/news\/flexiant-cloud-orchestrator-s-chem-ego-edyat\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2\" \/>\n\t\t<meta property=\"og:locale\" content=\"sq_AL\" \/>\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\udd47Flexiant Cloud Orchestrator: \u0441 \u0447\u0435\u043c \u0435\u0433\u043e \u0435\u0434\u044f\u0442 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0414\u043b\u044f \u043f\u0440\u0435\u0434\u043e\u0441\u0442\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u0443\u0441\u043b\u0443\u0433\u0438 IaaS (\u0412\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u044b\u0439.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sq\/blog\/news\/flexiant-cloud-orchestrator-s-chem-ego-edyat\" \/>\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:46:20+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T18:46:20+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\udd47Flexiant Cloud Orchestrator: \u00e7far\u00eb \u00ebsht\u00eb dhe si p\u00ebrdoret | ProHoster","description":"P\u00ebr ofrimin e sh\u00ebrbimit IaaS (Virtual).","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/news\/flexiant-cloud-orchestrator-s-chem-ego-edyat","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","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\udd47Flexiant Cloud Orchestrator: \u0441 \u0447\u0435\u043c \u0435\u0433\u043e \u0435\u0434\u044f\u0442 | ProHoster","og:description":"\u0414\u043b\u044f \u043f\u0440\u0435\u0434\u043e\u0441\u0442\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u0443\u0441\u043b\u0443\u0433\u0438 IaaS (\u0412\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u044b\u0439.","og:url":"https:\/\/prohoster.info\/sq\/blog\/news\/flexiant-cloud-orchestrator-s-chem-ego-edyat","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:46:20+00:00","article:modified_time":"2019-10-31T18:46:20+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"32318","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 10:19:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 03:00:23","updated":"2026-01-21 10:19:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/32318","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=32318"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/32318\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/24135"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=32318"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=32318"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=32318"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}