LFCA: Koyi Tushen Ka'idodin DevOps - Sashe na 21
DevOps ya kasance batu mai tasowa na ɗan lokaci kaɗan yanzu kuma ya sami nasarar jawo hankalin ƙwararrun fasaha da kamfanoni iri ɗaya. A matsayin mafari, yana iya zama ƙalubale don kunsa kan ku game da manufar DevOps, kuma a cikin wannan batu, za mu fitar da ainihin mahimman ra'ayoyin wannan buzzword na intanet.
Don farawa, DevOps babban hoto ne na kalmomi biyu: Ci gaba da Ayyuka. Saitin ayyuka da kayan aikin da ke haɓaka haɗin gwiwa tsakanin ƙungiyoyin ci gaba (Devs) da ayyuka (Ops). Manufar DevOps ita ce daidaita tsarin rayuwar ci gaban software, rage yawan gazawar, haɓaka mitar turawa, da cimma babbar software.
Don samun kyakkyawar fahimta game da DevOps a cikin yanayin IT na zamani na yau, bari mu kalli yadda ƙirar turawa ta kasance kafin zuwan DevOps.
Ayyukan IT na gargajiya
Kafin DevOps, ƙungiyoyin ci gaba da injiniyoyin QA sun yi amfani da samfurin ruwan ruwa na gargajiya. An rufe filin aiki sosai kuma gwaji da tura aikace-aikacen sun faru a keɓe. Wannan ya haifar da zoben aiki, gibi, jinkirin amsawa, da sauran gazawar da ke buƙatar ƙarin lokaci don kammala aikin. Iyakance da jinkirin amsa yana nufin ba a tantance ingancin software ɗin sosai ba har sai lokacin haɓakawa na ƙarshe.
Bugu da ƙari, kurakurai na ɗan adam sun sami damar tura lambar da hannu don haka ya buƙaci ƙarin lokaci a aikace-aikacen gyara kuskure. Har ila yau, ƙungiyoyi daban-daban suna da lokuta daban-daban don kammala ayyukansu kuma ba sabon abu ba ne don lokutan lokaci su fadi daga aiki tare da ke haifar da ƙarin jinkiri wajen gane samfurin ƙarshe.
An ɗauki ra'ayin DevOps wani lokaci tsakanin 2007 da 2010 ta masu haɓakawa biyu: Andrew Shafer da Patrick Debois. Tun lokacin da aka kafa ta, Ya haɓaka haɗin gwiwa mai sauƙi tsakanin aiki da ƙungiyoyin ci gaba a kowane mataki na ci gaban rayuwar software. Wannan ya ba da sanarwar sabbin dabaru irin su Ci gaba da Haɗuwa (CI) & Ci gaba da Bayarwa (CD) da sauransu da yawa waɗanda ke ba da gudummawa ga isar da software cikin sauri.
Samfurin DevOps da Ayyuka
DevOps ba kawai game da haɗin gwiwa ba ne da samun kyakkyawan tunani don cimma burin. Ya ƙunshi mafi kyawun ayyuka waɗanda ke nufin taimakawa isar da ingantattun software da shirye-shiryen kasuwa cikin ɗan gajeren lokaci mai yuwuwa. Bari mu kalli wasu daga cikin mafi kyawun ayyuka waɗanda zasu taimaka muku haɓaka inganci da saurin isar da lamba.
Ci gaba da Haɗuwa al'ada ce ta haɓaka software inda masu haɓakawa ke haɗa sauye-sauyen lambar zuwa wurin ajiya ɗaya na tsakiya. Bayan haka, ana aiwatar da gwaje-gwaje na atomatik da ginawa akan lambar. Manufar Ci gaba da Haɗuwa ita ce a hanzarta yin kuskuren aikace-aikacen, rage lokacin da aka ɗauka don sakin sabbin abubuwan sabunta software, da haɓaka ingancin software.
Isar da Ci gaba (CD) wani aiki ne inda aka gina canje-canje a lamba ta atomatik, kuma ana tura shi don gwaji mai ƙarfi. Daga baya, ana aiwatar da gwaje-gwaje ta atomatik akan lambar da aka tura don baiwa masu haɓakawa damar ganowa da gyara kurakuran. Yawancin lokaci, lambar tana ci gaba da fuskantar yanayin gwaji da yawa inda ta hanyar daidaitaccen tsari mai sarrafa kansa, lambar ta sami mafi girman alamar inganci.
Shahararrun kayan aikin CI/CD sun haɗa da Jenkins, Travis CI, Circle CI, Azure DevOps, da gina lambar AWS.
Makasudin ci gaba da gwaji shine gano kwari da yuwuwar hatsarori a farkon matakan ci gaban software don rage kurakuran da zasu bayyana a ƙarshen samfur. Lokacin da lambar ta gaza ƙaƙƙarfan gwaje-gwajen, yawanci ana aika ta zuwa ga mai haɓakawa don bita kafin a tura shi zuwa sashin Tabbacin Inganci don kimantawa da gwajin aiki. Kayan aikin gwaji na ci gaba da amfani da su sun haɗa da Travis da Selenium.
Kamar yadda zaku yi tsammani, aikace-aikace da kayan aikin da ke ƙasa suna buƙatar ci gaba da sa ido don bincika duk wani kurakurai ko lahani akan aikin su, da tabbatar da bin ka'idojin masana'antu daban-daban. Ana kula da ma'auni iri-iri da suka haɗa da:
- Memory da Amfanin CPU
- Amfani da sarari faifai
- Amfani da bandwidth
- Mu'amalar abokin ciniki
Ta hanyar saka idanu da nazarin bayanai da rajistan ayyukan da aikace-aikace ke samarwa, masu haɓakawa za su iya samun fahimtar yadda fasali ko daidaitawa ke tasiri masu amfani. Bugu da ƙari, daidaita faɗakarwa zai taimaka wajen gano kurakurai ko canje-canjen da ba a so kowane mataki na hanya. Ƙarshe, ci gaba da saka idanu yana tabbatar da yawan samuwa na aikace-aikace kuma yana ƙarfafa amincewa cewa abubuwa suna aiki kamar yadda aka sa ran.
Shahararrun kayan aikin sa ido sun haɗa da Prometheus, Netdata don ambata kaɗan.
An taƙaita shi azaman IaC, An bayyana Infrastructure as Code azaman turawa da sarrafa albarkatu kamar sabar sabar, & masu daidaita ma'aunin nauyi ta amfani da fayilolin daidaitawa na na'ura sabanin kayan aikin daidaitawa. Wannan yana da mahimmanci musamman a cikin mahallin Cloud kamar AWS inda zaku iya ƙididdige ƙididdiga cikin sauri ta hanyar ayyana cikakkun bayanai na misalin a cikin fayil ɗin sanyi da kayan aiki masu amfani kamar Terraform don tura albarkatun.
Misali, Amazon AWS yana ba da APIs waɗanda ke ba masu amfani damar yin hulɗa tare da tsarin Cloud daga layin umarni. Wannan yana sauƙaƙe jigilar kayan aiki cikin sauri ta hanyar kawar da tafiyar matakai na hannu da rashin ƙarfi. A taƙaice, IaC yana samun ƙarin aiki a cikin ɗan gajeren lokaci.
Gine-gine na Microservices shine inda aikace-aikacen guda ɗaya shine haɗin kai ko haɗakar wasu ƙananan ayyuka masu sassauƙa. Kowane sabis yana gudanar da kansa kuma yana sadarwa tare da sauran aikace-aikacen ta amfani da APIs na tushen HTTP. Ana iya tura ƙananan sabis ɗin azaman ƙungiyar sabis ko sabis ɗaya
Gine-ginen Microservices ya sha bamban da gine-ginen monolithic na gargajiya. A cikin gine-ginen gargajiya, aikace-aikace masu layi ɗaya ne kuma duk abubuwan haɗin gwiwa, gami da lambar da UI, an haɗa su cikin shiri ɗaya.
Microservices suna sauƙaƙe ƙaddamarwa mai zaman kanta da sarrafa albarkatu. Har ila yau, suna tabbatar da samuwa mai yawa ta hanyar hana guda ɗaya na gazawar. lokacin da aikace-aikacen guda ɗaya ya yi karo, sauran za su ci gaba da gudana.
Fa'idodin Samfurin DevOps
Bayan mun kalli mafi kyawun ayyuka na DevOps, bari yanzu mu mai da hankali kan fa'idodin ɗaukar ƙirar DevOps.
Haɗin kai tsakanin ƙungiyoyin haɓakawa & ƙungiyoyin aiki suna fassara alhakin haɗin gwiwa, wanda a ƙarshe yana haɓaka haɓaka aiki da haɓaka haɗin gwiwa.
Haɗin kai kuma yana bawa ƙungiyoyi damar cire lambar cikin sauƙi a kowane mataki kafin isa matakin ƙarshe. Wannan yana samar da ingantaccen software da shirye-shiryen kasuwa.
Aiwatar da aikace-aikacen ya fi sauƙi kuma ya fi sauri godiya ga kayan aikin atomatik da DevOps ke bayarwa (kamar Mai yiwuwa, Chef, da Puppet) & ci gaba da haɗin kai (CI).
Tun da ilimin samfurin ya bazu a sassa daban-daban, akwai maƙasudi da hangen nesa game da samfurin, fassara zuwa mafi kyawun yanke shawara a kowane mataki na ci gaba.
Tushen imani cewa ƙungiyoyin ci gaba da aiki dole ne su yi aiki dabam har abada ya daɗe da lahani. Falsafar da ba a kwance ba na iya kasancewa tana raye a wasu masana'antu, amma wannan ya haifar da rashin fa'ida a hanya.
DevOps yana neman haɓaka ƙungiyoyin haɓakawa da ƙungiyoyin aiki da haɓaka canjin al'adu daga tsohuwar hanyar yin aiki a cikin silos don yin aiki tare don rage kurakurai a cikin lamba, haɓaka ingancin software, hanzarta lokutan bayarwa da haɓaka yawan aiki gabaɗaya. Ƙarshe mai amfani na ƙarshe ya ƙare da samfur mai inganci a cikin lokaci.