{"id":36933,"date":"2019-10-31T22:14:50","date_gmt":"2019-10-31T19:14:50","guid":{"rendered":"https:\/\/prohoster.info\/blog\/slyorm-devops-ot-git-do-sre-so-vsemi-ostanovkami\/"},"modified":"2019-10-31T22:14:50","modified_gmt":"2019-10-31T19:14:50","slug":"slyorm-devops-ot-git-do-sre-so-vsemi-ostanovkami","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/slyorm-devops-ot-git-do-sre-so-vsemi-ostanovkami","title":{"rendered":"Sl\u00ebrm DevOps: nga Git deri n\u00eb SRE me t\u00eb gjitha ndalesat","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>4-6 Shtator n\u00eb Sh\u00ebn Peterburg, n\u00eb sall\u00ebn e konferencave Selectel do t\u00eb zhvillohet nj\u00eb ngjarje tre ditore <noindex><a rel=\"nofollow\" href=\"http:\/\/slurm.io\/devops\">Sleurm DevOps<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p><img decoding=\"async\" alt=\"Sl\u00ebrm DevOps: nga Git deri n\u00eb SRE me t\u00eb gjitha ndalesat\" src=\"\/wp-content\/uploads\/2019\/08\/3306f0eab4bfd6360eda928fdc317a59.png\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><\/p>\n<p>Ne e nd\u00ebrtuam programin duke u nisur nga mendimi se studimet teorike mbi DevOps, si dhe manualet p\u00ebr mjetet, secili mund t\u2019i lexoj\u00eb vet\u00eb. T\u00eb r\u00ebnd\u00ebsishme jan\u00eb vet\u00ebm p\u00ebrvoja dhe praktika: shpjegimi se si duhet dhe si nuk duhet ta b\u00ebjm\u00eb, dhe tregimi se si veprojm\u00eb ne.<\/p>\n<p><\/p>\n<p>N\u00eb \u00e7do kompani, \u00e7do administrator ose zhvillues ka nivelin e tij t\u00eb DevOps. Disa e p\u00ebrdorin gabimisht Git, t\u00eb tjer\u00eb implementojn\u00eb SRE. Kursi \u00ebsht\u00eb organizuar n\u00eb m\u00ebnyr\u00eb q\u00eb \u00e7do person t\u00eb gjej\u00eb di\u00e7ka relevante q\u00eb mund t\u00eb zbatohet k\u00ebtu dhe tani.<\/p>\n<p><\/p>\n<p>Ne fillojm\u00eb me Git, ndjekim m\u00eb pas zhvillimin e aplikacioneve, nd\u00ebrveprimin e kodit dhe infrastruktur\u00ebs, nd\u00ebrtojm\u00eb CI\/CD, p\u00ebrshkruajm\u00eb infrastruktur\u00ebn si kod (IaC), testojm\u00eb zgjidhjen e arritur, konfigurojm\u00eb monitorimin, grumbullojm\u00eb dhe studiojm\u00eb logot, dhe n\u00eb fund arrijm\u00eb te SRE: e kthejm\u00eb besueshm\u00ebrin\u00eb n\u00eb nj\u00eb histori t\u00eb matshme dhe t\u00eb menaxhueshme.<\/p>\n<p><noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h2 id=\"git\">Git<\/h2>\n<p><\/p>\n<p>Sot, vet\u00ebm ata q\u00eb blen\u00eb laptopin e par\u00eb dje nuk e p\u00ebrdorin Git. Ky \u00ebsht\u00eb nj\u00eb mjet banale dhe i p\u00ebrhapur, dhe megjithat\u00eb ne shpesh hasim p\u00ebrdorimin e tij t\u00eb gabuar: duke filluar nga forcimi i push-it n\u00eb master dhe p\u00ebrfunduar me kopjimin e skedar\u00ebve nga Git n\u00eb server p\u00ebrmes Ctrl-C, Ctrl-V.<\/p>\n<p><\/p>\n<p>Ne tregojm\u00eb se si nuk duhet t\u00eb b\u00ebhet, si duhet t\u00eb b\u00ebhet, si b\u00ebhet n\u00eb Southbridge.<br \/>\nShkojm\u00eb n\u00eb praktik\u00eb: bazat e Git, pun\u00ebn ekipore.<\/p>\n<p><\/p>\n<p><strong>Tema nr. 1: Bazat e pun\u00ebs me Git<\/strong><\/p>\n<p><\/p>\n<ul>\n<li>Komandat baz\u00eb git init, commit, add, diff, log, status, pull, push<\/li>\n<li>Git flow, deg\u00ebt dhe etiketat, strategjit\u00eb e bashkimit<\/li>\n<li>Puna me disa repo remote<\/li>\n<\/ul>\n<p><\/p>\n<p><strong>Tema nr. 2: Puna ekipore me Git<\/strong><\/p>\n<p><\/p>\n<ul>\n<li>GitHub flow<\/li>\n<li>Fork, remote, pull request<\/li>\n<li>Konfliktet, l\u00ebshimet, nj\u00eb her\u00eb tjet\u00ebr p\u00ebr Gitflow dhe flukset e tjera n\u00eb lidhje me ekipet<\/li>\n<\/ul>\n<p><\/p>\n<p>Materiali \u00ebsht\u00eb organizuar n\u00eb m\u00ebnyr\u00eb q\u00eb administrator\u00ebt dhe zhvilluesit t\u00eb mund t\u00eb zbatojn\u00eb menj\u00ebher\u00eb t\u00eb gjitha praktikat n\u00eb pun\u00eb.<\/p>\n<p><\/p>\n<p>Nga k\u00ebndv\u00ebshtrimi i DevOps, p\u00ebrdorimi i duhur i Git organizon dhe automatizon proceset e zhvillimit dhe administrat\u00ebs, e eliminon nj\u00eb s\u00ebr\u00eb problemeve t\u00eb p\u00ebrs\u00ebritura, dhe rrit produktivitetin e pun\u00ebs.<\/p>\n<p><\/p>\n<h2 id=\"devops-razrabotchika\">DevOps p\u00ebr zhvillues<\/h2>\n<p><\/p>\n<p>Shikojm\u00eb DevOps me syt\u00eb e zhvilluesit: aktivizojm\u00eb ambientin lokal, shkruajm\u00eb aplikacionin, konfigurojm\u00eb monitorimin dhe logimin e tij, e testojm\u00eb at\u00eb lokal, organizojm\u00eb ruajtjen e variablave\/sekreteve dhe zbulimin e sh\u00ebrbimeve, shikojm\u00eb gjurmimin (opentracing).<\/p>\n<p><\/p>\n<p><strong>Tema nr. 3: Puna me aplikacionin nga k\u00ebndv\u00ebshtrimi i zhvillimit<\/strong><\/p>\n<p><\/p>\n<ul>\n<li>Konfigurimi i ambientit lokal: rekomandime praktike<\/li>\n<li>Shkrimi i nj\u00eb mikrosistemi me Python (duke p\u00ebrfshir\u00eb testet)<\/li>\n<li>P\u00ebrdorimi i docker-compose n\u00eb zhvillim<\/li>\n<\/ul>\n<p><\/p>\n<p><strong>Tema \u21164: Nd\u00ebrveprimi i kodit dhe infrastruktur\u00ebs<\/strong><\/p>\n<p><\/p>\n<ul>\n<li>Praktika e pun\u00ebs me konfigurime<\/li>\n<\/ul>\n<p><\/p>\n<p>Si rezultat, zhvilluesit do t\u00eb shohin se si kodi duhet t\u00eb d\u00ebrgoj\u00eb logje, si t\u00eb testohet, si do t\u00eb depurohet m\u00eb von\u00eb. Administrator\u00ebt do t\u00eb kuptojn\u00eb nevojat e zhvilluesve: \u00e7far\u00eb gabimesh ka n\u00eb kod, si t'i organizojn\u00eb testimet p\u00ebr zhvilluesit, si t\u00eb testojn\u00eb vet\u00eb projektin.<\/p>\n<p><\/p>\n<p>N\u00eb k\u00ebt\u00eb faz\u00eb, zgjidhet detyra kryesore e DevOps: krijimi i nj\u00eb mir\u00ebkuptimi dhe bashk\u00ebpunimi midis zhvilluesve dhe administrator\u00ebve. Kjo \u00ebsht\u00eb nj\u00eb hap ky\u00e7 p\u00ebr t\u00eb kaluar nga kalimi i detyrave n\u00eb nj\u00eb bashk\u00ebpunim t\u00eb p\u00ebrgjegjsh\u00ebm.<\/p>\n<p><\/p>\n<p>Si rezultat, rritet shpejt\u00ebsia dhe cil\u00ebsia e pun\u00ebs.<\/p>\n<p><\/p>\n<h2 id=\"cicd\">CI\/CD<\/h2>\n<p><\/p>\n<p>Automatizimi modern parashikon CI\/CD. Ne do t\u00eb fillojm\u00eb duke par\u00eb automatizimin manual: makefile, git hooks, skripte. Do t\u00eb shqyrtojm\u00eb kur k\u00ebto mjete jan\u00eb akoma t\u00eb r\u00ebnd\u00ebsishme dhe kur nuk duhet t\u00eb p\u00ebrdoren.<\/p>\n<p><\/p>\n<p>M\u00eb pas do t\u00eb shikojm\u00eb praktikat m\u00eb t\u00eb mira t\u00eb CI moderne duke marr\u00eb si shembull Gitlab.<\/p>\n<p><\/p>\n<p><strong>Tema \u21165: CI\/CD hyrje n\u00eb automatizim<\/strong><\/p>\n<p><\/p>\n<ul>\n<li>Hyrje n\u00eb automatizim<\/li>\n<li>Mjetet (bash, make, gradle)<\/li>\n<li>P\u00ebrdorimi i git-hooks p\u00ebr automatizimin e proceseve<\/li>\n<li>Linjat e prodhimit t\u00eb fabrik\u00ebs dhe aplikimi i tyre n\u00eb IT<\/li>\n<li>Shembulli i nd\u00ebrtimit t\u00eb nj\u00eb pipeline 't\u00eb p\u00ebrbashk\u00ebt'<\/li>\n<li>Software moderne p\u00ebr CI\/CD: Drone CI, BitBucket Pipelines, Travis etj.<\/li>\n<\/ul>\n<p><\/p>\n<p><strong>Tema \u21166: CI\/CD: Pun\u00eb me Gitlab<\/strong><\/p>\n<p><\/p>\n<ul>\n<li>Gitlab CI \u2014 p\u00ebrmbledhje<\/li>\n<li>Gitlab Runner, llojet e tyre dhe aplikimi<\/li>\n<li>Gitlab CI, ve\u00e7orit\u00eb e konfigurimit, praktikat m\u00eb t\u00eb mira<\/li>\n<li>Hapat e Gitlab CI<\/li>\n<li>Variablat e Gitlab CI<\/li>\n<li>Nd\u00ebrtimi, testimi, deploy<\/li>\n<li>Kontrolli dhe kufizimet e ekzekutimit: vet\u00ebm, kur<\/li>\n<li>Puna me artefaktet<\/li>\n<li>Modelet brenda .gitlab-ci.yml, rip\u00ebrdorimi i veprimeve n\u00eb pjes\u00eb t\u00eb ndryshme t\u00eb pipeline<\/li>\n<li>Inkluziv \u2014 seksione<\/li>\n<li>Menaxhimi qendror i gitlab-ci.yml (nj\u00eb skedar dhe push automate n\u00eb repo t\u00eb tjera)<\/li>\n<\/ul>\n<p><\/p>\n<p>Bashk\u00ebpunimi midis administrator\u00ebve dhe zhvilluesve arrin n\u00eb nj\u00eb nivel t\u00eb ri: Administratori shkruan modelin CI, nd\u00ebrsa zhvilluesit e rregullojn\u00eb at\u00eb, duke krijuar CI t\u00eb tyre pa var\u00ebsi nga administratori.<\/p>\n<p><\/p>\n<p>Var\u00ebsia e zhvilluesve nga administrator\u00ebt zvog\u00eblohet, ulet sasia e pun\u00ebs manuale dhe zhduket problemi i 'personit t\u00eb vet\u00ebm q\u00eb di si t\u00eb punoj\u00eb me makefile-in'. D\u00ebrgesat b\u00ebhen t\u00eb sigurta dhe t\u00eb shpejta.<\/p>\n<p><\/p>\n<h2 id=\"iac\">IaC<\/h2>\n<p><\/p>\n<p>Tema 'Infrastructure as Code' p\u00ebrmes Terraform do t\u00eb shpjegohet nga administratori i cloud-it n\u00eb Selectel, Aleksei Stepanenko. Ai do t\u00eb tregoj\u00eb se si t\u00eb vendosni dhe t\u00eb shkall\u00ebzoni server\u00ebt shpejt dhe automatikisht, si t\u00eb paketoni automatikisht imazhet dhe si t\u00eb p\u00ebrdorni shabllonat e konfigurimit p\u00ebr t\u00eb marr\u00eb menj\u00ebher\u00eb makina t\u00eb konfiguruara.<\/p>\n<p><\/p>\n<p>Nj\u00eb njeri, i cili ka b\u00ebr\u00eb mij\u00ebra zgjidhje IaC, do t\u00eb tregoj\u00eb se si t\u00eb b\u00ebni si\u00e7 duhet dhe \u00e7far\u00eb nuk duhet t\u00eb b\u00ebni.<\/p>\n<p><\/p>\n<p>Zgjidhja p\u00ebr cloud-in Selectel me ndryshime minime p\u00ebrshtatet p\u00ebr cloud-et Google dhe Amazon.<\/p>\n<p><\/p>\n<p>Punonj\u00ebsi i Southbridge, Nikolai Mesropyan, n\u00ebp\u00ebrmjet Ansible do t\u00eb tregoj\u00eb se si t\u00eb vendosni nj\u00eb aplikacion t\u00eb pun\u00ebs q\u00eb funksionon pa r\u00ebnie t\u00eb sh\u00ebrbimit dhe t\u00eb verifikoni funksionimin e tij.<\/p>\n<p><\/p>\n<p>N\u00ebse ndryshoni infrastruktur\u00ebn me duar (konfiguroni server\u00ebt, instaloni biblioteka, paketa sipas nevoj\u00ebs), gjat\u00eb p\u00ebrpjekjes p\u00ebr t\u00eb ngritur nj\u00eb kopje t\u00eb ambientit, duhet t\u00eb kujtoni dhe t\u00eb riprodhoni t\u00eb gjitha veprimet tuaja. Ky detyr\u00eb leht\u00eb z\u00eb 3-5 dit\u00eb. Puna me infrastruktur\u00ebn si kod garanton q\u00eb keni nj\u00eb p\u00ebrshkrim t\u00eb p\u00ebrdit\u00ebsuar t\u00eb ambientit, i cili mund t\u00eb vendoset brenda disa minutash.<\/p>\n<p><\/p>\n<p>Nikolai do t\u00eb tregoj\u00eb se si t\u00eb shkruani playbooks, cilat gabime ndodhin, pse ndonj\u00ebher\u00eb playbooks punojn\u00eb ngadal\u00eb ose ndryshe nga sa pritej. Kjo \u00ebsht\u00eb p\u00ebrvoja e shum\u00eb viteve t\u00eb p\u00ebrdorimit t\u00eb IaC n\u00eb Southbridge.<\/p>\n<p><\/p>\n<p><strong>Tema \u21167: Infrastructure as Code<\/strong><\/p>\n<p><\/p>\n<ul>\n<li>IaC: qasje ndaj infrastruktur\u00ebs si kod<\/li>\n<li>Ofruesit e cloud si furnizues t\u00eb infrastruktur\u00ebs<\/li>\n<li>Mjetet e inicializimit t\u00eb sistemeve, nd\u00ebrtimi i imazheve (packer)<\/li>\n<li>IaC p\u00ebrmes Terraform<\/li>\n<li>Ruajtja e konfiguracioneve, bashk\u00ebpunimi, automatizimi i aplikacioneve<\/li>\n<li>Praktik\u00eb p\u00ebr krijimin e playbook-\u00ebve Ansible<\/li>\n<li>Idempotent\u00ebsi, deklarativitet<\/li>\n<li>IaC p\u00ebrmes Ansible<\/li>\n<li>Database as a Code \/ Q\u00ebndrueshm\u00ebria e PostgreSQL<\/li>\n<\/ul>\n<p><\/p>\n<p>Infrastruktura merr deklarativitet dhe idempotenc\u00eb.<br \/>\nAdministrator\u00ebt m\u00ebsojn\u00eb t\u00eb menaxhojn\u00eb infrastruktur\u00eb t\u00eb komplikuar: t\u00eb krijojn\u00eb shpejt ambiente t\u00eb reja, t\u00eb mbajn\u00eb unitetin e t\u00eb gjitha ambienteve, t\u00eb shikojn\u00eb historin\u00eb e ndryshimeve, \u00e7ka \u00ebsht\u00eb kritik kur projekti punohet nga disa ekipe.<br \/>\nProgramuesit mund t\u00eb studiojn\u00eb infrastruktur\u00ebn dhe t\u00eb vendosin ambientet e tyre.<\/p>\n<p><\/p>\n<p>Bonus i seksionit - krijimi dhe konfigurimi i nj\u00eb klasteri t\u00eb q\u00ebndruesh\u00ebm t\u00eb baz\u00ebs s\u00eb t\u00eb dh\u00ebnave PostgreSQL. Ne do t'u japim nj\u00eb playbook t\u00eb gatshme, t\u00eb cilin e p\u00ebrdorim n\u00eb Southbridge, ju do t\u00eb vendosni klasterin n\u00eb nj\u00eb sken\u00eb m\u00ebsimore dhe do t\u00eb mund ta p\u00ebrdorni k\u00ebt\u00eb zgjidhje n\u00eb kompanin\u00eb tuaj.<\/p>\n<p><\/p>\n<h2 id=\"testirovanie-infrastruktury-i-monitoring\">Testimi i Infrastruktur\u00ebs dhe Monitorimi<\/h2>\n<p><\/p>\n<p>Automatizimi lejon q\u00eb nj\u00eb gabim t\u00eb shp\u00ebrndahet menj\u00ebher\u00eb n\u00eb nj\u00eb mij\u00eb server\u00eb. Me \u00e7do ndryshim, testimi \u00ebsht\u00eb i nevojsh\u00ebm. Ndonj\u00ebher\u00eb, testimi manual merr kaq shum\u00eb koh\u00eb sa e anulohet p\u00ebrpar\u00ebsin\u00eb e automatizimit.<\/p>\n<p><\/p>\n<p>Do t\u00eb tregojm\u00eb n\u00eb praktik\u00eb se si t\u00eb shkruani testimin e roleve. Si rezultat, do t\u00eb jeni n\u00eb gjendje t\u00eb shkruani teste p\u00ebr kompanin\u00eb tuaj. Nuk do t\u00eb ket\u00eb nevoj\u00eb m\u00eb t\u00eb mbani mend parametrat q\u00eb keni vendosur, do t'i p\u00ebrshkruani ato n\u00eb teste dhe do t\u00eb kontrolloni automatikisht q\u00eb t\u00eb gjitha zgjidhjet dhe ndihmat e kaluara jan\u00eb ende n\u00eb vend.<\/p>\n<p><\/p>\n<p>Pastaj do t\u00eb m\u00ebsojm\u00eb si t\u00eb shtojm\u00eb automatikisht t\u00eb gjitha server\u00ebt e rinj n\u00eb monitorim. Do t\u00eb shqyrtojm\u00eb ve\u00e7mas monitorimin e infrastruktur\u00ebs dhe aplikacioneve. Do t\u00eb tregojm\u00eb praktika t\u00eb k\u00ebqija dhe t\u00eb mira.<\/p>\n<p><\/p>\n<p><strong>Tema \u21168: Testimi i infrastruktur\u00ebs<\/strong><\/p>\n<p><\/p>\n<ul>\n<li>Testimi dhe integrimi i vazhduesh\u00ebm me Molecule dhe Gitlab CI<\/li>\n<li>P\u00ebrdorimi i Vagrant<\/li>\n<\/ul>\n<p><\/p>\n<p><strong>Tema \u21169: Monitorimi i infrastruktur\u00ebs me Prometheus<\/strong><\/p>\n<p><\/p>\n<ul>\n<li>Pse nevojitet monitorimi<\/li>\n<li>Llojet e monitorimit<\/li>\n<li>Njoftimet n\u00eb sistemin e monitorimit<\/li>\n<li>Si t\u00eb nd\u00ebrtoni nj\u00eb sistem monitorimi t\u00eb sh\u00ebndetsh\u00ebm<\/li>\n<li>Njoftime t\u00eb lexueshme nga njeriu, p\u00ebr t\u00eb gjith\u00eb<\/li>\n<li>Kontrolli i Sh\u00ebndetit: \u00e7far\u00eb duhet t\u00eb keni parasysh<\/li>\n<li>Automatizimi n\u00eb baz\u00eb t\u00eb t\u00eb dh\u00ebnave nga monitorimi<\/li>\n<\/ul>\n<p><\/p>\n<p>Monitorimi q\u00eb funksionon keq \u00ebsht\u00eb justifikim p\u00ebr t\u00eb qen\u00eb pa monitorim. Biznesit nuk i intereson q\u00eb faqja kryesore e dyqanit online \u00ebsht\u00eb e qasshme, n\u00ebse forma e pages\u00ebs jep gabim.<\/p>\n<p><\/p>\n<p>N\u00eb konfigurimin e monitorimit dhe zgjidhjen e problemeve, zhvilluesit dhe administrator\u00ebt angazhohen nj\u00ebsoj. N\u00eb fakt, tradicionalisht detyrat e monitorimit bien mbi administrator\u00ebt. Kursi yn\u00eb do t'u tregoj\u00eb zhvilluesve se \u00e7far\u00eb roli ata luajn\u00eb n\u00eb krijimin e nj\u00eb monitorimi efektiv. Administrator\u00ebt do t\u00eb marrin praktikat m\u00eb t\u00eb mira nga Southbridge. Si rezultat, numri i humbjeve shkaktuar nga defektet dhe vonesat e faqes ose aplikacionit do t\u00eb bjer\u00eb shpejt.<\/p>\n<p><\/p>\n<p>Bonusi i seksionit: automatizimi n\u00eb baz\u00eb t\u00eb monitorimit. P\u00ebr shembull, monitorimi njofton q\u00eb ka ardhur ngarkes\u00eb n\u00eb sit dhe skelimi i server\u00ebve web fillohet automatikisht.<\/p>\n<p><\/p>\n<h2 id=\"logirovanie\">Regjistrimi<\/h2>\n<p><\/p>\n<p>Gabimi kryesor n\u00eb pun\u00ebn me regjistrat \u00ebsht\u00eb se administrator\u00ebt dhe zhvilluesit i shikojn\u00eb ato drejtp\u00ebrdrejt n\u00eb servera. N\u00ebse keni m\u00eb shum\u00eb se nj\u00eb server, kjo merr koh\u00eb. Kjo nuk \u00ebsht\u00eb e sigurt: zhvilluesi hyn n\u00eb server, ku nuk duhet t\u00eb jet\u00eb.<\/p>\n<p><\/p>\n<p>DevOps k\u00ebrkon mbledhjen, p\u00ebrpunimin dhe analitik\u00ebn e centralizuar t\u00eb regjistrave.<\/p>\n<p><\/p>\n<p><strong>Tema \u211610: Regjistrimi i aplikacioneve me ELK<\/strong><\/p>\n<p><\/p>\n<ul>\n<li>P\u00ebrdorimet dhe mund\u00ebsit\u00eb kryesore t\u00eb elastic (k\u00ebrkimi, ruajtja, ve\u00e7orit\u00eb e shp\u00ebrndarjes, fleksibiliteti n\u00eb konfigurim)<\/li>\n<li>P\u00ebrmbledhje e kibana (mund\u00ebsit\u00eb kryesore, gjuha e k\u00ebrkimeve, menaxhimi i paneleve, krijimi i grafik\u00ebve)<\/li>\n<li>P\u00ebrmbledhje e produkteve t\u00eb bazuara n\u00eb elastic dhe p\u00ebrdorimi i tyre<\/li>\n<li>Mblidhen metrikat n\u00eb APM (ndjekja e aplikacioneve)<\/li>\n<li>Shtes\u00eb: P\u00ebrmbledhje e produktit t\u00eb ri \u2014 SIEM<\/li>\n<\/ul>\n<p><\/p>\n<p>Implementimi i k\u00ebtij qasje do ta b\u00ebj\u00eb logun nj\u00eb mjet t\u00eb thjesht\u00eb dhe t\u00eb kuptuesh\u00ebm p\u00ebr analizimin, konfigurimin dhe optimizimin e aplikacionit dhe infrastruktur\u00ebs.<\/p>\n<p><\/p>\n<h2 id=\"sre\">SRE<\/h2>\n<p><\/p>\n<p>Dhe ne arrijm\u00eb te tema, p\u00ebr t\u00eb cil\u00ebn Southbridge \u00ebsht\u00eb duke u p\u00ebrgatitur dhe p\u00ebr t\u00eb cil\u00ebn fol\u00ebsit e tjer\u00eb d\u00ebshirojn\u00eb t\u00eb q\u00ebndrojn\u00eb deri n\u00eb dit\u00ebn e fundit t\u00eb Slerma. Ne jemi t\u00eb lumtur q\u00eb Ivan Kruglov nga Booking.com pranoi t\u00eb flas\u00eb p\u00ebr t\u00eb.<\/p>\n<p><\/p>\n<p>Projekti jeton n\u00eb bot\u00ebn reale, ku besueshm\u00ebria kurr\u00eb nuk \u00ebsht\u00eb absolute dhe \u00e7do vendim ka nj\u00eb kostos.<\/p>\n<p><\/p>\n<p>\u00c7far\u00eb \u00ebsht\u00eb SLA n\u00eb kontekstin e nj\u00eb projekti t\u00eb nd\u00ebrlikuar? Le t\u00eb themi, si mund t\u00eb vler\u00ebsojm\u00eb se faqja \u00ebsht\u00eb e aksesueshme, por imazhet ngarkohen me vones\u00eb. Cilat jan\u00eb metrikat e SLA, ku duhet t\u00eb merren ato, si duhen marr\u00eb?<\/p>\n<p><\/p>\n<p>Si t\u00eb vendosim SLA? Si t'i p\u00ebrmbushim ato?<\/p>\n<p><\/p>\n<p><strong>Tema Nr. 11: SRE<\/strong><br \/>\nP\u00ebrcaktimi i SLA, SLO, Error Budget dhe terma t\u00eb tjer\u00eb t\u00eb friksh\u00ebm nga bota e SRE<br \/>\nSRE: Praktika e monitorimit t\u00eb SLI dhe SLO<br \/>\nSRE: Praktika e aplikimit t\u00eb Error Budget<br \/>\nSRE: Menaxhimi i nd\u00ebrprerjeve dhe ngarkes\u00ebs operative (apigateway, service mesh, circuit brakers)<br \/>\nBiznesi d\u00ebshiron SRE. Edhe n\u00eb nivelin m\u00eb t\u00eb thjesht\u00eb: t\u00eb marr\u00eb nj\u00eb server rezerv\u00eb ose t\u00eb rikthej\u00eb nga backup? Nj\u00eb baz\u00eb t\u00eb dh\u00ebnash apo kluster? T\u00eb vendos\u00eb mbrojtje nga DDoS n\u00eb m\u00ebnyr\u00eb parandaluesh\u00ebm apo vet\u00ebm n\u00eb momentin e sulmit?<\/p>\n<p><\/p>\n<p>Drejtor\u00ebt nuk do t\u00eb p\u00ebrqafonin nj\u00eb histori t\u00eb th\u00ebn\u00eb se \"faqja funksionon\", kur nj\u00eb klient i telefonon dhe thot\u00eb se forma e porosis\u00eb nuk hapet.<\/p>\n<p><\/p>\n<p>Prandaj, \u00ebsht\u00eb e r\u00ebnd\u00ebsishme q\u00eb inxhinieri DevOps t\u00eb ket\u00eb t\u00eb pakt\u00ebn nj\u00eb kuptim t\u00eb p\u00ebrgjithsh\u00ebm t\u00eb SRE, p\u00ebr t\u00eb folur sakt\u00ebsisht me biznesin p\u00ebr nevojat e tij.<\/p>\n<p><\/p>\n<h2 id=\"itog\">P\u00ebrfundimi<\/h2>\n<p><\/p>\n<p>Gjat\u00eb koh\u00ebs <noindex><a rel=\"nofollow\" href=\"http:\/\/slurm.io\/devops\">Slerma DevOps<\/a><\/noindex> administrator\u00ebt dhe zhvilluesit do t\u00eb m\u00ebsojn\u00eb:<br \/>\n\u2014 t\u00eb punojn\u00eb si\u00e7 duhet me Git;<br \/>\n\u2014 t\u00eb organizojn\u00eb zhvillimin lokal;<br \/>\n\u2014 t\u00eb konfigurojn\u00eb (administrator\u00ebt) dhe t\u00eb p\u00ebrdorin (zhvilluesit) CI\/CD;<br \/>\n\u2014 t\u00eb punojn\u00eb me infrastruktur\u00ebn si kod;<br \/>\n\u2014 t\u00eb testojn\u00eb infrastruktur\u00ebn;<br \/>\n\u2014 t\u00eb monitorojn\u00eb infrastruktur\u00ebn dhe aplikacionin;<br \/>\n\u2014 t\u00eb konfigurojn\u00eb logimin;<br \/>\n\u2014 t\u00eb kuptojn\u00eb, dhe n\u00eb ideali \u2014 t\u00eb p\u00ebrdorin SRE.<\/p>\n<p><\/p>\n<p>P\u00ebr lexuesit e kujdessh\u00ebm \u2014 me kodin promocional habrapost ka nj\u00eb zbritje prej 15%.<\/p>\n<p><\/p>\n<p>P\u00ebr t\u00eb gjitha pikat ne po p\u00ebrgatisim praktik\u00eb dhe mjete. K\u00ebshtu q\u00eb \u00e7do pjes\u00ebmarr\u00ebs pas kthehjes nga Slerma do t\u00eb jet\u00eb n\u00eb gjendje t\u00eb \u00e7oj\u00eb kompanin\u00eb e tij n\u00eb nivelin e ardhsh\u00ebm t\u00eb DevOps.<\/p>\n<p><\/p>\n<p>P\u00ebr biznesin, kjo do t\u00eb thot\u00eb ulje t\u00eb kostos s\u00eb administrat\u00ebs dhe zhvillimit, reduktimin e koh\u00ebs s\u00eb papun\u00ebsis\u00eb, rritjen e besueshm\u00ebris\u00eb, dor\u00ebzimin m\u00eb t\u00eb shpejt\u00eb t\u00eb funksioneve dhe zgjidhjen e defekteve.<\/p>\n<p>Burimi: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/southbridge\/blog\/462879\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>4-6 \u0441\u0435\u043d\u0442\u044f\u0431\u0440\u044f \u0432 \u0421\u0430\u043d\u043a\u0442-\u041f\u0435\u0442\u0435\u0440\u0431\u0443\u0440\u0433\u0435, \u0432 \u043a\u043e\u043d\u0444\u0435\u0440\u0435\u043d\u0446-\u0437\u0430\u043b\u0435 Selectel \u043f\u0440\u043e\u0439\u0434\u0435\u0442 \u0442\u0440\u0435\u0445\u0434\u043d\u0435\u0432\u043d\u044b\u0439 \u0421\u043b\u0451\u0440\u043c DevOps. \u041c\u044b \u0441\u0442\u0440\u043e\u0438\u043b\u0438 \u043f\u0440\u043e\u0433\u0440\u0430\u043c\u043c\u0443, \u0438\u0441\u0445\u043e\u0434\u044f \u0438\u0437 \u043c\u044b\u0441\u043b\u0438, \u0447\u0442\u043e \u0442\u0435\u043e\u0440\u0435\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0435 \u0442\u0440\u0443\u0434\u044b \u043f\u043e DevOps, \u043a\u0430\u043a \u0438 \u043c\u0430\u043d\u0443\u0430\u043b\u044b \u043a \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u0430\u043c, \u043a\u0430\u0436\u0434\u044b\u0439 \u043c\u043e\u0436\u0435\u0442 \u043f\u0440\u043e\u0447\u0438\u0442\u0430\u0442\u044c \u0441\u0430\u043c\u043e\u0441\u0442\u043e\u044f\u0442\u0435\u043b\u044c\u043d\u043e. \u0418\u043d\u0442\u0435\u0440\u0435\u0441\u043d\u044b \u0442\u043e\u043b\u044c\u043a\u043e \u043e\u043f\u044b\u0442 \u0438 \u043f\u0440\u0430\u043a\u0442\u0438\u043a\u0430: \u043e\u0431\u044a\u044f\u0441\u043d\u0435\u043d\u0438\u0435, \u043a\u0430\u043a \u0434\u0435\u043b\u0430\u0442\u044c \u043d\u0430\u0434\u043e \u0438 \u043d\u0435 \u043d\u0430\u0434\u043e, \u0438 \u0440\u0430\u0441\u0441\u043a\u0430\u0437, \u043a\u0430\u043a \u0434\u0435\u043b\u0430\u0435\u043c \u043c\u044b. \u0412 \u043a\u0430\u0436\u0434\u043e\u0439 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0438, \u0443 \u043a\u0430\u0436\u0434\u043e\u0433\u043e \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0430\u0442\u043e\u0440\u0430 \u0438\u043b\u0438 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-36933","post","type-post","status-publish","format-standard","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.2.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"4-6 \u0441\u0435\u043d\u0442\u044f\u0431\u0440\u044f \u0432 \u0421\u0430\u043d\u043a\u0442-\u041f\u0435\u0442\u0435\u0440\u0431\u0443\u0440\u0433\u0435, \u0432 \u043a\u043e\u043d\u0444\u0435\u0440\u0435\u043d\u0446-\u0437\u0430\u043b\u0435 Selectel \u043f\u0440\u043e\u0439\u0434\u0435\u0442 \u0442\u0440\u0435\u0445\u0434\u043d\u0435\u0432\u043d\u044b\u0439 \u0421\u043b\u0451\u0440\u043c DevOps.\" \/>\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\/administrirovanie\/slyorm-devops-ot-git-do-sre-so-vsemi-ostanovkami\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2.1\" \/>\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\udd47\u0421\u043b\u0451\u0440\u043c DevOps: \u043e\u0442 Git \u0434\u043e SRE \u0441\u043e \u0432\u0441\u0435\u043c\u0438 \u043e\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0430\u043c\u0438 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"4-6 \u0441\u0435\u043d\u0442\u044f\u0431\u0440\u044f \u0432 \u0421\u0430\u043d\u043a\u0442-\u041f\u0435\u0442\u0435\u0440\u0431\u0443\u0440\u0433\u0435, \u0432 \u043a\u043e\u043d\u0444\u0435\u0440\u0435\u043d\u0446-\u0437\u0430\u043b\u0435 Selectel \u043f\u0440\u043e\u0439\u0434\u0435\u0442 \u0442\u0440\u0435\u0445\u0434\u043d\u0435\u0432\u043d\u044b\u0439 \u0421\u043b\u0451\u0440\u043c DevOps.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/slyorm-devops-ot-git-do-sre-so-vsemi-ostanovkami\" \/>\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-31T19:14:50+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T19:14:50+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\udd47Slerma DevOps: nga Git deri te SRE me t\u00eb gjitha ndalesat | ProHoster","description":"M\u00eb 4-6 Shtator n\u00eb Sh\u00ebn Petersburg, n\u00eb sall\u00ebn e konferencave Selectel do t\u00eb mbahet Slerma DevOps p\u00ebr tri dit\u00eb.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/slyorm-devops-ot-git-do-sre-so-vsemi-ostanovkami","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\udd47\u0421\u043b\u0451\u0440\u043c DevOps: \u043e\u0442 Git \u0434\u043e SRE \u0441\u043e \u0432\u0441\u0435\u043c\u0438 \u043e\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0430\u043c\u0438 | ProHoster","og:description":"4-6 \u0441\u0435\u043d\u0442\u044f\u0431\u0440\u044f \u0432 \u0421\u0430\u043d\u043a\u0442-\u041f\u0435\u0442\u0435\u0440\u0431\u0443\u0440\u0433\u0435, \u0432 \u043a\u043e\u043d\u0444\u0435\u0440\u0435\u043d\u0446-\u0437\u0430\u043b\u0435 Selectel \u043f\u0440\u043e\u0439\u0434\u0435\u0442 \u0442\u0440\u0435\u0445\u0434\u043d\u0435\u0432\u043d\u044b\u0439 \u0421\u043b\u0451\u0440\u043c DevOps.","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/slyorm-devops-ot-git-do-sre-so-vsemi-ostanovkami","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-31T19:14:50+00:00","article:modified_time":"2019-10-31T19:14:50+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"36933","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":"Article","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-22 05:23:22","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:36:24","updated":"2026-01-22 05:23:22","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\/36933","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=36933"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/36933\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=36933"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=36933"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=36933"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}