Hello, Habr! Ina gabatar muku da fassarar labarin by Steve Mezak.
Dangane da ra'ayin ku, DevOps zai yi bikin cika shekaru tara ko goma a wannan shekara. A cikin 2016, Rahoton RightScale' State of the Cloud ya lura cewa kashi 70 na SMBs suna ɗaukar ayyukan DevOps. Duk wata alama da ta ƙunshi wannan maki ya ƙaru tun daga lokacin. Kamar yadda DevOps ke shirin shiga shekaru goma na biyu, zai yi kyau a yi yawo a baya kuma komawa zuwa asalin DevOps-har ma da asalin sunan kanta.
Kafin 2007: Cikakken jerin abubuwan da suka faru
Kafin 2007, jerin yanayi sun haifar da abin da aka sani a yau kamar DevOps.
Lanƙwasa ya riga ya tabbatar da kansa a matsayin mafi kyawun aiki. Hakanan aka sani da Tsarin samar da Toyota, Lean Manufacturing yayi ƙoƙari don inganta matakai akan bene na masana'anta. (Ta hanyar, da farko an yi wahayi zuwa gudanar da Toyota ta hanyar ainihin hanyoyin layin taro da Kamfanin Motoci na Ford suka gabatar). Ci gaba da ingantawa shine mantra don ƙwaƙƙwaran masana'antu. A aikace, ana ƙididdige hanyoyi masu zuwa koyaushe:
- Kula da matakan ƙirƙira na albarkatun ƙasa da ƙãre kayayyakin zuwa mafi ƙanƙanta. Ƙarƙashin ƙira yana nufin ƙaramin adadin kayan da aka kera don samar da kaya da ƙaramar adadin samfuran da aka gama da ake jira a yi oda ko aikawa.
- Rage layin oda. Da kyau, an karɓi umarni nan da nan matsawa zuwa jihar da aka kammala. Makullin ma'auni don ƙirar ƙima koyaushe zai kasance lokaci daga karɓar oda zuwa bayarwa.
- Ƙaddamar da ingantaccen tsarin samarwa. Sake sabunta tsarin aiki da ingantattun injina suna haɗuwa don samar da kaya da sauri. Kowane yanki na samarwa tare da dukan hanyar (yanke, walda, taro, gwaji, da dai sauransu) ana kimanta don rashin aiki.
A cikin duniyar IT, hanyoyin gargajiya na samfurin ruwan ruwa na haɓaka software sun riga sun ba da hanya don saurin jujjuyawar hanyoyin kamar Agile. Gudun ya kasance kukan da ake taruwa, ko da ingancin wani lokacin ya sha wahala wajen neman ci gaba cikin sauri da turawa. Hakazalika, Cloud computing, musamman Abubuwan Gina-kamar-yadda-Sabis (IaaS) da Sabis ɗin-da-da-sabis (PaaS) sun tabbatar da kansu a matsayin manyan mafita a cikin hanyoyin IT da abubuwan more rayuwa.
A ƙarshe, kwanan nan kayan aiki sun fara bayyana don Haɗuwa ta ci gaba (CI). An haifi ra'ayin kayan aikin CI kuma Gradi Booch ya gabatar da shi a cikin 1991 a cikin Hanyar Booch.
2007-2008: Baƙi na Belgium
Mashawarcin Belgian, aikin Agile da manajan gudanarwa Patrick Debois ya karɓi alƙawari daga ma'aikatar gwamnatin Belgium don taimakawa tare da ƙaura na cibiyar bayanai. Musamman ma, ya shiga cikin takaddun shaida da gwajin shirye-shiryen. Ayyukansa sun buƙaci shi don daidaitawa da gina dangantaka tsakanin ƙungiyoyin haɓaka software da uwar garke, bayanai, da ƙungiyoyin ayyukan cibiyar sadarwa. Bacin ransa game da rashin haɗin kai da bangon da ke raba hanyoyin ci gaba da aiki sun bar shi da ɗaci. Sha'awar Desbois ya inganta ba da daɗewa ba ya kai shi mataki.
A taron Agile na 2008 a Toronto, Andrew Schaefer ya ba da shawarar daidaita wani taro na yau da kullun da aka tsara don tattauna batun "Agile kayayyakin more rayuwa"Kuma mutum ɗaya ne kawai ya zo don tattauna batun: Patrick DeBois. Tattaunawarsu da musayar ra'ayi sun inganta manufar gudanar da tsarin Agile. A wannan shekarar, DeBois da Schaefer sun kirkiro ƙungiyar Administrator Agile Systems Administrator a matsakaicin nasara a Google.
2009: Batun haɗin kai tsakanin Dev da Ops
A taron O'Reilly Velocity taro, ma'aikatan Flicker guda biyu, Babban Mataimakin Shugaban Ayyuka na Fasaha John Allspaw da CTO Paul Hammond, sun ba da sanannen gabatarwar yanzu. "Ayyukan 10 a Rana: Haɗin Dev da Ops a Flicker".
Gabatarwar wasan kwaikwayo ce, tare da Allspaw da Hammond suna sake sake fasalin hulɗar hadaddun tsakanin wakilan Ci gaba da Ayyuka a lokacin aikin tura software, cikakke tare da nuna yatsa da zargi tare da layin "Ba lambara ba ce, duk kwamfutocin ku ne!" Gabatarwar su ta tabbatar da cewa kawai zaɓi mai ma'ana shine don haɓaka software da ayyukan turawa su zama marasa ƙarfi, bayyanannu da cikakken haɗin kai. Bayan lokaci, wannan gabatarwar ya zama almara kuma yanzu ana ganin tarihi a matsayin babban ci gaba lokacin da masana'antar IT ta fara kira ga hanyar da aka sani a yau kamar DevOps.
2010: DevOps a cikin Amurka ta Amurka
Tare da ci gaba mai zuwa, an gudanar da taron DevOpsDays a karon farko a Amurka a Mountain View, California, nan da nan bayan taron Velocity na shekara-shekara. Ci gaba da sauri zuwa 2018, kuma akwai fiye da 30 DevOpsDays taro da aka shirya, gami da da yawa a cikin Amurka.
2013: Project "Phoenix"
Ga yawancin mu, wani lokaci mai mahimmanci a cikin tarihin DevOps shine buga littafin "The Phoenix Project" na Gene Kim, Kevin Behr da George Safford. Wannan labari ya ba da labarin wani manajan IT wanda ya sami kansa a cikin mawuyacin hali: yana da alhakin ceto wani muhimmin aikin kasuwancin e-commerce wanda ya ɓace. Mai ba da shawara mai ban mamaki na manajan - memba na kwamitin gudanarwa wanda ke da sha'awar hanyoyin masana'antu masu rahusa - yana ba da shawarar sabbin hanyoyi zuwa babban hali don yin tunani game da IT da haɓaka aikace-aikacen, yana tsammanin manufar DevOps. Ta hanyar, "The Phoenix Project" ya ƙarfafa mu mu rubuta littafin "Outsource ko kuma ..." game da irin wannan labarin kasuwanci wanda VP na software ke amfani da DevOps a lokacin haɓaka sabon samfurin da aka fitar.
DevOps na gaba
Yana da daraja kwatanta DevOps a matsayin tafiya, ko watakila buri, maimakon makoma ta ƙarshe. DevOps, kamar masana'anta maras nauyi, yana ƙoƙari don ci gaba da haɓakawa, haɓaka aiki da inganci, har ma da ci gaba da turawa. Kayan aiki na atomatik don tallafawa DevOps suna ci gaba da haɓakawa.
An samu abubuwa da yawa tun lokacin da aka fara DevOps a cikin shekaru goma da suka gabata, kuma muna sa ran ganin ma fiye da haka a cikin 2018 da bayan haka.
source: www.habr.com