{"id":75526,"date":"2020-03-26T19:42:18","date_gmt":"2020-03-26T17:42:18","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/kto-takoj-devops-i-kogda-on-ne-nuzhen"},"modified":"2020-03-26T19:42:18","modified_gmt":"2020-03-26T17:42:18","slug":"kto-takoj-devops-i-kogda-on-ne-nuzhen","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kto-takoj-devops-i-kogda-on-ne-nuzhen","title":{"rendered":"Kush \u00ebsht\u00eb DevOps dhe kur nuk nevojitet","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Kush \u00ebsht\u00eb DevOps dhe kur nuk nevojitet\" src=\"\/wp-content\/uploads\/2020\/03\/dd0004f6f305d9fbf44ac3ffe080157b.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nTema e DevOps ka b\u00ebr\u00eb shum\u00eb popullore k\u00ebto vitet e fundit. Shum\u00eb d\u00ebshirojn\u00eb t\u00eb bashkohen, por, si\u00e7 tregon praktika, shpesh kjo ndodh vet\u00ebm p\u00ebr shkak t\u00eb nivelit t\u00eb pagave.<\/p>\n<p>Disa e p\u00ebrmendin DevOps n\u00eb CV-n\u00eb e tyre, ndon\u00ebse nuk e kuptojn\u00eb plot\u00ebsisht termin. Disa mendojn\u00eb se duke studiuar Ansible, GitLab, Jenkins, Terraform dhe t\u00eb ngjashme (lista mund t\u00eb vazhdoj\u00eb sipas d\u00ebshir\u00ebs), ata menj\u00ebher\u00eb b\u00ebhen 'devops'. Kjo, natyrisht, nuk \u00ebsht\u00eb e v\u00ebrtet\u00eb.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nN\u00eb disa vitet e fundit, kam punuar kryesisht p\u00ebr zbatimin e DevOps n\u00eb kompani t\u00eb ndryshme. Para k\u00ebsaj, kam punuar p\u00ebr m\u00eb shum\u00eb se 20 vjet n\u00eb pozita nga administrator sistemi deri te drejtori IT. Tani jam DevOps Lead Engineer n\u00eb Playgendary. <\/p>\n<h3>Kush \u00ebsht\u00eb DevOps<\/h3>\n<p>\nIdeja p\u00ebr t\u00eb shkruar k\u00ebt\u00eb artikull lindi pas nj\u00eb pyetjeje tjet\u00ebr: 'kush \u00ebsht\u00eb DevOps?'. Ende nuk ka nj\u00eb term t\u00eb konsoliduar p\u00ebr at\u00eb ose k\u00eb do t\u00eb thot\u00eb. Disa p\u00ebrgjigje tashm\u00eb ekzistojn\u00eb n\u00eb k\u00ebt\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/youtu.be\/hlFDMWrkhoI\">video<\/a><\/noindex>. Fillimisht do t\u00eb nxjerr thelb\u00ebsore nga ai, pastaj do t\u00eb ndaj v\u00ebzhgimet dhe mendimet e mia.<\/p>\n<p>DevOps nuk \u00ebsht\u00eb nj\u00eb specialist q\u00eb mund t\u00eb angazhohet, nuk \u00ebsht\u00eb nj\u00eb grup mjetesh, as nj\u00eb departament zhvilluesish dhe inxhinier\u00ebsh.<\/p>\n<blockquote><p>DevOps \u00ebsht\u00eb nj\u00eb filozofi dhe metodologji.<\/p><\/blockquote>\n<p>\nMe fjal\u00eb t\u00eb tjera, \u00ebsht\u00eb nj\u00eb grup praktikash q\u00eb ndihmojn\u00eb n\u00eb nd\u00ebrveprimin e zhvilluesve me administrator\u00ebt e sistemeve. Pra, lidh dhe integrohet proceset e pun\u00ebs me nj\u00ebra-tjetr\u00ebn.<\/p>\n<p>Me ardhjen e DevOps, struktura dhe rolet e specialist\u00ebve mbeten t\u00eb nj\u00ebjta (ka zhvillues, ka inxhinier\u00eb), por rregullat e nd\u00ebrveprimit kan\u00eb ndryshuar. Kufijt\u00eb midis departamenteve jan\u00eb zbehur.<\/p>\n<p>Q\u00ebllimet e DevOps mund t\u00eb p\u00ebrshkruhen me tre pika: <\/p>\n<ul>\n<li>Softi duhet t\u00eb p\u00ebrdit\u00ebsohet rregullisht.<\/li>\n<li>Softi duhet t\u00eb zhvillohet shpejt.<\/li>\n<li>Softi duhet t\u00eb vendoset leht\u00eb dhe brenda nj\u00eb kohe t\u00eb shkurt\u00ebr.<\/li>\n<\/ul>\n<p>\nDevOps nuk ka nj\u00eb mjet t\u00eb vet\u00ebm. T\u00eb konfiguroni, instaloni dhe m\u00ebsoni disa produkte - nuk do t\u00eb thot\u00eb q\u00eb n\u00eb kompani ka DevOps. Ekzistojn\u00eb shum\u00eb mjete dhe t\u00eb gjitha p\u00ebrdoren n\u00eb faza t\u00eb ndryshme, por sh\u00ebrbejn\u00eb nj\u00eb q\u00ebllimi t\u00eb p\u00ebrbashk\u00ebt.<\/p>\n<p><img decoding=\"async\" alt=\"Kush \u00ebsht\u00eb DevOps dhe kur nuk nevojitet\" src=\"\/wp-content\/uploads\/2020\/03\/4f2d8b6dac21205bf5e3ab7fa283da12.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Dhe kjo \u00ebsht\u00eb vet\u00ebm nj\u00eb pjes\u00eb e mjeteve DevOps<\/i><\/p>\n<p>Q\u00eb prej m\u00eb shum\u00eb se 2 vjet\u00ebsh, po intervistoj njer\u00ebz p\u00ebr pozita DevOps-inxhinier dhe kam kuptuar se sa e r\u00ebnd\u00ebsishme \u00ebsht\u00eb t\u00eb kuptohet qart\u00eb thelbi i termit. Kam grumbulluar p\u00ebrvoj\u00eb specifike, v\u00ebzhgime dhe mendime q\u00eb dua t'i ndaj.<\/p>\n<p>Nga p\u00ebrvoja e intervistave shoh nj\u00eb pamje t\u00eb till\u00eb: <b>specialist\u00ebt q\u00eb e konsiderojn\u00eb DevOps si nj\u00eb pozicion zakonisht kan\u00eb keqkuptime me koleg\u00ebt<\/b>.<\/p>\n<p>Ishte nj\u00eb shembull i qart\u00eb. N\u00eb intervist\u00eb erdhi nj\u00eb djalosh me shum\u00eb fjal\u00eb t\u00eb men\u00e7ura n\u00eb CV-n\u00eb e tij. N\u00eb tri vendet e fundit t\u00eb pun\u00ebs kishte punuar nga 5-6 muaj. Nga dy startup-e kishte dal\u00eb, sepse \u201enuk fluturoi\u201c. Nd\u00ebrsa p\u00ebr kompanin\u00eb e tret\u00eb tha se askush nuk e kupton atje: zhvilluesit shkruajn\u00eb kod p\u00ebr Windows, nd\u00ebrsa drejtori e detyron t\u00eb \u201emb\u00ebshtjell\u00eb\u201c at\u00eb kod n\u00eb Docker t\u00eb zakonsh\u00ebm dhe ta integroj\u00eb n\u00eb pipeline-in CI\/CD. Djali tregoi shum\u00eb gj\u00ebra negative p\u00ebr vendin e tij aktual t\u00eb pun\u00ebs dhe koleg\u00ebt e tij \u2014 do t\u00eb doja t\u00eb p\u00ebrgjigjesha: \u201ePra ti nuk do ta shes\u00ebsh elefantin.\u201c<\/p>\n<p>Pastaj i b\u00ebra nj\u00eb pyetje, e cila n\u00eb list\u00ebn time \u00ebsht\u00eb nj\u00eb nga t\u00eb parat p\u00ebr \u00e7do kandidat.<\/p>\n<p>\u2014 \u00c7far\u00eb do t\u00eb thot\u00eb p\u00ebr ty personalisht DevOps?<br \/>\n\u2014 N\u00eb p\u00ebrgjith\u00ebsi apo si e perceptoj un\u00eb?<\/p>\n<p>M\u00eb interesonte mendimi i tij personal. Ai e dinte teorin\u00eb dhe origjin\u00ebn e termit, por ishte kategorikisht i pajtuar me ta. Ai mendonte se DevOps \u00ebsht\u00eb nj\u00eb pozite. K\u00ebtu fshihet rr\u00ebnja e problemeve t\u00eb tij, ashtu si dhe t\u00eb specialist\u00ebve t\u00eb tjer\u00eb me t\u00eb nj\u00ebjtin mendim.<\/p>\n<p>Pun\u00ebdh\u00ebn\u00ebsit, duke d\u00ebgjuar p\u00ebr \u201emagjin\u00eb DevOps\u201c, duan t\u00eb gjejn\u00eb njeriun q\u00eb do t\u00eb vij\u00eb dhe do t\u00eb krijoj\u00eb k\u00ebt\u00eb \u201emagji\u201c. Nd\u00ebrsa aplikant\u00ebt nga kategoria \u201eDevOps \u00ebsht\u00eb nj\u00eb pozit\u00eb\u201c nuk kuptojn\u00eb se me k\u00ebt\u00eb qasje nuk do t\u00eb mund t'i p\u00ebrmbushin pritshm\u00ebrit\u00eb. Dhe, n\u00eb p\u00ebrgjith\u00ebsi, shkruan n\u00eb CV-n\u00eb e tij DevOps, sepse \u00ebsht\u00eb nj\u00eb trend dhe paguhet shum\u00eb p\u00ebr k\u00ebt\u00eb. <\/p>\n<h3>Metodologjia dhe filozofia DevOps<\/h3>\n<p>\nMetodologjia mund t\u00eb jet\u00eb teorike dhe praktike. N\u00eb rastin ton\u00eb \u2014 e dyta. Si\u00e7 e p\u00ebrmenda m\u00eb lart, DevOps \u00ebsht\u00eb nj\u00eb grup praktikash dhe strategjish q\u00eb aplikohen p\u00ebr t\u00eb arritur q\u00ebllimet e deklaruara. Dhe n\u00eb \u00e7do rast, n\u00eb var\u00ebsi t\u00eb proceseve t\u00eb biznesit t\u00eb kompanis\u00eb, ajo mund t\u00eb diferencohet ndjesh\u00ebm. \u00c7far\u00eb nuk e b\u00ebn m\u00eb t\u00eb mir\u00eb ose m\u00eb t\u00eb keqe.<\/p>\n<blockquote><p>Metodologjia DevOps \u00ebsht\u00eb vet\u00ebm nj\u00eb mjet p\u00ebr t\u00eb arritur q\u00ebllimet e vendosura.<\/p><\/blockquote>\n<p>\nTani p\u00ebr at\u00eb q\u00eb \u00ebsht\u00eb filozofia DevOps. Dhe kjo, ndoshta, \u00ebsht\u00eb pyetja m\u00eb e v\u00ebshtir\u00eb.<\/p>\n<p>T\u00eb formuloj\u00eb nj\u00eb p\u00ebrgjigje t\u00eb shkurt\u00ebr dhe t\u00eb qart\u00eb \u00ebsht\u00eb mjaft e v\u00ebshtir\u00eb, sepse ajo ende nuk \u00ebsht\u00eb formalisht e p\u00ebrcaktuar. Dhe pasi ndjek\u00ebsit e filozofis\u00eb DevOps p\u00ebrdorin m\u00eb shum\u00eb praktik\u00ebn \u2014 nuk kan\u00eb koh\u00eb p\u00ebr filozofizime. Megjithat\u00eb, ky \u00ebsht\u00eb nj\u00eb proces shum\u00eb i r\u00ebnd\u00ebsish\u00ebm. P\u00ebr m\u00eb tep\u00ebr, ai lidhet drejtp\u00ebrdrejt me aktivitetin inxhinierik. Ka madje nj\u00eb fush\u00eb t\u00eb specializuar t\u00eb njohurive \u2014 <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/%D0%A4%D0%B8%D0%BB%D0%BE%D1%81%D0%BE%D1%84%D0%B8%D1%8F_%D1%82%D0%B5%D1%85%D0%BD%D0%B8%D0%BA%D0%B8\">filozofia e teknologjive<\/a><\/noindex>.<\/p>\n<p>N\u00eb universitetin tim nuk kishte nj\u00eb l\u00ebnd\u00eb t\u00eb till\u00eb, prandaj u detyrova t\u00eb studioj gjith\u00e7ka vet\u00eb me materialet q\u00eb mund t\u00eb gjeja n\u00eb vitet '90. Tema nuk \u00ebsht\u00eb e obligueshme p\u00ebr arsimimin inxhinierik, andaj edhe mungon formalizimi i p\u00ebrgjigjes. Por ata njer\u00ebz q\u00eb jan\u00eb angazhuar seriozisht n\u00eb DevOps fillojn\u00eb t\u00eb ndiejn\u00eb nj\u00ebfar\u00eb \"shpirti\" ose \"nj\u00eb gjith\u00ebp\u00ebrfshirshm\u00ebri t\u00eb paq\u00ebnderprer\u00eb\" t\u00eb gjith\u00eb proceseve t\u00eb kompanis\u00eb.<\/p>\n<p>Me p\u00ebrvoj\u00ebn time kam p\u00ebrpjekur t\u00eb formalizoj disa \"postulata\" t\u00eb k\u00ebsaj filozofie. Nga kjo doli:<\/p>\n<ul>\n<li>DevOps nuk \u00ebsht\u00eb di\u00e7ka e pavarur q\u00eb mund t\u00eb ve\u00e7ohet si nj\u00eb drejtim njohurish ose aktiviteti.<\/li>\n<li>T\u00eb gjith\u00eb punonj\u00ebsit e kompanis\u00eb duhet t\u00eb udh\u00ebheqin nga metodologjia DevOps gjat\u00eb planifikimit t\u00eb aktiviteteve t\u00eb tyre.<\/li>\n<li>DevOps prek t\u00eb gjith\u00eb proceset brenda kompanis\u00eb.<\/li>\n<li>DevOps ekziston p\u00ebr t\u00eb reduktuar koh\u00ebn e shpenzuar n\u00eb \u00e7do proces brenda kompanis\u00eb p\u00ebr t\u00eb siguruar zhvillimin e sh\u00ebrbimeve t\u00eb saj dhe maksimumin e komoditetit p\u00ebr klient\u00ebt.<\/li>\n<li>DevOps, n\u00eb gjuh\u00ebn moderne, \u00ebsht\u00eb pozita proaktive e \u00e7do punonj\u00ebsi t\u00eb kompanis\u00eb, e orientuar drejt reduktimit t\u00eb kostove t\u00eb koh\u00ebs dhe p\u00ebrmir\u00ebsimit t\u00eb cil\u00ebsis\u00eb s\u00eb produkteve IT q\u00eb na rrethojn\u00eb.<\/li>\n<\/ul>\n<p>\nMendoj se \"postulatet\" e mia jan\u00eb nj\u00eb tem\u00eb e ve\u00e7ant\u00eb p\u00ebr diskutim. Por tani ka nj\u00eb pik\u00eb referimi.<\/p>\n<h3>\u00c7far\u00eb b\u00ebn DevOps<\/h3>\n<p>\nFjal\u00eb ky\u00e7e k\u00ebtu \u00ebsht\u00eb \u2013 komunikimet. Ka shum\u00eb komunikime, iniciatori i t\u00eb cilave duhet t\u00eb jet\u00eb pik\u00ebrisht inxhinieri DevOps. Pse k\u00ebshtu? Sepse kjo \u00ebsht\u00eb nj\u00eb filozofi dhe metodologji, dhe pastaj jan\u00eb njohurit\u00eb inxhinierike.<\/p>\n<p>Nuk mund t\u00eb flas me 100% siguri p\u00ebr tregun per\u00ebndimor t\u00eb pun\u00ebs. Por p\u00ebr tregun DevOps n\u00eb Rusi di nj\u00eb sasi t\u00eb madhe. P\u00ebrve\u00e7 qindra intervistave, gjat\u00eb nj\u00eb viti e gjysm\u00eb kam marr\u00eb pjes\u00eb n\u00eb nj\u00ebqind presales teknike p\u00ebr sh\u00ebrbimin \"Zbatimi i DevOps\" p\u00ebr kompani t\u00eb m\u00ebdha ruse dhe banka.<\/p>\n<p>N\u00eb Rusi, DevOps \u00ebsht\u00eb akoma nj\u00eb tem\u00eb shum\u00eb e re, por \u00ebsht\u00eb duke u b\u00ebr\u00eb trend. Sipas t\u00eb dh\u00ebnave q\u00eb kam, vet\u00ebm n\u00eb Mosk\u00eb, mungesa e specialist\u00ebve t\u00eb till\u00eb p\u00ebr vitin 2019 ka qen\u00eb m\u00eb shum\u00eb se 1000 njer\u00ebz. Dhe fjala Kubernetes p\u00ebr pun\u00ebdh\u00ebn\u00ebsit \u00ebsht\u00eb gati si nj\u00eb p\u00eblhur\u00eb e kuqe p\u00ebr nj\u00eb bull. Adhept\u00ebt e k\u00ebtij instrumenti jan\u00eb t\u00eb gatsh\u00ebm ta p\u00ebrdorin at\u00eb madje edhe n\u00eb raste kur nuk \u00ebsht\u00eb e nevojshme dhe nuk \u00ebsht\u00eb ekonomikisht e dobishme. Pun\u00ebdh\u00ebn\u00ebsi nuk kupton gjithmon\u00eb n\u00eb cilat raste \u00ebsht\u00eb m\u00eb e arsyeshme t\u00eb p\u00ebrdoret, nd\u00ebrsa me nj\u00eb implementim t\u00eb duhur, kostot e klasterit Kubernetes jan\u00eb 2-3 her\u00eb m\u00eb t\u00eb larta se ato p\u00ebr implementimin e nj\u00eb aplikacioni sipas nj\u00eb skeme t\u00eb zakonshme klasteri. P\u00ebrdoreni atje ku \u00ebsht\u00eb me t\u00eb v\u00ebrtet\u00eb e nevojshme. <\/p>\n<p><img decoding=\"async\" alt=\"Kush \u00ebsht\u00eb DevOps dhe kur nuk nevojitet\" src=\"\/wp-content\/uploads\/2020\/03\/7f8a2a30abc7a2cd59b49083c7011211.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nZbatimi i DevOps nga pik\u00ebpamja financiare \u00ebsht\u00eb i shtrenjt\u00eb. Dhe \u00ebsht\u00eb i arsyesh\u00ebm vet\u00ebm aty ku sjell p\u00ebrfitime ekonomike n\u00eb fusha t\u00eb tjera, jo p\u00ebr vete.<\/p>\n<p>Inxhinier\u00ebt e DevOps, n\u00eb fakt, jan\u00eb pionier\u00eb \u2014 ata duhet t\u00eb jen\u00eb t\u00eb par\u00ebt q\u00eb e zbatonin k\u00ebt\u00eb metodologji n\u00eb kompani dhe t\u00eb ndihmojn\u00eb n\u00eb nd\u00ebrtimin e proceseve. Q\u00eb kjo t\u00eb ket\u00eb sukses, specialisti duhet t\u00eb bashk\u00ebpunoj\u00eb vazhdimisht me punonj\u00ebsit dhe koleg\u00ebt n\u00eb t\u00eb gjitha nivelet. Si\u00e7 thosh\u00eb zakonisht, n\u00eb procesin e zbatimit t\u00eb DevOps duhet t\u00eb p\u00ebrfshihen t\u00eb gjith\u00eb punonj\u00ebsit e kompanis\u00eb: nga pastruesja deri te CEO. Dhe kjo \u00ebsht\u00eb nj\u00eb kusht i domosdosh\u00ebm. N\u00ebse an\u00ebtari m\u00eb i ri i ekipit nuk do t\u00eb dij\u00eb dhe kuptoj\u00eb \u00e7far\u00eb \u00ebsht\u00eb DevOps dhe pse realizohen veprime t\u00eb caktuara organizative, zbatimi i suksessh\u00ebm nuk do t\u00eb ndodh\u00eb.<\/p>\n<p>P\u00ebr m\u00eb tep\u00ebr, inxhinier\u00ebt e DevOps duhet t'i p\u00ebrdorin her\u00eb pas here burimet administrative. P\u00ebr shembull, p\u00ebr t\u00eb p\u00ebrballuar \"rezistenc\u00ebn e mjedisit\" \u2014 kur ekipi nuk \u00ebsht\u00eb i gatsh\u00ebm t\u00eb pranoj\u00eb instrumentet dhe metodologjin\u00eb DevOps. <\/p>\n<p>Zhvilluesi duhet t\u00eb shkruaj vet\u00ebm kodin dhe testet. P\u00ebr k\u00ebt\u00eb, ai nuk ka nevoj\u00eb p\u00ebr nj\u00eb laptop super t\u00eb fuqish\u00ebm, n\u00eb t\u00eb cilin do t\u00eb zhvillonte dhe mbante lokalisht t\u00eb gjith\u00eb infrastruktur\u00ebn e projektit. P\u00ebr shembull, front-end developer mban n\u00eb laptopin e tij t\u00eb gjitha elementet e aplikacionit, duke p\u00ebrfshir\u00eb baz\u00ebn e t\u00eb dh\u00ebnave, emuluesin S3 (minio) dhe t\u00eb tjera. K\u00ebshtu, ai harxhon shum\u00eb koh\u00eb n\u00eb mbajtjen e k\u00ebsaj infrastrukture lokale dhe lufton vet\u00ebm me t\u00eb gjitha problemet e k\u00ebtij zgjidhjeje. N\u00eb vend q\u00eb t\u00eb zhvillonte kodin p\u00ebr frontin. T\u00eb till\u00eb njer\u00ebz mund t\u00eb ken\u00eb nj\u00eb rezistenc\u00eb t\u00eb madhe ndaj \u00e7do ndryshimi.<\/p>\n<p>Por otro lado, hay equipos que, al contrario, est\u00e1n contentos con la implementaci\u00f3n de nuevas herramientas y m\u00e9todos, y participan activamente en este proceso. Aunque incluso en este caso, la comunicaci\u00f3n entre el ingeniero de DevOps y el equipo no se ha cancelado.<\/p>\n<h3>Cuando DevOps no es necesario<\/h3>\n<p>\nHay situaciones en las que DevOps no es necesario. Es un hecho que se debe entender y aceptar.<\/p>\n<p>En primer lugar, esto se aplica a cualquier empresa (especialmente a las peque\u00f1as), cuando sus ganancias no dependen directamente de la presencia o ausencia de productos de TI que proporcionen servicios de informaci\u00f3n a los clientes. Y aqu\u00ed no se trata del sitio web de la empresa, ya sea una 'tarjeta de presentaci\u00f3n' est\u00e1tica o con bloques de noticias din\u00e1micas, etc.<\/p>\n<p>Se requiere DevOps cuando la satisfacci\u00f3n del cliente y su deseo de volver a acudir a usted depende de la existencia de estos servicios de informaci\u00f3n para interactuar con los clientes, de su calidad y de su direccionamiento.<\/p>\n<p>Un ejemplo destacado es un conocido banco. La empresa no tiene oficinas f\u00edsicas para clientes; el flujo de documentos se realiza por correo o mensajeros, y muchos empleados trabajan desde casa. La empresa ha dejado de ser solo un banco y, en mi opini\u00f3n, se ha convertido en una empresa de TI con avanzadas tecnolog\u00edas DevOps.<\/p>\n<p>Hay muchos otros ejemplos y conferencias que se pueden encontrar en los registros de meetups y conferencias tem\u00e1ticas. Parte de ellos los he asistido personalmente: es una experiencia muy \u00fatil para quienes desean desarrollarse en esta \u00e1rea. Aqu\u00ed hay enlaces a canales de YouTube con buenas conferencias y materiales sobre DevOps:<\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/www.youtube.com\/channel\/UCjnQreLMbpKsfJwDnHGZLxg\/featured\">DevOops<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/www.youtube.com\/channel\/UC1nDIT9thqoFSSxvLyPHF5w\/featured\">DevOpsConf<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/www.youtube.com\/user\/profyclub\/featured\">HighLoad++<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/www.youtube.com\/channel\/UCjmwHCZ-qh3ro7hHTQhqYQg\">Flant<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/www.youtube.com\/channel\/UCnvbzVff0AGuHHzxcDTtj6w\/featured\">MailRu Cloud Solution<\/a><\/noindex><\/li>\n<\/ul>\n<p>\nAhora observe su negocio y piense en lo siguiente: \u00bfcu\u00e1nto dependen su empresa y sus ganancias de los productos de TI que facilitan la interacci\u00f3n con el cliente? <\/p>\n<p>Si su empresa vende pescado en una peque\u00f1a tienda y el \u00fanico producto de TI son dos configuraciones de 1C: Enterprise (Contabilidad y UHN), probablemente no tenga sentido hablar de DevOps.<\/p>\n<p>Sin embargo, si trabaja en una gran empresa comercial y de producci\u00f3n (por ejemplo, produce escopetas de caza), entonces deber\u00eda reflexionar. Puede tomar la iniciativa y comunicar a su direcci\u00f3n las perspectivas de implementar DevOps. Y, de paso, liderar este proceso. Una postura proactiva es uno de los postulados importantes de la filosof\u00eda DevOps.<\/p>\n<blockquote><p>P\u00ebrmasat dhe volumi i xhiros financiare vjetore nuk jan\u00eb kritere thelb\u00ebsore p\u00ebr t\u00eb p\u00ebrcaktuar n\u00ebse kompanis\u00eb suaj i nevojitet DevOps.<\/p><\/blockquote>\n<p>\nImagjinoni nj\u00eb industri t\u00eb madhe q\u00eb nuk interakton drejtp\u00ebrdrejt me klient\u00ebt. P\u00ebr shembull, disa prodhues automjetesh dhe kompani t\u00eb prodhimit t\u00eb automjeteve. Tani nuk jam i sigurt, por nga p\u00ebrvoja ime e kaluar, p\u00ebr shum\u00eb vite, e gjith\u00eb nd\u00ebrveprimi me klient\u00ebt \u00ebsht\u00eb b\u00ebr\u00eb p\u00ebrmes post\u00ebs elektronike dhe telefonit. <\/p>\n<p>Klient\u00ebt e tyre jan\u00eb nj\u00eb list\u00eb e kufizuar e tregtar\u00ebve t\u00eb automjeteve. Dhe p\u00ebr secilin \u00ebsht\u00eb caktuar nj\u00eb specialist nga prodhuesi. T\u00eb gjith\u00eb dokumentacioni i brendsh\u00ebm ndodhi p\u00ebrmes ERP SAP. Punonj\u00ebsit e brendsh\u00ebm, n\u00eb thelb, jan\u00eb klient\u00eb t\u00eb sistemit informacionit. Por menaxhimi i k\u00ebtij sistemi informacioni kryhet me mjete klasike t\u00eb menaxhimit t\u00eb sistemeve klaster. Kjo p\u00ebrjashton mund\u00ebsin\u00eb e p\u00ebrdorimit t\u00eb praktikave DevOps.<\/p>\n<p>Pra, p\u00ebrfundimi: p\u00ebr t\u00eb tilla nd\u00ebrmarrje, implementimi i DevOps nuk \u00ebsht\u00eb di\u00e7ka kritikisht t\u00eb nevojshme, n\u00ebse e kujtojm\u00eb q\u00ebllimet e metodologjis\u00eb nga fillimi i artikullit. Por nuk p\u00ebrjashtoj q\u00eb disa mjete DevOps mund t\u00eb p\u00ebrdoren nga ata sot.<\/p>\n<p>Nga ana tjet\u00ebr, ka shum\u00eb kompani t\u00eb vogla q\u00eb zhvillojn\u00eb software duke p\u00ebrdorur metodologjin\u00eb, filozofin\u00eb, praktikat dhe mjetet DevOps. Dhe mendojn\u00eb se shpenzimet p\u00ebr implementimin e DevOps jan\u00eb shpenzime q\u00eb i lejojn\u00eb atyre t\u00eb konkurrojn\u00eb efikasht\u00eb n\u00eb tregun e softwares. Shembuj t\u00eb till\u00eb kompanish mund t\u00eb shihen <noindex><a rel=\"nofollow\" href=\"https:\/\/www.youtube.com\/channel\/UCjmwHCZ-qh3ro7hHTQhqYQg\">k\u00ebtu<\/a><\/noindex>.<\/p>\n<blockquote><p>Kriteri kryesor p\u00ebr t\u00eb kuptuar n\u00ebse ju nevojitet DevOps: \u00e7far\u00eb r\u00ebnd\u00ebsie kan\u00eb produktet tuaja IT p\u00ebr kompanin\u00eb dhe klient\u00ebt.<\/p><\/blockquote>\n<p>\nN\u00ebse produkti kryesor i kompanis\u00eb, i cili sjell t\u00eb ardhura, \u00ebsht\u00eb software \u2013 ju nevojitet DevOps. Dhe nuk ka r\u00ebnd\u00ebsi n\u00ebse ju shkoni me t\u00eb v\u00ebrtet\u00eb para me produkte t\u00eb tjera. K\u00ebtu p\u00ebrfshihen gjithashtu dyqanet online ose aplikacione mobile me loj\u00ebra.<\/p>\n<p>Cdo loj\u00eb ekziston fal\u00eb financimit: t\u00eb drejtp\u00ebrdrejt ose t\u00ebrthor nga lojtar\u00ebt. N\u00eb Playgendary ne zhvillojm\u00eb loj\u00ebra mobile falas, n\u00eb krijimin e t\u00eb cilave marrin pjes\u00eb m\u00eb shum\u00eb se 200 njer\u00ebz. Si e p\u00ebrdorim DevOps?<\/p>\n<p>Po, pik\u00ebrisht ashtu si\u00e7 p\u00ebrshkruhet m\u00eb lart. Un\u00eb kam komunikim t\u00eb vazhduesh\u00ebm me zhvilluesit dhe testuesit, organizoj trajnime t\u00eb brendshme p\u00ebr metodologjin\u00eb dhe mjetet DevOps. <\/p>\n<p>Aktualisht ne po p\u00ebrdorim Jenkins si nj\u00eb mjet p\u00ebr CI\/CD pipelines p\u00ebr t\u00eb ekzekutuar t\u00eb gjitha linjat e nd\u00ebrtimit me Unity dhe p\u00ebr depozitimin e m\u00ebpassh\u00ebm n\u00eb App Store dhe Play Market. Nga seti klasik i mjeteve: <\/p>\n<ul>\n<li>Asana \u2014 p\u00ebr menaxhimin e projekteve. Kemi vendosur integrimin me Jenkins.<\/li>\n<li>Google Meet \u2014 p\u00ebr mbajtjen e videokonferencave.<\/li>\n<li>Slack \u2014 p\u00ebr komunikime dhe njoftime t\u00eb ndryshme, duke p\u00ebrfshir\u00eb njoftimet nga Jenkins.<\/li>\n<li>Atlassian Confluence \u2014 p\u00ebr dokumentimin dhe pun\u00ebn n\u00eb grup.<\/li>\n<\/ul>\n<p>\nN\u00eb planet tona afatshkurtra \u00ebsht\u00eb implementimi i analiz\u00ebs statike t\u00eb kodit me SonarQube dhe realizimi i testimit t\u00eb automatizuar UI me mjetet e Selenium n\u00eb faz\u00ebn e Integrimit t\u00eb Vazhdush\u00ebm.<\/p>\n<h3>N\u00eb p\u00ebrfundim<\/h3>\n<p>\nDua t\u00eb p\u00ebrfundoj me k\u00ebt\u00eb mendim: p\u00ebr t'u b\u00ebr\u00eb nj\u00eb inxhinier DevOps me kualifikim t\u00eb lart\u00eb, \u00ebsht\u00eb thelb\u00ebsore t\u00eb m\u00ebsosh t\u00eb komunikosh n\u00eb m\u00ebnyr\u00eb aktive me njer\u00ebzit.<\/p>\n<p>Inxhinieri DevOps \u00ebsht\u00eb nj\u00eb lojtar ekipi. Ashtu si ndryshe. Iniciativa n\u00eb komunikimin me koleg\u00ebt duhet t\u00eb vij\u00eb prej tij vet\u00eb, dhe jo n\u00ebn ndikimin e ndonj\u00eb rrethane. Specialist\u00ebt DevOps duhet t\u00eb shikojn\u00eb dhe t\u00eb ofrojn\u00eb zgjidhjen m\u00eb t\u00eb mir\u00eb p\u00ebr ekipin. <\/p>\n<p>Dhe po, implementimi i \u00e7do zgjidhjeje do t\u00eb k\u00ebrkoj\u00eb shum\u00eb diskutime dhe deri n\u00eb fund mund t\u00eb ndryshoj\u00eb krejt\u00ebsisht. Duke u zhvilluar vet\u00eb, duke ofruar dhe realizuar idet\u00eb e tij \u2014 nj\u00eb njeri i till\u00eb p\u00ebrfaq\u00ebson nj\u00eb vler\u00eb gjithnj\u00eb e m\u00eb t\u00eb madhe si p\u00ebr ekipin, ashtu edhe p\u00ebr pun\u00ebdh\u00ebn\u00ebsin. \u00c7ka, p\u00ebrfundimisht, reflektohet n\u00eb madh\u00ebsin\u00eb e shp\u00ebrblimit t\u00eb tij mujor ose n\u00eb form\u00ebn e bonuseve shtes\u00eb.<br \/>\n<br \/>Burimi: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/playgendary\/blog\/493998\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0422\u0435\u043c\u0430 DevOps \u0437\u0430 \u043f\u043e\u0441\u043b\u0435\u0434\u043d\u0438\u0435 \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u043b\u0435\u0442 \u0441\u0442\u0430\u043b\u0430 \u043e\u0447\u0435\u043d\u044c \u043f\u043e\u043f\u0443\u043b\u044f\u0440\u043d\u043e\u0439. \u041c\u043d\u043e\u0433\u0438\u0435 \u043c\u0435\u0447\u0442\u0430\u044e\u0442 \u0432 \u043d\u0435\u0435 \u0432\u043b\u0438\u0442\u044c\u0441\u044f, \u043d\u043e, \u043a\u0430\u043a \u043f\u043e\u043a\u0430\u0437\u044b\u0432\u0430\u0435\u0442 \u043f\u0440\u0430\u043a\u0442\u0438\u043a\u0430, \u0447\u0430\u0441\u0442\u043e \u0442\u043e\u043b\u044c\u043a\u043e \u0438\u0437-\u0437\u0430 \u0443\u0440\u043e\u0432\u043d\u044f \u0437\u0430\u0440\u043f\u043b\u0430\u0442. \u041d\u0435\u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0443\u043a\u0430\u0437\u044b\u0432\u0430\u044e\u0442 \u0432 \u0441\u0432\u043e\u0435\u043c \u0440\u0435\u0437\u044e\u043c\u0435 DevOps, \u0445\u043e\u0442\u044f \u043d\u0435 \u0432\u0441\u0435\u0433\u0434\u0430 \u0437\u043d\u0430\u044e\u0442 \u0438 \u043f\u043e\u043d\u0438\u043c\u0430\u044e\u0442 \u0441\u0443\u0442\u044c \u0442\u0435\u0440\u043c\u0438\u043d\u0430. \u041a\u0442\u043e-\u0442\u043e \u0441\u0447\u0438\u0442\u0430\u0435\u0442, \u0447\u0442\u043e \u0438\u0437\u0443\u0447\u0438\u0432 Ansible, GitLab, Jenkins, Terraform \u0438 \u0438\u043c \u043f\u043e\u0434\u043e\u0431\u043d\u044b\u0435 (\u0441\u043f\u0438\u0441\u043e\u043a \u043c\u043e\u0436\u043d\u043e \u043f\u0440\u043e\u0434\u043e\u043b\u0436\u0430\u0442\u044c \u043d\u0430 \u0441\u0432\u043e\u0439 \u0432\u043a\u0443\u0441), \u0442\u043e [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":75527,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-75526","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.2 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0422\u0435\u043c\u0430 DevOps \u0437\u0430 \u043f\u043e\u0441\u043b\u0435\u0434\u043d\u0438\u0435 \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u043b\u0435\u0442 \u0441\u0442\u0430\u043b\u0430 \u043e\u0447\u0435\u043d\u044c.\" \/>\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\/kto-takoj-devops-i-kogda-on-ne-nuzhen\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2\" \/>\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\u041a\u0442\u043e \u0442\u0430\u043a\u043e\u0439 DevOps \u0438 \u043a\u043e\u0433\u0434\u0430 \u043e\u043d \u043d\u0435 \u043d\u0443\u0436\u0435\u043d | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0422\u0435\u043c\u0430 DevOps \u0437\u0430 \u043f\u043e\u0441\u043b\u0435\u0434\u043d\u0438\u0435 \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u043b\u0435\u0442 \u0441\u0442\u0430\u043b\u0430 \u043e\u0447\u0435\u043d\u044c.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kto-takoj-devops-i-kogda-on-ne-nuzhen\" \/>\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=\"2020-03-26T17:42:18+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-03-26T17:42:18+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\udd47Kush \u00ebsht\u00eb DevOps dhe kur ai nuk \u00ebsht\u00eb i nevojsh\u00ebm | ProHoster","description":"Tema DevOps \u00ebsht\u00eb b\u00ebr\u00eb shum\u00eb e njohur vitet e fundit.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kto-takoj-devops-i-kogda-on-ne-nuzhen","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\u041a\u0442\u043e \u0442\u0430\u043a\u043e\u0439 DevOps \u0438 \u043a\u043e\u0433\u0434\u0430 \u043e\u043d \u043d\u0435 \u043d\u0443\u0436\u0435\u043d | ProHoster","og:description":"\u0422\u0435\u043c\u0430 DevOps \u0437\u0430 \u043f\u043e\u0441\u043b\u0435\u0434\u043d\u0438\u0435 \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u043b\u0435\u0442 \u0441\u0442\u0430\u043b\u0430 \u043e\u0447\u0435\u043d\u044c.","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kto-takoj-devops-i-kogda-on-ne-nuzhen","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":"2020-03-26T17:42:18+00:00","article:modified_time":"2020-03-26T17:42:18+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"75526","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":"","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":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 17:55:26","updated":"2022-09-27 16:15:47","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\/75526","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=75526"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/75526\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/75527"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=75526"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=75526"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=75526"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}