{"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\/no\/blog\/news\/flexiant-cloud-orchestrator-s-chem-ego-edyat","title":{"rendered":"Flexiant Cloud Orchestrator: hva er det?","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Flexiant
\n
\nFor providing the IaaS (Virtual Data Center) service, we at Rusonyx<\/a><\/noindex> use a commercial orchestrator Flexiant Cloud Orchestrator<\/a><\/noindex> (FCO). This solution has a fairly unique architecture that distinguishes it from the widely known Openstack and CloudStack.<\/a><\/noindex> <\/p>\n

As hypervisors for compute nodes, KVM, VmWare, Xen, Virtuozzo6\/7, as well as containers from the same Virtuozzo are supported. Supported storage includes local, NFS, Ceph, and Virtuozzo Storage.<\/p>\n

FCO supports the creation of multiple clusters and managing them from a single interface. That is, it is possible to manage a Virtuozzo cluster and a KVM + Ceph cluster by switching between them with a mouse click.<\/p>\n

Essentially, FCO is a comprehensive solution for cloud providers that, besides orchestration, also includes billing, with all the settings, payment plugins, invoices, notifications, resellers, tariffs, and so on. However, the billing part is not able to cover all the nuances in Russia, so we opted out of using it in favor of another solution.<\/p>\n

We are pleased with the flexible system for distributing rights to all cloud resources: images, disks, products, servers, firewalls \u2013 all of this can be 'shared' and rights can be issued among users, even between users of different clients. Each client can create several independent data centers in their cloud and manage them from a single control panel.<\/p>\n

\"Flexiant
\n
\nArchitecturally, FCO consists of several parts, each with its own independent code, and some even have their own database.<\/p>\n

Skyline<\/b> \u2013 admin and user interface
\nJade<\/b> \u2013 business logic, billing, task management
\nTigerlily<\/b> \u2013 service coordinator, manages and coordinates the exchange of information between business logic and clusters.
\nXVPManager<\/b> \u2013 management of cluster elements: nodes, storage, networks, and virtual machines.
\nXVPAgent <\/b>\u2013 agent installed on nodes to interact with XVPManager<\/p>\n

\"Flexiant
\n
\nWe plan to include a detailed account of the architecture of each component in a series of articles, if, of course, the topic generates interest.<\/p>\n

Den st\u00f8rste fordelen med FCO kommer fra dens \"kasseformat\". Du f\u00e5r enkelhet og minimalisme. For styringsnodene allokeres en virtuell maskin p\u00e5 Ubuntu, der alle n\u00f8dvendige pakker installeres. Alle innstillinger lagres i konfigurasjonsfiler som en variabel-verdi:<\/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
Hele konfigurasjonen blir opprinnelig redigert i maler, deretter starter generatoren.
\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
\nSom du kan se, best\u00e5r grensesnittet av widgets, som brukeren har tilgang til \u00e5 administrere. Han kan enkelt legge til eller fjerne widgets fra siden, og dermed forme sin \u00f8nskede dashboard.<\/p>\n
Til tross for sin lukkede natur, er FCO et sv\u00e6rt tilpassbart system. Det har et stort antall innstillinger og inngangspunkter for \u00e5 endre arbeidsflyten:<\/p>\n
    \n
  1. Egne plugins st\u00f8ttes, for eksempel kan du skrive din egen betalingsmetode eller egen ekstern ressurs for \u00e5 tilby brukeren.<\/li>\n
  2. Egne triggere st\u00f8ttes for spesifikke hendelser, for eksempel ved \u00e5 legge til den f\u00f8rste virtuelle maskinen til kunden ved opprettelsen.<\/li>\n
  3. Egnet tilpassede widgets i grensesnittet, for eksempel \u00e5 integrere videoer fra YouTube direkte i brukergrensesnittet.<\/li>\n<\/ol>\n
    \nAll tilpasning skrives p\u00e5 FDL-spr\u00e5ket, som er basert p\u00e5 Lua. Hvis du kjenner Lua, vil det ikke v\u00e6re noen problemer med FDL.<\/p>\n
    Her er et eksempel p\u00e5 en av de enkleste triggerne vi bruker. Denne triggeren forhindrer brukere fra \u00e5 dele sine egne avbildninger med andre kunder. Vi gj\u00f8r dette for \u00e5 hindre at en bruker kan lage skadelige avbilder for andre.<\/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
    Register-funksjonen vil bli kalt av FCO-kjernen. Den vil returnere navnet p\u00e5 funksjonen som m\u00e5 kalles. Parameteren \"p\" for denne funksjonen lagrer konteksten for anropet, og ved f\u00f8rste anrop vil den v\u00e6re tom (nil). Dette lar oss registrere v\u00e5r trigger. I triggerType viser vi at triggeren kalles F\u00d8R publiseringsoperasjonen, og det gjelder kun for brukere. Systemadministratorer f\u00e5r selvsagt lov til \u00e5 publisere alt. I triggerOptions detaljert vi operasjonene som triggeren skal aktiveres for.<\/p>\n
    Og viktigst av alt \u2013 return {exitState = \"CANCEL\"}, som triggeren ble utviklet for. Den vil returnere en feil n\u00e5r brukeren pr\u00f8ver \u00e5 dele sin avbildning i kontrollpanelet.<\/p>\n
    I FCO-arkitekturen blir ethvert objekt (disk, server, bilde, nettverk, nettverksadapter osv.) representert som en enhet kalt Resource, som har felles parametere:<\/p>\n