{"id":32497,"date":"2019-10-31T21:47:23","date_gmt":"2019-10-31T18:47:23","guid":{"rendered":"https:\/\/prohoster.info\/blog\/devopsforum-2019-vnedryat-devops-nelzya-zhdat\/"},"modified":"2019-10-31T21:47:23","modified_gmt":"2019-10-31T18:47:23","slug":"devopsforum-2019-vnedryat-devops-nelzya-zhdat","status":"publish","type":"post","link":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/devopsforum-2019-vnedryat-devops-nelzya-zhdat","title":{"rendered":"DevOpsForum 2019. Zav\u00e1d\u011bn\u00ed DevOps nelze odkl\u00e1dat.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Ned\u00e1vno jsem se z\u00fa\u010dastnila DevOpsForum 2019, kterou po\u0159\u00e1dal Logrocon. Na t\u00e9to konferenci se \u00fa\u010dastn\u00edci sna\u017eili naj\u00edt \u0159e\u0161en\u00ed a nov\u00e9 n\u00e1stroje pro efektivn\u00ed spolupr\u00e1ci mezi podniky a specialisty na v\u00fdvoj a informa\u010dn\u00ed technologie.<\/p>\n

\"DevOpsForum
\n
\nKonference byla \u00fasp\u011b\u0161n\u00e1: bylo tam opravdu hodn\u011b u\u017eite\u010dn\u00fdch prezentac\u00ed, zaj\u00edmav\u00e9 form\u00e1ty vystoupen\u00ed a spousta komunikace s p\u0159edn\u00e1\u0161ej\u00edc\u00edmi. A co je zejm\u00e9na d\u016fle\u017eit\u00e9, nikdo se mi nesna\u017eil nic prodat, co\u017e je posledn\u00ed dobou \u010dast\u00fd jev u p\u0159edn\u00e1\u0161ej\u00edc\u00edch na velk\u00fdch konferenc\u00edch.<\/p>\n

Shrnut\u00ed z vystoupen\u00ed Raiffeisen Bank, Alfa Insurance, zku\u0161enosti Mango Telecom p\u0159i zav\u00e1d\u011bn\u00ed automatizace a dal\u0161\u00ed podrobnosti najdete pod odkazem. <\/a><\/noindex><\/p>\n

Jmenuji se Jana, pracuji jako tester, zab\u00fdv\u00e1m se automatizac\u00ed a tak\u00e9 DevOps a miluji \u00fa\u010dast na konferenc\u00edch a meetupech. Za posledn\u00ed dva roky jsem nav\u0161t\u00edvila konference Olega Bunina (HighLoad++, TeamLead Conf), akce Jug (Heisenbug, JPoint), TestCon Moscow, DevOps Pro Moscow, Big Data Moscow. <\/p>\n

Nejd\u0159\u00edve se soust\u0159ed\u00edm na program konference. M\u00e9n\u011b m\u011b zaj\u00edm\u00e1, o \u010dem bude p\u0159edn\u00e1\u0161ka, v\u00edce m\u011b zaj\u00edm\u00e1 p\u0159edn\u00e1\u0161ej\u00edc\u00ed. I kdy\u017e m\u016f\u017ee b\u00fdt prezentace velmi technologick\u00e1 a zaj\u00edmav\u00e1, nen\u00ed zaru\u010deno, \u017ee budete moci aplikovat n\u011bkter\u00e9 osv\u011bd\u010den\u00e9 postupy z p\u0159edn\u00e1\u0161ky ve sv\u00e9 firm\u011b. A tehdy pot\u0159ebujete dobr\u00e9ho p\u0159edn\u00e1\u0161ej\u00edc\u00edho.\n<\/p><\/blockquote>\n

Sv\u011btlo na konci pipeline v Raiffeisen Bank.<\/h2>\n

\nObvykle p\u00e1tr\u00e1m po zaj\u00edmav\u00fdch p\u0159edn\u00e1\u0161ej\u00edc\u00edch v z\u00e1kulis\u00ed. Na DevOpsForum 2019 m\u011b zaujal p\u0159edn\u00e1\u0161ej\u00edc\u00ed z Raiffeisen Bank \u2014 Michail Bi\u017ean. B\u011bhem vystoupen\u00ed hovo\u0159il o tom, jak postupn\u011b zav\u00e1d\u011bj\u00ed sv\u00fdm t\u00fdm\u016fm DevOps, pro\u010d je to pot\u0159ebn\u00e9 a jak prodat my\u0161lenku DevOps transformace byznysu. Takt\u00e9\u017e hovo\u0159il o tom, jak vid\u011bt sv\u011btlo na konci pipeline.<\/p>\n

\"DevOpsForum
\nMichail Bi\u017ean, \u0159editel automatizace v Raiffeisen Bank.<\/i><\/p>\n

V sou\u010dasn\u00e9 dob\u011b ve spole\u010dnosti nemaj\u00ed \u201eskute\u010dn\u00fd DevOps\u201c. To znamen\u00e1, \u017ee je skute\u010dn\u00fd, ale ne ve v\u0161ech t\u00fdmech. P\u0159i zav\u00e1d\u011bn\u00ed DevOps se op\u00edraj\u00ed o p\u0159ipravenost t\u00fdm\u016f jak z hlediska konkr\u00e9tn\u00edch in\u017een\u00fdr\u016f, tak z hlediska pot\u0159eb produktu a zralosti platformy, na kter\u00e9 je tento produkt postaven. M\u00ed\u0161a vysv\u011btlil, jak obh\u00e1jit byznysu, pro\u010d je DevOps pot\u0159ebn\u00fd. <\/p>\n

Bankovn\u00ed sektor m\u00e1 n\u011bkolik motor\u016f r\u016fstu: cena slu\u017eeb a roz\u0161\u00ed\u0159en\u00ed klientsk\u00e9 z\u00e1kladny. Zvy\u0161ov\u00e1n\u00ed cen slu\u017eeb nen\u00ed p\u0159\u00edli\u0161 siln\u00fdm faktorem, ale r\u016fst klientsk\u00e9 z\u00e1kladny je naopak pozitivn\u00ed. Pokud konkurenti uvedou na trh skute\u010dn\u011b atraktivn\u00ed produkt, v\u0161ichni klienti odejdou tam, a a\u017e \u010dasem se trh vyrovn\u00e1. Proto je zav\u00e1d\u011bn\u00ed nov\u00fdch produkt\u016f a rychlost jejich uveden\u00ed na trh kl\u00ed\u010dov\u00e1 z\u00e1le\u017eitost, na kterou se banky zam\u011b\u0159uj\u00ed. Pr\u00e1v\u011b pro to je pot\u0159ebn\u00fd DevOps, a podniky to ch\u00e1pou.<\/p>\n

Dal\u0161\u00ed d\u016fle\u017eit\u00fd bod: DevOps ne v\u017edy zkracuje \u010das na uveden\u00ed na trh. DevOps nem\u016f\u017ee fungovat s\u00e1m, je to jen \u010d\u00e1st procesu v\u00fdvoje a uv\u00e1d\u011bn\u00ed produktu na trh od v\u00fdvoje po produkci (od k\u00f3du ke klientovi). V\u0161echno, co je p\u0159ed k\u00f3dem, nem\u00e1 s DevOps p\u0159\u00edmou souvislost. To znamen\u00e1, \u017ee marketingov\u00ed specialist\u00e9 mohou roky zkoumat trh a cel\u00fd \u017eivot doh\u00e1n\u011bt konkurenty. Je nutn\u00e9 rychle pochopit, co klient pot\u0159ebuje, a pl\u00e1novat realizaci ur\u010dit\u00e9 funkce \u2014 \u010dasto pr\u00e1v\u011b to chyb\u00ed, aby DevOps fungoval a spole\u010dnost dos\u00e1hla c\u00edle. Proto se v Raiffeisenbank nejprve dohodli s podnikem, \u017ee se mus\u00ed nau\u010dit vyu\u017e\u00edvat DevOps. Automatizace pro automatizaci p\u0159\u00edli\u0161 nepom\u016f\u017ee v boji o nov\u00e9 klienty.<\/p>\n

Celkov\u011b M\u00ed\u0161a pova\u017euje, \u017ee DevOps je t\u0159eba zav\u00e1d\u011bt, ale s rozmyslem. A je t\u0159eba b\u00fdt p\u0159ipraven na to, \u017ee na za\u010d\u00e1tku transformace klesne produktivita t\u00fdmu, budou vyd\u011bl\u00e1vat m\u00e9n\u011b pen\u011bz, ale nakonec se to vyplat\u00ed.<\/p>\n

Automatizace testov\u00e1n\u00ed v \u201eMango Telecom\u201c<\/h2>\n

\nDal\u0161\u00ed zaj\u00edmavou prezentaci pro m\u011b jako testera p\u0159ednesl E\u0433\u043e\u0440 \u041c\u0430\u0441\u043b\u043e\u0432 z \"Mango Telecom\". Prezentace se naz\u00fdvala \u201eAutomatizace pln\u00e9ho cyklu testov\u00e1n\u00ed v SCRUM t\u00fdmu\u201c. E\u0433\u043e\u0440 v\u011b\u0159\u00ed, \u017ee DevOps je stvo\u0159en pr\u00e1v\u011b pro SCRUM, ale implementovat DevOps do SCRUM t\u00fdmu je docela problematick\u00e9. D\u016fvodem je to, \u017ee SCRUM t\u00fdm neust\u00e1le n\u011bkam sp\u011bch\u00e1, nem\u00e1 \u010das se soust\u0159edit na novinky a p\u0159estav\u011bt proces. Dal\u0161\u00edm probl\u00e9mem je, \u017ee SCRUM nep\u0159edpokl\u00e1d\u00e1 rozd\u011blen\u00ed v t\u00fdmu na sub-t\u00fdmy (t\u00fdm tester\u016f, t\u00fdm v\u00fdvoj\u00e1\u0159\u016f atd.). A krom\u011b toho, k automatizaci st\u00e1vaj\u00edc\u00edho procesu je pot\u0159eba dokumentace, ale v SCRUMu v\u011bt\u0161inou dokumentace zcela chyb\u00ed \u2013 \"produkt je d\u016fle\u017eit\u011bj\u0161\u00ed ne\u017e n\u011bjak\u00e9 psan\u00ed.\"<\/p>\n

Po p\u0159echodu na SCRUM za\u010dali teste\u0159i radit s v\u00fdvoj\u00e1\u0159i, jak testovat nov\u00e9 funkce. Postupn\u011b se objem funkcionality zvy\u0161oval, dokumentace chyb\u011bla a za\u010dali nach\u00e1zet mnoho chyb v funkcionalit\u011b, kter\u00e1 nem\u011bla pokryt\u00ed testy a ji\u017e nebylo jasn\u00e9, kdo a kdy ji testoval. Jin\u00fdmi slovy \u2013 rozvrat a chaos. Rozhodli se p\u0159ej\u00edt na automatizaci testov\u00e1n\u00ed. Ale ani pot\u00e9 to skon\u010dilo naprost\u00fdm ne\u00fasp\u011bchem. P\u0159ivedli extern\u00ed specialisty na automatizaci, kte\u0159\u00ed psali v pro n\u011b nezn\u00e1m\u00e9m technologick\u00e9m stacku. R\u00e1mec pro automatizovan\u00e9 testy samoz\u0159ejm\u011b fungoval, ale pot\u00e9, co externist\u00e9 ode\u0161li, vydr\u017eel jen 14 dn\u00ed. N\u00e1sledovalo dal\u0161\u00ed pokus o zaveden\u00ed automatizovan\u00e9ho testov\u00e1n\u00ed \u010d\u00edslo dv\u011b. Za\u010dalo to t\u00edm, \u017ee v\u0161echno mus\u00ed b\u00fdt vybudov\u00e1no uvnit\u0159 spole\u010dnosti, vlastn\u00edmi silami (spr\u00e1vn\u00fd sm\u011br: zvy\u0161ujte odborn\u00e9 znalosti uvnit\u0159), v r\u00e1mci SCRUMu, a b\u011bhem procesu vytv\u00e1\u0159et dokumentaci. Stack pro automatizaci by m\u011bl odpov\u00eddat stacku produktu (zde souhlas\u00edm, netestujte projekt na JavaScript n\u011b\u010d\u00edm jin\u00fdm). Na konci sprintu po\u0159\u00e1dali demo toho, jak funguje automatizovan\u00fd test, za \u00fa\u010dasti cel\u00e9ho t\u00fdmu (u\u017eite\u010dn\u00e9). T\u00edmto zp\u016fsobem se zvy\u0161ovala anga\u017eovanost v\u0161ech \u010dlen\u016f t\u00fdmu v procesu automatizace, stejn\u011b jako d\u016fv\u011bra v automatizovan\u00e9 testy a \u0161ance, \u017ee tento automatizovan\u00fd test bude skute\u010dn\u011b pou\u017e\u00edv\u00e1n (a nebude za m\u011bs\u00edc zakomentov\u00e1n z d\u016fvodu neust\u00e1l\u00fdch ne\u00fasp\u011bch\u016f).<\/p>\n

Na DevOpsForum 2019 byl otev\u0159en\u00fd mikrofon \u2013 dlouho zn\u00e1m\u00fd a, podle m\u00e9ho n\u00e1zoru, u\u017eite\u010dn\u00fd form\u00e1t p\u0159edn\u00e1\u0161ek. Chod\u00edte, poslouch\u00e1te prezentace a pak se rozhodnete, \u017ee na konferenci je pot\u0159eba prodiskutovat n\u011bjak\u00e9 t\u00e9ma nebo probl\u00e9m, sd\u00edlet relevantn\u00ed zku\u0161enosti s \u0159e\u0161en\u00edm \u00fakolu.<\/p>\n

Tak\u00e9 jsem si v\u0161imla, \u017ee organiz\u00e1to\u0159i vytvo\u0159ili sekci kr\u00e1tk\u00fdch prezentac\u00ed. Ka\u017ed\u00e1 prezentace trv\u00e1 maxim\u00e1ln\u011b 10 minut, pot\u00e9 n\u00e1sledovaly ot\u00e1zky. Takto je mo\u017en\u00e9 pokr\u00fdt mnoho t\u00e9mat a polo\u017eit ot\u00e1zky \u0159e\u010dn\u00edk\u016fm, kte\u0159\u00ed v\u00e1s zaujali.<\/p><\/blockquote>\n

\"DevOpsForum
\n\"DevOpsForum
\nMezi p\u0159edn\u00e1\u0161kami jsem se pro\u0161la po st\u00e1nc\u00edch partner\u016f konference a z\u00edskala mnoho r\u016fzn\u00fdch v\u011bc\u00ed. Ach, miluji propaga\u010dn\u00ed materi\u00e1ly!<\/i><\/p>\n

Kulat\u00fd st\u016fl a ot\u00e1zky DevOps s \u0159editelem v\u00fdvoje v AlfaStrakhovanie.<\/h2>\n

\nT\u0159e\u0161inkou na dortu DevOpsForum 2019 pro m\u011b byla hodinov\u00e1 plen\u00e1rn\u00ed sezen\u00ed s odborn\u00edky na DevOps. Byli pozv\u00e1ni \u010dty\u0159i \u00fa\u010dastn\u00edci sezen\u00ed, kte\u0159\u00ed m\u011bli pohl\u00ed\u017eet na DevOps z r\u016fzn\u00fdch \u00fahl\u016f: Anton Isanin (AlfaStrakhovanie, \u0159editel v\u00fdvoje), Nailya Zamashkina (Fintech Lab, provozn\u00ed \u0159editel), Oleg Egorkin (Rostelecom, Agile kou\u010d) a Anton Martyanov (nez\u00e1visl\u00fd expert, posuzoval DevOps z pohledu podnik\u00e1n\u00ed). <\/p>\n

Odborn\u00edci se usadili bl\u00ed\u017ee k lidem a za\u010dalo se: cel\u00fd hodinov\u00fd blok \u00fa\u010dastn\u00edci z publika kladli sv\u00e9 ot\u00e1zky, a odborn\u00edci se sna\u017eili odpov\u00eddat. N\u011bkdy vznikly skute\u010dn\u00e9 debaty. Ot\u00e1zky byly velmi rozmanit\u00e9, nap\u0159\u00edklad: jsou DevOps in\u017een\u00fd\u0159i v\u016fbec pot\u0159ebn\u00ed, pro\u010d je nelze vychovat z administr\u00e1tor\u016f syst\u00e9m\u016f, m\u011bla by se DevOps nab\u00edzet v\u0161em, jak\u00e1 je jej\u00ed hodnota a tak d\u00e1le.<\/p>\n

Pot\u00e9 jsem se osobn\u011b setkala s Antonem Isaninem. Diskutovali jsme o pot\u0159eb\u011b \u0161\u00ed\u0159it kulturu DevOps do ka\u017ed\u00e9ho domu a odhalili temnou str\u00e1nku transformace DevOps.<\/p>\n

P\u0159edstavme si, \u017ee se v\u0161ichni se\u0161li a rozhodli, \u017ee DevOps je pot\u0159eba jak pro produkt, tak pro byznys a t\u00fdm. Pustili se do implementace. V\u0161e se poda\u0159ilo. Vydechli jsme. DevOps n\u00e1s p\u0159ibl\u00ed\u017eil k z\u00e1kazn\u00edkovi, nyn\u00ed m\u016f\u017eeme rychle plnit v\u0161echny jeho p\u0159\u00e1n\u00ed. Nakonec m\u00e1me velk\u00e9 odd\u011blen\u00ed Ops se striktn\u00edmi pravidly a po\u017eadavky, a neust\u00e1le hl\u00e1s\u00ed chyby do produktu, vytv\u00e1\u0159ej\u00edc\u00ed spoustu \u017e\u00e1dost\u00ed. P\u0159itom v\u0161echny chyby maj\u00ed status \u201eokam\u017eit\u011b\u201c, i kdy\u017e si klient ne\u010dekan\u011b p\u0159\u00e1l, aby se tla\u010d\u00edtko obarvilo na \u017elutou m\u00edsto zelen\u00e9. Projekt roste, roste po\u010det vyd\u00e1n\u00ed a t\u00edm i po\u010det chyb a nedorozum\u011bn\u00ed s novou funk\u010dnost\u00ed ze strany z\u00e1kazn\u00edk\u016f. Ops naj\u00edm\u00e1 dal\u0161\u00edch 10 lid\u00ed, aby st\u00edhali hl\u00e1sit chyby, zat\u00edmco v\u00fdvoj\u00e1\u0159i naj\u00edmaj\u00ed dal\u0161\u00edch 15, aby je stihli opravovat. A m\u00edsto toho, aby implementovali nov\u00e9 funkce, t\u00fdm pracuje na nekone\u010dn\u00fdch SD a vysv\u011btluje funk\u010dnost u\u017eivatel\u016fm i podpo\u0159e. Nakonec jsou jak Ops, tak v\u00fdvoj\u00e1\u0159i zam\u011bstnan\u00ed, ale z\u00e1kazn\u00edk a byznys jsou nespokojeni: nov\u00e9 funkce uv\u00edzly. Tak\u017ee DevOps sice existuje, ale jako by nebyl.<\/p>\n

O nutnosti implementace DevOps Anton jednozna\u010dn\u011b prohl\u00e1sil, \u017ee to p\u0159\u00edmo z\u00e1vis\u00ed na rozsahu byznysu. Pokud spr\u00e1va jednoho klienta za rok p\u0159in\u00e1\u0161\u00ed firm\u011b miliardu \u2014 DevOps nen\u00ed pot\u0159eba (pokud nen\u00ed t\u0159eba pravideln\u011b zav\u00e1d\u011bt nov\u00e9 zm\u011bny pro tohoto klienta). V\u0161echno je v po\u0159\u00e1dku. Ale pokud byznys roste a po\u010det klient\u016f se zvy\u0161uje, je nutn\u00e9 se tomuto p\u0159izp\u016fsobit. Obvykle v firm\u011b ze za\u010d\u00e1tku skv\u011bl\u00fd Ops nen\u00ed. Nejd\u0159\u00edve vyv\u00edj\u00edme produkt a a\u017e pot\u00e9 si uv\u011bdom\u00edme, \u017ee aby produkt fungoval, je t\u0159eba sledovat dod\u00e1vky. servery<\/a>, sledovat dod\u00e1vky. Tehdy se tak\u00e9 zrod\u00ed Ops. Z\u016fst\u00e1v\u00e1 pochopit, \u017ee Ops jako samostatn\u00e9 odd\u011blen\u00ed za\u010dne zav\u00e1d\u011bt spoustu p\u0159ek\u00e1\u017eek pro v\u00fdvoj a v\u0161echny dod\u00e1vky za\u010dnou v\u00e1znout. To znamen\u00e1, \u017ee v tomto p\u0159\u00edpad\u011b je kultura DevOps ji\u017e aktu\u00e1ln\u00ed, jen je t\u0159eba nezapom\u00ednat na jej\u00ed temnou str\u00e1nku.
\n
Zdroj: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u041d\u0435\u0434\u0430\u0432\u043d\u043e \u044f \u043f\u043e\u0431\u044b\u0432\u0430\u043b\u0430 \u043d\u0430 DevOpsForum 2019, \u043a\u043e\u0442\u043e\u0440\u0443\u044e \u0443\u0441\u0442\u0440\u0430\u0438\u0432\u0430\u043b Logrocon. \u041d\u0430 \u044d\u0442\u043e\u0439 \u043a\u043e\u043d\u0444\u0435\u0440\u0435\u043d\u0446\u0438\u0438 \u0443\u0447\u0430\u0441\u0442\u043d\u0438\u043a\u0438 \u043f\u044b\u0442\u0430\u043b\u0438\u0441\u044c \u043d\u0430\u0439\u0442\u0438 \u0440\u0435\u0448\u0435\u043d\u0438\u044f \u0438 \u043d\u043e\u0432\u044b\u0435 \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u044b \u0434\u043b\u044f \u044d\u0444\u0444\u0435\u043a\u0442\u0438\u0432\u043d\u043e\u0433\u043e \u0432\u0437\u0430\u0438\u043c\u043e\u0434\u0435\u0439\u0441\u0442\u0432\u0438\u044f \u0431\u0438\u0437\u043d\u0435\u0441\u0430 \u0438 \u0441\u043f\u0435\u0446\u0438\u0430\u043b\u0438\u0441\u0442\u043e\u0432 \u043f\u043e \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0435 \u0438 \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u043e\u043d\u043d\u043e-\u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u0447\u0435\u0441\u043a\u043e\u043c\u0443 \u043e\u0431\u0441\u043b\u0443\u0436\u0438\u0432\u0430\u043d\u0438\u044e. \u041a\u043e\u043d\u0444\u0435\u0440\u0435\u043d\u0446\u0438\u044f \u0443\u0434\u0430\u043b\u0430\u0441\u044c: \u0431\u044b\u043b\u043e \u0440\u0435\u0430\u043b\u044c\u043d\u043e \u043c\u043d\u043e\u0433\u043e \u043f\u043e\u043b\u0435\u0437\u043d\u044b\u0445 \u0434\u043e\u043a\u043b\u0430\u0434\u043e\u0432, \u0438\u043d\u0442\u0435\u0440\u0435\u0441\u043d\u044b\u0435 \u0444\u043e\u0440\u043c\u0430\u0442\u044b \u0432\u044b\u0441\u0442\u0443\u043f\u043b\u0435\u043d\u0438\u0439 \u0438 \u043a\u0443\u0447\u0430 \u043e\u0431\u0449\u0435\u043d\u0438\u044f \u0441 \u0434\u043e\u043a\u043b\u0430\u0434\u0447\u0438\u043a\u0430\u043c\u0438. \u0418 \u043e\u0441\u043e\u0431\u0435\u043d\u043d\u043e \u0432\u0430\u0436\u043d\u043e, \u0447\u0442\u043e \u043c\u043d\u0435 \u043d\u0438\u043a\u0442\u043e \u043d\u0438\u0447\u0435\u0433\u043e \u043d\u0435 \u043f\u044b\u0442\u0430\u043b\u0441\u044f \u043f\u0440\u043e\u0434\u0430\u0442\u044c, […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":24300,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-32497","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\udd47DevOpsForum 2019. Implementaci DevOps nelze odkl\u00e1dat | ProHoster","description":"Ned\u00e1vno jsem se z\u00fa\u010dastnila DevOpsForum 2019, kter\u00e9 organizoval Logrocon.","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/devopsforum-2019-vnedryat-devops-nelzya-zhdat","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\udd47DevOpsForum 2019. \u0412\u043d\u0435\u0434\u0440\u044f\u0442\u044c DevOps \u043d\u0435\u043b\u044c\u0437\u044f \u0436\u0434\u0430\u0442\u044c | ProHoster","og:description":"\u041d\u0435\u0434\u0430\u0432\u043d\u043e \u044f \u043f\u043e\u0431\u044b\u0432\u0430\u043b\u0430 \u043d\u0430 DevOpsForum 2019, \u043a\u043e\u0442\u043e\u0440\u0443\u044e \u0443\u0441\u0442\u0440\u0430\u0438\u0432\u0430\u043b Logrocon.","og:url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/devopsforum-2019-vnedryat-devops-nelzya-zhdat","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-31T18:47:23+00:00","article:modified_time":"2019-10-31T18:47:23+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"32497","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-19 09:14:07","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 02:57:23","updated":"2026-02-19 09:14:07","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\/32497","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=32497"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/32497\/revisions"}],"predecessor-version":[{"id":161790,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/32497\/revisions\/161790"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media\/24300"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=32497"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=32497"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=32497"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}