{"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\/novosti-interneta\/flexiant-cloud-orchestrator-s-chem-ego-edyat","title":{"rendered":"Flexiant Cloud Orchestrator: \u00e7far\u00eb \u00ebsht\u00eb dhe si p\u00ebrdoret","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Flexiant
\n
\nP\u00ebr ofrimin e sh\u00ebrbimit IaaS (Qend\u00ebr virtuale t\u00eb t\u00eb dh\u00ebnave), ne n\u00eb Rusonyx<\/a><\/noindex> p\u00ebrdorim orkestra komerciale Flexiant Cloud Orchestrator<\/a><\/noindex> (FCO). Ky zgjidhje ka nj\u00eb arkitektur\u00eb mjaft unike q\u00eb e ndan at\u00eb nga Openstack dhe CloudStack, t\u00eb njohura p\u00ebr publikun.<\/a><\/noindex> <\/p>\n

Si hipervizor\u00eb p\u00ebr nodat compute mb\u00ebshteten KVM, VmWare, Xen, Virtuozzo6\/7, si dhe kontejner\u00ebt nga i nj\u00ebjti Virtuozzo. Nga ruajtjet e mb\u00ebshtetura \u2013 lokale, NFS, Ceph dhe Virtuozzo Storage.<\/p>\n

FCO mb\u00ebshtet krijimin e klaster\u00ebve t\u00eb shumt\u00eb dhe menaxhimin e tyre nga nj\u00eb nd\u00ebrfaqe. Dometh\u00ebn\u00eb, mund t\u00eb menaxhoni nj\u00eb klaster Virtuozzo dhe nj\u00eb klaster KVM + Ceph duke kaluar mes tyre me nj\u00eb klik t\u00eb mice.<\/p>\n

FCO, n\u00eb thelb, \u00ebsht\u00eb nj\u00eb zgjidhje komplekse p\u00ebr ofruesit e cloud-it, e cila p\u00ebrve\u00e7 orkestrimit p\u00ebrfshin edhe faturimin, me t\u00eb gjitha konfigurimet, plugin\u00ebt p\u00ebr pagesa, faturat, njoftimet, rimaqet, tarifat dhe k\u00ebshtu me radh\u00eb. Megjithat\u00eb, pjesa e faturimit nuk \u00ebsht\u00eb n\u00eb gjendje t\u00eb mbuloj\u00eb t\u00eb gjitha nuancat ruse, prandaj ne u rindam\u00eb nga p\u00ebrdorimi i saj n\u00eb favor t\u00eb nj\u00eb zgjidhjeje tjet\u00ebr.<\/p>\n

Na g\u00ebzon nj\u00eb sistem fleksib\u00ebl p\u00ebr shp\u00ebrndarjen e t\u00eb drejtave mbi t\u00eb gjitha burimet e cloud-it: imazhe, disqe, produkte, servera, firewalls \u2013 gjith\u00e7ka mund t\u00eb \"ndahen\" dhe t\u00eb jepen t\u00eb drejta midis p\u00ebrdoruesve, dhe 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 t\u00eb dh\u00ebnave t\u00eb pavarura dhe t'i menaxhoj\u00eb ato nga nj\u00eb panel t\u00eb vet\u00ebm.<\/p>\n

\"Flexiant
\n
\nArkitektonikisht, FCO p\u00ebrb\u00ebhet nga disa pjes\u00eb, \u00e7do nj\u00ebra ka kodin e saj t\u00eb pavarur, dhe disa madje edhe databaz\u00ebn e vet.<\/p>\n

Skyline<\/b> \u2013 nd\u00ebrfaqja administrative dhe ajo e p\u00ebrdoruesit
\nJade<\/b> \u2013 logjika e biznesit, faturimi, menaxhimi i detyrave
\nTigerlily<\/b> \u2013 koordinatori i sh\u00ebrbimeve, menaxhon dhe koordinon shk\u00ebmbimin e informacionit mes logjik\u00ebs s\u00eb biznesit dhe klaster\u00ebve.
\nXVPManager<\/b> \u2013 menaxhimi i elementeve t\u00eb klasterit: nodat, ruajtja, rrjeti dhe makinat virtuale.
\nXVPAgent <\/b>\u2013 agjenti q\u00eb vendoset n\u00eb nodat p\u00ebr t\u00eb bashk\u00ebpunuar me XVPManager<\/p>\n

\"Flexiant
\n
\nNj\u00eb tregim t\u00eb detajuar mbi arkitektur\u00ebn e \u00e7do komponente ne planifikojm\u00eb ta vendosim n\u00eb nj\u00eb cik\u00ebl artikujsh, n\u00ebse, natyrisht, tema do t\u00eb shpreh\u00eb interes.<\/p>\n

Avantazhi kryesor i FCO-s\u00eb del nga \"paketimi\" i tij. Ju keni n\u00eb dispozicion thjesht\u00ebsin\u00eb dhe minimalizmin. P\u00ebr nod\u00ebn menaxhuese ndarja nj\u00eb makin\u00eb virtuale n\u00eb Ubuntu, n\u00eb t\u00eb cil\u00ebn instalohen t\u00eb gjitha paketat e nevojshme. T\u00eb gjitha konfigurimet i jepen skedar\u00ebve t\u00eb konfigurimit n\u00eb form\u00ebn variab\u00ebl-vler\u00eb:<\/p>\n

# 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
E gjith\u00eb konfigurimi rregullohet fillimisht n\u00eb shabllon\u00ebt, m\u00eb pas aktivizohet gjeneratori
\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
\"Flexiant
\n
\nSi\u00e7 duket, nd\u00ebrfaqja p\u00ebrb\u00ebhet nga widget-e, menaxhimi i t\u00eb cilave \u00ebsht\u00eb i disponuesh\u00ebm p\u00ebr p\u00ebrdoruesin. Ai mund t\u00eb shtoj\u00eb\/fshini leht\u00ebsisht widget-e nga faqja, duke formuar k\u00ebshtu dashboard-in q\u00eb d\u00ebshiron.<\/p>\n
Pavar\u00ebsisht mbylljes s\u00eb saj, FCO \u00ebsht\u00eb nj\u00eb sistem shum\u00eb i personalizuesh\u00ebm. Ajo ka nj\u00eb num\u00ebr t\u00eb madh konfigurimesh dhe pikash hyr\u00ebse p\u00ebr ndryshimin e workflow-it:<\/p>\n
    \n
  1. Mb\u00ebshteten plugin\u00eb t\u00eb personalizuar, p\u00ebr shembull, ju mund t\u00eb shkruani nj\u00eb metod\u00eb faturimi t\u00eb vet\u00ebshkruar ose nj\u00eb burim t\u00eb jasht\u00ebm p\u00ebr ofrimin e m\u00eb t\u00eb mir\u00ebs p\u00ebr p\u00ebrdoruesin<\/li>\n
  2. Mb\u00ebshteten trigger t\u00eb personalizuar 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
  3. Mb\u00ebshteten widget-e t\u00eb personalizuar n\u00eb nd\u00ebrfaqe, p\u00ebr shembull, integrimi i nj\u00eb videoje nga youtube direkt n\u00eb nd\u00ebrfaqen e p\u00ebrdoruesit.<\/li>\n<\/ol>\n
    \nE gjith\u00eb personalizimi shkruhet n\u00eb gjuh\u00ebn FDL, e cila \u00ebsht\u00eb e bazuar n\u00eb Lua. N\u00ebse njihni Lua-n, me FDL nuk do t\u00eb keni probleme.<\/p>\n
    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 p\u00ebr t\u00eb siguruar q\u00eb nj\u00eb p\u00ebrdorues t\u00eb mos krijoj\u00eb imazhe p\u00ebrcjell\u00ebse p\u00ebr p\u00ebrdorues t\u00eb tjer\u00eb.<\/p>\n
    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
    Funksioni register do t\u00eb thirret nga b\u00ebrthama FCO. Ai do t\u00eb kthej\u00eb emrin e funksionit q\u00eb duhet t\u00eb thirret. Parametri \u201cp\u201d i k\u00ebtij funksioni mban kontekstin e thirrjes, dhe n\u00eb thirrjen e par\u00eb ai do t\u00eb jet\u00eb i zbraz\u00ebt (nil). Kjo do t\u00eb na lejoj\u00eb t\u00eb regjistrojm\u00eb trigger-in ton\u00eb. N\u00eb triggerType ne tregojm\u00eb se trigger-i thirret PARA operacionit t\u00eb publikimit, dhe p\u00ebrhapet vet\u00ebm p\u00ebr p\u00ebrdoruesit. Sigurisht, ne lejojm\u00eb administrator\u00ebt e sistemit t\u00eb publikojn\u00eb gjith\u00e7ka. N\u00eb triggerOptions ne detajojm\u00eb operacionet p\u00ebr t\u00eb cilat trigger-i do t\u00eb zbatohet.<\/p>\n
    Dhe m\u00eb e r\u00ebnd\u00ebsishmja \u2013 return {exitState = \u201cCANCEL\u201d}, p\u00ebr at\u00eb p\u00ebr t\u00eb cilin trigger-i \u00ebsht\u00eb zhvilluar. Ai do t\u00eb kthej\u00eb d\u00ebshtim, kur p\u00ebrdoruesi p\u00ebrpiqet t\u00eb ndaj\u00eb imazhin e tij n\u00eb panelin e menaxhimit.<\/p>\n
    N\u00eb arkitektur\u00ebn e FCO \u2013 \u00e7do objekt (disk, server, imazh, rrjet, adaptori i rrjetit etj.) p\u00ebrfaq\u00ebsohen n\u00eb form\u00ebn e nj\u00eb entiteti Resource, i cili ka parametra t\u00eb p\u00ebrbashk\u00ebt:<\/p>\n