{"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 fal\u00eb Kubernetes dhe automatizimit t\u00eb migrosh n\u00eb cloud brenda dy or\u00ebsh","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Si
\n
\nKompania \u00abURUS\u00bb provoi Kubernetes n\u00eb forma t\u00eb ndryshme: vendosje t\u00eb pavarur n\u00eb bare metal, n\u00eb Google Cloud, dhe m\u00eb pas transferoi platform\u00ebn e saj n\u00eb cloud t\u00eb Mail.ru Cloud Solutions (MCS). Si u zgjodh ofruesi i ri i cloud dhe si arrit\u00ebm t\u00eb migrojm\u00eb te ai p\u00ebr nj\u00eb rekord dy or\u00eb rr\u00ebfen Igor Shishkin (t3ran<\/a><\/noindex>), administrator i lart\u00eb i sistemeve n\u00eb \u00abURUS\u00bb.
\n<\/a><\/noindex><\/p>\n

\u00c7far\u00eb b\u00ebn \u00abURUS\u00bb <\/h2>\n

\nKa shum\u00eb m\u00ebnyra p\u00ebr t\u00eb p\u00ebrmir\u00ebsuar cil\u00ebsin\u00eb e ambientit urban, dhe nj\u00eb nga to \u00ebsht\u00eb ta b\u00ebsh at\u00eb ekologjikisht t\u00eb sigurt. Pik\u00ebrisht n\u00eb k\u00ebt\u00eb punojn\u00eb n\u00eb kompanin\u00eb \u00abURUS \u2014 Sh\u00ebrbime digjitale inteligjente\u00bb. K\u00ebtu implementohen zgjidhje q\u00eb ndihmojn\u00eb bizneset t\u00eb kontrollojn\u00eb treguesit e r\u00ebnd\u00ebsish\u00ebm ekologjik\u00eb dhe t\u00eb reduktojn\u00eb ndikimin negativ n\u00eb mjedis. Sensor\u00ebt mblidhni t\u00eb dh\u00ebna mbi p\u00ebrb\u00ebrjen e ajrit, nivelin e zhurm\u00ebs dhe parametra t\u00eb tjer\u00eb, dhe pastaj i d\u00ebrgojn\u00eb ato n\u00eb platform\u00ebn e p\u00ebrbashk\u00ebt \u00abURUS \u2014 Ekomon\u00bb p\u00ebr analiz\u00eb dhe hartimin e rekomandimeve. <\/p>\n

Si funksionon brenda \u00abURUS\u00bb<\/h2>\n

\nKlienti tipik i \u00abURUS\u00bb jan\u00eb kompani q\u00eb ndodhen n\u00eb nj\u00eb zon\u00eb banimi ose af\u00ebr saj. Kjo mund t\u00eb jet\u00eb nj\u00eb fabrik\u00eb, port, depo hekurudhor ose ndonj\u00eb objekt tjet\u00ebr. N\u00ebse klienti yn\u00eb ka marr\u00eb tashm\u00eb nj\u00eb paralajm\u00ebrim, \u00ebsht\u00eb d\u00ebnuar p\u00ebr ndotje t\u00eb ambientit, ose d\u00ebshiron vet\u00eb t\u00eb prodhoj\u00eb m\u00eb pak zhurm\u00eb dhe t\u00eb reduktoj\u00eb sasin\u00eb e emetimeve t\u00eb d\u00ebmshme, ai vihet n\u00eb kontakt me ne, dhe ne i ofrojm\u00eb nj\u00eb zgjidhje t\u00eb gatshme p\u00ebr monitorimin ekologjik.<\/p>\n

\"Si
\nN\u00eb grafikun e monitorimit t\u00eb koncentracionit t\u00eb H2S, duket qart\u00eb emetimi i rregullt nat\u00ebn nga nj\u00eb kompani af\u00ebr.<\/i><\/p>\n

Pajisjet q\u00eb p\u00ebrdorim n\u00eb \u00abURUS\u00bb p\u00ebrmbajn\u00eb disa sensore 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. Numri i sakt\u00eb i sensor\u00ebve p\u00ebrcaktohet gjithmon\u00eb nga detyra specifike.<\/p>\n

\"Si
\nN\u00eb var\u00ebsi t\u00eb specifikave t\u00eb matjeve, pajisjet me sensor\u00eb mund t\u00eb vendosen n\u00eb muret e nd\u00ebrtesave, shtyllat dhe n\u00eb vende t\u00eb tjera t\u00eb rastit. \u00c7do pajisje e till\u00eb mbledh informacione, i agregon ato dhe i d\u00ebrgon n\u00eb port\u00ebn e pranimit t\u00eb t\u00eb dh\u00ebnave. Atje ne ruajm\u00eb t\u00eb dh\u00ebnat p\u00ebr ruajtje afatgjat\u00eb dhe i p\u00ebrpunojm\u00eb ato p\u00ebr analiza t\u00eb m\u00ebvonshme. Nj\u00eb shembull i thjesht\u00eb i asaj q\u00eb ne marrim si rezultat pas analiz\u00ebs \u00ebsht\u00eb indeksi i cil\u00ebsis\u00eb s\u00eb ajrit, i njohur ndryshe si AQI.<\/p>\n

Paralelisht, n\u00eb platform\u00ebn ton\u00eb funksionojn\u00eb shum\u00eb sh\u00ebrbime t\u00eb tjera, por kryesisht ato kan\u00eb karakter sh\u00ebrbimi. P\u00ebr shembull, sh\u00ebrbimi i notifikimeve u d\u00ebrgon klient\u00ebve njoftime n\u00ebse ndonj\u00eb nga parametrat e monitoruar (p.sh., p\u00ebrmbajtja 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 monitorimit t\u00eb ekosistem\u00ebve \u00abURUS\u00bb ekzistojn\u00eb disa depo t\u00eb dh\u00ebnash. N\u00eb nj\u00eb prej tyre mbajm\u00eb t\u00eb dh\u00ebnat \u00abe pap\u00ebrpunuara\u00bb \u2014 ato q\u00eb kemi marr\u00eb drejtp\u00ebrdrejt nga pajisjet. Kjo depo p\u00ebrb\u00ebn nj\u00eb \u00abt\u00eb dh\u00ebna magnetike\u00bb, si\u00e7 ishin kasetat e vjetra, me historikun e t\u00eb gjith\u00eb treguesve. Lloji i dyt\u00eb i depove p\u00ebrdoret p\u00ebr t\u00eb dh\u00ebna t\u00eb p\u00ebrpunuara paraprakisht \u2014 t\u00eb dh\u00ebna nga pajisjet, t\u00eb pasuruara me metadata rreth lidhjeve t\u00eb sensor\u00ebve dhe leximeve t\u00eb vet\u00eb pajisjeve, p\u00ebrkat\u00ebsis\u00eb ndaj organizatave, vendeve t\u00eb pozicionimit etj. K\u00ebto informacione lejojn\u00eb t\u00eb vler\u00ebsojm\u00eb n\u00eb dinamik\u00eb se si ka ndryshuar nj\u00eb tregues i caktuar p\u00ebr nj\u00eb periudh\u00eb t\u00eb caktuar kohe. Depoja e t\u00eb dh\u00ebnave \u00abt\u00eb pap\u00ebrpunuara\u00bb p\u00ebrdoret gjithashtu si nj\u00eb kopje rezerv\u00eb dhe p\u00ebr rikuperimin e t\u00eb dh\u00ebnave t\u00eb p\u00ebrpunuara paraprakisht, n\u00eb rast se do t\u00eb lind\u00eb nj\u00eb nevoj\u00eb e till\u00eb.<\/p>\n

Kur disa vjet m\u00eb par\u00eb, kur po k\u00ebrkonim nj\u00eb zgjidhje p\u00ebr problemin e ruajtjes, b\u00ebm\u00eb zgjedhjen midis dy platformave: Kubernetes dhe OpenStack. Duke e par\u00eb se OpenStack duket mjaft i madh (mjafton t\u00eb shikoni arkitektur\u00ebn e tij p\u00ebr ta kuptuar), vendos\u00ebm t\u00eb zgjidhnim Kubernetes. Nj\u00eb tjet\u00ebr argument p\u00ebr t\u00eb ishte menaxhimi i thjesht\u00eb programor dhe mund\u00ebsia p\u00ebr t\u00eb ndar\u00eb edhe nodet fizike n\u00eb m\u00ebnyr\u00eb m\u00eb fleksib\u00ebl sipas burimeve. <\/p>\n

P\u00ebrve\u00e7 m\u00ebsimit t\u00eb Kubernetes, ne studiuam edhe metodat e ruajtjes s\u00eb t\u00eb dh\u00ebnave. Nd\u00ebrsa mbajt\u00ebm t\u00eb gjitha magazinat tona n\u00eb Kubernetes n\u00eb harduerin ton\u00eb, fituam nj\u00eb ekspertiz\u00eb t\u00eb shk\u00eblqyer. \u00c7do gj\u00eb q\u00eb kishim at\u00ebher\u00eb, ishte pik\u00ebrisht n\u00eb Kubernetes: magazinimi me gjendje, sistemi i monitoringut, CI\/CD. Kubernetes u b\u00eb p\u00ebr ne nj\u00eb platform\u00eb all-in-one. <\/p>\n

Por ne dojm\u00eb si t\u00eb punojm\u00eb me Kubernetes si nj\u00eb sh\u00ebrbim, jo t\u00eb angazhohemi n\u00eb mb\u00ebshtetje dhe zhvillim t\u00eb tij. P\u00ebr m\u00eb tep\u00ebr, nuk na p\u00eblqente kostot q\u00eb na shkaktonte n\u00eb bare metal, nd\u00ebrsa zhvillimi k\u00ebrkohej vazhdimisht! P\u00ebr shembull, nj\u00eb nga detyrat e para ishte t\u00eb integroheshin kontrolluesit Ingress t\u00eb Kubernetes n\u00eb infrastruktur\u00ebn ton\u00eb rrjetore. Kjo \u00ebsht\u00eb nj\u00eb detyr\u00eb e ngarkuar, ve\u00e7an\u00ebrisht kur e mendon q\u00eb n\u00eb at\u00eb koh\u00eb nuk kishte asgj\u00eb t\u00eb gatshme p\u00ebr menaxhimin programatik t\u00eb burimeve si regjistrat DNS apo ndarjen IP-adresave<\/a>. M\u00eb von\u00eb, filluam t\u00eb eksperimentojm\u00eb me ruajtjen e t\u00eb dh\u00ebnave t\u00eb jashtme. Nuk arrit\u00ebm kurr\u00eb t\u00eb implementonim kontrolluesin PVC, por at\u00ebher\u00eb u b\u00eb e qart\u00eb se ishte nj\u00eb volum i madh pune, p\u00ebr t\u00eb cilin duhej t\u00eb angazhonim specialist\u00eb t\u00eb ve\u00e7ant\u00eb.<\/p>\n

Kalimi n\u00eb Google Cloud Platform \u00ebsht\u00eb nj\u00eb zgjidhje e p\u00ebrkohshme<\/h2>\n

\nKuptuam se nuk mund t\u00eb vazhdojm\u00eb k\u00ebshtu m\u00eb tej, 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 megjithat\u00eb ne zgjodh\u00ebm zgjidhjen nga Google. At\u00ebher\u00eb na dukej se ishte m\u00eb ekonomikisht e favorshme, m\u00eb af\u00ebr Upstream, pa p\u00ebrmendur se Google vet\u00eb \u00ebsht\u00eb nj\u00eb lloj PoC Kubernetes n\u00eb Prodhuese.<\/p>\n

Problemi i par\u00eb serioz u shfaq n\u00eb horizont paralelisht me rritjen e baz\u00ebs son\u00eb t\u00eb klient\u00ebve. Kur na u shfaq nevoja p\u00ebr t\u00eb ruajtur t\u00eb dh\u00ebnat personale, u gjend\u00ebm p\u00ebrball\u00eb nj\u00eb zgjedhjeje: ose punojm\u00eb me Google dhe shkelim ligjet ruse, ose k\u00ebrkojm\u00eb nj\u00eb alternativ\u00eb brenda RF. Zgjedhja, n\u00eb p\u00ebrgjith\u00ebsi, ishte parashikueshme. \ud83d\ude42<\/p>\n

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

\nN\u00eb fillim t\u00eb k\u00ebrkimeve ne tashm\u00eb e dinim se \u00e7far\u00eb ishim duke k\u00ebrkuar nga ofruesi i ardhsh\u00ebm t\u00eb cloud. \u00c7far\u00eb sh\u00ebrbimi po k\u00ebrkonim:<\/p>\n