Kwanan nan na halarci DevOpsForum 2019, wanda Logrocon ya shirya. A wannan taron, mahalarta sun yi ƙoƙarin nemo mafita da sabbin kayan aiki don ingantaccen hulɗa tsakanin kasuwanci da haɓakawa da ƙwararrun sabis na fasahar bayanai.
Taron ya yi nasara: hakika akwai rahotanni masu amfani da yawa, tsarin gabatarwa mai ban sha'awa da kuma yawan sadarwa tare da masu magana. Kuma yana da mahimmanci cewa babu wanda ya yi ƙoƙari ya sayar da ni wani abu, wani abu da masu magana a manyan taro sun kasance masu laifi a kwanan nan.
Wani yanki daga jawabai na Raiffeisenbank, Alfastrakhovie, ƙwarewar Mango Telecom wajen aiwatar da aiki da kai da sauran cikakkun bayanai a ƙarƙashin yanke.
Sunana Yana, Ina aiki a matsayin mai gwadawa, Ina yin aiki da kai, da kuma DevOps, kuma ina son zuwa taro da taro. A cikin shekaru biyu da suka gabata, na kasance zuwa taron Oleg Bunin (HighLoad ++, TeamLead Conf), Jug events (Heisenbug, JPoint), TestCon Moscow, DevOps Pro Moscow, Big Data Moscow.
Da farko, na jawo hankali ga shirin taro. Ina kallon abin da rahoton zai kasance game da shi, da ƙari ga mai magana. Ko da rahoton ya zama fasaha da ban sha'awa sosai, ba gaskiya ba ne cewa za ku iya amfani da wasu mafi kyawun ayyuka daga rahoton a cikin kamfanin ku. Sannan kuna buƙatar lasifika.
Haske a ƙarshen bututun a Raiffeisenbank
Yawancin lokaci, Ina farautar masu magana a gefen da ke sha'awar ni. A DevOpsForum 2019, mai magana daga Raiffeisenbank, Mikhail Bizhan, ya sami sha'awata. A yayin jawabin nasa, ya yi magana game da yadda sannu a hankali suke samun ƙungiyoyin su akan DevOps, dalilin da yasa suke buƙata, da kuma yadda ake siyar da ra'ayin DevOps canzawa zuwa kasuwanci. To, gabaɗaya, na yi magana game da yadda ake ganin haske a ƙarshen bututun.
Mikhail Bizhan, darektan sarrafa kansa a bankin Raiffeisen
Yanzu ba su da "DevOps" a cikin kamfanin su. Wato yana aiki, amma ba a cikin dukkan ƙungiyoyi ba. Lokacin aiwatar da DevOps, sun dogara da shirye-shiryen ƙungiyoyin, duka cikin ƙayyadaddun injiniyoyi, da kuma dangane da buƙatun samfurin da balaga da dandamali wanda aka gina wannan samfur. Misha ya faɗi yadda ake bayyana wa kasuwanci dalilin da yasa ake buƙatar DevOps.
Bangaren banki yana da direbobin haɓaka da yawa: farashin sabis da faɗaɗa tushen abokin ciniki. Ƙara farashin sabis ba direba mai kyau ba ne, amma haɓaka tushen abokin ciniki shine akasin haka. Idan masu fafatawa sun saki samfur mai sanyi da gaske, duk abokan ciniki suna zuwa can, sannan a kan lokaci kasuwa ya ƙare. Don haka, gabatar da sabbin kayayyaki a kasuwa da saurin gabatarwar su shine babban abin da bankunan ke mayar da hankali a kai. Wannan shine ainihin abin da DevOps ke nufi, kuma 'yan kasuwa sun fahimci wannan.
Bayani mai mahimmanci na gaba: DevOps ba koyaushe yana rage lokaci zuwa kasuwa ba. DevOps ba zai iya aiki shi kaɗai ba, kawai wani ɓangare ne na tsarin ƙirƙira da kawo samfuri zuwa kasuwa daga haɓakawa zuwa samarwa (daga lamba zuwa abokin ciniki). Amma duk abin da ke gaban lambar ba shi da alaƙa kai tsaye da DevOps. Wato 'yan kasuwa na iya yin nazarin kasuwa na tsawon shekaru kuma su kashe rayuwarsu gaba ɗaya don cim ma masu fafatawa. Wajibi ne a hanzarta fahimtar abin da abokin ciniki ke bukata da kuma tsara aiwatar da wannan ko wannan fasalin - sau da yawa wannan shine abin da bai isa ba don DevOps yayi aiki da kamfanin don cimma burinsa. Saboda haka, da farko, Raiffeisenbank ya yarda da kasuwanci cewa ya zama dole don koyon yadda ake amfani da DevOps. Automation don kare kanka da sarrafa kansa ba zai taimaka da yawa a cikin yaƙi don sababbin abokan ciniki ba.
Gabaɗaya, Misha ya yi imanin cewa DevOps yana buƙatar aiwatarwa, amma cikin hikima. Kuma dole ne mu kasance a shirye don gaskiyar cewa a farkon sauye-sauyen aikin ƙungiyar zai ragu, zai sami kuɗi kaɗan, amma sai ya zama barata.
Automation na gwaji a Mango Telecom
Wani rahoto mai ban sha'awa a gare ni a matsayin mai gwadawa an ba shi Egor Maslov daga Mango Telecom. An kira gabatarwar "Automation na cikakken gwajin gwaji a cikin ƙungiyar SCRUM." Egor ya yi imanin cewa an halicci DevOps musamman don SCRUM, amma a lokaci guda, gabatar da DevOps a cikin ƙungiyar SCRUM yana da matsala sosai. Wannan yana faruwa ne saboda ƙungiyar SCRUM koyaushe tana gudana a wani wuri, babu lokacin da za a shagala da sabbin abubuwa da sake gina tsarin. Matsalar kuma ta ta'allaka ne akan gaskiyar cewa SCRUM ba ya haɗa da rarrabuwa na ƙananan ƙungiyoyi a cikin ƙungiyar (ƙungiyar gwaji, ƙungiyar ci gaba, da sauransu). Da kyau, ban da, don sarrafa tsarin da ke akwai, ana buƙatar takardu, kuma a cikin SCRUM, galibi babu takaddun gabaɗaya - "samfurin yana da mahimmanci fiye da wani nau'in rubutu."
Bayan canzawa zuwa SCRUM, masu gwadawa sun fara tuntuɓar masu haɓakawa kan yadda ake gwada fasali. A hankali, ƙarar aikin ya karu, babu takardun shaida, kuma sun fara kama kwari da yawa a cikin ayyukan da ba a rufe su ta hanyar gwaje-gwaje kuma a gaba ɗaya ba a bayyana wanda ya gwada shi da kuma lokacin da. A takaice - rudani da rudani. Mun yanke shawarar canzawa zuwa gwaji ta atomatik. Amma ko a lokacin an yi kasa a gwiwa sosai. Sun dauki hayar ƙwararrun ƙwararrun kera waɗanda suka yi rubuce-rubuce a kan tarin da ba a san su ba ga masu gwajin gida. Tsarin don autotests yayi aiki, ba shakka, amma bayan masu fitar da waje sun tafi, ya ɗauki makonni biyu. Na gaba shine yunƙurin gabatar da lamba na biyu ta atomatik. Ya fara da gaskiyar cewa duk abin da ke buƙatar ginawa a cikin kamfani, a kan ku (madaidaicin vector: haɓaka gwaninta a ciki), a cikin tsarin SCRUM, da ƙirƙirar takardu a cikin tsari. Tarin don sarrafa kansa yakamata ya zama daidai da tarin samfurin (a nan ina ƙara shi, kar a gwada aikin JavaScript ɗinku da wani abu). A ƙarshen sprint, sun yi demo na yadda autotest ke aiki tare da duka ƙungiyar (mai taimako). Don haka, shigar da duk membobin ƙungiyar a cikin tsarin sarrafa kansa ya karu, da kuma dogara ga autotest da damar cewa tabbas za a yi amfani da wannan autotest (kuma ba za a yi sharhi a cikin wata ɗaya ba saboda gazawar ci gaba).
Af, a DevOpsForum 2019 akwai buɗaɗɗen makirufo - sanannen sananne kuma, a ganina, tsarin maganganu masu amfani. Kuna yawo kamar wannan, sauraron rahotanni, sannan ku yanke shawara cewa a taron yana da kyau a tattauna wani batu ko matsala, raba abubuwan da suka dace don magance matsalar.
Na kuma lura cewa masu shirya taron sun yi takaitattun rahotanni. Kowane rahoto bai wuce mintuna 10 ba, sai tambayoyi. Ta wannan hanyar za ku iya ɗaukar batutuwa da yawa a lokaci ɗaya kuma ku yi tambayoyi ga masu magana da ke sha'awar ku.
Tsakanin gabatarwa, na zagaya cikin rumfuna na abokan taron kuma na sata / lashe abubuwa da yawa. Oh, ina son handout ɗin!
Tebur mai zagaye da batutuwan DevOps tare da darektan ci gaba a Alfastrakhovie
Icing a kan kek na DevOpsForum 2019 a gare ni shine taron na tsawon sa'o'i tare da masana DevOps. An gayyaci mahalarta hudu don kallon DevOps daga kusurwoyi daban-daban: Anton Isanin (Alfastrakhovie, darektan ci gaba), Nailya Zamashkina (Fintech Lab, darektan aiki), Oleg Egorkin (Rostelecom, kocin Agile) da Anton Martyanov (kwararre mai zaman kansa, ya dubi DevOps). daga mahangar kasuwanci).
Kwararrun sun zauna kusa da mutane sannan abubuwa suka fara faruwa: tsawon sa'a guda daya, mahalarta taron sun tambayi tambayoyinsu, kuma masana sun dauki rap. Wani lokaci ana yin muhawara ta gaske. Tambayoyin sun bambanta sosai, alal misali: injiniyoyin DevOps ne da ake buƙata kwata-kwata, me yasa ba za a iya horar da su azaman masu gudanar da tsarin ba, ya kamata a ba da DevOps ga kowa da kowa, menene ƙimarsa, da sauransu.
Sa'an nan, na yi magana da Anton Isanin da kaina. Mun tattauna batun buƙatar kawo al'adun DevOps zuwa kowane gida kuma mun bayyana yanayin duhu na canjin DevOps.
Bari mu yi tunanin cewa kowa ya taru kuma ya yanke shawarar cewa ana buƙatar DevOps duka ta samfurin da kasuwanci da ƙungiyar. Mu je aiwatar da shi. Komai yayi kyau. Muka fitar da numfashi. DevOps ya kawo mu kusa da abokin ciniki, yanzu za mu iya cika duk burinsa da sauri. Sakamakon haka, muna da babban sashin Ops tare da tsauraran ƙa'idodi da buƙatu, kuma koyaushe yana samun lahani a cikin samfurin kuma yana ƙirƙirar buƙatun buƙatun. Haka kuma, duk lahani an sanya matsayin "gaggawa", koda kuwa abokin ciniki ba zato ba tsammani ya so ya canza launin rawaya maballin maimakon kore. Aikin yana girma, adadin sakewa yana girma kuma, daidai da haka, yawan lahani da rashin fahimtar sababbin ayyuka ta abokan ciniki. Ops yana ɗaukar ƙarin mutane 10 don ci gaba da ba da rahoton lahani, kuma ci gaba yana ɗaukar ƙarin 15 don ci gaba da rufe su. Kuma maimakon gabatar da sabbin abubuwa, ƙungiyar tana aiki tare da SD mara iyaka, tana bayyana ayyukan ga mai amfani da tallafi a lokaci guda. A sakamakon haka, duka Ops da ci gaba suna aiki, amma abokin ciniki da kasuwanci ba su da farin ciki: sababbin siffofi sun makale. Ya bayyana cewa DevOps da alama ya wanzu, amma ba ze wanzu ba.
Game da buƙatar aiwatar da DevOps, Anton ya bayyana a sarari cewa wannan kai tsaye ya dogara da sikelin kasuwancin. Idan hidimar abokin ciniki ɗaya a shekara yana kawo kamfani biliyan, DevOps ba a buƙata (idan har ba kwa buƙatar fitar da sabbin canje-canje ga wannan abokin ciniki akai-akai). An rufe komai da cakulan. Amma idan kasuwancin ya girma kuma ƙarin abokan ciniki sun bayyana, to kuna buƙatar bi. A matsayinka na mai mulki, babu Ops mai sanyi a cikin kamfanin da farko. Da farko mun yanke samfurin, sannan kawai mu fahimci cewa don samfurin ya yi aiki, muna buƙatar sa ido kan sabar da sa ido kan kayayyaki. Wannan shine lokacin da Ops ya kasance. Ya kamata a fahimci cewa Ops, a matsayin wani yanki na daban, zai fara sanya gungun shinge don ci gaba kuma duk abubuwan da aka kawo zasu fara tsayawa. Wato, a wannan yanayin, al'adun DevOps sun riga sun dace, amma kada mu manta game da gefen duhu.
source: www.habr.com