{"id":37684,"date":"2019-10-31T22:19:05","date_gmt":"2019-10-31T19:19:05","guid":{"rendered":"https:\/\/prohoster.info\/blog\/zachem-nuzhen-devops-i-kto-takie-devops-spetsialisty\/"},"modified":"2019-10-31T22:19:05","modified_gmt":"2019-10-31T19:19:05","slug":"zachem-nuzhen-devops-i-kto-takie-devops-spetsialisty","status":"publish","type":"post","link":"https:\/\/prohoster.info\/lv\/blog\/administrirovanie\/zachem-nuzhen-devops-i-kto-takie-devops-spetsialisty","title":{"rendered":"K\u0101p\u0113c nepiecie\u0161ams DevOps un kas ir DevOps speci\u0101listi","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Kad programma nefunkcion\u0113, vismaz ko nev\u0113lies dzird\u0113t no kol\u0113\u0123iem, ir fr\u0101ze \"probl\u0113ma ir j\u016bsu pus\u0113\". Rezult\u0101t\u0101 cie\u0161 lietot\u0101ji \u2013 un vi\u0146iem ir vienalga, kura komandas da\u013ca ir atbild\u012bga par trauc\u0113jumiem. DevOps kult\u016bra rad\u0101s tie\u0161i t\u0101p\u0113c, lai salied\u0113tu izstr\u0101di un atbalstu un apvienotu tos kop\u012bg\u0101 atbild\u012bb\u0101 par gala produktu.<\/p>\n

K\u0101das prakses iek\u013caujas DevOps j\u0113dzien\u0101 un k\u0101p\u0113c t\u0101s ir nepiecie\u0161amas? Ar ko nodarbojas DevOps in\u017eenieri un ko vi\u0146i j\u0101prot? Uz \u0161iem un citiem jaut\u0101jumiem atbild eksperti no EPAM: Kirils Sergejevs, sist\u0113mu in\u017eenieris un DevOps eva\u0146\u0123\u0113lists, un Igors Boiko, vado\u0161ais sist\u0113mu in\u017eenieris un vienas no DevOps komand\u0101m koordinators uz\u0146\u0113mum\u0101.<\/p>\n

\"K\u0101p\u0113c
\n<\/a><\/noindex><\/p>\n

K\u0101p\u0113c nepiecie\u0161ams DevOps?<\/h3>\n

\nAgr\u0101k starp izstr\u0101d\u0101t\u0101jiem un atbalsta (t. i., operations) darbiniekiem past\u0101v\u0113ja barjera. Izklaus\u0101s paradoks\u0101li, bet vi\u0146iem bija da\u017e\u0101di m\u0113r\u0137i un KPI, lai gan vi\u0146i veica kop\u012bgu uzdevumu. Izstr\u0101des m\u0113r\u0137is bija p\u0113c iesp\u0113jas \u0101tr\u0101k \u012bstenot biznesa pras\u012bbas un pievienot t\u0101s str\u0101d\u0101jo\u0161am produktam. Atbalsts atbild\u0113ja par to, lai programma stabil\u0101 darbotos \u2013 un jebkuras izmai\u0146as apdraud stabilit\u0101ti. Redzama intere\u0161u konflikta rezult\u0101t\u0101 \u2013 DevOps rad\u0101s, lai to atrisin\u0101tu.<\/p>\n

Kas ir DevOps?<\/h3>\n

\nJaut\u0101jums ir labs \u2013 un str\u012bd\u012bgs: pasaul\u0113 par to v\u0113l nav pan\u0101kta vieno\u0161an\u0101s. EPAM uzskata, ka DevOps apvieno tehnolo\u0123ijas, procesus un komandas sadarb\u012bbas kult\u016bru. \u0160\u012b apvieno\u0161ana ir v\u0113rsta uz v\u0113rt\u012bbu nep\u0101rtrauktu pieg\u0101di gala lietot\u0101jiem.<\/p>\n

Kirils Sergejevs<\/b>: \"Izstr\u0101d\u0101t\u0101ji raksta kodu, test\u0113t\u0101ji to p\u0101rbauda, bet administratori instal\u0113 gala produktu ra\u017eo\u0161anas vid\u0113. Ilgu laiku \u0161\u012bs komandas da\u013cas bija diezgan atdal\u012btas, bet p\u0113c tam rad\u0101s ideja t\u0101s apvienot kop\u012bg\u0101 proces\u0101. T\u0101d\u0113j\u0101di rad\u0101s DevOps prakses.\"<\/p>\n

Ir pien\u0101cis tas br\u012bdis, kad izstr\u0101d\u0101t\u0101ji un sist\u0113mu in\u017eenieri s\u0101ka interes\u0113ties par citu darbu. Barjera starp ra\u017eo\u0161anu un atbalstu s\u0101ka dzist. T\u0101d\u0113j\u0101di rad\u0101s DevOps, kas ietver prakses, kult\u016bru un sadarb\u012bbas k\u0101rt\u012bbu komand\u0101.<\/p>\n

\"K\u0101p\u0113c
\n<\/p>\n

K\u0101ds ir DevOps kult\u016bras pamats?<\/h3>\n

\nAt the core, the responsibility for the final outcome rests with each member of the team. The most interesting and complex aspect of DevOps philosophy is realizing that an individual is not just responsible for their particular phase of work, but for how the entire product will function. The issue does not lie on anyone\u2019s side \u2013 it is a shared challenge, and every team member contributes to its resolution.<\/p>\n

A fundamental aspect of DevOps culture is addressing problems, not just applying DevOps practices. Moreover, these practices are not implemented 'on someone\u2019s side' but throughout the entire product. A project does not merely need a DevOps engineer; it requires a solution to a problem, and the role of a DevOps engineer can be distributed among several team members with different specializations.<\/p>\n

What DevOps practices exist?<\/h3>\n

\nDevOps practices encompass all stages of the software lifecycle.<\/p>\n

Igors Boiko<\/b>: 'The ideal scenario is to start using DevOps practices right at the project initiation. Along with the architects, we plan what the architectural landscape of the application will be, where it will be located, and how it will scale, choosing the platform. Currently, microservices architecture is in vogue \u2013 we select an orchestration system for it: it is necessary to manage each component of the application independently and update it without affecting others. Another practice is \u201cinfrastructure as code\u201d. This refers to an approach where the project\u2019s infrastructure is created and managed through code rather than direct interaction with servers.<\/p>\n

Next, we move on to the development stage. Here, one of the largest practices is building CI\/CD: we need to help developers integrate changes into the product quickly, in small increments, more frequently and with less pain. CI\/CD encompasses code checking, merging to the master branch, and deploying the application in testing and production environments.<\/p>\n

At the CI\/CD stages, the code goes through quality gates. These are used to ensure that the code released from the developer's workstation meets the specified quality criteria. Unit testing and UI testing are introduced here. For rapid, painless, and focused product deployment, an appropriate type of deployment can be selected.<\/p>\n

DevOps praks\u0113m ir vieta ar\u012b atbalsta posm\u0101, kad produkts ir gatavs. T\u0101s tiek izmantotas uzraudz\u012bbai, atgriezeniskajai saitei, dro\u0161\u012bbai un izmai\u0146u ievie\u0161anai. DevOps uz \u0161iem uzdevumiem skat\u0101s k\u0101 b\u016btisk\u0101m uzlabo\u0161anas iesp\u0113j\u0101m. M\u0113s cen\u0161amies samazin\u0101t atk\u0101rtotas darb\u012bbas un automatiz\u0113t t\u0101s. \u0160eit ietilpst ar\u012b migr\u0101cijas, lietotnes papla\u0161in\u0101\u0161ana, k\u0101 ar\u012b darba sp\u0113jas uztur\u0113\u0161ana.<\/p>\n

K\u0101das priek\u0161roc\u012bbas sniedz DevOps prakses?<\/h3>\n

\nJa m\u0113s rakst\u012btu m\u0101c\u012bbu gr\u0101matu par m\u016bsdienu DevOps praks\u0113m, t\u0101s pirmaj\u0101 lap\u0101 tiktu iek\u013cauti tr\u012bs punkti: automatiz\u0101cija, izlai\u0161anas pa\u0101trin\u0101\u0161ana un \u0101tra atgriezenisk\u0101 saite no lietot\u0101jiem.<\/p>\n

Kirils Sergejevs<\/b>: \"Pirmais punkts \u2013 automatiz\u0101cija. M\u0113s varam automatiz\u0113t visu sadarb\u012bbu komand\u0101: uzrakst\u012bj\u0101m kodu \u2013 izlaides \u2013 p\u0101rbaud\u012bj\u0101m \u2013 instal\u0113j\u0101m \u2013 apkopoju\u0161i atsauksmes \u2013 atgriez\u0101mies s\u0101kum\u0101. Viss \u0161is process tiek veikts autom\u0101tiski.<\/p>\n

Otrais punkts \u2013 izlai\u0161anas pa\u0101trin\u0101\u0161ana un pat izstr\u0101des vienk\u0101r\u0161o\u0161ana. Pas\u016bt\u012bt\u0101jam vienm\u0113r ir svar\u012bgi, lai produkts non\u0101ktu tirg\u016b p\u0113c iesp\u0113jas \u0101tr\u0101k un s\u0101ktu g\u016bt ieguvumus agr\u0101k nek\u0101 konkurentu analogi. Produkta pieg\u0101des procesu var bezgal\u012bgi uzlabot: sa\u012bsin\u0101t laiku, pievienot papildu kontroles punktus, pilnveidot uzraudz\u012bbu.<\/p>\n

Tre\u0161ais punkts \u2013 \u0101tr\u0101ka atgriezenisk\u0101 saite no lietot\u0101jiem. Ja lietot\u0101jam ir piez\u012bmes, m\u0113s varam nekav\u0113joties veikt labojumus un t\u016bl\u012bt atjaunin\u0101t lietotni.<\/p>\n

\"K\u0101p\u0113c
\n<\/p>\n

K\u0101 sapl\u016bst j\u0113dzieni \"sist\u0113mu in\u017eenieris\", \"build in\u017eenieris\" un \"DevOps in\u017eenieris\"?<\/h3>\n

\nTie p\u0101rkl\u0101jas, bet attiecas uz nedaudz at\u0161\u0137ir\u012bg\u0101m jom\u0101m.<\/p>\n

Sist\u0113mu in\u017eenieris uz\u0146\u0113mum\u0101 EPAM ir amats. Tie ir da\u017e\u0101dos l\u012bme\u0146os: no junior l\u012bdz Chief Specialist.<\/p>\n

Build in\u017eenieris ir dr\u012bz\u0101k loma, kuru var veikt projekt\u0101. Pa\u0161laik t\u0101 sauc cilv\u0113kus, kas ir atbild\u012bgi par CI\/CD.<\/p>\n

DevOps in\u017eenieris ir speci\u0101lists, kur\u0161 projekt\u0101 ievie\u0161 DevOps prakses.<\/p>\n

Ja visu to apkopojam, san\u0101k sekojo\u0161ais: cilv\u0113ks, kas ie\u0146em sist\u0113mu in\u017eeniera amatu, projekt\u0101 veic build in\u017eeniera lomu un nodarbojas ar DevOps prak\u0161u ievie\u0161anu.<\/p>\n

Ar ko tie\u0161i nodarbojas DevOps in\u017eenieris?<\/h3>\n

\nDevOps in\u017eenieri apvieno visas projekta sast\u0101vda\u013cas. Vi\u0146i p\u0101rzina programm\u0113t\u0101ju, test\u0113t\u0101ju un sist\u0113mu administratoru darba specifiku un pal\u012bdz vienk\u0101r\u0161ot vi\u0146u darbu. Vi\u0146i izprot biznesa vajadz\u012bbas un pras\u012bbas, t\u0101 lomu izstr\u0101des proces\u0101, un veido procesu, \u0146emot v\u0113r\u0101 pas\u016bt\u012bt\u0101ja intereses.<\/p>\n

M\u0113s daudz run\u0101j\u0101m par automatiz\u0101ciju \u2013 ar to DevOps in\u017eenieri nodarbojas vispirms. Tas ir \u013coti b\u016btisks punkts, kur\u0101, starp citu, ietilpst apk\u0101rtnes sagatavo\u0161ana.<\/p>\n

Kirils Sergejevs<\/b>: \"Pirms atjaunin\u0101jumu ievie\u0161anas produkt\u0101, tos nepiecie\u0161ams p\u0101rbaud\u012bt tre\u0161\u0101s puses vid\u0113. To sagatavo DevOps in\u017eenieri. Vi\u0146i ar\u012b ievie\u0161 DevOps kult\u016bru projekt\u0101 kopum\u0101: ievie\u0161 DevOps prakses visos savus projektu sl\u0101\u0146os. \u0160ie tr\u012bs principi: automatiz\u0101cija, vienk\u0101r\u0161o\u0161ana, pa\u0101trin\u0101\u0161ana \u2013 tie tiek ieviesti visur, kur vi\u0146i var sasniegt.\"<\/p>\n

Ko b\u016btu j\u0101zina DevOps in\u017eenierim?<\/h3>\n

\nPamat\u0101 vi\u0146am j\u0101b\u016bt zin\u0101\u0161an\u0101m no da\u017e\u0101d\u0101m jom\u0101m: programm\u0113\u0161ana, darbs ar oper\u0113t\u0101jsist\u0113m\u0101m, datu b\u0101z\u0113m, kompil\u0101cijas un konfigur\u0101cijas sist\u0113m\u0101m. Tam pievienojas prasmes str\u0101d\u0101t ar m\u0101ko\u0146a infrastrukt\u016bru, or\u0137estr\u0101cijas un uzraudz\u012bbas sist\u0113m\u0101m.<\/p>\n

1. Programm\u0113\u0161anas valodas<\/b><\/p>\n

DevOps in\u017eenieri p\u0101rvalda vair\u0101kas pamata valodas automatiz\u0101cijai un var, piem\u0113ram, teikt programm\u0113t\u0101jam: \"Varb\u016bt tu dar\u012bsi koda uzst\u0101d\u012b\u0161anu nevis manu\u0101li, bet gan ar m\u016bsu skriptu, kas visu automatiz\u0113? M\u0113s sagatavosim tam config failu, kur\u0161 b\u016bs \u0113rti las\u0101ms gan tev, gan mums \u2013 un m\u0113s jebkur\u0101 br\u012bd\u012b var\u0113sim to main\u012bt. Un v\u0113l m\u0113s redz\u0113sim, kur\u0161, kad un k\u0101d\u0113\u013c veic izmai\u0146as taj\u0101.\"<\/p>\n

DevOps in\u017eenieris var apg\u016bt vienu vai vair\u0101kas no \u0161\u012bm valod\u0101m: Python, Groovy, Bash, Powershell, Ruby, Go. Nav nepiecie\u0161ams t\u0101s zin\u0101t dzi\u013c\u0101 l\u012bmen\u012b \u2013 pietiek ar pamatiem sintaks\u0113, OOP principiem, sp\u0113j\u0101m uzrakst\u012bt vienk\u0101r\u0161us skriptus automatiz\u0101cijai.<\/p>\n

2. Oper\u0113t\u0101jsist\u0113mas<\/b><\/p>\n

DevOps in\u017eenierim j\u0101izprot, uz k\u0101 servera tiks uzst\u0101d\u012bts produkts, k\u0101d\u0101 vid\u0113 tas darbosies, ar k\u0101d\u0101m pakalpojumiem tas mijiedarbosies. Var izv\u0113l\u0113ties specializ\u0101ciju uz Windows vai Linux \u0123imen\u0113.<\/p>\n

3. Versiju kontroles sist\u0113mas<\/b><\/p>\n

Bez zin\u0101\u0161an\u0101m par versiju kontroles sist\u0113m\u0101m DevOps in\u017eenierim nav kur doties. Git \u2013 \u0161obr\u012bd viena no popul\u0101r\u0101kaj\u0101m sist\u0113m\u0101m.<\/p>\n

4. M\u0101ko\u0146u pakalpojumu sniedz\u0113ji<\/b><\/p>\n

AWS, Google, Azure \u2013 \u012bpa\u0161i, ja m\u0113s run\u0101jam par Windows virzienu.<\/p>\n

Kirils Sergejevs<\/b>: \u00abM\u0101ko\u0146u pakalpojumu sniedz\u0113ji pied\u0101v\u0101 mums virtu\u0101los serverus<\/a>, kas lieliski iek\u013caujas CI\/CD sist\u0113m\u0101s.<\/p>\n

Desmit instal\u0113\u0161ana fizisko serveru<\/a> prasa apm\u0113ram simts manu\u0101las darb\u012bbas. Katru serveri ir j\u0101palai\u017e, j\u0101instal\u0113 un j\u0101iestata nepiecie\u0161am\u0101 oper\u0113t\u0101jsist\u0113ma, j\u0101instal\u0113 m\u016bsu lietotne uz \u0161iem desmit serveriem un p\u0113c tam desmit reizes j\u0101veic visi p\u0101rbaudes. M\u0101ko\u0146u pakalpojumi aizvieto \u0161o proced\u016bru ar desmit koda rind\u0101m, un labam DevOps in\u017eenierim j\u0101sp\u0113j \u0161\u012bs iesp\u0113jas izmantot. T\u0101d\u0113j\u0101di vi\u0146\u0161 ietaupa laiku, p\u016bles un naudu \u2013 gan pas\u016bt\u012bt\u0101jam, gan uz\u0146\u0113mumam\u00bb.<\/p>\n

5. Orkestr\u0101cijas sist\u0113mas: Docker un Kubernetes<\/b><\/p>\n

Kirils Sergejevs<\/b>: \u00abVirtu\u0101lie serveri tiek sadal\u012bti konteineros, kuru katr\u0101 m\u0113s varam instal\u0113t m\u016bsu lietotni. Kad konteineru ir daudz, ir nepiecie\u0161ama to p\u0101rvald\u012b\u0161ana: vienu iesl\u0113gt, otru izsl\u0113gt, kaut kur veikt dubl\u0113jumus. Tas k\u013c\u016bst diezgan sare\u017e\u0123\u012bti, t\u0101p\u0113c ir nepiecie\u0161ama orkestr\u0101cijas sist\u0113ma.<\/p>\n

Agr\u0101k katru lietotni apkalpoja atsevi\u0161\u0137s serveris \u2013 jebkuras izmai\u0146as t\u0101s darb\u012bb\u0101 var\u0113ja ietekm\u0113t lietotnes darb\u012bbu. Pateicoties konteineriem, lietotnes k\u013c\u016bst izol\u0113tas un tiek palaistas atsevi\u0161\u0137i \u2013 katra sav\u0101 virtu\u0101laj\u0101 ma\u0161\u012bn\u0101. Ja notiek k\u013c\u016bme, nav nepiecie\u0161ams t\u0113r\u0113t laiku, lai mekl\u0113tu c\u0113lo\u0146us. Vienk\u0101r\u0161\u0101k ir izn\u012bcin\u0101t veco konteineru un pievienot jauno\u00bb.<\/p>\n

6. Konfigur\u0101cijas sist\u0113mas: Chef, Ansible, Puppet<\/b><\/p>\n

Kad ir nepiecie\u0161ams apkalpot visu serveru parku, j\u0101veic daudz l\u012bdz\u012bgu darb\u012bbu. Tas ir ilgs un sare\u017e\u0123\u012bts process, turkl\u0101t manu\u0101lais darbs palielina k\u013c\u016bdu iesp\u0113ju. \u0160eit n\u0101k pal\u012bg\u0101 konfigur\u0101cijas sist\u0113mas. Ar to pal\u012bdz\u012bbu izveido skriptu, kuru ir \u0113rti las\u012bt gan programm\u0113t\u0101jiem, gan DevOps in\u017eenieriem, gan sist\u0113mu administratoriem. \u0160is skripts pal\u012bdz autom\u0101tiski veikt vien\u0101das darb\u012bbas serveros. T\u0101d\u0113j\u0101di manu\u0101lo darb\u012bbu (un, l\u012bdz ar to, k\u013c\u016bdu) k\u013c\u016bst maz\u0101k.<\/p>\n

K\u0101du karjeru var veidot DevOps in\u017eenieris?<\/h3>\n

\nAtt\u012bst\u012bba var notikt gan horizont\u0101li, gan vertik\u0101li.<\/p>\n

Igors Boiko<\/b>: \u00abNo horizont\u0101l\u0101 att\u012bst\u012bbas viedok\u013ca DevOps in\u017eenieriem tagad ir vispla\u0161\u0101k\u0101s iesp\u0113jas. Viss past\u0101v\u012bgi main\u0101s, un prasmes var att\u012bst\u012bt visda\u017e\u0101d\u0101kajos virzienos: no versiju kontroles l\u012bdz monitor\u0113\u0161anai, no konfigur\u0101ciju p\u0101rvald\u012bbas l\u012bdz datub\u0101z\u0113m.<\/p>\n

Vai k\u013c\u016bt par sist\u0113mu arhitektu, ja darbiniekam interes\u0113 izprast, k\u0101 lietotne darbojas visos t\u0101s dz\u012bves cikla posmos \u2013 no izstr\u0101des l\u012bdz atbalstam.<\/p>\n

K\u0101 k\u013c\u016bt par DevOps in\u017eenieri?<\/h3>\n

<\/p>\n

    \n
  1. Izlasiet gr\u0101matas \u00abProjektu \u201cF\u0113nikss\u201d\u00bb un DevOps rokasgr\u0101matu. Tie ir patiesi DevOps filozofijas p\u012bl\u0101ri, pirm\u0101 ir m\u0101kslas rom\u0101ns.<\/li>\n
  2. Stud\u0113jiet tehnolo\u0123ijas no iepriek\u0161 min\u0113t\u0101 saraksta: patst\u0101v\u012bgi vai tie\u0161saistes kursos.<\/li>\n
  3. Pievienojieties k\u0101 DevOps in\u017eenieris atv\u0113rt\u0101 pirmkoda projektam.<\/li>\n
  4. Praktiz\u0113jiet un pied\u0101v\u0101jiet DevOps prakses savos personiskajos un darba projektos.<\/li>\n<\/ol>\n

    Avots: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

    \u041a\u043e\u0433\u0434\u0430 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0435 \u043d\u0435 \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442, \u043c\u0435\u043d\u044c\u0448\u0435 \u0432\u0441\u0435\u0433\u043e \u0445\u043e\u0447\u0435\u0442\u0441\u044f \u0443\u0441\u043b\u044b\u0448\u0430\u0442\u044c \u043e\u0442 \u043a\u043e\u043b\u043b\u0435\u0433 \u0444\u0440\u0430\u0437\u0443 \u00ab\u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u043d\u0430 \u0432\u0430\u0448\u0435\u0439 \u0441\u0442\u043e\u0440\u043e\u043d\u0435\u00bb. \u0412 \u0438\u0442\u043e\u0433\u0435 \u0441\u0442\u0440\u0430\u0434\u0430\u044e\u0442 \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u0438 \u2013 \u0430 \u0438\u043c \u0432\u0441\u0451 \u0440\u0430\u0432\u043d\u043e, \u043a\u0430\u043a\u0430\u044f \u0447\u0430\u0441\u0442\u044c \u043a\u043e\u043c\u0430\u043d\u0434\u044b \u043d\u0435\u0441\u0435\u0442 \u043e\u0442\u0432\u0435\u0442\u0441\u0442\u0432\u0435\u043d\u043d\u043e\u0441\u0442\u044c \u0437\u0430 \u043f\u043e\u043b\u043e\u043c\u043a\u0443. \u041a\u0443\u043b\u044c\u0442\u0443\u0440\u0430 DevOps \u043f\u043e\u044f\u0432\u0438\u043b\u0430\u0441\u044c \u043a\u0430\u043a \u0440\u0430\u0437 \u0437\u0430\u0442\u0435\u043c, \u0447\u0442\u043e\u0431\u044b \u0441\u043f\u043b\u043e\u0442\u0438\u0442\u044c \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0443 \u0438 \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u043a\u0443 \u0438 \u043e\u0431\u044a\u0435\u0434\u0438\u043d\u0438\u0442\u044c \u0438\u0445 \u0432\u043e\u043a\u0440\u0443\u0433 \u043e\u0431\u0449\u0435\u0439 \u043e\u0442\u0432\u0435\u0442\u0441\u0442\u0432\u0435\u043d\u043d\u043e\u0441\u0442\u0438 \u0437\u0430 \u043a\u043e\u043d\u0435\u0447\u043d\u044b\u0439 \u043f\u0440\u043e\u0434\u0443\u043a\u0442. \u041a\u0430\u043a\u0438\u0435 \u043f\u0440\u0430\u043a\u0442\u0438\u043a\u0438 \u0432\u0445\u043e\u0434\u044f\u0442 \u0432 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":28282,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-37684","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\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\udd47K\u0101p\u0113c nepiecie\u0161ams DevOps un kas ir DevOps speci\u0101listi | ProHoster","description":"Kad lietotne nedarbojas, vismaz\u0101k v\u0113laties dzird\u0113t no kol\u0113\u0123iem fr\u0101zi \u00abprobl\u0113ma j\u016bsu pus\u0113\u00bb. Rezult\u0101t\u0101 cie\u0161 lietot\u0101ji \u2013 un vi\u0146iem ir vienalga, kura komandas da\u013ca ir atbild\u012bga par av\u0101riju.","canonical_url":"https:\/\/prohoster.info\/lv\/blog\/administrirovanie\/zachem-nuzhen-devops-i-kto-takie-devops-spetsialisty","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"lv_LV","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\u0417\u0430\u0447\u0435\u043c \u043d\u0443\u0436\u0435\u043d DevOps \u0438 \u043a\u0442\u043e \u0442\u0430\u043a\u0438\u0435 DevOps-\u0441\u043f\u0435\u0446\u0438\u0430\u043b\u0438\u0441\u0442\u044b | ProHoster","og:description":"\u041a\u043e\u0433\u0434\u0430 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0435 \u043d\u0435 \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442, \u043c\u0435\u043d\u044c\u0448\u0435 \u0432\u0441\u0435\u0433\u043e \u0445\u043e\u0447\u0435\u0442\u0441\u044f \u0443\u0441\u043b\u044b\u0448\u0430\u0442\u044c \u043e\u0442 \u043a\u043e\u043b\u043b\u0435\u0433 \u0444\u0440\u0430\u0437\u0443 \u00ab\u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u043d\u0430 \u0432\u0430\u0448\u0435\u0439 \u0441\u0442\u043e\u0440\u043e\u043d\u0435\u00bb. \u0412 \u0438\u0442\u043e\u0433\u0435 \u0441\u0442\u0440\u0430\u0434\u0430\u044e\u0442 \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u0438 \u2013 \u0430 \u0438\u043c \u0432\u0441\u0451 \u0440\u0430\u0432\u043d\u043e, \u043a\u0430\u043a\u0430\u044f \u0447\u0430\u0441\u0442\u044c \u043a\u043e\u043c\u0430\u043d\u0434\u044b \u043d\u0435\u0441\u0435\u0442 \u043e\u0442\u0432\u0435\u0442\u0441\u0442\u0432\u0435\u043d\u043d\u043e\u0441\u0442\u044c \u0437\u0430 \u043f\u043e\u043b\u043e\u043c\u043a\u0443.","og:url":"https:\/\/prohoster.info\/lv\/blog\/administrirovanie\/zachem-nuzhen-devops-i-kto-takie-devops-spetsialisty","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:19:05+00:00","article:modified_time":"2019-10-31T19:19:05+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37684","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-02-09 16:46:30","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:22:29","updated":"2026-02-09 16:46:30","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/posts\/37684","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/comments?post=37684"}],"version-history":[{"count":2,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/posts\/37684\/revisions"}],"predecessor-version":[{"id":158512,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/posts\/37684\/revisions\/158512"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/media\/28282"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/media?parent=37684"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/categories?post=37684"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/tags?post=37684"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}