{"id":37551,"date":"2019-10-31T22:18:16","date_gmt":"2019-10-31T19:18:16","guid":{"rendered":"https:\/\/prohoster.info\/blog\/govorim-o-devops-na-ponyatnom-yazyke\/"},"modified":"2019-10-31T22:18:16","modified_gmt":"2019-10-31T19:18:16","slug":"govorim-o-devops-na-ponyatnom-yazyke","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/news\/govorim-o-devops-na-ponyatnom-yazyke","title":{"rendered":"Vorbind despre DevOps \u00eentr-o limb\u0103 accesibil\u0103","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Este greu s\u0103 apuci esen\u021ba vorbind despre DevOps? Am adunat pentru tine analogii sugestive, formule expresive \u0219i sfaturi de la exper\u021bi care te vor ajuta s\u0103 ajungi la miezul problemei chiar \u0219i f\u0103r\u0103 o preg\u0103tire tehnic\u0103. La final, un bonus \u2013 conceptul de DevOps al angaja\u021bilor Red Hat.<\/p>\n

\"Vorbind
\n
\nTermenul DevOps a ap\u0103rut acum 10 ani \u0219i a evoluat de la un hashtag pe Twitter la o mi\u0219care cultural\u0103 puternic\u0103 \u00een lumea IT, o adev\u0103rat\u0103 filozofie care \u00eencurajeaz\u0103 dezvoltatorii s\u0103 ob\u021bin\u0103 rezultate mai repede, s\u0103 experimenteze \u0219i s\u0103 progreseze prin itera\u021bii. DevOps s-a conectat indisolubil de conceptul de transformare digital\u0103. Dar, a\u0219a cum se \u00eent\u00e2mpl\u0103 adesea cu terminologia IT, \u00een decurs de un deceniu DevOps a acumulat o mul\u021bime de defini\u021bii, interpret\u0103ri \u0219i confuzii.
\n<\/a><\/noindex>
\nDe aceea, despre DevOps se aud frecvent \u00eentreb\u0103ri precum: este acela\u0219i lucru cu agile? Sau este o metodologie special\u0103? Sau este doar un alt sinonim pentru \u00abcolaborare\u00bb?<\/p>\n

DevOps include multe concepte diferite (livrare continu\u0103, integrare continu\u0103, automatizare etc.), a\u0219a c\u0103 a desprinde esen\u021ba poate fi complicat, mai ales c\u00e2nd ai o afec\u021biune pentru subiect. Totu\u0219i, aceast\u0103 abilitate este foarte util\u0103, indiferent dac\u0103 \u00eencerci s\u0103 \u00ee\u021bi comunici ideile superiorilor sau pur \u0219i simplu poveste\u0219ti despre munca ta cu cei dragi. A\u0219adar, s\u0103 l\u0103s\u0103m deoparte nuan\u021bele terminologice ale DevOps \u0219i s\u0103 ne concentr\u0103m pe imaginea de ansamblu.<\/p>\n

Ce este DevOps: 6 defini\u021bii \u0219i analogii<\/h3>\n

\nAm rugat speciali\u0219tii s\u0103 explice esen\u021ba DevOps c\u00e2t mai simplu \u0219i concis, astfel \u00eenc\u00e2t valoarea acestuia s\u0103 fie clar\u0103 pentru cititorii cu orice nivel de preg\u0103tire tehnic\u0103. \u00cen urma acestor discu\u021bii, am selectat cele mai sugestive analogii \u0219i formule expresive care \u00ee\u021bi vor ajuta s\u0103 \u00ee\u021bi construie\u0219ti povestea despre DevOps.<\/p>\n

1. DevOps \u2013 este o mi\u0219care cultural\u0103<\/h4>\n

\n\u00abDevOps este o mi\u0219care cultural\u0103, \u00een cadrul c\u0103reia ambele p\u0103r\u021bi (dezvoltatorii de software \u0219i speciali\u0219tii \u00een operarea sistemelor IT) recunosc c\u0103 software-ul nu aduce beneficii reale p\u00e2n\u0103 c\u00e2nd nu \u00eencepe cineva s\u0103 \u00eel foloseasc\u0103: clien\u021bi, clien\u021bi, angaja\u021bi, nu conteaz\u0103\u00bb, afirm\u0103 Eveline Oehrlich, analist senior la Institutul DevOps. \u2013 De aceea, ambele p\u0103r\u021bi asigur\u0103 \u00eempreun\u0103 livrarea rapid\u0103 \u0219i de calitate a software-ului\u00bb.<\/p>\n

2. DevOps \u2013 este ceea ce \u00eemputernice\u0219te dezvoltatorii<\/h4>\n

\n\u00abDevOps \u00eemputernice\u0219te dezvoltatorii s\u0103 de\u021bin\u0103 aplica\u021bii, s\u0103 le lanseze \u0219i s\u0103 gestioneze livrarea de la \u00eenceput p\u00e2n\u0103 la sf\u00e2r\u0219it\u00bb<\/b><\/p>\n

\u00abDe obicei, se vorbe\u0219te despre DevOps ca despre un mod de a accelera livrarea aplica\u021biilor \u00een produc\u021bie prin crearea \u0219i aplicarea unor procese automatizate\u00bb, spune Jai Schniepp, director de platforme DevOps la compania de asigur\u0103ri Liberty Mutual. \u2013 \u201eDar pentru mine, aceasta este o chestiune mult mai fundamental\u0103. DevOps \u00eemputernice\u0219te dezvoltatorii s\u0103 de\u021bin\u0103 aplica\u021bii sau anumite p\u0103r\u021bi ale software-ului, s\u0103 le lanseze \u0219i s\u0103 gestioneze livrarea de la \u00eenceput p\u00e2n\u0103 la sf\u00e2r\u0219it. DevOps elimin\u0103 confuzia \u00een responsabilit\u0103\u021bi \u0219i \u00eei ghideaz\u0103 pe to\u021bi participan\u021bii la proces spre crearea unei infrastructuri automate \u0219i controlate de dezvoltatori.\u201d<\/p>\n

3. DevOps \u2013 este colaborarea \u00een crearea \u0219i livrarea aplica\u021biilor<\/h4>\n

\n\u00abPe scurt, DevOps este o abordare a produc\u021biei \u0219i livr\u0103rii software-ului \u00een care to\u021bi lucreaz\u0103 \u00eempreun\u0103\u00bb, subliniaz\u0103 Gur Staff, pre\u0219edintele \u0219i \u0219eful departamentului de automatizare a afacerilor digitale la BMC.<\/p>\n

4. DevOps \u2013 este un conveior<\/h4>\n

\n\u00abMontajul pe conveior este posibil doar dac\u0103 toate piesele se potrivesc \u00eentre ele\u00bb.<\/b><\/p>\n

\u00abA\u0219 compara DevOps cu un conveior de asamblare a automobilelor\u00bb, continu\u0103 Gur Staff. \u2013 \u201eIdeea este de a proiecta \u0219i construi toate piesele astfel \u00eenc\u00e2t s\u0103 poat\u0103 fi asamblate f\u0103r\u0103 ajust\u0103ri individuale. Montajul pe conveior este posibil doar dac\u0103 toate piesele se potrivesc \u00eentre ele. Cei care proiecteaz\u0103 \u0219i construiesc motorul trebuie s\u0103 ia \u00een considerare modul \u00een care acesta va fi fixat la caroserie sau cadru. Cei care construiesc fr\u00e2nele trebuie s\u0103 se g\u00e2ndeasc\u0103 la ro\u021bi, \u0219i a\u0219a mai departe. La fel trebuie s\u0103 fie \u0219i cu software-ul.\u201d <\/p>\n

Dezvoltatorul care creeaz\u0103 logica de afaceri sau interfa\u021ba utilizatorului trebuie s\u0103 se g\u00e2ndeasc\u0103 la baza de date care stocheaz\u0103 informa\u021bii despre clien\u021bi, la m\u0103surile de securitate pentru protec\u021bia datelor utilizatorilor \u0219i, de asemenea, la modul \u00een care toate acestea vor func\u021biona atunci c\u00e2nd serviciul va \u00eencepe s\u0103 deserveasc\u0103 o audien\u021b\u0103 mare, posibil chiar multimilionar\u0103.<\/p>\n

\u201eS\u0103 facem astfel \u00eenc\u00e2t oamenii s\u0103 colaboreze \u0219i s\u0103 se g\u00e2ndeasc\u0103 la p\u0103r\u021bile muncii care sunt realizate de al\u021bii, nu doar s\u0103 se concentreze exclusiv pe sarcinile lor, este cea mai mare provocare de dep\u0103\u0219it. Dac\u0103 reu\u0219i\u021bi, ave\u021bi \u0219anse excelente pentru transformarea digital\u0103\u201d, adaug\u0103 Gur Staff.<\/p>\n

5. DevOps este combina\u021bia corect\u0103 de oameni, procese \u0219i automatizare<\/h4>\n

\nJayne Groll, director executiv al Institutului DevOps, a oferit o analogie excelent\u0103 pentru a explica DevOps. Potrivit acesteia, \u201eDevOps este ca o re\u021bet\u0103 culinar\u0103, \u00een care exist\u0103 trei categorii principale de ingrediente: oameni, procese \u0219i automatizare. Majoritatea acestor ingrediente pot fi preluate din alte domenii \u0219i surse: Lean, Agile, SRE, CI\/CD, ITIL, leadership, cultur\u0103, instrumente. Secretul DevOps, la fel ca orice re\u021bet\u0103 bun\u0103, este modul \u00een care combin\u0103m corect aceste ingrediente pentru a cre\u0219te viteza \u0219i eficien\u021ba \u00een dezvoltarea \u0219i livrarea aplica\u021biilor\u201d.<\/p>\n

6. DevOps este atunci c\u00e2nd programatorii lucreaz\u0103 ca o echip\u0103 de Formula 1<\/h4>\n

\n\u201eCursele sunt planificate nu de la start la finis, ci invers, de la finis la start\u201d.<\/b><\/p>\n

\u201eVorbind despre ce s\u0103 ne a\u0219tept\u0103m de la ini\u021biativa DevOps, dau exemplul unei echipe de curse NASCAR sau Formula 1\u201d, spune Chris Short, managerul principal de marketing pentru platformele de cloud de la Red Hat \u0219i editor al newsletterului DevOps\u2019ish. \u201eUn lider al unei astfel de echipe are un singur obiectiv: s\u0103 ob\u021bin\u0103 cele mai bune rezultate \u00een func\u021bie de resursele echipei \u0219i provoc\u0103rile \u00eent\u00e2mpinate. \u00cen acela\u0219i timp, cursa este planificat\u0103 nu de la start la finis, ci invers, de la finis la start. La \u00eenceput se stabile\u0219te un obiectiv ambi\u021bios, iar apoi se definesc modalit\u0103\u021bile de a-l atinge. Dup\u0103 aceea, acestea sunt \u00eemp\u0103r\u021bite \u00een sub-sarcini \u0219i delegate membrilor echipei.\u201d<\/p>\n

\u201ePe parcursul \u00eentregii s\u0103pt\u0103m\u00e2ni \u00eenainte de curs\u0103, echipa \u00ee\u0219i perfec\u021bioneaz\u0103 pit-stopurile. Se antreneaz\u0103 \u00een for\u021b\u0103 \u0219i la cardio pentru a fi \u00een form\u0103 \u00eentr-o zi obositoare de curse. Lucreaz\u0103 \u00eempreun\u0103 pentru a rezolva orice probleme care ar putea ap\u0103rea pe parcursul cursei. La fel, echipa de dezvoltare trebuie s\u0103 exerseze abilit\u0103\u021bile de lansare frecvent\u0103 a noilor versiuni. Cu astfel de abilit\u0103\u021bi \u0219i un sistem de securitate bine pus la punct, lansarea noilor versiuni \u00een produc\u021bie devine, de asemenea, mai frecvent\u0103. Din aceast\u0103 perspectiv\u0103, cre\u0219terea vitezei \u00eenseamn\u0103 cre\u0219terea securit\u0103\u021bii\u201d, spune Short.<\/p>\n

\u201eNu este vorba despre a face \u201elucrurile corecte\u201d, adaug\u0103 Short, \u201eci despre a elimina c\u00e2t mai multe obstacole posibile care stau \u00een calea rezultatului dorit. Colabora\u021bi \u0219i adapta\u021bi-v\u0103 \u00een func\u021bie de feedback-ul pe care \u00eel primi\u021bi \u00een timp real. Fi\u021bi preg\u0103ti\u021bi pentru anomalii \u0219i lucra\u021bi la \u00eembun\u0103t\u0103\u021birea calit\u0103\u021bii pentru a minimiza impactul lor asupra progresului c\u0103tre obiectiv. Acesta este exact ceea ce ne a\u0219teapt\u0103 \u00een lumea DevOps\u201d.<\/p>\n

\"Vorbind
\n<\/p>\n

Cum s\u0103 scala\u021bi DevOps: 10 sfaturi de la exper\u021bi<\/h3>\n

\nDevOps simplu \u0219i DevOps de mas\u0103 sunt lucruri complet diferite. V\u0103 vom explica cum s\u0103 dep\u0103\u0219i\u021bi barierele pe calea de la unul la cel\u0103lalt.<\/b><\/p>\n

Pentru multe organiza\u021bii, drumul c\u0103tre DevOps \u00eencepe u\u0219or \u0219i pl\u0103cut. Se formeaz\u0103 echipe mici pasionate, procesele vechi sunt \u00eenlocuite cu unele noi, iar primele succese nu \u00eent\u00e2rzie s\u0103 apar\u0103.<\/p>\n

Din p\u0103cate, aceasta este doar o str\u0103lucire fals\u0103, o iluzie de progres, a\u0219a cum spune Ben Grinnell, director general \u0219i lider al domeniului tehnologiilor digitale la firma de consultan\u021b\u0103 North Highland. Primele victorii sunt desigur \u00eencurajatoare, dar nu ajut\u0103 la atingerea obiectivului final, \u0219i anume utilizarea pe scar\u0103 larg\u0103 a DevOps \u00een organiza\u021bie.<\/p>\n

Este u\u0219or de v\u0103zut c\u0103, \u00een urma acestui proces, se formeaz\u0103 o cultur\u0103 a diviz\u0103rii \u00eentre \u201enoi\u201d \u0219i \u201eei\u201d.<\/b><\/p>\n

\u201eAdesea, organiza\u021biile lanseaz\u0103 astfel de proiecte-pionier, crez\u00e2nd c\u0103 acestea vor deschide calea pentru DevOps la scar\u0103 larg\u0103, f\u0103r\u0103 a se g\u00e2ndi dac\u0103 ceilal\u021bi vor dori sau vor putea s\u0103 urmeze acest drum\u201d, explic\u0103 Ben Greennell. \u201eEchipele care implementeaz\u0103 astfel de proiecte sunt de obicei alc\u0103tuite din \u201evikingi\u201d \u00eencrez\u0103tori, care au mai realizat ceva similar \u00een alte p\u0103r\u021bi, dar care sunt novice \u00een organiza\u021bia dvs. \u00cen acela\u0219i timp, sunt \u00eencuraja\u021bi s\u0103 strice \u0219i s\u0103 ignore regulile care r\u0103m\u00e2n obligatorii pentru to\u021bi ceilal\u021bi. Este u\u0219or de observat c\u0103, \u00een rezultat, se formeaz\u0103 o cultur\u0103 a diviz\u0103rii \u00eentre \u201enoi\u201d \u0219i \u201eei\u201d, care \u00eempiedic\u0103 transmiterea cuno\u0219tin\u021belor \u0219i abilit\u0103\u021bilor.\u201d<\/p>\n

\u201e\u0218i aceast\u0103 problem\u0103 cultural\u0103 este doar una dintre cauzele pentru care DevOps este greu de scalat. Echipele DevOps se confrunt\u0103 cu cre\u0219terea dificult\u0103\u021bilor tehnice specifice companiilor \u00een expansiune rapid\u0103 care s-au bazat pe tehnologiile IT\u201d, afirm\u0103 Steve Newman, fondator \u0219i pre\u0219edinte al companiei Scalyr.<\/p>\n

\u201e\u00cen lumea modern\u0103, serviciile se schimb\u0103 imediat ce apare o necesitate. Implementarea constant\u0103 \u0219i introducerea de noi func\u021bionalit\u0103\u021bi este, desigur, grozav, dar coordonarea acestui proces \u0219i solu\u021bionarea problemelor ap\u0103rute reprezint\u0103 o adev\u0103rat\u0103 b\u0103taie de cap\u201d, adaug\u0103 Steve Newman. \u201e\u00cen organiza\u021biile \u00een decolare rapid\u0103, inginerii din echipele cross-func\u021bionale se lupt\u0103 s\u0103 \u00ee\u0219i p\u0103streze capacitatea de a urm\u0103ri modific\u0103rile \u0219i efectele \u00een cascad\u0103 pe nivelurile de dependen\u021b\u0103. Mai mult, inginerilor nu le face pl\u0103cere c\u00e2nd li se ia aceast\u0103 posibilitate, iar \u00een consecin\u021b\u0103 devine mai greu s\u0103 \u00een\u021beleag\u0103 natura problemelor ap\u0103rute.\u201d<\/p>\n

Cum putem dep\u0103\u0219i dificult\u0103\u021bile men\u021bionate mai sus \u0219i transita c\u0103tre utilizarea pe scar\u0103 larg\u0103 a DevOps \u00eentr-o organiza\u021bie mare? Exper\u021bii recomand\u0103 s\u0103 ave\u021bi r\u0103bdare, chiar dac\u0103 scopul vostru final este s\u0103 accelera\u021bi ciclul de dezvoltare a software-ului \u0219i procesele de afaceri.<\/b><\/p>\n

1. Aminti\u021bi-v\u0103 c\u0103 schimb\u0103rile culturale necesit\u0103 timp<\/h4>\n

\nJane Groll, director executiv al Institutului DevOps:<\/b> \u201e\u00cen opinia mea, extinderea DevOps ar trebui s\u0103 fie la fel de treptat\u0103 \u0219i iterativ\u0103 ca \u0219i dezvoltarea agile (\u0219i s\u0103 implice \u00een aceea\u0219i m\u0103sur\u0103 cultura). \u00cen Agile \u0219i DevOps, accentul se pune pe echipe mici. Dar pe m\u0103sur\u0103 ce num\u0103rul \u0219i integrarea acestor echipe cresc, avem din ce \u00een ce mai mul\u021bi oameni care aplic\u0103 noi metode de lucru, iar ca urmare, apare o transformare cultural\u0103 de amploare.\u201d<\/p>\n

2. Acorda\u021bi suficient timp pentru planificare \u0219i alegerea platformei<\/h4>\n

\nEran Kinsbruner, evanghelist tehnic principal al companiei Perfecto:<\/b> \u201ePentru ca scalarea s\u0103 func\u021bioneze, echipele DevOps trebuie mai \u00eent\u00e2i s\u0103 \u00eenve\u021be s\u0103 combine procesele, instrumentele \u0219i abilit\u0103\u021bile tradi\u021bionale, iar apoi s\u0103 dezvolte treptat fiecare faz\u0103 a DevOps \u0219i s\u0103 o stabilizeze. Totul \u00eencepe cu o planificare atent\u0103 a pove\u0219tilor utilizatorilor \u0219i a fluxurilor de creare a valorii, dup\u0103 care urmeaz\u0103 etapa de scriere a software-ului \u0219i controlul versiunilor, utiliz\u00e2nd dezvoltarea bazat\u0103 pe trunk sau alte abord\u0103ri mai potrivite pentru ramificarea \u0219i \u00eembinarea codului.\u201d<\/p>\n

\u201eApoi urmeaz\u0103 etapa de integrare \u0219i testare, unde este necesar\u0103 deja o platform\u0103 scalabil\u0103 pentru automatizare. Aici, echipele DevOps trebuie s\u0103 aleag\u0103 platforma potrivit\u0103, care s\u0103 corespund\u0103 nivelului lor de abilit\u0103\u021bi \u0219i obiectivelor finale ale proiectului.\u201d <\/p>\n

Faza urm\u0103toare este desf\u0103\u0219urarea \u00een mediu de produc\u021bie, iar aceasta trebuie s\u0103 fie complet automatizat\u0103 cu instrumente de orchestrare \u0219i containere. Este important s\u0103 existe medii virtualizate \u00een toate etapele DevOps (simularea mediului de produc\u021bie, mediu de control al calit\u0103\u021bii \u0219i, de fapt, mediu de produc\u021bie) \u0219i s\u0103 se foloseasc\u0103 \u00eentotdeauna cele mai recente date pentru teste, pentru a ob\u021bine concluzii relevante. Analiza trebuie s\u0103 fie inteligent\u0103 \u0219i capabil\u0103 s\u0103 gestioneze date mari cu feedback rapid \u0219i eficient.\u201d<\/p>\n

3. Elibera\u021bi responsabilitatea de gustul vinov\u0103\u021biei<\/h4>\n

\nGordon Haff, evanghelist RedHat:<\/b> \u201eCrearea unui sistem \u0219i a unei atmosfere care s\u0103 permit\u0103 \u0219i s\u0103 \u00eencurajeze experimentele permite realizarea a ceea ce se nume\u0219te e\u0219ecuri de succes \u00een dezvoltarea software-ului agile. Asta nu \u00eenseamn\u0103 c\u0103 nimeni nu mai este responsabil pentru e\u0219ecuri. De fapt, stabilirea unui responsabil devine chiar mai simpl\u0103, deoarece \u201ea fi responsabil\u201d nu mai \u00eenseamn\u0103 \u201ea fi vinovat de accident\u201d. Cu alte cuvinte, esen\u021ba responsabilit\u0103\u021bii se schimb\u0103 calitativ. \u00cen acest sens, patru factori devin extrem de importan\u021bi: amploarea e\u0219ecului, abord\u0103rile, procesele de produc\u021bie \u0219i stimulentele.\u201d (Mai multe despre ace\u0219ti factori pute\u021bi citi \u00een articolul lui Gordon Huff \u201eLec\u021bii DevOps: 4 aspecte ale experimentelor s\u0103n\u0103toase.\u201d)<\/p>\n

4. Elibera\u021bi drumul \u00eenainte<\/h4>\n

\nBen Grinnell, director general \u0219i lider al departamentului de tehnologie digital\u0103 al firmei de consultan\u021b\u0103 North Highland:<\/b> \u201ePentru a atinge scalabilitatea, recomand s\u0103 desf\u0103\u0219ura\u021bi simultan cu proiectele de pionierat un program de \u201eeliberare a c\u0103ii\u201d. Scopul acestui program este de a cur\u0103\u021ba resturile l\u0103sate de pionierii DevOps, cum ar fi regulile dep\u0103\u0219ite \u0219i alte lucruri similare, astfel \u00eenc\u00e2t drumul \u00eenainte s\u0103 r\u0103m\u00e2n\u0103 liber.\u201d<\/p>\n

\u201eOferi\u021bi oamenilor suport organiza\u021bional \u0219i insufla\u021bi impuls prin comunicare, care s\u0103 dep\u0103\u0219easc\u0103 cu mult grupul pionierilor, celebr\u00e2nd pe larg succesele noilor metode de lucru. Forma\u021bi persoanele implicate \u00een urm\u0103toarea etap\u0103 a proiectelor DevOps \u0219i care sunt nelini\u0219tite pentru c\u0103 utilizeaz\u0103 DevOps pentru prima dat\u0103. \u0218i aminti\u021bi-v\u0103 c\u0103 ace\u0219ti oameni sunt foarte diferi\u021bi de pionieri.\u201d<\/p>\n

5. Face\u021bi instrumentele mai democratice<\/h4>\n

\nSteve Newman, fondator \u0219i pre\u0219edinte al consiliului de administra\u021bie al companiei Scalyr:<\/b> \u201eInstrumentele nu ar trebui ascunse de oameni \u0219i ar trebui s\u0103 fie relativ simple de \u00eenv\u0103\u021bat pentru oricine este dispus s\u0103 investeasc\u0103 timp \u00een asta. Dac\u0103 oportunitatea de a solicita jurnale este oferit\u0103 doar la trei persoane \u201ecertificate\u201d pentru a lucra cu un anumit instrument, ve\u021bi avea \u00eentotdeauna un maxim de trei persoane capabile s\u0103 se ocupe de problema respectiv\u0103, chiar dac\u0103 ave\u021bi un mediu de calcul foarte mare. Cu alte cuvinte, aici apare o restric\u021bie, care poate avea consecin\u021be grave (pentru afacere).<\/p>\n

6. Crea\u021bi condi\u021bii ideale pentru echip\u0103<\/h4>\n

\nTom Clark, liderul departamentului Common Platform la compania ITV:<\/b> \u201ePute\u021bi face orice, dar nu totul deodat\u0103. A\u0219a c\u0103 stabili\u021bi obiective mari, \u00eencepe\u021bi cu pa\u0219i mici \u0219i avansa\u021bi rapid prin itera\u021bii. \u00cen timp, ve\u021bi c\u00e2\u0219tiga reputa\u021bia unei echipe care reu\u0219e\u0219te, ceea ce va determina \u0219i pe al\u021bii s\u0103 doreasc\u0103 s\u0103 utilizeze metodele dumneavoastr\u0103. \u0218i nu urm\u0103ri\u021bi doar formarea unei echipe de \u00eenalt\u0103 performan\u021b\u0103. \u00cen schimb, oferi\u021bi oamenilor condi\u021bii ideale de lucru \u0219i eficien\u021ba va veni de la sine.\u201d<\/p>\n

7. Nu uita\u021bi de legea Conway \u0219i tablourile Kanban<\/h4>\n

\nLogan Daigle, director de livrare software \u0219i strategie DevOps la CollabNetVersionOne:<\/b> \u201eEste important s\u0103 con\u0219tientiz\u0103m consecin\u021bele legii Conway. Pe scurt, aceast\u0103 lege spune c\u0103 produsele pe care le cre\u0103m \u0219i procesele pe care le folosim, inclusiv DevOps, sunt organizate la fel ca organiza\u021bia noastr\u0103.\u201d<\/p>\n

\u201eDac\u0103 \u00een organiza\u021bie exist\u0103 o mare fragmentare, iar la planificarea, crearea \u0219i lansarea software-ului managementul se transfer\u0103 frecvent de la o persoan\u0103 la alta, efectul scal\u0103rii va fi zero sau de scurt\u0103 durat\u0103. Pe de alt\u0103 parte, dac\u0103 organiza\u021bia formeaz\u0103 echipe interfunc\u021bionale \u00een jurul produselor care sunt finan\u021bate cu orientare pe pia\u021b\u0103, \u0219ansele de succes cresc brusc.\u201d<\/p>\n

\u201eUn alt aspect important al scal\u0103rii este s\u0103 reflect\u0103m pe tablourile Kanban toate lucr\u0103rile aflate \u00een desf\u0103\u0219urare (WIP, work in progress). Atunci c\u00e2nd apare un loc \u00een organiza\u021bie unde oamenii pot vedea aceste lucruri, acest lucru stimuleaz\u0103 semnificativ colaborarea, ceea ce are un impact pozitiv asupra scal\u0103rii.\u201d<\/p>\n

8. C\u0103uta\u021bi vechile cicatrici<\/h4>\n

\nManuel Pais, consultant DevOps \u0219i coautor al c\u0103r\u021bii \u201eTeam Topologies\u201d:<\/b> \u201eExtinderea practicilor DevOps dincolo de Dev \u0219i Ops \u0219i \u00eencercarea de a le aplica altor func\u021bii nu poate fi considerat\u0103 o abordare optim\u0103. Cu siguran\u021b\u0103, va avea un anumit efect (de exemplu, prin automatizarea managementului manual), dar se poate ob\u021bine mult mai mult dac\u0103 \u00eencepem cu \u00een\u021belegerea proceselor de livrare \u0219i feedback.\u201d<\/p>\n

\u201eDac\u0103 \u00een sistemul IT al organiza\u021biei exist\u0103 cicatrici vechi \u2013 proceduri \u0219i mecanisme de gestionare, care au fost implementate \u00een urma incidentelor anterioare, dar \u0219i-au pierdut relevan\u021ba (din cauza schimb\u0103rii produselor, tehnologiilor sau proceselor), atunci acestea trebuie f\u0103r\u0103 \u00eendoial\u0103 eliminate sau atenuate, nu automatizate procese ineficiente sau inutile.\u201d<\/p>\n

9. Nu crea\u021bi variante de DevOps<\/h4>\n

\nAntony Edwards, director de produc\u021bie la Eggplant:<\/b> \u201eDevOps este un termen foarte vag, prin urmare, fiecare echip\u0103 ajunge s\u0103 aib\u0103 propria variant\u0103 de DevOps. \u0218i nu exist\u0103 nimic mai r\u0103u dec\u00e2t atunci c\u00e2nd \u00een organiza\u021bie apar simultan 20 de variante de DevOps, care nu coabiteaz\u0103 bine \u00eempreun\u0103. Nu poate fiecare dintre cele trei echipe de dezvoltare s\u0103 aib\u0103 propria interfa\u021b\u0103 \u00eentre dezvoltare \u0219i gestionarea produsului. La fel, produsele nu pot avea a\u0219tept\u0103ri unice \u00een ceea ce prive\u0219te gestionarea feedback-ului c\u00e2nd sunt transferate \u00een simularea mediului de produc\u021bie. \u00cen caz contrar, nu ve\u021bi reu\u0219i niciodat\u0103 s\u0103 scala\u021bi DevOps.\u201d<\/p>\n

10. Promova\u021bi valoarea DevOps pentru afaceri<\/h4>\n

\nSteve Newman, fondator \u0219i pre\u0219edinte al consiliului de administra\u021bie al companiei Scalyr:<\/b> \u201eLucra\u021bi la recunoa\u0219terea valorii DevOps. \u00cenv\u0103\u021ba\u021bi \u0219i nu ezita\u021bi s\u0103 vorbi\u021bi despre beneficiile a ceea ce face\u021bi. DevOps economise\u0219te incredibil de mult timp \u0219i bani (g\u00e2ndi\u021bi-v\u0103: mai pu\u021bin timp de nefunc\u021bionare, un timp mediu de recuperare mai scurt), iar echipele DevOps trebuie s\u0103 sublinieze (\u0219i s\u0103 promoveze) constant importan\u021ba acestor ini\u021biative pentru succesul afacerii. Astfel, ve\u021bi putea extinde cercul sus\u021bin\u0103torilor \u0219i s\u0103 cre\u0219te\u021bi influen\u021ba DevOps \u00een organiza\u021bie.\u201d<\/p>\n

BONUS<\/h3>\n

\nPe Red Hat Forum Rusia<\/a><\/noindex> Pe 13 septembrie, va veni propriul nostru DevOps \u2013 da, Red Hat, ca furnizor de software, are propriile echipe \u0219i practici de DevOps.<\/b><\/p>\n

Inginerul nostru, Mark Birger, care se ocup\u0103 de dezvoltarea serviciilor de automatizare intern\u0103 pentru alte grupuri din \u00eentreaga organiza\u021bie, va povesti \u00een rus\u0103 despre propria sa experien\u021b\u0103 \u2013 cum echipa DevOps de la Red Hat a migrat aplica\u021biile din medii virtuale Hat Virtualization, gestionate de Ansible, \u00eentr-un format complet containerizat pe platforma OpenShift.<\/p>\n

Dar nici asta nu este tot:<\/b><\/p>\n

Dup\u0103 ce organiza\u021biile au mutat sarcinile de lucru \u00een containere, metodele tradi\u021bionale de monitorizare a aplica\u021biilor pot s\u0103 nu mai func\u021bioneze. \u00cen al doilea raport, ne vom explica motiva\u021bia de a schimba modul de \u00eenregistrare \u0219i vom ar\u0103ta continuarea c\u0103ii care ne-a condus la metodele moderne de jurnalizare \u0219i monitorizare.
\n
Sursa: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u0422\u0440\u0443\u0434\u043d\u043e \u0443\u043b\u043e\u0432\u0438\u0442\u044c \u0433\u043b\u0430\u0432\u043d\u043e\u0435, \u0433\u043e\u0432\u043e\u0440\u044f \u043e DevOps? \u041c\u044b \u0441\u043e\u0431\u0440\u0430\u043b\u0438 \u0434\u043b\u044f \u0432\u0430\u0441 \u044f\u0440\u043a\u0438\u0435 \u0430\u043d\u0430\u043b\u043e\u0433\u0438\u0438, \u0443\u0434\u0430\u0440\u043d\u044b\u0435 \u0444\u043e\u0440\u043c\u0443\u043b\u0438\u0440\u043e\u0432\u043a\u0438 \u0438 \u0441\u043e\u0432\u0435\u0442\u044b \u043e\u0442 \u044d\u043a\u0441\u043f\u0435\u0440\u0442\u043e\u0432, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043f\u043e\u043c\u043e\u0433\u0443\u0442 \u0434\u043e\u0439\u0442\u0438 \u0434\u043e \u0441\u0443\u0442\u0438 \u0434\u0430\u0436\u0435 \u043d\u0435\u0441\u043f\u0435\u0446\u0438\u0430\u043b\u0438\u0441\u0442\u0430\u043c. \u0412 \u043a\u043e\u043d\u0446\u0435 \u0431\u043e\u043d\u0443\u0441 \u2013 \u0441\u043e\u0431\u0441\u0442\u0432\u0435\u043d\u043d\u044b\u0439 DevOps \u0441\u043e\u0442\u0440\u0443\u0434\u043d\u0438\u043a\u043e\u0432 Red Hat. \u0422\u0435\u0440\u043c\u0438\u043d DevOps \u0432\u043e\u0437\u043d\u0438\u043a 10 \u043b\u0435\u0442 \u043d\u0430\u0437\u0430\u0434 \u0438 \u043f\u0440\u043e\u0448\u0435\u043b \u043f\u0443\u0442\u044c \u043e\u0442 \u0445\u044d\u0448\u0442\u0435\u0433\u0430 \u0432 \u0422\u0432\u0438\u0442\u0442\u0435\u0440\u0435 \u0434\u043e \u043c\u043e\u0449\u043d\u043e\u0433\u043e \u043a\u0443\u043b\u044c\u0442\u0443\u0440\u043d\u043e\u0433\u043e \u0434\u0432\u0438\u0436\u0435\u043d\u0438\u044f \u0432 \u043c\u0438\u0440\u0435 \u0418\u0422, \u043d\u0430\u0441\u0442\u043e\u044f\u0449\u0435\u0439 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":28183,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[702],"tags":[],"class_list":["post-37551","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Discut\u0103m despre DevOps \u00eentr-o limb\u0103 accesibil\u0103 | ProHoster","description":"Este greu s\u0103 prinzi esen\u021ba vorbind despre DevOps? Am adunat pentru voi analogii clare, formul\u0103ri impactante \u0219i sfaturi de la exper\u021bi care vor ajuta chiar \u0219i nespeciali\u0219tii s\u0103 ajung\u0103 la miezul problemei.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/news\/govorim-o-devops-na-ponyatnom-yazyke","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","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\u0413\u043e\u0432\u043e\u0440\u0438\u043c \u043e DevOps \u043d\u0430 \u043f\u043e\u043d\u044f\u0442\u043d\u043e\u043c \u044f\u0437\u044b\u043a\u0435 | ProHoster","og:description":"\u0422\u0440\u0443\u0434\u043d\u043e \u0443\u043b\u043e\u0432\u0438\u0442\u044c \u0433\u043b\u0430\u0432\u043d\u043e\u0435, \u0433\u043e\u0432\u043e\u0440\u044f \u043e DevOps? \u041c\u044b \u0441\u043e\u0431\u0440\u0430\u043b\u0438 \u0434\u043b\u044f \u0432\u0430\u0441 \u044f\u0440\u043a\u0438\u0435 \u0430\u043d\u0430\u043b\u043e\u0433\u0438\u0438, \u0443\u0434\u0430\u0440\u043d\u044b\u0435 \u0444\u043e\u0440\u043c\u0443\u043b\u0438\u0440\u043e\u0432\u043a\u0438 \u0438 \u0441\u043e\u0432\u0435\u0442\u044b \u043e\u0442 \u044d\u043a\u0441\u043f\u0435\u0440\u0442\u043e\u0432, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043f\u043e\u043c\u043e\u0433\u0443\u0442 \u0434\u043e\u0439\u0442\u0438 \u0434\u043e \u0441\u0443\u0442\u0438 \u0434\u0430\u0436\u0435 \u043d\u0435\u0441\u043f\u0435\u0446\u0438\u0430\u043b\u0438\u0441\u0442\u0430\u043c.","og:url":"https:\/\/prohoster.info\/ro\/blog\/news\/govorim-o-devops-na-ponyatnom-yazyke","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:18:16+00:00","article:modified_time":"2019-10-31T19:18:16+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37551","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":"2026-01-23 18:20:51","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:24:25","updated":"2026-01-23 18:20:51","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/37551","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=37551"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/37551\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/28183"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=37551"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=37551"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=37551"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}