DevOps ya zama babban jigo a cikin ƴan shekarun da suka gabata. Mutane da yawa suna mafarkin shiga shi, amma, kamar yadda aikin ya nuna, sau da yawa kawai saboda matakin albashi.
Wasu mutane suna jera DevOps akan aikin su, kodayake ba koyaushe suke sani ko fahimtar ainihin kalmar ba. Wasu mutane suna tunanin cewa bayan nazarin Mai yiwuwa, GitLab, Jenkins, Terraform da makamantansu (za a iya ci gaba da lissafin bisa ga dandano), nan da nan za ku zama "mai son zuciya". Wannan, ba shakka, ba gaskiya ba ne.
A cikin 'yan shekarun da suka gabata, na kasance da hannu a cikin aiwatar da DevOps a cikin kamfanoni daban-daban. Kafin haka, ya yi aiki sama da shekaru 20 a mukamai tun daga mai kula da tsarin zuwa darektan IT. A halin yanzu DevOps Jagoran Injiniya a Playgendary.
Wanene DevOps
Tunanin rubuta labarin ya taso bayan wata tambaya: "wane ne DevOps?" Har yanzu babu wani takamaiman wa'adi na menene ko wanene. Wasu amsoshin sun riga sun kasance a cikin wannan . Da farko, zan haskaka muhimman batutuwa daga cikinsa, sannan kuma in bayyana abubuwan lura da tunani na.
DevOps ba ƙwararre ba ne wanda za a iya ɗauka, ba saitin kayan aiki ba, kuma ba sashen masu haɓakawa tare da injiniyoyi ba.
DevOps falsafa ce da hanya.
A takaice dai, saitin ayyuka ne da ke taimaka wa masu haɓakawa yin hulɗa tare da masu gudanar da tsarin. Wato, haɗawa da haɗa hanyoyin aiki cikin juna.
Tare da zuwan DevOps, tsari da matsayin ƙwararru sun kasance iri ɗaya (akwai masu haɓakawa, akwai injiniyoyi), amma ka'idodin hulɗar sun canza. Iyakoki tsakanin sassan sun yi duhu.
Ana iya siffanta manufofin DevOps a cikin maki uku:
- Dole ne a sabunta software akai-akai.
- Software dole ne a yi sauri.
- Ya kamata a tura software ɗin cikin sauƙi kuma cikin ɗan gajeren lokaci.
Babu kayan aiki guda ɗaya don DevOps. Saita, isarwa da kuma nazarin samfuran da yawa baya nufin DevOps ya bayyana a cikin kamfanin. Akwai kayan aiki da yawa kuma ana amfani da su duka a matakai daban-daban, amma suna yin manufa ɗaya.
Kuma wannan yanki ne kawai na kayan aikin DevOps
Na yi hira da mutane don matsayin injiniyan DevOps fiye da shekaru 2 yanzu, kuma na fahimci yadda yake da muhimmanci a fahimci ainihin kalmar. Na tara takamaiman gogewa, lura da tunani waɗanda nake so in raba.
Daga gwanintar hira, ina ganin hoto mai zuwa: ƙwararrun da suka ɗauki DevOps matsayin aikin yawanci suna samun rashin fahimta tare da abokan aiki.
Akwai misali mai ban mamaki. Wani matashi yazo hira da kalmomi masu wayo akan cigaban sa. A ayyukansa uku na ƙarshe, yana da ƙwarewar watanni 5-6. Na bar farawa biyu saboda "ba su tashi ba." Amma game da kamfani na uku, ya ce babu wanda ya fahimce shi a can: masu haɓakawa sun rubuta lambar akan Windows, kuma darektan ya tilasta wannan lambar don "nannade" a cikin Docker na yau da kullum kuma an gina shi a cikin bututun CI / CD. Mutumin ya faɗi abubuwa mara kyau game da wurin aikinsa na yanzu da abokan aikinsa - Ina so in amsa: "Don haka ba za ku sayar da giwa ba."
Sai na yi masa tambayar da ke cikin jerin sunayena ga kowane dan takara.
- Menene DevOps yake nufi a gare ku da kanku?
- Gaba ɗaya ko ta yaya zan gane shi?
Ina sha'awar ra'ayinsa na sirri. Ya san ka'idar da asalin kalmar, amma ya yi sabani sosai da su. Ya yi imani DevOps taken aiki ne. Anan ne tushen matsalolinsa yake. Kazalika da sauran kwararru masu irin wannan ra'ayi.
Masu daukan ma'aikata, da suka ji da yawa game da "sihiri na DevOps", suna so su sami mutumin da zai zo ya haifar da wannan "sihiri". Kuma masu nema daga rukunin "DevOps aiki ne" ba su fahimci cewa tare da wannan hanyar ba za su iya cimma abin da ake tsammani ba. Kuma, gabaɗaya, sun rubuta DevOps akan ci gaban su saboda yanayin yanayi ne kuma suna biyan shi da yawa.
Hanyar DevOps da falsafa
Hanyar na iya zama ta tunani da aiki. A cikin yanayinmu, shi ne na biyu. Kamar yadda na ambata a sama, DevOps wani tsari ne na ayyuka da dabarun da ake amfani da su don cimma manufofin da aka bayyana. Kuma a kowane hali, dangane da tsarin kasuwancin kamfani, yana iya bambanta sosai. Wanda ba ya sa ya fi ko muni.
Hanyar DevOps hanya ce kawai don cimma burin.
Yanzu game da menene falsafar DevOps. Kuma tabbas wannan ita ce tambaya mafi wahala.
Yana da matukar wahala a tsara gajeriyar amsa, domin har yanzu ba a tsara ta ba. Kuma tun da masu bin falsafar DevOps sun fi tsunduma a aikace, babu lokaci don falsafa. Duk da haka, wannan tsari ne mai mahimmanci. Haka kuma, yana da alaƙa kai tsaye da ayyukan injiniya. Akwai ma fannin ilimi na musamman - .
Babu irin wannan batun a jami'a, dole ne in yi nazarin komai da kaina ta amfani da kayan da zan iya samu a cikin 90s. Batun zaɓi ne don ilimin injiniyanci, don haka rashin daidaituwar amsar. Amma waɗancan mutanen da suka nutsar da gaske a cikin DevOps sun fara jin wani “ruhu” ko “cikakkiyar fahimta” na duk ayyukan kamfanin.
Yin amfani da gogewar kaina, na yi ƙoƙari in tsara wasu “postulates” na wannan falsafar. Sakamakon shine kamar haka:
- DevOps ba wani abu bane mai zaman kansa wanda za'a iya raba shi zuwa wani yanki na ilimi ko aiki daban.
- Duk ma'aikatan kamfanin yakamata su kasance jagora ta hanyar DevOps lokacin tsara ayyukansu.
- DevOps yana rinjayar duk matakai a cikin kamfani.
- DevOps ya wanzu don rage farashin lokaci don kowane tsari a cikin kamfani don tabbatar da haɓaka ayyukan sa da matsakaicin kwanciyar hankali na abokin ciniki.
- DevOps, a cikin yare na zamani, shine matsayi na kowane ma'aikaci na kamfanin, wanda ke nufin rage farashin lokaci da inganta ingancin samfuran IT da ke kewaye da mu.
Ina tsammanin cewa “postulates” nawa wani jigo ne daban don tattaunawa. Amma yanzu akwai abin da za a gina a kai.
Abin da DevOps ke Yi
Mabuɗin kalmar anan shine sadarwa. Akwai hanyoyin sadarwa da yawa, wanda ya kamata ya fara zama injiniyan DevOps iri ɗaya. Me yasa haka? Domin wannan falsafa ce da dabara, sannan kuma ilimin injiniya.
Ba zan iya magana da amincewa 100% game da kasuwar aiki na Yamma ba. Amma na san abubuwa da yawa game da kasuwar DevOps a Rasha. Baya ga ɗaruruwan tambayoyin, a cikin shekara da rabi da ta gabata na shiga cikin daruruwan presales na fasaha don sabis na "aiwatar da DevOps" ga manyan kamfanoni da bankunan Rasha.
A cikin Rasha, DevOps har yanzu matashi ne, amma riga mai tasowa batun. Kamar yadda na sani, a cikin Moscow kawai ƙarancin irin waɗannan ƙwararrun a cikin 2019 ya fi mutane 1000. Kuma kalmar Kubernetes ga masu daukar ma'aikata kusan kamar jajayen ja ne ga bijimin. Masu bin wannan kayan aiki suna shirye su yi amfani da shi ko da a inda ba lallai ba ne kuma suna da riba a tattalin arziki. Mai aiki ba koyaushe yana fahimtar abin da ya fi dacewa don amfani da shi ba, kuma tare da turawa da ya dace, kula da gunkin Kubernetes sau 2-3 fiye da tura aikace-aikacen ta amfani da tsarin gungu na al'ada. Yi amfani da shi a inda kuke buƙatar gaske.
Aiwatar da DevOps yana da tsada ta fuskar kuɗi. Kuma ana halatta ne kawai a inda ya kawo fa'idar tattalin arziki a wasu fannoni, ba a kan kansa ba.
Injiniyoyin DevOps, a gaskiya ma, majagaba ne - su ne waɗanda yakamata su zama farkon aiwatar da wannan hanyar a cikin kamfani da gina matakai. Don wannan ya yi nasara, dole ne ƙwararren ya yi hulɗa tare da ma'aikata da abokan aiki a kowane mataki. Kamar yadda na saba fada, duk ma'aikatan kamfanin ya kamata su shiga cikin tsarin aiwatar da DevOps: daga uwar tsafta zuwa Shugaba. Kuma wannan sharadi ne. Idan mafi ƙaramin memba na ƙungiyar bai sani ba kuma ya fahimci abin da DevOps yake da kuma dalilin da yasa ake aiwatar da wasu ayyukan ƙungiyar, to aiwatar da nasara ba zai yi aiki ba.
Hakanan, injiniyan DevOps yana buƙatar amfani da albarkatun gudanarwa lokaci zuwa lokaci. Misali, don shawo kan "juriya na muhalli" - lokacin da ƙungiyar ba ta shirya karɓar kayan aikin DevOps da hanyoyin ba.
Mai haɓakawa yakamata ya rubuta lamba da gwaje-gwaje kawai. Don yin wannan, baya buƙatar kwamfutar tafi-da-gidanka mai ƙarfi wanda zai tura kuma a cikin gida yana tallafawa duk kayan aikin. Misali, mai haɓakawa na gaba yana adana duk abubuwan da ke cikin aikace-aikacen akan kwamfutar tafi-da-gidanka, gami da bayanan bayanai, S3 emulator (minio), da sauransu. Wato yana ciyar da lokaci mai yawa don kula da wannan kayan aiki na gida kuma yana gwagwarmaya da duk matsalolin irin wannan mafita. Maimakon haɓaka lambar don gaba. Irin waɗannan mutane suna iya jure wa kowane canji.
Amma akwai ƙungiyoyi waɗanda, akasin haka, suna farin cikin gabatar da sababbin kayan aiki da hanyoyin, kuma suna shiga cikin wannan tsari. Kodayake ko a wannan yanayin, sadarwa tsakanin injiniyan DevOps da tawagar ba a soke ba.
Lokacin da ba a buƙatar DevOps
Akwai yanayi lokacin da ba a buƙatar DevOps. Wannan gaskiya ne - yana buƙatar fahimta kuma a yarda da shi.
Da farko dai, wannan ya shafi kowane kamfani (musamman ƙananan kamfanoni), lokacin da ribarsu ba ta dogara kai tsaye ga kasancewar ko rashin kayayyakin IT waɗanda ke ba da sabis na bayanai ga abokan ciniki. Kuma a nan ba muna magana ne game da gidan yanar gizon kamfanin ba, ya zama “katin kasuwanci” a tsaye ko tare da tubalan labarai masu ƙarfi, da sauransu.
Ana buƙatar DevOps lokacin da gamsuwar abokin cinikin ku da sha'awarsa ta sake komawa gare ku ya dogara da samuwar waɗannan sabis ɗin bayanai don hulɗa tare da abokin ciniki, ingancin su da kuma niyya.
Misali mai ban sha'awa shine sanannen banki. Kamfanin ba shi da ofisoshin abokin ciniki na gargajiya, ana aiwatar da kwararar takardu ta hanyar wasiku ko masu aikawa, kuma ma'aikata da yawa suna aiki daga gida. Kamfanin ya daina zama banki kawai kuma, a ganina, ya zama kamfanin IT tare da fasahar DevOps.
Ana iya samun wasu misalai da laccoci da yawa a cikin rikodin tarurrukan jigo da taro. Na ziyarci wasu daga cikinsu da kaina - wannan ƙwarewa ce mai matukar amfani ga waɗanda suke son haɓaka ta wannan hanyar. Anan akwai hanyoyin haɗi zuwa tashoshin YouTube tare da kyawawan laccoci da kayan aiki akan DevOps:
Yanzu duba kasuwancin ku kuma kuyi tunani game da wannan: Nawa ne kamfanin ku da ribar sa ya dogara da samfuran IT don ba da damar hulɗar abokin ciniki?
Idan kamfanin ku yana siyar da kifi a cikin ƙaramin shago kuma samfurin IT kawai shine 1C guda biyu: Tsarin kasuwanci (Accounting da UNF), to da wuya a yi magana game da DevOps.
Idan kuna aiki a babban kasuwancin kasuwanci da masana'antu (misali, kuna samar da bindigogin farauta), to yakamata kuyi tunani akai. Kuna iya ɗaukar himma kuma ku isar da ma'aikatan ku abubuwan da ake fatan aiwatar da DevOps. To, kuma a lokaci guda, jagoranci wannan tsari. Matsayi mai faɗakarwa yana ɗaya daga cikin mahimman ka'idodin falsafar DevOps.
Girma da girma na yawan kuɗin kuɗin shekara-shekara ba shine babban ma'auni don ƙayyade ko kamfanin ku yana buƙatar DevOps ba.
Bari mu yi tunanin babban kamfani na masana'antu wanda ba ya hulɗa kai tsaye tare da abokan ciniki. Misali, wasu masu kera motoci da kamfanonin kera motoci. Ban tabbata ba a yanzu, amma daga gogewar da na yi a baya, tsawon shekaru da yawa ana yin hulɗar abokan ciniki ta imel da waya.
Abokan cinikin su ƙayyadaddun jerin dilolin mota ne. Kuma kowane ɗayan an ba shi ƙwararre daga masana'anta. Duk kwararar daftarin aiki na ciki yana faruwa ta hanyar SAP ERP. Ma'aikatan cikin gida da gaske abokan cinikin tsarin bayanai ne. Amma ana sarrafa wannan IS ta hanyoyin gargajiya na sarrafa tsarin tari. Wanda ya keɓance yuwuwar amfani da ayyukan DevOps.
Saboda haka ƙarshe: don irin waɗannan kamfanoni, aiwatar da DevOps ba wani abu bane mai mahimmanci, idan muka tuna da manufofin tsarin tun farkon labarin. Amma ban yanke hukuncin cewa suna amfani da wasu kayan aikin DevOps a yau ba.
A gefe guda, akwai ƙananan kamfanoni da yawa waɗanda ke haɓaka software ta amfani da tsarin DevOps, falsafa, ayyuka da kayan aiki. Kuma sun yi imanin cewa farashin aiwatar da DevOps shine tsadar da ke ba su damar yin gasa sosai a cikin kasuwar software. Ana iya ganin misalan irin waɗannan kamfanoni .
Babban ma'auni don fahimtar ko ana buƙatar DevOps: menene ƙimar samfuran ku na IT ga kamfani da abokan ciniki.
Idan babban samfurin kamfanin da ke samar da riba shine software, kuna buƙatar DevOps. Kuma ba shi da mahimmanci idan kun sami kuɗi na gaske ta amfani da wasu samfurori. Wannan kuma ya haɗa da shagunan kan layi ko aikace-aikacen hannu tare da wasanni.
Duk wani wasanni yana wanzuwa saboda samun kuɗi: kai tsaye ko kai tsaye daga ƴan wasa. A Playgendary, muna haɓaka wasannin hannu kyauta tare da mutane sama da 200 da ke da hannu kai tsaye a cikin ƙirƙirar su. Ta yaya muke amfani da DevOps?
Ee, daidai kamar yadda aka bayyana a sama. Kullum ina sadarwa tare da masu haɓakawa da masu gwadawa, da kuma gudanar da horo na ciki ga ma'aikata akan hanyoyin DevOps da kayan aikin.
Yanzu muna amfani da Jenkins a matsayin kayan aikin bututun CI / CD don aiwatar da duk bututun taro tare da Haɗin kai da kuma turawa zuwa App Store da Play Market. Ƙari daga kayan aikin gargajiya:
- Asana - don gudanar da aikin. An daidaita haɗin kai tare da Jenkins.
- Google Meet - don taron bidiyo.
- Slack - don sadarwa da faɗakarwa iri-iri, gami da sanarwa daga Jenkins.
- Atlassian Confluence - don takardu da aikin rukuni.
Shirye-shiryenmu na kai tsaye sun haɗa da gabatar da ƙididdigar ƙididdiga ta amfani da SonarQube da gudanar da gwajin UI mai sarrafa kansa ta amfani da Selenium a matakin Haɗin kai na Ci gaba.
Maimakon a ƙarshe
Ina so in ƙare da tunani mai zuwa: don zama ƙwararren injiniyan DevOps, yana da mahimmanci don koyon yadda ake sadarwa kai tsaye tare da mutane.
Injiniyan DevOps ɗan wasan ƙungiyar ne. Kuma ba komai. Shirin sadarwa tare da abokan aiki ya kamata ya fito daga gare shi, kuma ba a ƙarƙashin rinjayar wasu yanayi ba. Dole ne ƙwararren DevOps ya gani kuma ya ba da shawarar mafi kyawun mafita ga ƙungiyar.
Kuma a, aiwatar da kowane bayani zai buƙaci tattaunawa mai yawa, kuma a ƙarshe zai iya canzawa gaba ɗaya. Haɓakawa da kansa, ba da shawara da aiwatar da ra'ayoyinsa, irin wannan mutumin yana ƙara darajar duka ga ƙungiyar da ma'aikaci. Wanda, a ƙarshe, yana nunawa a cikin adadin kuɗin da ake biya na wata-wata ko kuma ta hanyar ƙarin kari.
source: www.habr.com