{"id":38075,"date":"2019-10-31T22:21:32","date_gmt":"2019-10-31T19:21:32","guid":{"rendered":"https:\/\/prohoster.info\/blog\/kak-blagodarya-kubernetes-i-avtomatizatsii-migrirovat-v-oblako-za-dva-chasa\/"},"modified":"2019-10-31T22:21:32","modified_gmt":"2019-10-31T19:21:32","slug":"kak-blagodarya-kubernetes-i-avtomatizatsii-migrirovat-v-oblako-za-dva-chasa","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kak-blagodarya-kubernetes-i-avtomatizatsii-migrirovat-v-oblako-za-dva-chasa","title":{"rendered":"Si si falas\u00eb Kubernetes dhe automatizmi migrohet n\u00eb cloud brenda dy or\u00ebsh","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Si
\n
\nKompania 'URUS' e provoi Kubernetes n\u00eb forma t\u00eb ndryshme: implementim t\u00eb pavarur n\u00eb bare metal, n\u00eb Google Cloud dhe m\u00eb pas transfert\u00ebn e platform\u00ebs s\u00eb saj n\u00eb cloud-in Mail.ru Cloud Solutions (MCS). Si e zgjodh\u00ebn ofruesin e ri t\u00eb sh\u00ebrbimeve cloud dhe si ia dol\u00ebn t\u00eb migronin brenda nj\u00eb kohe rekord prej dy or\u00ebsh, tregon Igor Shishkin (t3ran<\/a><\/noindex>), administrator i lart\u00eb i sistemeve 'URUS'.
\n<\/a><\/noindex><\/p>\n

\u00c7far\u00eb b\u00ebn 'URUS' <\/h2>\n

\nKa shum\u00eb m\u00ebnyra p\u00ebr t\u00eb p\u00ebrmir\u00ebsuar cil\u00ebsin\u00eb e ambientit urban, dhe nj\u00ebra prej tyre \u00ebsht\u00eb ta b\u00ebsh at\u00eb ekologjikisht t\u00eb sigurt. Pik\u00ebrisht p\u00ebr k\u00ebt\u00eb punon kompania 'URUS - Sh\u00ebrbimet digjitale t\u00eb men\u00e7ura'. Aty aplikohet zgjidhje q\u00eb ndihmojn\u00eb bizneset t\u00eb monitorojn\u00eb treguesit e r\u00ebnd\u00ebsish\u00ebm ekologjik dhe t\u00eb zvog\u00eblojn\u00eb ndikimin negativ n\u00eb mjedis. Sensor\u00ebt mbledhin t\u00eb dh\u00ebna mbi p\u00ebrb\u00ebrjen e ajrit, nivelin e zhurm\u00ebs dhe parametra t\u00eb tjer\u00eb, dhe m\u00eb pas i d\u00ebrgojn\u00eb n\u00eb platform\u00ebn e p\u00ebrbashk\u00ebt 'URUS - Ekomon' p\u00ebr analiz\u00eb dhe p\u00ebrpilim rekomandimesh. <\/p>\n

Si funksionon 'URUS' nga brenda<\/h2>\n

\nKlienti tipik i 'URUS' \u00ebsht\u00eb nj\u00eb kompani q\u00eb ndodhet n\u00eb nj\u00eb zon\u00eb banimi ose pran\u00eb saj. Kjo mund t\u00eb jet\u00eb nj\u00eb fabrik\u00eb, port, depo hekurudhore ose \u00e7do objekt tjet\u00ebr. N\u00ebse klienti yn\u00eb ka marr\u00eb tashm\u00eb paralajm\u00ebrime, \u00ebsht\u00eb gjobitur p\u00ebr ndotjen e mjedisit, ose d\u00ebshiron t\u00eb emitoj\u00eb m\u00eb pak zhurma dhe t\u00eb reduktoj\u00eb sasin\u00eb e emetimeve t\u00eb d\u00ebmshme, ai vjen te ne, dhe ne tashm\u00eb i ofrojm\u00eb nj\u00eb zgjidhje t\u00eb gatshme p\u00ebr monitorimin ekologjik.<\/p>\n

\"Si
\nN\u00eb grafikun e monitorimit t\u00eb p\u00ebrqendrimit t\u00eb H2S-s\u00eb duken shp\u00ebrthimet e rregullta nat\u00ebn nga nj\u00eb kompani q\u00eb ndodhet pran\u00eb.<\/i><\/p>\n

Dispozitivet q\u00eb ne p\u00ebrdorim n\u00eb 'URUS' p\u00ebrmbajn\u00eb disa sensor\u00eb q\u00eb mbledhin informacion mbi p\u00ebrmbajtjen e gazrave t\u00eb caktuar, nivelin e zhurm\u00ebs dhe t\u00eb dh\u00ebna t\u00eb tjera p\u00ebr vler\u00ebsimin e situat\u00ebs ekologjike. Sasia e sakt\u00eb e sensor\u00ebve p\u00ebrcaktohet gjithmon\u00eb nga detyra specifike.<\/p>\n

\"Si
\nN\u00eb var\u00ebsi t\u00eb specifik\u00ebs s\u00eb matjeve, pajisjet me sensore mund t\u00eb vendosen n\u00eb muret e nd\u00ebrtesave, shtylla dhe n\u00eb vendet e tjera t\u00eb rast\u00ebsishme. \u00c7do pajisje e till\u00eb mbledh informacion, e agregon at\u00eb dhe e d\u00ebrgon n\u00eb portin e marrjes s\u00eb t\u00eb dh\u00ebnave. Aty ne ruajm\u00eb t\u00eb dh\u00ebnat p\u00ebr nj\u00eb periudh\u00eb t\u00eb gjat\u00eb dhe i p\u00ebrpunojm\u00eb p\u00ebr analiz\u00ebn e m\u00ebvonshme. Nj\u00eb shembull i thjesht\u00eb t\u00eb asaj q\u00eb ne marrim n\u00eb dalje pas analiz\u00ebs \u00ebsht\u00eb indeksi i cil\u00ebsis\u00eb s\u00eb ajrit, i njohur gjithashtu si AQI.<\/p>\n

N\u00eb m\u00ebnyr\u00eb paralele, shum\u00eb sh\u00ebrbime t\u00eb tjera funksionojn\u00eb n\u00eb platform\u00ebn ton\u00eb, por kryesisht ato jan\u00eb sh\u00ebrbime mb\u00ebshtet\u00ebse. P\u00ebr shembull, sh\u00ebrbimi i njoftimit d\u00ebrgon klient\u00ebve njoftime n\u00ebse ndonj\u00eb nga parametrat e ndjekur (p.sh., p\u00ebrqindja e CO2) ka tejkaluar vler\u00ebn e lejuar.<\/p>\n

Si i ruajm\u00eb t\u00eb dh\u00ebnat. Historia me Kubernetes n\u00eb bare metal<\/h2>\n

\nN\u00eb projektin e ekomonitorimit \"URUS\" ka disa depo t\u00eb t\u00eb dh\u00ebnave. N\u00eb nj\u00eb nga to ne ruajm\u00eb t\u00eb dh\u00ebnat \"e pap\u00ebrpunuara\" - ato q\u00eb kemi marr\u00eb drejtp\u00ebrdrejt nga pajisjet vet\u00eb. Kjo depo p\u00ebrfaq\u00ebson nj\u00eb \"band\u00eb\" magnetike, si\u00e7 ishin kasetat e vjetra, me historikun e t\u00eb gjith\u00eb treguesve. Lloji i dyt\u00eb i depozit\u00ebs p\u00ebrdoret p\u00ebr t\u00eb dh\u00ebnat e p\u00ebrpunuara paraprakisht - t\u00eb dh\u00ebna nga pajisjet, t\u00eb pasuruara me metadata rreth lidhjeve t\u00eb sensor\u00ebve dhe leximeve t\u00eb pajisjeve vet\u00eb, p\u00ebrkat\u00ebsin\u00eb ndaj organizatave, vendndodhjeve etj. Kjo informacion na lejon t\u00eb vler\u00ebsojm\u00eb dinamikisht se si ka ndryshuar nj\u00eb tregues i caktuar gjat\u00eb nj\u00eb periudhe t\u00eb caktuar kohe. Depoja e t\u00eb dh\u00ebnave \"e pap\u00ebrpunuara\" p\u00ebrdoret gjithashtu si nj\u00eb backup dhe p\u00ebr rikuperimin e t\u00eb dh\u00ebnave t\u00eb p\u00ebrpunuara paraprakisht, n\u00ebse ndonj\u00ebher\u00eb do t\u00eb ket\u00eb nevoj\u00eb p\u00ebr t\u00eb.<\/p>\n

Kur disa vite m\u00eb par\u00eb k\u00ebrkuam nj\u00eb zgjidhje p\u00ebr problemin e ruajtjes, kishim dy mund\u00ebsi p\u00ebr t\u00eb zgjedhur platform\u00ebn: Kubernetes dhe OpenStack. Por pasi q\u00eb e dyta duket mjaft monstruoze (thjesht shikoni arkitektur\u00ebn e saj p\u00ebr t'u bindur p\u00ebr k\u00ebt\u00eb), ne vendos\u00ebm t\u00eb p\u00ebrdorim pik\u00ebrisht Kubernetes. Nj\u00eb argument tjet\u00ebr n\u00eb favor t\u00eb saj ishte menaxhimi mjaft i leht\u00eb programatik, mund\u00ebsia p\u00ebr t\u00eb ndar\u00eb m\u00eb fleksib\u00ebl edhe nodet harduerike sipas burimeve. <\/p>\n

Paralelisht me m\u00ebsimin e Kubernetes vet\u00eb, ne studiuam edhe m\u00ebnyrat e ruajtjes s\u00eb t\u00eb dh\u00ebnave. Nd\u00ebrsa ruanim t\u00eb gjitha depozitat tona n\u00eb Kubernetes n\u00eb pajisjet tona, fituam nj\u00eb p\u00ebrvoj\u00eb shum\u00eb t\u00eb mir\u00eb. \u00c7do gj\u00eb q\u00eb kishim at\u00ebher\u00eb jetonte pik\u00ebrisht n\u00eb Kubernetes: depozita stateful, sistemi i monitorimit, CI\/CD. Kubernetes u b\u00eb p\u00ebr ne nj\u00eb platform\u00eb all-in-one. <\/p>\n

Por na p\u00eblqente t\u00eb punonim me Kubernetes si nj\u00eb sh\u00ebrbim, e jo t\u00eb merreshim me mb\u00ebshtetje dhe zhvillim t\u00eb tij. Gjithashtu, nuk na p\u00eblqente kostoja e mbajtjes s\u00eb tij n\u00eb bare metal, dhe zhvillimi k\u00ebrkohej vazhdimisht! P\u00ebr shembull, nj\u00eb nga detyrat e para ishte t\u00eb integrojm\u00eb Ingress-controllerat e Kubernetes n\u00eb infrastruktur\u00ebn rrjetore t\u00eb organizat\u00ebs ton\u00eb. Kjo \u00ebsht\u00eb nj\u00eb detyr\u00eb e madhe, sidomos n\u00ebse imagjinojm\u00eb se n\u00eb at\u00eb koh\u00eb nuk kishte asgj\u00eb t\u00eb gatshme p\u00ebr menaxhimin programatik t\u00eb burimeve si regjistrimet DNS ose ndarjet. IP-adresat<\/a>. M\u00eb von\u00eb filluam t\u00eb eksperimentojm\u00eb me depozita ekst\u00ebrne t\u00eb t\u00eb dh\u00ebnave. Nuk arrit\u00ebm t\u00eb zbatojm\u00eb controllerin PVC, por at\u00ebher\u00eb u kuptua q\u00eb ky ishte nj\u00eb front i madh pun\u00ebsh, p\u00ebr t\u00eb cilin duhej t\u00eb angazhoheshin specialist\u00eb t\u00eb ve\u00e7ant\u00eb.<\/p>\n

Kalimi n\u00eb Google Cloud Platform - nj\u00eb zgjidhje temporary.<\/h2>\n

\nKuptuam se k\u00ebshtu nuk mund t\u00eb vazhdohej dhe transferuam t\u00eb dh\u00ebnat tona nga bare metal n\u00eb Google Cloud Platform. N\u00eb t\u00eb v\u00ebrtet\u00eb, at\u00ebher\u00eb p\u00ebr nj\u00eb kompani ruse nuk kishte shum\u00eb mund\u00ebsi interesante: p\u00ebrve\u00e7 Google Cloud Platform, nj\u00eb sh\u00ebrbim t\u00eb ngjash\u00ebm ofronte vet\u00ebm Amazon, por ne zgjodh\u00ebm zgjidhjen nga Google. At\u00ebher\u00eb na dukej m\u00eb ekonomikisht e favorshme, m\u00eb af\u00ebr Upstream, p\u00ebr t\u00eb mos p\u00ebrmendur se Google vet\u00eb \u00ebsht\u00eb nj\u00eb lloj PoC Kubernetes n\u00eb Production.<\/p>\n

Problemi i par\u00eb serioz doli n\u00eb horizont paralelisht me rritjen e baz\u00ebs son\u00eb t\u00eb klient\u00ebve. Kur na u nevojit t\u00eb ruanim t\u00eb dh\u00ebna personale, u paraqit nevoja p\u00ebr t\u00eb zgjedhur: ose punojm\u00eb me Google dhe shkelim ligjet ruse, ose k\u00ebrkojm\u00eb nj\u00eb alternativ\u00eb n\u00eb RF. Zgjedhja, n\u00eb p\u00ebrgjith\u00ebsi, ishte e parashikueshme. \ud83d\ude42<\/p>\n

Si e shihnim ne sh\u00ebrbimin ideal t\u00eb cloud.<\/h2>\n

\nM\u00eb fillim t\u00eb k\u00ebrkimeve, ne tashm\u00eb e dinim se \u00e7far\u00eb d\u00ebshironim t\u00eb merrnim nga ofruesi i ardhsh\u00ebm t\u00eb cloud. \u00c7far\u00eb sh\u00ebrbimi po k\u00ebrkonim:<\/p>\n