{"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\/cs\/blog\/administrirovanie\/zachem-nuzhen-devops-i-kto-takie-devops-spetsialisty","title":{"rendered":"Pro\u010d je DevOps pot\u0159ebn\u00fd a kdo jsou odborn\u00edci na DevOps","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Kdy\u017e aplikace nefunguje, nejm\u00e9n\u011b chcete sly\u0161et od koleg\u016f fr\u00e1zi \u201eprobl\u00e9m je na va\u0161\u00ed stran\u011b\u201c. V d\u016fsledku toho utrp\u00ed u\u017eivatel\u00e9 \u2013 a jim je jedno, kter\u00e1 \u010d\u00e1st t\u00fdmu nese odpov\u011bdnost za v\u00fdpadek. Kultura DevOps vznikla pr\u00e1v\u011b proto, aby spojila v\u00fdvoj a podporu a sjednotila je kolem spole\u010dn\u00e9 odpov\u011bdnosti za koncov\u00fd produkt.<\/p>\n

Jak\u00e9 praktiky pat\u0159\u00ed do pojmu DevOps a k \u010demu jsou pot\u0159ebn\u00e9? \u010c\u00edm se zab\u00fdvaj\u00ed DevOps in\u017een\u00fd\u0159i a co by m\u011bli um\u011bt? Na tyto a dal\u0161\u00ed ot\u00e1zky odpov\u00eddaj\u00ed odborn\u00edci z EPAM: Kirill Sergejev, syst\u00e9mov\u00fd in\u017een\u00fdr a DevOps evangelista, a Igor Bojko, vedouc\u00ed syst\u00e9mov\u00fd in\u017een\u00fdr a koordin\u00e1tor jednoho z DevOps t\u00fdm\u016f spole\u010dnosti.<\/p>\n

\"Pro\u010d
\n<\/a><\/noindex><\/p>\n

Pro\u010d je DevOps pot\u0159ebn\u00fd?<\/h3>\n

\nD\u0159\u00edve existovala mezi v\u00fdvoj\u00e1\u0159i a podporou (tzv. operations) bari\u00e9ra. Zn\u00ed to paradoxn\u011b, ale m\u011bli r\u016fzn\u00e9 c\u00edle a KPI, i kdy\u017e d\u011blali spole\u010dnou pr\u00e1ci. C\u00edlem v\u00fdvoje bylo co nejrychleji realizovat obchodn\u00ed po\u017eadavky a p\u0159idat je do funk\u010dn\u00edho produktu. Podpora byla odpov\u011bdn\u00e1 za stabiln\u00ed fungov\u00e1n\u00ed aplikace \u2013 a jak\u00e9koli zm\u011bny ohro\u017eovaly stabilitu. Je tu jasn\u00fd konflikt z\u00e1jm\u016f \u2013 DevOps vznikl, aby jej vy\u0159e\u0161il.<\/p>\n

Co je DevOps?<\/h3>\n

\nOt\u00e1zka je dobr\u00e1 \u2013 a sporn\u00e1: kone\u010dn\u011b se na tom sv\u011bt je\u0161t\u011b nedohodl. V EPAM pova\u017euj\u00ed, \u017ee DevOps spojuje technologie, procesy a kulturu spolupr\u00e1ce uvnit\u0159 t\u00fdmu. Tento souhrn je zam\u011b\u0159en na kontinu\u00e1ln\u00ed dod\u00e1v\u00e1n\u00ed hodnot koncov\u00fdm u\u017eivatel\u016fm.<\/p>\n

Kirill Sergejev<\/b>: \u201eV\u00fdvoj\u00e1\u0159i p\u00ed\u0161\u00ed k\u00f3d, testova\u010di ho kontroluj\u00ed a administr\u00e1to\u0159i nasazuj\u00ed fin\u00e1ln\u00ed produkt do provozn\u00edho prost\u0159ed\u00ed. Dlouho byly tyto \u010d\u00e1sti t\u00fdmu pon\u011bkud rozd\u011blen\u00e9, a pak p\u0159i\u0161la my\u0161lenka spojit je spole\u010dn\u00fdm procesem. Tak vznikly DevOps praktiky.\u201c<\/p>\n

Nastal den, kdy se v\u00fdvoj\u00e1\u0159i a syst\u00e9mov\u00ed in\u017een\u00fd\u0159i za\u010dali zaj\u00edmat o pr\u00e1ci jeden druh\u00e9ho. Bari\u00e9ra mezi v\u00fdrobou a podporou se za\u010dala rozmaz\u00e1vat. Tak vznikl DevOps, kter\u00fd zahrnuje praktiky, kulturu a \u0159\u00e1d spolupr\u00e1ce v t\u00fdmu.<\/p>\n

\"Pro\u010d
\n<\/p>\n

V \u010dem spo\u010d\u00edv\u00e1 podstata DevOps kultury?<\/h3>\n

\nZodpov\u011bdnost za kone\u010dn\u00fd v\u00fdsledek le\u017e\u00ed na ka\u017ed\u00e9m \u010dlenu t\u00fdmu. Nejzaj\u00edmav\u011bj\u0161\u00ed a nejv\u00edce komplikovan\u00e9 na filozofii DevOps je pochopit, \u017ee konkr\u00e9tn\u00ed \u010dlov\u011bk nen\u00ed zodpov\u011bdn\u00fd pouze za svou \u010d\u00e1st pr\u00e1ce, ale nese odpov\u011bdnost za to, jak bude cel\u00fd produkt fungovat. Probl\u00e9m nele\u017e\u00ed na jedn\u00e9 stran\u011b \u2013 je spole\u010dn\u00fd a ka\u017ed\u00fd \u010dlen t\u00fdmu p\u0159isp\u00edv\u00e1 k jeho \u0159e\u0161en\u00ed.<\/p>\n

Nejd\u016fle\u017eit\u011bj\u0161\u00ed z\u00e1sadou kultury DevOps je skute\u010dn\u011b \u0159e\u0161it probl\u00e9my, nikoli jen aplikovat praktik DevOps. Co v\u00edce, tyto praktiky se neimplementuj\u00ed \u201ana n\u011b\u010d\u00ed stran\u011b\u2018, ale v cel\u00e9m produktu. Projekt nepot\u0159ebuje pouze DevOps in\u017een\u00fdra \u2013 pot\u0159ebuje \u0159e\u0161en\u00ed probl\u00e9mu a roli DevOps in\u017een\u00fdra m\u016f\u017ee vykon\u00e1vat n\u011bkolik \u010dlen\u016f t\u00fdmu s r\u016fzn\u00fdmi specializacemi.<\/p>\n

Jak\u00e9 jsou praktiky DevOps?<\/h3>\n

\nPraktiky DevOps pokr\u00fdvaj\u00ed v\u0161echny f\u00e1ze \u017eivotn\u00edho cyklu softwaru.<\/p>\n

Igor Bojko<\/b>: \u201eIde\u00e1ln\u00ed situace je, kdy\u017e za\u010d\u00edn\u00e1me pou\u017e\u00edvat praktiky DevOps hned p\u0159i iniciaci projektu. Spolu s architekty pl\u00e1nujeme, jakou bude m\u00edt aplikace architektonickou strukturu, kde se bude nach\u00e1zet a jak se bude \u0161k\u00e1lovat, vyb\u00edr\u00e1me platformu. Nyn\u00ed je m\u00f3dn\u00ed mikroservisn\u00ed architektura \u2013 pro tu vyb\u00edr\u00e1me syst\u00e9m orchestrace: mus\u00edme um\u011bt \u0159\u00eddit ka\u017ed\u00fd prvek aplikace jednotliv\u011b a aktualizovat ho nez\u00e1visle na ostatn\u00edch. Dal\u0161\u00ed praktikou je \u2018infrastruktura jako k\u00f3d\u2019. Tak se naz\u00fdv\u00e1 p\u0159\u00edstup, p\u0159i kter\u00e9m je infrastruktura projektu vytv\u00e1\u0159ena a spravov\u00e1na pomoc\u00ed k\u00f3du, nikoli prost\u0159ednictv\u00edm p\u0159\u00edm\u00e9 interakce se servery.<\/p>\n

D\u00e1le p\u0159ech\u00e1z\u00edme na f\u00e1zi v\u00fdvoje. Zde je jednou z nejv\u011bt\u0161\u00edch praktik budov\u00e1n\u00ed CI\/CD: je nutn\u00e9 pomoci v\u00fdvoj\u00e1\u0159\u016fm rychle integrovat zm\u011bny do produktu v mal\u00fdch mno\u017estv\u00edch, \u010dast\u011bji a bezbolestn\u011b. CI\/CD pokr\u00fdv\u00e1 jak kontrolu k\u00f3du, tak odes\u00edl\u00e1n\u00ed masteru do k\u00f3dov\u00e9 z\u00e1kladny, stejn\u011b jako nasazen\u00ed aplikace na testovac\u00ed a produk\u010dn\u00ed prost\u0159ed\u00ed.<\/p>\n

Ve f\u00e1z\u00edch CI\/CD proch\u00e1z\u00ed k\u00f3d kvalifika\u010dn\u00edmi br\u00e1nami. S jejich pomoc\u00ed se kontroluje, zda k\u00f3d, kter\u00fd vy\u0161el z pracovn\u00ed stanice v\u00fdvoj\u00e1\u0159e, spl\u0148uje stanoven\u00e1 krit\u00e9ria kvality. Zde se p\u0159id\u00e1vaj\u00ed unit a UI testy. Pro rychl\u00e9, bezbolestn\u00e9 a c\u00edlen\u00e9 nasazen\u00ed produktu je mo\u017en\u00e9 vybrat vhodn\u00fd typ nasazen\u00ed.<\/p>\n

DevOps praktiky maj\u00ed sv\u00e9 m\u00edsto i ve f\u00e1zi podpory hotov\u00e9ho produktu. Pou\u017e\u00edvaj\u00ed se k monitorov\u00e1n\u00ed, z\u00edsk\u00e1v\u00e1n\u00ed zp\u011btn\u00e9 vazby, zaji\u0161t\u011bn\u00ed bezpe\u010dnosti a implementaci zm\u011bn. Na v\u0161echny tyto \u00fakoly se DevOps d\u00edv\u00e1 z pohledu neust\u00e1l\u00e9ho zlep\u0161ov\u00e1n\u00ed. Minimalizujeme opakuj\u00edc\u00ed se operace a automatizujeme je. Sem tak\u00e9 pat\u0159\u00ed migrace, roz\u0161i\u0159ov\u00e1n\u00ed aplikace a zaji\u0161t\u011bn\u00ed funk\u010dnosti.<\/p>\n

Jak\u00e9 v\u00fdhody p\u0159in\u00e1\u0161ej\u00ed DevOps praktiky?<\/h3>\n

\nPokud bychom psali u\u010debnici modern\u00edch DevOps praktiky, na jej\u00ed prvn\u00ed str\u00e1nce by bylo uvedeno t\u0159i body: automatizace, urychlen\u00ed vyd\u00e1n\u00ed a rychl\u00e1 zp\u011btn\u00e1 vazba od u\u017eivatel\u016f.<\/p>\n

Kirill Sergejev<\/b>: \u201ePrvn\u00ed je automatizace. V\u0161echny interakce v t\u00fdmu m\u016f\u017eeme automatizovat: napsali jsme k\u00f3d \u2013 nasadili jsme \u2013 zkontrolovali jsme \u2013 instalovali jsme \u2013 shrom\u00e1\u017edili jsme zp\u011btnou vazbu \u2013 vr\u00e1tili jsme se na za\u010d\u00e1tek. To v\u0161e automaticky.<\/p>\n

Druh\u00e9 je urychlen\u00ed vyd\u00e1n\u00ed a zjednodu\u0161en\u00ed v\u00fdvoje. Z\u00e1kazn\u00edkovi je v\u017edy d\u016fle\u017eit\u00e9, aby produkt vstoupil na trh co nejd\u0159\u00edve a za\u010dal p\u0159in\u00e1\u0161et u\u017eitek d\u0159\u00edve ne\u017e konkurence. Proces dod\u00e1vky produktu lze neust\u00e1le zlep\u0161ovat: zkracovat \u010das, p\u0159id\u00e1vat dal\u0161\u00ed kontroln\u00ed body, vylep\u0161ovat monitoring.<\/p>\n

T\u0159et\u00ed je urychlen\u00ed zp\u011btn\u00e9 vazby od u\u017eivatele. Pokud m\u00e1 p\u0159ipom\u00ednky, m\u016f\u017eeme okam\u017eit\u011b prov\u00e9st \u00fapravy a ihned aktualizovat aplikaci.<\/p>\n

\"Pro\u010d
\n<\/p>\n

Jak se vztahuj\u00ed pojmy \u201esyst\u00e9mov\u00fd in\u017een\u00fdr\u201c, \u201ebuild in\u017een\u00fdr\u201c a \u201eDevOps in\u017een\u00fdr\u201c?<\/h3>\n

\nP\u0159ekr\u00fdvaj\u00ed se, ale pat\u0159\u00ed do pon\u011bkud r\u016fzn\u00fdch oblast\u00ed.<\/p>\n

Syst\u00e9mov\u00fd in\u017een\u00fdr v EPAM je pozice. M\u016f\u017ee m\u00edt r\u016fzn\u00e9 \u00farovn\u011b: od juniora po chief specialistu.<\/p>\n

Build in\u017een\u00fdr je sp\u00ed\u0161e role, kterou lze vykon\u00e1vat v projektu. Dnes se tak ozna\u010duj\u00ed lid\u00e9 odpov\u011bdn\u00ed za CI\/CD.<\/p>\n

DevOps in\u017een\u00fdrem je ozna\u010dov\u00e1n specialista, kter\u00fd zav\u00e1d\u00ed DevOps praktiky do projektu.<\/p>\n

Pokud to shrneme, vych\u00e1z\u00ed p\u0159ibli\u017en\u011b na toto: \u010dlov\u011bk v pozici syst\u00e9mov\u00e9ho in\u017een\u00fdra vykon\u00e1v\u00e1 v projektu roli build in\u017een\u00fdra a zab\u00fdv\u00e1 se tam implementac\u00ed DevOps praktiky.<\/p>\n

Co p\u0159esn\u011b d\u011bl\u00e1 DevOps in\u017een\u00fdr?<\/h3>\n

\nDevOps in\u017een\u00fd\u0159i spojuj\u00ed v\u0161echny \u010d\u00e1sti projektu dohromady. Zna\u010dn\u011b znaj\u00ed specifika pr\u00e1ce program\u00e1tor\u016f, tester\u016f, syst\u00e9mov\u00fdch administr\u00e1tor\u016f a pom\u00e1haj\u00ed zjednodu\u0161it jejich pr\u00e1ci. Rozum\u011bj\u00ed pot\u0159eb\u00e1m a po\u017eadavk\u016fm podnik\u00e1n\u00ed, jeho roli v procesu v\u00fdvoje \u2013 a buduj\u00ed proces s ohledem na z\u00e1jmy z\u00e1kazn\u00edka.<\/p>\n

Hodn\u011b jsme mluvili o automatizaci \u2013 tou se DevOps in\u017een\u00fd\u0159i zab\u00fdvaj\u00ed p\u0159edev\u0161\u00edm. Je to velmi d\u016fle\u017eit\u00fd bod, do kter\u00e9ho mimo jin\u00e9 pat\u0159\u00ed p\u0159\u00edprava prost\u0159ed\u00ed.<\/p>\n

Kirill Sergejev<\/b>: \u201eNe\u017e implementujeme aktualizace do produktu, je nutn\u00e9 je otestovat ve vedlej\u0161\u00edm prost\u0159ed\u00ed. To p\u0159ipravuj\u00ed DevOps in\u017een\u00fd\u0159i. Ti tak\u00e9 zav\u00e1d\u011bj\u00ed kulturu DevOps v projekt\u011b jako celku: implementuj\u00ed DevOps praktiky na v\u0161ech \u00farovn\u00edch sv\u00fdch projekt\u016f. T\u0159i z\u00e1kladn\u00ed principy: automatizace, zjednodu\u0161en\u00ed, zrychlen\u00ed \u2013 tyto principy p\u0159in\u00e1\u0161ej\u00ed v\u0161ude tam, kam mohou dos\u00e1hnout.\u201c<\/p>\n

Co by m\u011bl DevOps in\u017een\u00fdr v\u011bd\u011bt?<\/h3>\n

\nZjednodu\u0161en\u011b \u0159e\u010deno, m\u011bl by m\u00edt znalosti z r\u016fzn\u00fdch oblast\u00ed: programov\u00e1n\u00ed, pr\u00e1ce s opera\u010dn\u00edmi syst\u00e9my, datab\u00e1zemi, syst\u00e9my sestaven\u00ed a konfigurace. K tomu p\u0159id\u00e1v\u00e1 schopnost pracovat s cloudovou infrastrukturou, syst\u00e9my orchestrace a monitorov\u00e1n\u00ed.<\/p>\n

1. Programovac\u00ed jazyky<\/b><\/p>\n

DevOps in\u017een\u00fd\u0159i znaj\u00ed n\u011bkolik z\u00e1kladn\u00edch jazyk\u016f pro automatizaci a mohou nap\u0159\u00edklad \u0159\u00edct program\u00e1torovi: \u201eCo kdybychom instalaci k\u00f3du ned\u011blali ru\u010dn\u011b, ale pomoc\u00ed na\u0161eho skriptu, kter\u00fd v\u0161e automatizuje? P\u0159iprav\u00edme k n\u011bmu config soubor, kter\u00fd bude pohodln\u011b \u010diteln\u00fd pro tebe i pro n\u00e1s \u2013 a kdykoliv ho budeme moci zm\u011bnit. Nav\u00edc budeme vid\u011bt, kdo, kdy a pro\u010d provedl zm\u011bny.\u201c<\/p>\n

DevOps in\u017een\u00fdr se m\u016f\u017ee nau\u010dit jeden nebo v\u00edce z t\u011bchto jazyk\u016f: Python, Groovy, Bash, Powershell, Ruby, Go. Nen\u00ed pot\u0159eba zn\u00e1t je na hlubok\u00e9 \u00farovni \u2013 sta\u010d\u00ed z\u00e1kladn\u00ed znalost syntaxe, princip\u016f OOP a schopnost ps\u00e1t jednoduch\u00e9 skripty pro automatizaci.<\/p>\n

2. Opera\u010dn\u00ed syst\u00e9my<\/b><\/p>\n

DevOps in\u017een\u00fdr by m\u011bl rozum\u011bt tomu, na kter\u00e9m serveru bude produkt nainstalov\u00e1n, v jak\u00e9m prost\u0159ed\u00ed se bude spou\u0161t\u011bt a s jak\u00fdmi slu\u017ebami bude spolupracovat. M\u016f\u017ee si zvolit specializaci na Windows nebo rodinu Linux.<\/p>\n

3. Syst\u00e9my \u0159\u00edzen\u00ed verz\u00ed<\/b><\/p>\n

Bez znalosti syst\u00e9m\u016f \u0159\u00edzen\u00ed verz\u00ed se DevOps in\u017een\u00fdr neobejde. Git je v sou\u010dasnosti jedn\u00edm z nejpopul\u00e1rn\u011bj\u0161\u00edch syst\u00e9m\u016f.<\/p>\n

4. Cloudov\u00ed poskytovatel\u00e9<\/b><\/p>\n

AWS, Google, Azure \u2013 obzvl\u00e1\u0161\u0165 pokud hovo\u0159\u00edme o zam\u011b\u0159en\u00ed na Windows.<\/p>\n

Kirill Sergejev<\/b>: \u201eCloudov\u00ed poskytovatel\u00e9 n\u00e1m nab\u00edzej\u00ed virtu\u00e1ln\u00ed servery<\/a>, kter\u00e1 se skv\u011ble hod\u00ed na CI\/CD.<\/p>\n

Nastaven\u00ed deseti fyzick\u00fdch server\u016f<\/a> vy\u017eaduje p\u0159ibli\u017en\u011b sto ru\u010dn\u00edch operac\u00ed. Ka\u017ed\u00fd server je pot\u0159eba ru\u010dn\u011b spustit, nainstalovat a nakonfigurovat pot\u0159ebn\u00fd opera\u010dn\u00ed syst\u00e9m, nainstalovat na\u0161i aplikaci na t\u011bchto deseti serverech a pak desetkr\u00e1t v\u0161e zkontrolovat. Cloudov\u00e9 slu\u017eby nahrazuj\u00ed tento proces deseti \u0159\u00e1dky k\u00f3du a dobr\u00fd DevOps in\u017een\u00fdr by m\u011bl um\u011bt s nimi manipulovat. T\u00edm \u0161et\u0159\u00ed \u010das, \u00fasil\u00ed a pen\u00edze \u2013 jak pro z\u00e1kazn\u00edka, tak pro firmu.\u201c<\/p>\n

5. Orchestrace: Docker a Kubernetes<\/b><\/p>\n

Kirill Sergejev<\/b>: \u201eVirtu\u00e1ln\u00ed servery jsou rozd\u011bleny na kontejnery, do kter\u00fdch m\u016f\u017eeme nainstalovat na\u0161i aplikaci. Kdy\u017e je kontejnery mnoho, je pot\u0159eba je \u0159\u00eddit: jeden zapnout, jin\u00fd vypnout, n\u011bkde ud\u011blat z\u00e1lohy. To se st\u00e1v\u00e1 docela slo\u017eit\u00fdm \u00fakolem, pro kter\u00fd je pot\u0159eba syst\u00e9m orchestrace.<\/p>\n

D\u0159\u00edve m\u011bl ka\u017edou aplikaci na starosti samostatn\u00fd server \u2013 jak\u00e9koliv zm\u011bny v jeho fungov\u00e1n\u00ed mohly ovlivnit spr\u00e1vnost aplikace. D\u00edky kontejner\u016fm se aplikace st\u00e1vaj\u00ed izolovan\u00fdmi a spou\u0161t\u00ed se samostatn\u011b \u2013 ka\u017ed\u00e1 na sv\u00e9 virtu\u00e1ln\u00ed ma\u0161in\u011b. Pokud dojde k chyb\u011b, nen\u00ed t\u0159eba tr\u00e1vit \u010das hled\u00e1n\u00edm p\u0159\u00ed\u010diny. Je jednodu\u0161\u0161\u00ed zni\u010dit star\u00fd kontejner a p\u0159idat nov\u00fd.\u201c<\/p>\n

6. Konfigura\u010dn\u00ed syst\u00e9my: Chef, Ansible, Puppet<\/b><\/p>\n

Kdy\u017e je t\u0159eba spravovat cel\u00e9 portfolio server\u016f, je nutn\u00e9 prov\u00e1d\u011bt mnoho podobn\u00fdch operac\u00ed. To je zdlouhav\u00e9 a slo\u017eit\u00e9, a nav\u00edc manu\u00e1ln\u00ed pr\u00e1ce zvy\u0161uje \u0161anci na chybu. Tady p\u0159ich\u00e1zej\u00ed na pomoc konfigura\u010dn\u00ed syst\u00e9my. S jejich pomoc\u00ed se vytv\u00e1\u0159\u00ed skript, kter\u00fd je pohodln\u011b \u010diteln\u00fd jak pro program\u00e1tory, tak pro DevOps in\u017een\u00fdry a syst\u00e9mov\u00e9 administr\u00e1tory. Tento skript pom\u00e1h\u00e1 prov\u00e1d\u011bt stejn\u00e9 operace na serverech automaticky. Tak se sni\u017euje po\u010det ru\u010dn\u00edch operac\u00ed (a t\u00edm p\u00e1dem chyb).<\/p>\n

Jakou kari\u00e9ru si m\u016f\u017ee vybudovat DevOps in\u017een\u00fdr?<\/h3>\n

\nLze se rozv\u00edjet jak horizont\u00e1ln\u011b, tak vertik\u00e1ln\u011b.<\/p>\n

Igor Bojko<\/b>: \u201eZ hlediska horizont\u00e1ln\u00edho rozvoje maj\u00ed DevOps in\u017een\u00fd\u0159i dnes nej\u0161ir\u0161\u00ed vyhl\u00eddky. V\u0161e se neust\u00e1le m\u011bn\u00ed a dovednosti lze roz\u0161i\u0159ovat v mnoha r\u016fzn\u00fdch sm\u011brech: od syst\u00e9m\u016f pro spr\u00e1vu verz\u00ed a\u017e po monitorov\u00e1n\u00ed, od spr\u00e1vy konfigurac\u00ed po datab\u00e1ze.<\/p>\n

M\u016f\u017eete se st\u00e1t syst\u00e9mov\u00fdm architektem, pokud v\u00e1s zaj\u00edm\u00e1, jak aplikace funguje ve v\u0161ech f\u00e1z\u00edch sv\u00e9ho \u017eivotn\u00edho cyklu \u2013 od v\u00fdvoje a\u017e po podporu.<\/p>\n

Jak se st\u00e1t DevOps in\u017een\u00fdrem?<\/h3>\n

<\/p>\n

    \n
  1. P\u0159e\u010dt\u011bte si knihy \u201eProjekt Phoenix\u201c a DevOps Handbook. Jsou to skute\u010dn\u00e9 pil\u00ed\u0159e filozofie DevOps, p\u0159i\u010dem\u017e prvn\u00ed je beletristick\u00fd rom\u00e1n.<\/li>\n
  2. Studujte technologie ze seznamu v\u00fd\u0161e: samostatn\u011b nebo na online kurzech.<\/li>\n
  3. P\u0159ipojte se jako DevOps in\u017een\u00fdr k open source projektu.<\/li>\n
  4. Praxe a n\u00e1vrh DevOps praktik na sv\u00fdch osobn\u00edch a pracovn\u00edch projektech.<\/li>\n<\/ol>\n

    Zdroj: 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\udd47Pro\u010d je DevOps pot\u0159ebn\u00fd a kdo jsou DevOps specialist\u00e9 | ProHoster","description":"Kdy\u017e aplikace nefunguje, nejm\u00e9n\u011b bychom cht\u011bli sly\u0161et od koleg\u016f v\u011btu \u201eprobl\u00e9m je na va\u0161\u00ed stran\u011b\u201c. Nakonec trp\u00ed u\u017eivatel\u00e9 \u2013 a ti je nezaj\u00edm\u00e1, kter\u00e1 \u010d\u00e1st t\u00fdmu nese odpov\u011bdnost za chybu.","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/zachem-nuzhen-devops-i-kto-takie-devops-spetsialisty","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"cs_CZ","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\/cs\/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\/cs\/wp-json\/wp\/v2\/posts\/37684","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/comments?post=37684"}],"version-history":[{"count":2,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/37684\/revisions"}],"predecessor-version":[{"id":158512,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/37684\/revisions\/158512"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media\/28282"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=37684"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=37684"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=37684"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}