{"id":37221,"date":"2019-10-31T22:16:24","date_gmt":"2019-10-31T19:16:24","guid":{"rendered":"https:\/\/prohoster.info\/blog\/pochemu-sistemnye-administratory-dolzhny-stanovitsya-devops-inzhenerami\/"},"modified":"2019-10-31T22:16:24","modified_gmt":"2019-10-31T19:16:24","slug":"pochemu-sistemnye-administratory-dolzhny-stanovitsya-devops-inzhenerami","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/pochemu-sistemnye-administratory-dolzhny-stanovitsya-devops-inzhenerami","title":{"rendered":"De ce ar trebui administratorii de sistem s\u0103 devin\u0103 ingineri DevOps","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"De
\n<\/p>\n

Pentru \u00eenv\u0103\u021bare, nu exist\u0103 un moment mai bun dec\u00e2t ast\u0103zi.<\/p><\/blockquote>\n

<\/i>
\nEste anul 2019, iar tema DevOps este mai relevant\u0103 ca niciodat\u0103. Se spune c\u0103 zilele administratorilor de sistem sunt num\u0103rate, a\u0219a cum a trecut epoca mainframe-urilor. Dar este asta adev\u0103rat?
\nA\u0219a cum se \u00eent\u00e2mpl\u0103 adesea \u00een IT, situa\u021bia s-a schimbat. A ap\u0103rut metodologia DevOps, dar aceasta nu poate exista f\u0103r\u0103 o persoan\u0103 cu abilit\u0103\u021bi de administrator de sistem, adic\u0103 f\u0103r\u0103 Ops.<\/p>\n

\u00cenainte ca abordarea DevOps s\u0103 capete forma sa modern\u0103, m\u0103 consideram parte din categoria Ops. \u0218tiu foarte bine ce simte un administrator de sistem c\u00e2nd \u00ee\u0219i d\u0103 seama c\u00e2te multe nu \u0219tie \u0219i c\u00e2t de pu\u021bin timp are s\u0103 \u00eenve\u021be.<\/a><\/noindex><\/p>\n

\"De<\/p>\n

Dar este totul at\u00e2t de alarmant? A\u0219 spune c\u0103 nu ar trebui s\u0103 percepem lipsa de cuno\u0219tin\u021be ca pe o problem\u0103 serioas\u0103. Este mai mult o provocare profesional\u0103. <\/p>\n

Produsele de tip web-scale se bazeaz\u0103 pe Linux sau pe alte software-uri cu cod surs\u0103 deschis, iar pe pia\u021b\u0103 exist\u0103 din ce \u00een ce mai pu\u021bini speciali\u0219ti capabili s\u0103 le \u00eentre\u021bin\u0103. Cererea a dep\u0103\u0219it deja num\u0103rul de profesioni\u0219ti din acest domeniu. Administratorul de sistem nu \u00ee\u0219i va putea continua munca f\u0103r\u0103 s\u0103 \u00ee\u0219i \u00eembun\u0103t\u0103\u021beasc\u0103 nivelul de calificare. Trebuie s\u0103 aib\u0103 abilit\u0103\u021bi de automatizare pentru a gestiona un num\u0103r mare de servere\/noduri \u0219i s\u0103 \u00een\u021beleag\u0103 bine principiile lor de func\u021bionare pentru a rezolva problemele ap\u0103rute.<\/p>\n

\u00cenainte de a deveni membru al echipei DevOps, va trebui s\u0103 parcurge\u021bi un drum destul de lung, dar interesant, \u00eenv\u0103\u021b\u00e2nd tehnologii noi \u0219i diverse instrumente necesare pentru a \u00eentre\u021bine sistemul conform standardelor DevOps. <\/p>\n

Deci, cum poate un administrator de sistem s\u0103 treac\u0103 de la abordarea obi\u0219nuit\u0103 la noua concep\u021bie DevOps? Totul este ca de obicei: mai \u00eent\u00e2i trebuie s\u0103 v\u0103 schimba\u021bi mentalitatea. Nu este deloc u\u0219or s\u0103 renun\u021bi la abordarea pe care ai urmat-o \u00een ultimii zece sau dou\u0103zeci de ani \u0219i s\u0103 \u00eencepi s\u0103 faci lucrurile diferit, dar este necesar.<\/p>\n

\u00cen primul r\u00e2nd, este important s\u0103 \u00een\u021belegem c\u0103 DevOps nu este o func\u021bie specific\u0103 \u00eentr-o companie, ci un set de practici definite. Aceste practici implic\u0103 distribuirea sistemelor izolate, reducerea impactului erorilor \u0219i bug-urilor, actualizarea frecvent\u0103 \u0219i la timp a software-ului, o colaborare eficient\u0103 \u00eentre dezvoltatori (Dev) \u0219i administratori (Ops), precum \u0219i testarea constant\u0103 nu doar a codului, ci \u0219i a \u00eentregii structuri \u00een cadrul procesului integr\u0103rii \u0219i livr\u0103rii continue (CI\/CD)<\/a><\/noindex>.<\/p>\n

Pe l\u00e2ng\u0103 schimbarea mentalit\u0103\u021bii, trebuie s\u0103 \u00eenv\u0103\u021b\u0103m s\u0103 sus\u021binem infrastructura \u0219i s\u0103 asigur\u0103m func\u021bionarea ei stabil\u0103, fiabilitatea \u0219i accesibilitatea pentru integrarea \u0219i livrarea continu\u0103 a aplica\u021biilor, serviciilor \u0219i software-ului.<\/p>\n

Ceea ce s-ar putea s\u0103 \u00ee\u021bi lipseasc\u0103 ca specialist Ops este abilit\u0103\u021bi de programare. \u00cen prezent, scrierea de scripturi (scripts), pe care administratorii de sistem le folosesc pentru instalarea automat\u0103 a patch-urilor pe server, gestionarea fi\u0219ierelor \u0219i conturilor, pentru depanare \u0219i documentare, este considerat\u0103 deja \u00eenvechit\u0103. \u00cen cazuri relativ simple, scripturile sunt \u00eenc\u0103 folosite, dar conceptul DevOps implic\u0103 rezolvarea sarcinilor la scar\u0103 larg\u0103, fie c\u0103 este vorba despre implementare, testare, lucru cu pachetele sau desf\u0103\u0219urare.<\/p>\n

Astfel, dac\u0103 dore\u0219ti s\u0103 \u00eenve\u021bi automatizarea, trebuie s\u0103 st\u0103p\u00e2ne\u0219ti m\u0103car pu\u021bin programarea, chiar dac\u0103 nu e\u0219ti dezvoltator, deoarece \u00een acest stadiu al dezvolt\u0103rii tale automatia infrastructurii<\/a><\/noindex> \u00een DevOps necesit\u0103 aceast\u0103 abilitate.<\/p>\n

Ce s\u0103 faci? Pentru a r\u0103m\u00e2ne un specialist c\u0103utat, trebuie s\u0103 dob\u00e2nde\u0219ti abilit\u0103\u021bi actuale - s\u0103 \u00eenve\u021bi m\u0103car un limbaj de programare, de exemplu Python. Persoanei care se ocup\u0103 profesional de administrare i se poate p\u0103rea dificil, deoarece este obi\u0219nuit s\u0103 cread\u0103 c\u0103 doar dezvoltatorii programeaz\u0103. Nu trebuie neap\u0103rat s\u0103 devii expert, totu\u0219i, cunoa\u0219terea unui limbaj de programare (poate fi Python, Bash sau chiar Powershell<\/a><\/noindex>), f\u0103r\u0103 \u00eendoial\u0103, va fi un avantaj.<\/p>\n

Pentru a \u00eenv\u0103\u021ba s\u0103 programezi, ai nevoie de ceva timp. Fii atent \u0219i r\u0103bd\u0103tor \u2014 acest lucru te va ajuta s\u0103 men\u021bii o bun\u0103 \u00een\u021belegere a situa\u021biei atunci c\u00e2nd comunici cu dezvoltatorii din echipa DevOps \u0219i cu clien\u021bii. O jum\u0103tate de or\u0103 pe zi, o or\u0103 sau mai mult \u2014 studiul unui limbaj de programare ar trebui s\u0103 devin\u0103 principalul t\u0103u obiectiv.<\/p>\n

Administratorii de sistem \u0219i speciali\u0219tii DevOps rezolv\u0103 probleme similare, \u00eens\u0103 exist\u0103 \u0219i o diferen\u021b\u0103 semnificativ\u0103. Se consider\u0103 c\u0103 un administrator de sistem nu poate face tot ceea ce poate face un inginer DevOps. Se spune c\u0103 administratorul este mai concentrat pe configurarea, \u00eentre\u021binerea \u0219i asigurarea func\u021bion\u0103rii sistemelor server, pe c\u00e2nd inginerul DevOps se ocup\u0103 de tot acest lucru \u0219i \u00eenc\u0103 pu\u021bin.<\/p>\n

Dar c\u00e2t de adev\u0103rat este acest lucru?<\/p>\n

Administrator de sistem: singur \u00een c\u00e2mp este r\u0103zboinic<\/h3>\n

\n\u00cen ciuda distin\u021bilor deosebiri \u0219i asem\u0103n\u0103ri men\u021bionate \u00een acest articol, consider c\u0103 \u00eentre administrarea sistemelor \u0219i DevOps nu exist\u0103 o diferen\u021b\u0103 semnificativ\u0103. Administratorii de sistem au realizat \u00eentotdeauna acelea\u0219i func\u021bii ca \u0219i speciali\u0219tii DevOps, doar c\u0103 \u00eenainte nimeni nu le numea DevOps. Cred c\u0103 nu are sens s\u0103 c\u0103ut\u0103m cu tot dinadinsul diferen\u021be, mai ales dac\u0103 acestea nu sunt legate de o anumit\u0103 sarcin\u0103. Nu trebuie s\u0103 uit\u0103m nici de faptul c\u0103, spre deosebire de administratorul de sistem, DevOps nu este un post, ci o conceptie.<\/p>\n

Trebuie s\u0103 men\u021bion\u0103m \u00eenc\u0103 un lucru important, f\u0103r\u0103 de care discu\u021bia despre administrare \u0219i DevOps va fi incomplet\u0103. Administrarea sistemelor, \u00een sensul s\u0103u obi\u0219nuit, presupune ca specialistul s\u0103 aib\u0103 un set specific de abilit\u0103\u021bi \u0219i s\u0103 fie orientat spre \u00eentre\u021binerea diverselor tipuri de infrastructur\u0103. Nu \u00een sensul c\u0103 acesta este un angajat universal, ci \u00een acela c\u0103 exist\u0103 o serie de sarcini \u00eendeplinite de to\u021bi administratorii.<\/p>\n

De exemplu, ace\u0219tia trebuie, din c\u00e2nd \u00een c\u00e2nd, s\u0103 joace rolul unui fel de muncitor tehnic, adic\u0103 s\u0103 fac\u0103 literalmente totul. \u0218i dac\u0103 un astfel de administrator este singurul din \u00eentreaga organiza\u021bie, el va efectua \u00eentr-adev\u0103r toat\u0103 munca tehnic\u0103. Aceasta poate fi orice: de la \u00eentre\u021binerea imprimantelor \u0219i copiatoarelor p\u00e2n\u0103 la \u00eendeplinirea sarcinilor legate de re\u021bea, cum ar fi configurarea \u0219i gestionarea routerelor \u0219i switch-urilor sau configurarea firewall-ului.<\/p>\n

El va r\u0103spunde, de asemenea, pentru actualizarea hardware-ului, verificarea \u0219i analiza jurnalelor, auditul de securitate, instalarea patch-urilor pe server, depanarea, analiza cauzelor principale \u0219i automatizarea \u2014 de obicei, prin scripturi PowerShell, Python sau Bash. Un exemplu de utilizare scripturi<\/a><\/noindex> este gestionarea conturilor de utilizator \u0219i a grupurilor. Crearea conturilor de utilizator \u0219i atribuirea permisiunilor este o sarcin\u0103 extrem de obositoare, deoarece utilizatorii apar \u0219i dispar aproape \u00een fiecare zi. Automatizarea prin scripturi permite economisirea timpului pentru a se ocupa de sarcini infrastructurale mai importante, cum ar fi actualizarea switch-urilor \u0219i serverelor \u0219i realizarea altor proiecte care afecteaz\u0103 rentabilitatea companiei \u00een care admininstratorul lucreaz\u0103 (de\u0219i se consider\u0103 c\u0103 departamentul IT nu aduce venituri direct).<\/p>\n

Sarcina administratorului de sistem este de a nu pierde timpul \u0219i de a economisi bani companiei \u00een orice mod posibil. Uneori, administratorii de sistem lucreaz\u0103 ca membri ai unei echipe mari care reune\u0219te, de exemplu, administratorii de Linux, Windows, baze de date, stocare \u0219i altele. Programul de lucru poate varia. De exemplu, o tur\u0103 dintr-o zon\u0103 orar\u0103 la sf\u00e2r\u0219itul zilei pred\u0103 treburile turei urm\u0103toare dintr-o alt\u0103 zon\u0103 orar\u0103, pentru ca procesele s\u0103 nu se opreasc\u0103 (follow-the-sun); sau angaja\u021bii au o zi obi\u0219nuit\u0103 de lucru de la 9 la 5; sau este vorba de munc\u0103 \u00eentr-un centru de date care func\u021bioneaz\u0103 24\/7.<\/p>\n

Administratorii de sistem au \u00eenv\u0103\u021bat \u00een timp s\u0103 g\u00e2ndeasc\u0103 strategic \u0219i s\u0103 \u00eembine sarcinile importante cu cele de rutin\u0103. Echipele \u0219i departamentele \u00een care lucreaz\u0103 de obicei resimt lipsa de resurse, dar to\u021bi \u00eencearc\u0103 s\u0103 execute sarcinile zilnice \u00een \u00eentregime.<\/p>\n

DevOps: dezvoltare \u0219i \u00eentre\u021binere comune<\/h3>\n

\nDevOps<\/a><\/noindex> este o filozofie de proces pentru dezvoltare \u0219i \u00eentre\u021binere. Aceast\u0103 abordare \u00een lumea IT a devenit cu adev\u0103rat inovatoare. <\/p>\n

Sub egida DevOps se afl\u0103, pe de o parte, echipa de dezvoltatori de software, iar pe de alta, echipa de speciali\u0219ti \u00een operare. Adesea, la ei se al\u0103tur\u0103 speciali\u0219ti \u00een managementul de produs, teste \u0219i design de interfa\u021b\u0103 utilizator. Unind eforturile, aceste speciali\u0219ti optimizeaz\u0103 opera\u021biunile de lucru pentru a lansa rapid aplica\u021bii noi \u0219i a actualiza codul, av\u00e2nd ca scop \u00eentre\u021binerea \u0219i \u00eembun\u0103t\u0103\u021birea eficien\u021bei organiza\u021biei.<\/p>\n

La baza DevOps se afl\u0103 controlul dezvolt\u0103rii \u0219i func\u021bion\u0103rii software-ului pe parcursul \u00eentregului s\u0103u ciclu de via\u021b\u0103. Speciali\u0219tii \u00een operare trebuie s\u0103 sprijine dezvoltatorii, iar sarcina dezvoltatorilor este s\u0103 \u00een\u021beleag\u0103 nu doar API-urile utilizate \u00een sisteme. Ei trebuie s\u0103 \u00een\u021beleag\u0103 ceea ce se afl\u0103 \u201esub capot\u0103\u201d (adic\u0103 cum func\u021bioneaz\u0103 hardware-ul \u0219i sistemele de operare), pentru a face fa\u021b\u0103 mai bine erorilor, a rezolva problemele \u0219i a colabora cu speciali\u0219tii \u00een operare.<\/p>\n

Administratorii de sistem pot face tranzi\u021bia c\u0103tre echipa DevOps dac\u0103 doresc s\u0103 \u00eenve\u021be cele mai noi tehnologii \u0219i sunt deschi\u0219i la idei \u0219i solu\u021bii inovatoare. A\u0219a cum am men\u021bionat, nu este necesar s\u0103 devin\u0103 programatori comple\u021bi, \u00eens\u0103 st\u0103p\u00e2nirea limbajelor de programare, precum Ruby, Python sau Go, \u00eei va ajuta s\u0103 devin\u0103 membri foarte valoro\u0219i ai echipei. De\u0219i administratorii de sistem, \u00een mod tradi\u021bional, \u00eendeplinesc toate sarcinile pe cont propriu \u0219i sunt adesea percepu\u021bi ca fiind solitari, \u00een DevOps ei vor experimenta exact opusul, c\u00e2nd to\u021bi participan\u021bii interac\u021bioneaz\u0103 unii cu al\u021bii.<\/p>\n

Tema automatiz\u0103rii devine din ce \u00een ce mai relevant\u0103. At\u00e2t administratorii de sistem, c\u00e2t \u0219i speciali\u0219tii DevOps sunt interesa\u021bi de scalarea opera\u021bional\u0103, reducerea num\u0103rului de erori \u0219i de identificarea \u0219i remedierea rapid\u0103 a problemelor existente. Astfel, automatizarea este un concept unde cele dou\u0103 domenii converg. Administratorii de sistem sunt responsabili pentru servicii cloud precum AWS, Azure \u0219i Google Cloud Platform. Ei trebuie s\u0103 \u00een\u021beleag\u0103 principiile integr\u0103rii \u0219i livr\u0103rii continue \u0219i cum s\u0103 utilizeze \u00een activitatea lor instrumente de tipul Jenkins<\/a><\/noindex>.<\/p>\n

\u00cen plus, administratorii de sistem trebuie s\u0103 aplice instrumente de configurare \u0219i management precum Ansible<\/a><\/noindex>, necesare pentru desf\u0103\u0219urarea paralel\u0103 a zece sau dou\u0103zeci de servere.<\/p>\n

Conceptul principal este infrastructura ca cod<\/a><\/noindex>. Software \u00een toate. Practic, pentru ca profesia de administrator de sistem s\u0103 r\u0103m\u00e2n\u0103 relevant\u0103, este necesar s\u0103 schimbi doar pu\u021bin accentul. Administratorii de sistem se ocup\u0103 cu \u00eentre\u021binerea \u0219i trebuie s\u0103 fie capabili s\u0103 interac\u021bioneze eficient cu dezvoltatorii \u0219i invers. A\u0219a cum se spune, o minte este bun\u0103, dar dou\u0103 sunt mai bune.<\/p>\n

\u0218i ultima detaliere \u00een acest mecanism este Git<\/a><\/noindex>. Lucrul cu Git este una dintre responsabilit\u0103\u021bile tradi\u021bionale zilnice ale administratorului de sistem. Aceast\u0103 sistem\u0103 de gestionare a versiunilor este folosit\u0103 pe scar\u0103 larg\u0103 de dezvoltatori, speciali\u0219ti DevOps, echipe Agile \u0219i mul\u021bi al\u021bii. Dac\u0103 munca ta este legat\u0103 de ciclul de via\u021b\u0103 al software-ului, atunci cu siguran\u021b\u0103 vei lucra cu Git.<\/p>\n

Git are multe posibilit\u0103\u021bi. Cel mai probabil, nu vei \u00eenv\u0103\u021ba niciodat\u0103 toate comenzile Git, dar cu siguran\u021b\u0103 vei \u00een\u021belege de ce acest instrument este considerat principalul \u00een comunicarea \u0219i colaborarea asupra software-ului. Cunoa\u0219terea temeinic\u0103 a Git este extrem de important\u0103 dac\u0103 lucrezi \u00eentr-o echip\u0103 DevOps.<\/p>\n

Dac\u0103 e\u0219ti administrator de sistem, trebuie s\u0103 \u00eenve\u021bi mai bine Git, s\u0103 \u00een\u021belegi cum se construie\u0219te gestionarea versiunilor \u0219i s\u0103 memorezi comenzile frecvente: git status, git commit -m, git add, git pull, git push, git rebase, git branch, git diff <\/b>\u0219i altele. Exist\u0103 multe cursuri online \u0219i c\u0103r\u021bi care te vor ajuta s\u0103 \u00eenve\u021bi acest subiect de la zero \u0219i s\u0103 devii un profesionist cu abilit\u0103\u021bi specifice. Exist\u0103, de asemenea, minunata schem\u0103 de comenzi Git<\/a><\/noindex>, a\u0219a c\u0103 nu trebuie s\u0103 le memorezi pe toate, dar cu c\u00e2t folose\u0219ti mai mult Git, cu at\u00e2t va fi mai u\u0219or pentru tine.<\/p>\n

Concluzie<\/h3>\n

\n\u00cen cele din urm\u0103, tu decizi dac\u0103 vrei s\u0103 devii specialist DevOps sau s\u0103 r\u0103m\u00e2i administrator de sistem. A\u0219a cum vezi, pentru a face tranzi\u021bia este necesar s\u0103 te educi, dar cu c\u00e2t \u00eencepi mai devreme, cu at\u00e2t mai bine. Alege un limbaj de programare \u0219i \u00eenva\u021b\u0103 \u00een paralel instrumente precum Git<\/a><\/noindex> (controlul versiunilor), Jenkins<\/a><\/noindex> (CI\/CD, integrare continu\u0103) \u0219i Ansible<\/a><\/noindex> (configurare \u0219i automatizare). Indiferent de op\u021biunea pe care o alegi, nu uita c\u0103 trebuie s\u0103 continui s\u0103 \u00eenve\u021bi \u0219i s\u0103-\u021bi \u00eembun\u0103t\u0103\u021be\u0219ti abilit\u0103\u021bile.
\n
Sursa: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u0414\u043b\u044f \u043e\u0431\u0443\u0447\u0435\u043d\u0438\u044f \u0432 \u0436\u0438\u0437\u043d\u0438 \u043d\u0435\u0442 \u043b\u0443\u0447\u0448\u0435\u0433\u043e \u0432\u0440\u0435\u043c\u0435\u043d\u0438, \u0447\u0435\u043c \u0441\u0435\u0433\u043e\u0434\u043d\u044f. \u041d\u0430 \u0434\u0432\u043e\u0440\u0435 2019 \u0433\u043e\u0434, \u0438 \u0442\u0435\u043c\u0430 DevOps \u0441\u0435\u0439\u0447\u0430\u0441 \u0430\u043a\u0442\u0443\u0430\u043b\u044c\u043d\u0430, \u043a\u0430\u043a \u043d\u0438\u043a\u043e\u0433\u0434\u0430. \u0413\u043e\u0432\u043e\u0440\u044f\u0442, \u0447\u0442\u043e \u0434\u043d\u0438 \u0441\u0438\u0441\u0442\u0435\u043c\u043d\u044b\u0445 \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0430\u0442\u043e\u0440\u043e\u0432 \u043f\u0440\u043e\u0448\u043b\u0438, \u043a\u0430\u043a \u043c\u0438\u043d\u043e\u0432\u0430\u043b\u0430 \u044d\u043f\u043e\u0445\u0430 \u043c\u0435\u0439\u043d\u0444\u0440\u0435\u0439\u043c\u043e\u0432. \u041d\u043e \u0442\u0430\u043a \u043b\u0438 \u044d\u0442\u043e \u043d\u0430 \u0441\u0430\u043c\u043e\u043c \u0434\u0435\u043b\u0435? \u041a\u0430\u043a \u044d\u0442\u043e \u0447\u0430\u0441\u0442\u043e \u0431\u044b\u0432\u0430\u0435\u0442 \u0432 IT, \u0441\u0438\u0442\u0443\u0430\u0446\u0438\u044f \u0438\u0437\u043c\u0435\u043d\u0438\u043b\u0430\u0441\u044c. \u041f\u043e\u044f\u0432\u0438\u043b\u0430\u0441\u044c \u043c\u0435\u0442\u043e\u0434\u043e\u043b\u043e\u0433\u0438\u044f DevOps, \u043d\u043e \u043e\u043d\u0430 \u043d\u0435 \u043c\u043e\u0436\u0435\u0442 \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u043e\u0432\u0430\u0442\u044c \u0431\u0435\u0437 \u0447\u0435\u043b\u043e\u0432\u0435\u043a\u0430 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":27910,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-37221","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"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\udd47De ce administratorii de sistem ar trebui s\u0103 devin\u0103 ingineri DevOps | ProHoster","description":"Pentru.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/pochemu-sistemnye-administratory-dolzhny-stanovitsya-devops-inzhenerami","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\u041f\u043e\u0447\u0435\u043c\u0443 \u0441\u0438\u0441\u0442\u0435\u043c\u043d\u044b\u0435 \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0430\u0442\u043e\u0440\u044b \u0434\u043e\u043b\u0436\u043d\u044b \u0441\u0442\u0430\u043d\u043e\u0432\u0438\u0442\u044c\u0441\u044f DevOps-\u0438\u043d\u0436\u0435\u043d\u0435\u0440\u0430\u043c\u0438 | ProHoster","og:description":"\u0414\u043b\u044f.","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/pochemu-sistemnye-administratory-dolzhny-stanovitsya-devops-inzhenerami","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:16:24+00:00","article:modified_time":"2019-10-31T19:16:24+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37221","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 16:48:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:31:24","updated":"2026-01-23 16:48:19","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\/37221","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=37221"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/37221\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/27910"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=37221"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=37221"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=37221"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}