{"id":33504,"date":"2019-10-31T21:52:58","date_gmt":"2019-10-31T18:52:58","guid":{"rendered":"https:\/\/prohoster.info\/blog\/rukovodstvo-dlya-chajnikov-sozdanie-tsepochek-devops-s-pomoshhyu-instrumentov-s-otkrytym-ishodnym-kodom\/"},"modified":"2019-10-31T21:52:58","modified_gmt":"2019-10-31T18:52:58","slug":"rukovodstvo-dlya-chajnikov-sozdanie-tsepochek-devops-s-pomoshhyu-instrumentov-s-otkrytym-ishodnym-kodom","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/rukovodstvo-dlya-chajnikov-sozdanie-tsepochek-devops-s-pomoshhyu-instrumentov-s-otkrytym-ishodnym-kodom","title":{"rendered":"Udh\u00ebzues p\u00ebr fillestar\u00ebt: krijimi i zinxhir\u00ebve DevOps me mjete me burim t\u00eb hapur","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Udh\u00ebzues
\nKrijimi i zinxhirit tuaj t\u00eb par\u00eb DevOps n\u00eb pes\u00eb hapa p\u00ebr fillestar\u00ebt.<\/em><\/p>\n

<\/p>\n

DevOps \u00ebsht\u00eb b\u00ebr\u00eb ila\u00e7i p\u00ebr proceset e zhvillimit q\u00eb jan\u00eb shum\u00eb t\u00eb ngadalta, t\u00eb ndara dhe me probleme t\u00eb tjera. Por, k\u00ebrkohen njohuri minimale n\u00eb DevOps. K\u00ebtu do t\u00eb shqyrtojm\u00eb konceptet si zinxhiri DevOps dhe si ta krijoni at\u00eb n\u00eb pes\u00eb hapa. Ky nuk \u00ebsht\u00eb nj\u00eb udh\u00ebzues i plot\u00eb, por vet\u00ebm nj\u00eb 'peshk', q\u00eb mund t\u00eb zgjerohet. Le t\u00eb fillojm\u00eb me historin\u00eb.<\/p>\n

<\/p>\n

Njohja ime me DevOps<\/h3>\n

<\/p>\n

Dikur kam punuar me cloud n\u00eb Citi Group dhe kam zhvilluar nj\u00eb aplikacion IaaS p\u00ebr menaxhimin e infrastruktur\u00ebs cloud t\u00eb Citi, por gjithmon\u00eb kam qen\u00eb i interesuar se si mund t\u00eb optimizohet zinxhiri i zhvillimit dhe si t\u00eb p\u00ebrmir\u00ebsohej kultura mes zhvilluesve. Greg Lavender, drejtori yn\u00eb teknik p\u00ebr arkitektur\u00ebn dhe infrastruktur\u00ebn cloud, m\u00eb k\u00ebshilloi t\u00eb lexoj librin Projekti 'Feniks'<\/a><\/noindex>. Ai shpjegon shk\u00eblqyer parimet e DevOps, duke u lexuar si nj\u00eb roman.<\/p>\n

<\/a><\/noindex><\/p>\n

Tabela n\u00eb an\u00ebn tjet\u00ebr tregon se sa shpesh kompanit\u00eb nxjerrin versionet e reja:<\/p>\n

<\/p>\n

\"Udh\u00ebzues<\/a><\/noindex><\/p>\n

<\/p>\n

Si arrijn\u00eb Amazon, Google dhe Netflix t\u00eb nxjerrin kaq shum\u00eb? E t\u00ebra \u00ebsht\u00eb e thjesht\u00eb: ata kan\u00eb kuptuar se si t\u00eb krijojn\u00eb nj\u00eb zinxhir DevOps pothuajse perfekt.<\/p>\n

<\/p>\n

N\u00eb Citi, gjith\u00e7ka ishte ndryshe derisa kaluam n\u00eb DevOps. N\u00eb at\u00eb koh\u00eb, ekipi im kishte mjedise t\u00eb ndryshme, por ne e b\u00ebnim dor\u00ebzimin n\u00eb serverin e zhvillimit manualisht. T\u00eb gjith\u00eb zhvilluesit kishin qasje vet\u00ebm n\u00eb nj\u00eb server zhvillimi q\u00eb bazohej n\u00eb IBM WebSphere Application Server Community Edition. Me tentativa t\u00eb nj\u00ebkohshme t\u00eb dor\u00ebzimit, serveri \u2018rr\u00ebzohej\u2019, dhe na duhej t\u00eb \u2018bisedonim\u2019 \u00e7do her\u00eb n\u00eb m\u00ebnyr\u00eb \u2018t\u00eb v\u00ebshtir\u00eb\u2019. Po ashtu, kishim mbulim t\u00eb pamjaftuesh\u00ebm t\u00eb kodit me teste, nj\u00eb proces t\u00eb lodhsh\u00ebm dor\u00ebzimi manual dhe asnj\u00eb mund\u00ebsi p\u00ebr t\u00eb ndjekur dor\u00ebzimin e kodit sipas ndonj\u00eb k\u00ebrkese apo detyre t\u00eb klientit.<\/p>\n

<\/p>\n

I was clear that something needed to be done urgently, so I found a like-minded colleague. We decided to create our first DevOps pipeline together \u2014 he set up the virtual machine and the Tomcat application server, while I handled Jenkins, integration with Atlassian Jira and Bitbucket, as well as code coverage testing. The project was successful: we fully automated the development pipeline, achieved nearly 100% uptime for the development server, could track and improve code coverage testing, and linked the Git branch to deployment and Jira tasks. Almost all the tools we used to build the DevOps pipeline were open source.<\/p>\n

<\/p>\n

In reality, the pipeline was simplified since we didn't even use advanced configurations with Jenkins or Ansible. But we made it work. Perhaps this is a consequence of the principle Pareto<\/a><\/noindex> (also known as the 80\/20 rule).<\/p>\n

<\/p>\n

A brief overview of the DevOps and CI\/CD pipeline<\/h3>\n

<\/p>\n

DevOps ka ndryshime t\u00eb ndryshme. Si\u00e7 \u00ebsht\u00eb Agile, DevOps p\u00ebrfshin disiplina t\u00eb shumta. Por shumica do t\u00eb bien dakord me k\u00ebt\u00eb p\u00ebrkufizim: DevOps \u00ebsht\u00eb nj\u00eb metod\u00eb, ose cikli i jet\u00ebs, i zhvillimit t\u00eb softuerit, parimi kryesor i t\u00eb cilit \u00ebsht\u00eb krijimi i nj\u00eb kulture ku zhvilluesit dhe punonj\u00ebsit e tjer\u00eb jan\u00eb \"n\u00eb t\u00eb nj\u00ebjt\u00ebn wavelength\", puna manuale \u00ebsht\u00eb automatizuar, secili merret me at\u00eb q\u00eb din\u00eb m\u00eb s\u00eb miri, rritet frekuenca e dor\u00ebzimeve, p\u00ebrmir\u00ebsohet produktiviteti dhe rritet fleksibiliteti.<\/p>\n

<\/p>\n

Dhe, ndon\u00ebse vet\u00ebm mjetet nuk mjaftojn\u00eb p\u00ebr t\u00eb krijuar nj\u00eb ambient DevOps, ato jan\u00eb thelb\u00ebsore. Mjeti m\u00eb i r\u00ebnd\u00ebsish\u00ebm \u00ebsht\u00eb integrimi dhe dor\u00ebzimi i vazhduesh\u00ebm (CI\/CD). N\u00eb zinxhirin p\u00ebr \u00e7do ambient ka faza t\u00eb ndryshme (p\u00ebr shembull, DEV (zhvillim), INT (integrim), TST (testim), QA (kontrolli i cil\u00ebsis\u00eb), UAT (testimi i p\u00ebrdoruesve), STG (p\u00ebrgatitje), PROD (p\u00ebrdorim)), detyrat manuale jan\u00eb automatizuar, zhvilluesit mund t\u00eb krijojn\u00eb kod t\u00eb cil\u00ebsis\u00eb s\u00eb lart\u00eb, ta dor\u00ebzojn\u00eb dhe t\u00eb ristrukturohen leht\u00ebsisht.<\/p>\n

<\/p>\n

Ky kjo sh\u00ebnim p\u00ebrshkruan se si t\u00eb krijoni nj\u00eb zinxhir DevOps n\u00eb pes\u00eb hapa, si\u00e7 tregohet n\u00eb imazhin m\u00eb posht\u00eb, duke p\u00ebrdorur mjete me kod burim t\u00eb hapur.<\/p>\n

<\/p>\n

\"Udh\u00ebzues<\/a><\/noindex><\/p>\n

<\/p>\n

Le t\u00eb kalojm\u00eb n\u00eb pun\u00eb.<\/p>\n

<\/p>\n

Hapi 1: Platforma CI\/CD<\/h3>\n

<\/p>\n

E para q\u00eb ju nevojitet \u00ebsht\u00eb nj\u00eb mjet CI\/CD. Jenkins \u00ebsht\u00eb nj\u00eb mjet CI\/CD me kod burim t\u00eb hapur, i shkruar n\u00eb Java me licenc\u00eb MIT, i cili sh\u00ebnoi fillimin e popularizimit t\u00eb l\u00ebvizjes DevOps dhe q\u00eb u b\u00eb de-fakto standardi p\u00ebr CICD.<\/p>\n

<\/p>\n

Por \u00e7far\u00eb \u00ebsht\u00eb Jenkins? Imagjinoni se keni nj\u00eb telekomand\u00eb magjike p\u00ebr sh\u00ebrbime dhe mjete t\u00eb ndryshme. Vet\u00ebm si nj\u00eb mjet CI\/CD, si Jenkins, \u00ebsht\u00eb i pamjaftuesh\u00ebm, por me mjete dhe sh\u00ebrbime t\u00eb ndryshme, b\u00ebhet gjith\u00ebfuqish\u00ebm.<\/p>\n

<\/p>\n

P\u00ebrve\u00e7 Jenkins, ekzistojn\u00eb shum\u00eb mjete t\u00eb tjera me kod burim t\u00eb hapur, zgjidhni cilindo. <\/p>\n

<\/p>\n

\"Udh\u00ebzues<\/a><\/noindex><\/p>\n

<\/p>\n

Ja si duket procesi DevOps me nj\u00eb mjet CI\/CD<\/p>\n

<\/p>\n

\"Udh\u00ebzues<\/a><\/noindex><\/p>\n

<\/p>\n

Keni nj\u00eb mjet CI\/CD n\u00eb localhost, por p\u00ebr momentin nuk keni shum\u00eb p\u00ebr t\u00eb b\u00ebr\u00eb. Le t\u00eb kalojm\u00eb n\u00eb hapat e tjer\u00eb.<\/p>\n

<\/p>\n

Hapi 2: menaxhimi i versioneve<\/h3>\n

<\/p>\n

M\u00ebnyra m\u00eb e mir\u00eb (dhe ndoshta m\u00eb e leht\u00eb) p\u00ebr t\u00eb provuar magjin\u00eb e mjetit CI\/CD \u00ebsht\u00eb t'i integrosh me nj\u00eb mjet t\u00eb menaxhimit t\u00eb versioneve (source control management, SCM). Pse \u00ebsht\u00eb e nevojshme menaxhimi i versioneve? Supozoni se po krijoni nj\u00eb aplikacion. E shkruani at\u00eb n\u00eb Java, Python, C++, Go, Ruby, JavaScript ose n\u00eb \u00e7do gjuh\u00eb tjet\u00ebr, t\u00eb cilat jan\u00eb t\u00eb shumta. Ajo q\u00eb shkruani quhet kod burimor. N\u00eb fillim, sidomos n\u00ebse punoni vet\u00ebm, mund ta ruani gjith\u00e7ka n\u00eb nj\u00eb katalog lokal. Por kur projekti shtrihet dhe m\u00eb shum\u00eb njer\u00ebz i bashkohen, ju nevojitet nj\u00eb m\u00ebnyr\u00eb p\u00ebr t\u00eb ndar\u00eb ndryshimet n\u00eb kod, duke shmangur konfliktet gjat\u00eb bashkimeve. Gjithashtu, ju nevojitet nj\u00eb m\u00ebnyr\u00eb p\u00ebr t\u00eb rikuperuar versionet e m\u00ebparshme pa p\u00ebrdorimin e kopjeve rezerv\u00eb dhe metod\u00ebs s\u00eb kopjim-ngjitjes p\u00ebr skedar\u00ebt me kod.<\/p>\n

<\/p>\n

Dhe k\u00ebtu SCM \u00ebsht\u00eb i paz\u00ebvend\u00ebsuesh\u00ebm. SCM ruan kodin n\u00eb depo, menaxhon versionet e tij dhe e koordinon at\u00eb mes zhvilluesve.<\/p>\n

<\/p>\n

Ka shum\u00eb mjete SCM, por standardi de-fakto me merita \u00ebsht\u00eb Git. Un\u00eb rekomandoj ta p\u00ebrdorni at\u00eb, por ka edhe mund\u00ebsi t\u00eb tjera.<\/p>\n

<\/p>\n

\"Udh\u00ebzues<\/p>\n

<\/p>\n

K\u00ebtu \u00ebsht\u00eb si duket pipeline-i DevOps pas shtimit t\u00eb SCM.<\/p>\n

<\/p>\n

\"Udh\u00ebzues<\/a><\/noindex><\/p>\n

<\/p>\n

Instrumenti CI\/CD mund t\u00eb automatizoj\u00eb ngarkimin dhe shkarkimin e kodeve burimore dhe bashk\u00ebpunimin n\u00eb ekip. Shum\u00eb mir\u00eb? Por si ta kthejm\u00eb k\u00ebt\u00eb n\u00eb nj\u00eb aplikacion funksional, t\u00eb preferuar nga miliarda p\u00ebrdorues?<\/p>\n

<\/p>\n

Hapi 3: instrumenti i automatizimit t\u00eb nd\u00ebrtimit<\/h3>\n

<\/p>\n

Gjith\u00e7ka po shkon sipas planit. Mund t\u00eb shkarkoni kodin dhe t\u00eb regjistroni ndryshimet n\u00eb sistemin e kontrollit t\u00eb versioneve, si edhe t\u00eb ftoni miq p\u00ebr t\u00eb punuar me ju. Por ende nuk keni aplikacion. P\u00ebr ta b\u00ebr\u00eb k\u00ebt\u00eb nj\u00eb aplikacion web, duhet ta kompilon dhe ta vendosni n\u00eb nj\u00eb paket\u00eb p\u00ebr shp\u00ebrndarje ose ta aktivizoni si nj\u00eb skedar ekzekutiv. (Gjuha e programimit t\u00eb interpretuar, si JavaScript ose PHP, nuk ka nevoj\u00eb p\u00ebr kompilim.)<\/p>\n

<\/p>\n

P\u00ebrdorni instrumentin e automatizimit t\u00eb nd\u00ebrtimit. \u00c7far\u00ebdo instrumenti q\u00eb t\u00eb zgjidhni, ai do t\u00eb ndihmoj\u00eb n\u00eb nd\u00ebrtimin e kodit n\u00eb formatin e duhur dhe n\u00eb automatizimin e pastrimit, kompilimit, testimit dhe shp\u00ebrndarjes. Ka lloje t\u00eb ndryshme t\u00eb mjeteve t\u00eb nd\u00ebrtimit n\u00eb var\u00ebsi t\u00eb gjuh\u00ebs, por zakonisht p\u00ebrdoren k\u00ebto mund\u00ebsi me kod t\u00eb hapur.<\/p>\n

<\/p>\n

\"Udh\u00ebzues<\/p>\n

<\/p>\n

Shk\u00eblqyesh\u00ebm! Tani do t\u00eb vendosim skedar\u00ebt e konfigurimit t\u00eb instrumentit t\u00eb automatizimit t\u00eb nd\u00ebrtimit n\u00eb sistemin e kontrollit t\u00eb versioneve, n\u00eb m\u00ebnyr\u00eb q\u00eb instrumenti CI\/CD t'i ndihmoj\u00eb ata.<\/p>\n

<\/p>\n

\"Udh\u00ebzues<\/a><\/noindex><\/p>\n

<\/p>\n

Duket se gjith\u00e7ka \u00ebsht\u00eb n\u00eb rregull. Por ku duhet ta publikojm\u00eb tani t\u00eb gjith\u00eb k\u00ebt\u00eb?<\/p>\n

<\/p>\n

Hapi 4: serveri i aplikacioneve web<\/h3>\n

<\/p>\n

Pra, keni nj\u00eb skedh\u00eb t\u00eb paketuar q\u00eb mund t\u00eb ekzekutohet ose t\u00eb publikohet. P\u00ebr ta b\u00ebr\u00eb aplikacionin t\u00eb dobish\u00ebm, duhet t\u00eb ket\u00eb ndonj\u00eb sh\u00ebrbim ose nd\u00ebrfaqe, por duhet ta vendosni diku t\u00eb gjith\u00eb k\u00ebt\u00eb.<\/p>\n

<\/p>\n

Aplikacioni web mund t\u00eb vendoset n\u00eb serverin e aplikacioneve web. Serveri i aplikacioneve ofron nj\u00eb ambient ku mund t\u00eb ekzekutohet logjika programore nga paketa, t\u00eb realizohet vizualizimi i nd\u00ebrfaqes dhe t\u00eb hapen sh\u00ebrbime web p\u00ebrmes soketeve. Ju nevojitet nj\u00eb server HTTP dhe disa ambiente t\u00eb tjera (si virtual machine, p\u00ebr shembull) p\u00ebr t\u00eb instaluar serverin e aplikacioneve. Deri tani le t\u00eb supozojm\u00eb se jeni duke e menaxhuar k\u00ebt\u00eb n\u00eb proces (ndon\u00ebse do t\u00eb flas p\u00ebr kontejner\u00ebt m\u00eb posht\u00eb).<\/p>\n

<\/p>\n

Ka disa server\u00eb t\u00eb hapur aplikacionesh web.<\/p>\n

<\/p>\n

\"Udh\u00ebzues<\/a><\/noindex><\/p>\n

<\/p>\n

Kemi krijuar pothuajse nj\u00eb zinxhir funksional DevOps. Pun\u00eb e shk\u00eblqyer!<\/p>\n

<\/p>\n

\"Udh\u00ebzues<\/a><\/noindex><\/p>\n

<\/p>\n

N\u00eb parim, k\u00ebtu mund t\u00eb ndaleni, m\u00eb pas do t\u00eb krijoni vet\u00eb, por \u00ebsht\u00eb ende e vyer t\u00eb flasim p\u00ebr cil\u00ebsin\u00eb e kodit.<\/p>\n

<\/p>\n

Hapi 5: Mbulimi i provimeve<\/h3>\n

<\/p>\n

Testimi k\u00ebrkon shum\u00eb koh\u00eb dhe p\u00ebrpjekje, por \u00ebsht\u00eb m\u00eb mir\u00eb t\u00eb identifikosh menj\u00ebher\u00eb gabimet dhe t\u00eb p\u00ebrmir\u00ebsosh kodin p\u00ebr t\u00eb k\u00ebnaqur p\u00ebrdoruesit p\u00ebrfundimtar\u00eb. P\u00ebr k\u00ebt\u00eb q\u00ebllim ka shum\u00eb mjete t\u00eb hapura q\u00eb jo vet\u00ebm q\u00eb testojn\u00eb kodin, por edhe ofrojn\u00eb k\u00ebshilla se si ta p\u00ebrmir\u00ebsosh at\u00eb. Shumica e mjeteve CI\/CD mund t\u00eb lidhen me k\u00ebto mjete dhe t\u00eb automatizojn\u00eb procesin.<\/p>\n

<\/p>\n

Testimi \u00ebsht\u00eb i ndar\u00eb n\u00eb dy pjes\u00eb: kornizat e testimit p\u00ebr t\u00eb shkruar dhe ekzekutuar teste, dhe mjetet me sugjerime p\u00ebr p\u00ebrmir\u00ebsimin e cil\u00ebsis\u00eb s\u00eb kodit.<\/p>\n

<\/p>\n

Kornizat e testimit<\/h3>\n

<\/p>\n

\"Udh\u00ebzues<\/a><\/noindex><\/p>\n

<\/p>\n

Mjetet me sugjerime p\u00ebr cil\u00ebsin\u00eb<\/p>\n

<\/p>\n

\"Udh\u00ebzues<\/a><\/noindex><\/p>\n

<\/p>\n

Shumica e k\u00ebtyre mjeteve dhe kornizave jan\u00eb shkruar p\u00ebr Java, Python dhe JavaScript, pasi C++ dhe C# jan\u00eb pron\u00ebsor\u00eb (megjith\u00ebse GCC ka kod t\u00eb hapur).<\/p>\n

<\/p>\n

Ne kemi aplikuar mjetet e mbulimit t\u00eb testeve, dhe tani pipeline-i DevOps duhet t\u00eb duket si\u00e7 \u00ebsht\u00eb ilustruar n\u00eb fillim t\u00eb udh\u00ebzimit.<\/p>\n

<\/p>\n

Hapat shtes\u00eb<\/h2>\n

<\/p>\n

Kontejner\u00ebt<\/h3>\n

<\/p>\n

Si\u00e7 kam th\u00ebn\u00eb m\u00eb par\u00eb, serveri i aplikacioneve mund t\u00eb vendoset n\u00eb nj\u00eb makin\u00eb virtuale ose server, por kontejner\u00ebt jan\u00eb m\u00eb t\u00eb njohur.<\/p>\n

<\/p>\n

\u00c7far\u00eb jan\u00eb kontejner\u00ebt<\/a><\/noindex>? \u0412\u043a\u0440\u0430\u0442\u0446\u0435, \u0432 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u043e\u0439 \u043c\u0430\u0448\u0438\u043d\u0435 \u043e\u043f\u0435\u0440\u0430\u0446\u0438\u043e\u043d\u043d\u0430\u044f \u0441\u0438\u0441\u0442\u0435\u043c\u0430 \u0447\u0430\u0449\u0435 \u0432\u0441\u0435\u0433\u043e \u0437\u0430\u043d\u0438\u043c\u0430\u0435\u0442 \u0431\u043e\u043b\u044c\u0448\u0435 \u043c\u0435\u0441\u0442\u0430, \u0447\u0435\u043c \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0435, \u0430 \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u0443 \u043e\u0431\u044b\u0447\u043d\u043e \u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u043e \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u0438\u0445 \u0431\u0438\u0431\u043b\u0438\u043e\u0442\u0435\u043a \u0438 \u043a\u043e\u043d\u0444\u0438\u0433\u0443\u0440\u0430\u0446\u0438\u0438. \u0412 \u043d\u0435\u043a\u043e\u0442\u043e\u0440\u044b\u0445 \u0441\u043b\u0443\u0447\u0430\u044f\u0445 \u0431\u0435\u0437 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u044b\u0445 \u043c\u0430\u0448\u0438\u043d \u043d\u0435 \u043e\u0431\u043e\u0439\u0442\u0438\u0441\u044c, \u043d\u043e \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440 \u0432\u043c\u0435\u0449\u0430\u0435\u0442 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0435 \u0432\u043c\u0435\u0441\u0442\u0435 \u0441 \u0441\u0435\u0440\u0432\u0435\u0440\u043e\u043c \u0431\u0435\u0437 \u043b\u0438\u0448\u043d\u0438\u0445 \u0437\u0430\u0442\u0440\u0430\u0442.<\/p>\n

<\/p>\n

P\u00ebr kontejner\u00ebt zakonisht p\u00ebrdoren Docker dhe Kubernetes, megjith\u00ebse ka edhe mund\u00ebsi t\u00eb tjera.<\/p>\n

<\/p>\n

\"Udh\u00ebzues<\/a><\/noindex><\/p>\n

<\/p>\n

Lexoni artikujt rreth Docker dhe Kubernetes n\u00eb Opensource.com<\/a><\/noindex>:<\/p>\n

<\/p>\n