{"id":57574,"date":"2021-10-01T12:40:57","date_gmt":"2021-10-01T12:40:57","guid":{"rendered":"https:\/\/www.globallogic.com\/sk\/?post_type=insightsection&p=57574"},"modified":"2025-03-08T18:05:45","modified_gmt":"2025-03-08T18:05:45","slug":"devops-nie-je-technologicky-checklist","status":"publish","type":"insightsection","link":"https:\/\/www.globallogic.com\/sk\/insights\/blogs\/devops-nie-je-technologicky-checklist\/","title":{"rendered":"DevOps nie je technologick\u00fd checklist"},"content":{"rendered":"
E\u0161te ned\u00e1vno by ste pojem DevOps m\u00e1rne h\u013eadali v knih\u00e1ch a vo vyh\u013ead\u00e1va\u010doch. Toto slov\u00ed\u010dko <\/span>ale<\/span> v sebe skr\u00fdva prevratn\u00fa metodol\u00f3giu, ktor\u00e1 zefekt\u00edvnila, u\u013eah\u010dila a spr\u00edjemnila pr\u00e1cu mnoh\u00fdm IT profesion\u00e1lom po celom svete a \u010fal\u0161\u00edm dala n\u00e1vod, ako spoji\u0165 dovtedy nespojite\u013en\u00e9 svety developerov a administr\u00e1torov.<\/span><\/p>\n

Ve\u013ea \u013eud\u00ed pohybuj\u00facich sa v IT si sp\u00e1ja DevOps s konkr\u00e9tnymi n\u00e1strojmi ako napr\u00edklad Azure DevOps, AWS, Chef, Puppet alebo Docker.<\/strong> Ale toto s\u00fa len samotn\u00e9 n\u00e1stroje, nie DevOps metodol\u00f3gia<\/strong>. \u010co rob\u00ed tieto n\u00e1stroje \u201eDevOps\u201c je <\/span>ale<\/span> sp\u00f4sob ich pou\u017e\u00edvania, nie samotn\u00e1 charakteristika n\u00e1strojov ako tak\u00fdch. Aj ke\u010f je DevOps metodol\u00f3gia silno ovplyvnen\u00e1 in\u00fdmi (napr. Agile), jej aplikovanie je v\u00fdznamnej\u0161ie, preto\u017ee Agile sa zameriava iba na str\u00e1nku v\u00fdvoja, zatia\u013e \u010do DevOps zah\u0155\u0148a viac ako len programovanie a testovanie. Jeho aplik\u00e1cia nie je obmedzen\u00e1 iba na IT profesion\u00e1lov. DevOps je naj\u00fa\u010dinnej\u0161\u00ed pr\u00e1ve vtedy, ke\u010f si jeho ideu a koncept osvoj\u00ed a praktizuje cel\u00e1 organiz\u00e1cia. V\u0161etky t\u00edmy v r\u00e1mci organiz\u00e1cie by mali by\u0165 zapojen\u00e9 \u2013 vr\u00e1tane security, podpory, HR, pr\u00e1vneho oddelenia \u2013 aby boli \u010do najefekt\u00edvnej\u0161ie. Napr\u00edklad efekt\u00edvne DevOps procesy medzi pr\u00e1vnym a predajn\u00fdm oddelen\u00edm by mohli umo\u017eni\u0165 automatizovan\u00e9 vytv\u00e1ranie kontraktov na z\u00e1klade stanoven\u00e9ho katal\u00f3gu predaja.<\/span><\/p>\n

\u0160tyri piliere efekt\u00edvneho DevOps<\/b><\/h3>\n

Nie je to teda iba o r\u00f4znych v\u00fdvoj\u00e1rskych met\u00f3dach, ako napr\u00edklad automatiz\u00e1cia infra\u0161trukt\u00fary, continuous integration (CI) \u010di continuous delivery (CD). Je to viac ako iba spojenie jednotliv\u00fdch \u010dast\u00ed. Je to kult\u00fara a nastavenie mysle \u013eud\u00ed zamestnan\u00fdch vo firme. Ke\u010f\u017ee ka\u017ed\u00e1 firma m\u00e1 in\u00fdch zamestnancov, in\u00e9 potreby a in\u00e9 probl\u00e9my, nem\u00f4\u017ee existova\u0165 jedno rie\u0161enie a jedin\u00fd \u201espr\u00e1vny\u201c sp\u00f4sob ako robi\u0165 DevOps. Na to, aby sme vo firme mohli implementova\u0165 DevOps, mus\u00ed dan\u00e1 firma obetova\u0165 \u010das a \u00fasilie na takzvan\u00e9 <\/span>\u0161tyri hlavn\u00e9 piliere efekt\u00edvneho DevOps:<\/b><\/p>\n

    \n
  • Spolupr\u00e1ca<\/strong><\/li>\n
  • Sympatia<\/strong><\/li>\n
  • N\u00e1stroje<\/strong><\/li>\n
  • \u0160k\u00e1lovanie<\/strong><\/li>\n<\/ul>\n

    Pre za\u010diatok by si mala firma vybra\u0165 jeden alebo dva z t\u00fdchto pilierov naraz a sna\u017ei\u0165 sa o zmenu, pri\u010dom cie\u013eom je st\u00e1le kombin\u00e1cia v\u0161etk\u00fdch \u0161tyroch pilierov. Je ve\u013emi d\u00f4le\u017eit\u00e9 neprehliadnu\u0165 prv\u00e9 dva piliere a nesna\u017ei\u0165 sa aplikova\u0165 iba n\u00e1stroje. N\u00e1stroje s\u00fa samozrejme d\u00f4le\u017eit\u00e9, av\u0161ak nie dostato\u010dn\u00e9. Ak by to tak bolo, posta\u010dovalo by vymenova\u0165 \u201ebest practices\u201c r\u00f4znych n\u00e1strojov. Spolupr\u00e1ca a sympatia s\u00fa d\u00f4le\u017eit\u00e9 z poh\u013eadu dlhodob\u00e9ho udr\u017eania dobr\u00fdch a dlhotrvaj\u00facich vz\u0165ahov, ktor\u00e9 vytv\u00e1raj\u00fa produkt\u00edvne DevOps prostredie.<\/span><\/p>\n

    \"\"<\/p>\n

    Obr. 1. \u0160tyri piliere efekt\u00edvneho DevOps<\/p>\n

    Spolupr\u00e1ca<\/b><\/h4>\n

    Spolupr\u00e1ca je proces dosiahnutia v\u00fdsledkov cez podporu vz\u00e1jomnej interakcie a vstupov viacer\u00fdch \u013eud\u00ed. <\/span>Ve\u010f<\/span> Pr\u00e1ve spolupr\u00e1ca softv\u00e9rov\u00fdch v\u00fdvoj\u00e1rov a administr\u00e1torov pomohla vytvori\u0165 DevOps. Predt\u00fdm, ako sa t\u00edm nau\u010d\u00ed efekt\u00edvne komunikova\u0165 s in\u00fdm t\u00edmom, musia sa \u010dlenovia t\u00edmu najsk\u00f4r nau\u010di\u0165 komunikova\u0165 medzi sebou. Bez dobrej spolupr\u00e1ce v r\u00e1mci t\u00edmu je ve\u013emi mal\u00e1 n\u00e1dej na dobr\u00fa spolupr\u00e1cu medzi t\u00edmami.<\/span><\/p>\n

    Sympatia<\/b><\/h4>\n

    Navy\u0161e<\/span> K rastu a udr\u017eiavaniu pracovn\u00fdch vz\u0165ahov medzi jednotlivcami, t\u00edmami a oddeleniami v organiz\u00e1cii je potrebn\u00e9 budova\u0165 siln\u00e9 vz\u0165ahy. Na prv\u00fd poh\u013ead sa m\u00f4\u017ee tento pilier zda\u0165 ako zanedbate\u013en\u00fd, ke\u010f sa ale na pilier Sympatia pozrieme z h\u013eadiska efektivity, pr\u00eddeme na to, \u017ee je k\u013e\u00fa\u010dov\u00fd rovnako ako ostatn\u00e9 tri. V\u010faka budovaniu siln\u00fdch vz\u0165ahov, \u010di u\u017e medzi t\u00edmami alebo dokonca r\u00f4znymi organiz\u00e1ciami, vieme ve\u013emi \u00fa\u010dinne skr\u00e1ti\u0165 \u010das dodania pr\u00e1ce t\u00fdm, \u017ee odstra\u0148ujeme komunika\u010dn\u00fa bari\u00e9ru a pracujeme na z\u00e1klade silnej d\u00f4very.<\/span><\/p>\n

    N\u00e1stroje<\/b><\/h4>\n

    N\u00e1stroje vn\u00edmame ako akceler\u00e1tor zmeny. M\u00f4\u017ee sa zda\u0165, \u017ee posta\u010duje zmeni\u0165 n\u00e1stroje, ktor\u00e9 t\u00edm pou\u017e\u00edva, a premena na DevOps je ukon\u010den\u00e1. Tento poh\u013ead je ve\u013emi \u010dast\u00fd, no \u017eia\u013e <\/span>je<\/span> ve\u013emi chybn\u00fd. Probl\u00e9my, ktor\u00e9 m\u00e1 organiz\u00e1cia alebo t\u00edm, sa neodstr\u00e1nia sam\u00e9 bez zmeny kult\u00fary a hodn\u00f4t, ktor\u00fdmi sa riadia. Tak isto, ak m\u00e1 t\u00edm probl\u00e9my s n\u00e1strojmi, ktor\u00e9 pou\u017e\u00edva, pr\u00edpadne nepou\u017e\u00edva, iniciat\u00edva na zmenu nemus\u00ed by\u0165 \u00faspe\u0161n\u00e1, pokia\u013e sa neodstr\u00e1nia aj tieto prek\u00e1\u017eky. Na prv\u00fd poh\u013ead ve\u013ek\u00e1 invest\u00edcia v za\u010diatkoch spolupr\u00e1ce je v tomto pr\u00edpade st\u00e1le men\u0161ia, ako cena bez invest\u00edcie do spr\u00e1vnych n\u00e1strojov.<\/span><\/p>\n

    \u0160k\u00e1lovanie<\/b><\/h4>\n

    Mus\u00edme sa tie\u017e pozera\u0165 na aplikovate\u013enos\u0165 DevOps nielen vo ve\u013ek\u00fdch organiz\u00e1ci\u00e1ch, ale aj v men\u0161\u00edch podnikoch, \u010di dokonca start-upoch. Tu vstupuje do hry \u0161k\u00e1lovanie, \u0161pecifick\u00fd pr\u00edstup a vyu\u017e\u00edvanie DevOps metodol\u00f3gie v t\u00edmoch a organiz\u00e1ci\u00e1ch r\u00f4znych ve\u013ekost\u00ed. DevOps mus\u00ed dynamicky reflektova\u0165 zmeny \u010di u\u017e person\u00e1lnych z h\u013eadiska po\u010dtu \u010dlenov t\u00edmu, organiz\u00e1cie, v\u00fd\u0161ky zisku, roz\u0161irovania pobo\u010diek alebo tzv. zrelosti a pripravenosti. To znamen\u00e1, \u017ee nemus\u00ed ma\u0165 rovnak\u00fd \u00faspech proces zaveden\u00fd v organiz\u00e1cii, ktor\u00e1 m\u00e1 500 zamestnancov a v startupe, na ktorom pracuj\u00fa \u0161tyria v\u00fdvoj\u00e1ri. Ka\u017ed\u00fd z t\u00fdchto syst\u00e9mov je \u0161pecifick\u00fd a je k nim potrebn\u00fd \u0161pecifick\u00fd pr\u00edstup.<\/span><\/p>\n

    Cultural-debt<\/b><\/h3>\n

    Pojem \u201ctech-debt\u201d<\/strong> pozn\u00e1 asi ka\u017ed\u00fd v\u00fdvoj\u00e1r. Vypoved\u00e1 o potencion\u00e1lnych n\u00e1sledkoch technick\u00fdch rozhodnut\u00ed, ako napr\u00edklad syst\u00e9mov\u00fd dizajn, architekt\u00fara softwaru, alebo v\u00fdber technol\u00f3gi\u00ed. Menej z nich pozn\u00e1 alebo rozumie v\u00fdrazu \u201ccultural-debt\u201d.<\/strong> Ozna\u010duj\u00fa sa n\u00edm podobne ako pri predo\u0161lom pojme, mo\u017en\u00e9 n\u00e1sledky, av\u0161ak v tomto pr\u00edpade rozhodnutia, ktor\u00e9 sa t\u00fdkaj\u00fa naberaniu alebo prep\u00fa\u0161\u0165aniu zamestnancov, firemn\u00e9 alebo t\u00edmov\u00e9 \u0161tandardy a hodnoty. Rovnako ako \u201ctech-debt\u201d, aj \u201ccultural-debt\u201d v\u017edy organiz\u00e1ciu alebo t\u00edm dobehne a musia \u010deli\u0165 n\u00e1sledkom. Taktie\u017e plat\u00ed aj fakt, \u010d\u00edm nesk\u00f4r sa na \u0148om za\u010dne pracova\u0165, t\u00fdm bude \u0165a\u017e\u0161ie sa z tohto dlhu dosta\u0165. \u010casto sa tieto probl\u00e9my nedaj\u00fa vyrie\u0161i\u0165 zo d\u0148a na de\u0148, ale vy\u017eaduj\u00fa kontinu\u00e1lnu pr\u00e1cu na kult\u00fare d\u00f4very, jednoty a bez obvi\u0148ovania. Nieko\u013eko pr\u00edkladov na \u201cculture-debt\u201d, ktor\u00e9 mo\u017eno pozorujete aj vo va\u0161ej organiz\u00e1cii alebo t\u00edme:<\/span><\/p>\n

      \n
    • kolega, s ktor\u00fdm sa ve\u013emi \u0165a\u017eko spolupracuje a t\u00edm mu rad\u0161ej ust\u00fapi alebo zamestnanci od\u00eddu, ako by ho poprosil o zmenu jeho problematick\u00e9ho spr\u00e1vania,<\/span><\/li>\n
    • pr\u00edli\u0161 ve\u013ea vrstiev stredn\u00e9ho mana\u017ementu, ktor\u00fd v kone\u010dnom d\u00f4sledku br\u00e1ni a spoma\u013euje v\u00fdvoj aplik\u00e1cie,<\/span><\/li>\n
    • tolerovanie ur\u00e1\u017eliv\u00e9ho slovn\u00edka v mailoch a in\u00fdch komunik\u00e1ci\u00e1ch,<\/span><\/li>\n
    • t\u00edmov\u00e9 prostredie, kde s\u00fa zamestnanci dostupn\u00ed aj v neskor\u00fdch ve\u010dern\u00fdch hodin\u00e1ch a odpovedaj\u00fa na maily a in\u00e9 po\u017eiadavky.<\/span><\/li>\n<\/ul>\n

      Ak sa posunieme od hodn\u00f4t, ktor\u00e9 prezentuje organiz\u00e1cia zamestnancom a dostaneme sa \u010falej, bli\u017e\u0161ie ku jednotliv\u00fdm zamestnancom, m\u00f4\u017eeme pr\u00eds\u0165 na to, \u017ee hodnoty s\u00fa r\u00f4zne aj v r\u00e1mci jedn\u00e9ho t\u00edmu. Hovorili sme, ako r\u00f4zne hodnoty a ciele naru\u0161ia chod t\u00edmu a v kone\u010dnom d\u00f4sledku aj celej organiz\u00e1cie. Sna\u017ei\u0165 sa r\u00fdchlo doru\u010dova\u0165 nov\u00e9 funkcionality alebo za ka\u017ed\u00fa cenu udr\u017eiava\u0165 stabiln\u00fa webstr\u00e1nku? Tak\u00e9to rozli\u010dn\u00e9 vn\u00edmanie cie\u013ea sp\u00f4sobuje probl\u00e9my pri chode aplik\u00e1cie a takisto aj v t\u00edme samotnom. Z dlhodob\u00e9ho h\u013eadiska je tak\u00fdto pr\u00edstup s nedostatkom komunik\u00e1cie a s nezhodami na hlavn\u00fdch hodnot\u00e1ch a cie\u013eoch t\u00edmu neudr\u017eate\u013en\u00fd.<\/span><\/p>\n

      Ako na efekt\u00edvny DevOps<\/b><\/h3>\n

      Tieto a r\u00f4zne in\u00e9 probl\u00e9my v\u0161ak nevyrie\u0161i iba vsunutie slov\u00ed\u010dka DevOps<\/strong> pred pracovn\u00fa poz\u00edciu alebo meno t\u00edmu. DevOps nie je o n\u00e1kupe nov\u00fdch technol\u00f3gi\u00ed na kontajneriz\u00e1ciu alebo \u00fa\u010dtov na cloude. Nie je to iba jedna z mnoh\u00fdch vec\u00ed na zozname, nie je to nie\u010do, \u010do sa niekedy d\u00e1 pova\u017eova\u0165 za \u201chotov\u00e9\u201d. Devops je postupn\u00fd proces, ktor\u00fd sa mus\u00ed neust\u00e1le vyv\u00edja\u0165 a aktualizova\u0165, inak nezostane v organiz\u00e1cii a t\u00edme zdie\u013ean\u00fd pr\u00edli\u0161 dlho. DevOps je o porozumen\u00ed, empatii a prepojenosti \u0161tyroch hlavn\u00fdch pilierov. Spolu tieto piliere tvoria a posil\u0148uj\u00fa z\u00e1klady udr\u017eate\u013enej kult\u00fary a pracoviska. Z\u00e1rove\u0148 tie\u017e pestuj\u00fa zdrav\u00e9 medzi\u013eudsk\u00e9 vz\u0165ahy v t\u00edme, kde to nie je len o jednej hviezde, ktor\u00fa v\u0161etci uzn\u00e1vaj\u00fa, ale sk\u00f4r o orchestri, kde je ka\u017ed\u00fd \u010dlen t\u00edmu je rovnako d\u00f4le\u017eit\u00fd a takisto je ka\u017ed\u00fd \u00faspech \u00faspechom cel\u00e9ho t\u00edmu.<\/span><\/p>\n

      Referencie
      \n<\/strong>Literat\u00fara: Effective DevOps by Jennifer Davis & Ryn Daniels<\/span><\/div>\n","protected":false},"excerpt":{"rendered":"

      DevOps v sebe skr\u00fdva prevratn\u00fa metodol\u00f3giu, ktor\u00e1 zefekt\u00edvnila, u\u013eah\u010dila a spr\u00edjemnila pr\u00e1cu mnoh\u00fdm IT profesion\u00e1lom po celom svete. Ak\u00e9 s\u00fa \u0161tyri z\u00e1kladn\u00e9 piliere efekt\u00edvneho DevOps?<\/p>\n","protected":false},"author":36,"featured_media":57622,"parent":0,"menu_order":0,"template":"","insight":[41],"insight-subcats":[54],"insight-industry":[750],"insight-services":[],"insight-partners":[],"class_list":["post-57574","insightsection","type-insightsection","status-publish","has-post-thumbnail","hentry","insight-blogs","insight-subcats-devops-as-a-service","insight-industry-technology"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.globallogic.com\/sk\/wp-json\/wp\/v2\/insightsection\/57574","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.globallogic.com\/sk\/wp-json\/wp\/v2\/insightsection"}],"about":[{"href":"https:\/\/www.globallogic.com\/sk\/wp-json\/wp\/v2\/types\/insightsection"}],"author":[{"embeddable":true,"href":"https:\/\/www.globallogic.com\/sk\/wp-json\/wp\/v2\/users\/36"}],"version-history":[{"count":2,"href":"https:\/\/www.globallogic.com\/sk\/wp-json\/wp\/v2\/insightsection\/57574\/revisions"}],"predecessor-version":[{"id":102445,"href":"https:\/\/www.globallogic.com\/sk\/wp-json\/wp\/v2\/insightsection\/57574\/revisions\/102445"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.globallogic.com\/sk\/wp-json\/wp\/v2\/media\/57622"}],"wp:attachment":[{"href":"https:\/\/www.globallogic.com\/sk\/wp-json\/wp\/v2\/media?parent=57574"}],"wp:term":[{"taxonomy":"insight","embeddable":true,"href":"https:\/\/www.globallogic.com\/sk\/wp-json\/wp\/v2\/insight?post=57574"},{"taxonomy":"insight-subcats","embeddable":true,"href":"https:\/\/www.globallogic.com\/sk\/wp-json\/wp\/v2\/insight-subcats?post=57574"},{"taxonomy":"insight-industry","embeddable":true,"href":"https:\/\/www.globallogic.com\/sk\/wp-json\/wp\/v2\/insight-industry?post=57574"},{"taxonomy":"insight-services","embeddable":true,"href":"https:\/\/www.globallogic.com\/sk\/wp-json\/wp\/v2\/insight-services?post=57574"},{"taxonomy":"insight-partners","embeddable":true,"href":"https:\/\/www.globallogic.com\/sk\/wp-json\/wp\/v2\/insight-partners?post=57574"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}