A halin yanzu, wannan shine kusan matsayi mafi tsada a kasuwa. Haushin da ke tattare da injiniyoyin "DevOps" ya wuce duk iyakoki da ake iya tunani, har ma da muni da manyan injiniyoyin DevOps.
Ina aiki a matsayin shugaban sashen haɗin kai da aiki da kai, yi tunanin ƙaddamar da turanci - DevOps Manager. Yana da wuya cewa rubutun Ingilishi ya nuna ayyukanmu na yau da kullum, amma fassarar Rasha a cikin wannan yanayin ya fi dacewa. Saboda yanayin aikina, yana da kyau ina buƙatar yin hira da membobin ƙungiyara nan gaba, kuma a cikin shekarar da ta gabata, mutane kusan 50 ne suka wuce ta wurina, kuma an katse adadin wannan lambar a prescreen tare da ma'aikata na.
Har yanzu muna neman abokan aiki, saboda a bayan alamar DevOps akwai babban nau'in injiniyoyi daban-daban da ke ɓoye.
Duk abin da aka rubuta a ƙasa ra'ayi na ne, ba lallai ne ku yarda da shi ba, amma na yarda cewa zai ƙara wasu launi zuwa halin ku ga batun. Duk da hadarin fadowa daga tagomashi, na buga ra'ayi na saboda na yi imani cewa yana da wurin zama.
Kamfanoni suna da fahimta daban-daban na wanene injiniyoyin DevOps kuma, saboda saurin daukar ma'aikata, suna rataye wannan lakabin akan kowa. Halin yana da ban mamaki, tun da kamfanoni suna shirye su biya kudaden da ba su dace ba ga waɗannan mutane, suna karɓar, a mafi yawan lokuta, mai sarrafa kayan aiki a gare su.
To su wanene injiniyoyin DevOps?
Bari mu fara da tarihin bayyanarsa - Ayyukan haɓaka sun bayyana a matsayin wani mataki na inganta hulɗa a cikin ƙananan ƙungiyoyi don ƙara saurin samar da samfur, sakamakon sakamakon da ake sa ran. Manufar ita ce don ƙarfafa ƙungiyar haɓakawa tare da sanin hanyoyin da hanyoyin da za a sarrafa yanayin samfurin. A wasu kalmomi, mai haɓakawa dole ne ya fahimci kuma ya san yadda samfurinsa ke aiki a wasu yanayi, dole ne ya fahimci yadda za a tura samfurinsa, wane halaye na yanayi za a iya daidaitawa don inganta aikin. Don haka, na ɗan lokaci, masu haɓakawa tare da tsarin DevOps sun bayyana. Masu haɓaka DevOps sun rubuta rubutun gini da tattarawa don sauƙaƙe ayyukansu da aikin yanayin samarwa. Koyaya, rikitaccen tsarin gine-ginen mafita da tasirin haɗin gwiwar abubuwan abubuwan more rayuwa na tsawon lokaci sun fara lalata ayyukan mahalli; tare da kowane juzu'i, ana buƙatar ƙarin zurfin fahimtar wasu abubuwan haɗin gwiwa, rage yawan haɓakar mai haɓakawa saboda ƙarin ƙari. farashin fahimtar abubuwan da aka gyara da tsarin daidaitawa don takamaiman aiki. Farashin mai haɓaka ya karu, farashin samfurin tare da shi, buƙatun sabbin masu haɓakawa a cikin ƙungiyar sun yi tsalle sosai, saboda suna buƙatar ɗaukar nauyin ci gaban “tauraro” kuma, a zahiri, “taurari” sun zama ƙasa da ƙasa. kuma ƙasa da samuwa. Hakanan yana da kyau a lura cewa, a cikin gogewa na, ƴan haɓakawa ne ke sha'awar ƙayyadaddun sarrafa fakiti ta kernel ɗin tsarin aiki, ƙa'idodin fakiti, da bangarorin tsaro. Mataki na ma'ana shine don jawo hankalin mai gudanarwa wanda ya saba da wannan kuma ya ba shi irin wannan nauyin, wanda, godiya ga kwarewarsa, ya sa ya yiwu a cimma daidaitattun alamomi a ƙananan farashi idan aka kwatanta da farashin ci gaban "tauraro". An sanya irin waɗannan masu gudanarwa a cikin ƙungiya kuma babban aikinsa shi ne gudanar da gwaje-gwaje da yanayin samarwa, bisa ga ka'idodin ƙayyadaddun ƙungiya, tare da albarkatun da aka ba wa wannan ƙungiya ta musamman. Wannan shine yadda, a zahiri, DevOps ya bayyana a cikin zukatan yawancin.
A wani bangare ko gaba daya, bayan lokaci, wadannan masu gudanar da tsarin sun fara fahimtar bukatun wannan kungiya ta musamman a fagen ci gaba, yadda za a sauƙaƙe rayuwa ga masu haɓakawa da masu gwadawa, yadda za a fitar da sabuntawa kuma ba dole ba ne a kwana a ranar Jumma'a ofishin, gyara kurakurai turawa. Lokaci ya wuce, kuma yanzu "taurari" sune masu gudanar da tsarin da suka fahimci abin da masu haɓaka ke so. Don rage tasirin tasirin, kayan aikin gudanarwa sun fara tasowa; kowa ya tuna da tsoffin hanyoyin amintattun hanyoyin ware matakin OS, wanda ya ba da damar rage abubuwan da ake buƙata don tsaro, sarrafa sashin cibiyar sadarwa, da tsarin mai watsa shiri azaman gaba ɗaya kuma, a sakamakon haka, rage abubuwan da ake buƙata don sababbin "taurari".
Wani abu "mai ban mamaki" ya bayyana - docker. Me yasa ban mamaki? Ee, kawai saboda ƙirƙirar keɓancewa a cikin chroot ko kurkuku, kazalika da OpenVZ, yana buƙatar ilimin da ba ƙaramin abu ba game da OS, akasin haka, mai amfani yana ba ku damar ƙirƙirar keɓantaccen yanayin aikace-aikacen akan wani mai watsa shiri tare da duk abin da ake buƙata a ciki da hannu. a kan ci gaban ci gaba kuma, kuma mai sarrafa tsarin zai iya sarrafawa tare da mai watsa shiri ɗaya kawai, yana tabbatar da tsaro da samuwa mai yawa - sauƙi mai ma'ana. Amma ci gaban bai tsaya cak ba kuma tsarin yana sake zama mai rikitarwa, ana samun ƙarin abubuwan da suka dace, mai masaukin baki ɗaya ya daina biyan bukatun tsarin kuma ya zama dole a gina cluster, muna sake komawa ga masu gudanar da tsarin waɗanda suke. iya gina waɗannan tsarin.
Zagayowar bayan sake zagayowar, tsarin daban-daban suna bayyana waɗanda ke sauƙaƙe haɓakawa da/ko gudanarwa, tsarin ƙungiyar kade-kade ya bayyana, waɗanda, har sai kun buƙaci karkata daga daidaitaccen tsari, suna da sauƙin amfani. Microservice gine kuma ya bayyana tare da manufar sauƙaƙe duk abin da aka kwatanta a sama - ƙananan dangantaka, sauƙin sarrafawa. A cikin kwarewata, ban sami tsarin gine-gine na microservice gaba daya ba, zan ce 50 zuwa 50 - 50 bisa dari na microservices, akwatunan baƙar fata, sun shigo, sun fito ana sarrafa su, sauran 50 din monolith ne mai tsage, ayyuka ba su iya yin aiki dabam da sauran. aka gyara. Duk wannan ya sake sanya takunkumi kan matakin ilimin masu haɓakawa da masu gudanarwa.
Irin wannan “swings” a matakin ilimin ƙwararru na takamaiman albarkatu yana ci gaba har yau. Amma mun ɗan ɗan yi zurfi, akwai maki da yawa da ya kamata a bayyana.
Gina Injiniya / Injiniya Saki
Kwararrun injiniyoyi na musamman waɗanda suka fito azaman hanyar daidaita tsarin gina software da sakewa. A cikin tsarin gabatar da Agile mai yaduwa, da alama sun daina nema, amma wannan yayi nisa da lamarin. Wannan ƙwarewa ta bayyana a matsayin hanyar daidaita haɗawa da isar da software akan sikelin masana'antu, watau. ta amfani da daidaitattun dabaru don duk samfuran kamfani. Tare da zuwan DevOps, masu haɓakawa sun rasa ayyukansu, tunda masu haɓakawa ne suka fara shirya samfuran don isarwa, kuma sun ba da sauye-sauyen ababen more rayuwa da tsarin isar da sauri da sauri ba tare da la'akari da inganci ba, a kan lokaci sun juya zuwa. mai dakatar da canje-canje, tun da bin ka'idodin inganci ba makawa yana rage kai kawo. Don haka, a hankali, ɓangaren aikin injiniyoyin Gina/Saki sun yi ƙaura zuwa kafaɗun masu gudanar da tsarin.
Ops sun bambanta sosai
Muna ci gaba da sake kasancewar manyan ayyuka masu yawa da kuma rashin ƙwararrun ma'aikata yana tura mu zuwa ƙwarewa mai tsauri, kamar namomin kaza bayan ruwan sama, Ayyuka daban-daban suna bayyana:
- TechOps - masu gudanar da tsarin enikey aka HelpDesk Engineer
- LiveOps - masu gudanar da tsarin suna da alhakin samar da yanayin samarwa
- CloudOps - masu gudanar da tsarin ƙware a cikin girgije jama'a Azure, AWS, GCP, da sauransu.
- PlatOps/InfraOps/SysOps - masu gudanar da tsarin ababen more rayuwa.
- NetOps - masu gudanar da hanyar sadarwa
- SecOps - masu gudanar da tsarin ƙware kan tsaro na bayanai - yarda da PCI, yarda da CIS, faci, da sauransu.
DevOps shine (a cikin ka'idar) mutumin da ya fahimci farko-hannun duk hanyoyin ci gaba na ci gaba - haɓakawa, gwaji, fahimtar ƙirar samfuran, yana iya tantance haɗarin tsaro, ya saba da hanyoyin da kayan aikin sarrafa kansa, aƙalla a babban matsayi. matakin, ban da wannan, kuma yana fahimtar gaba da aiwatarwa. Tallafin sakin samfur. Mutumin da ke da ikon yin aiki a matsayin mai ba da shawara ga Ayyuka da Ci gaba, wanda ke ba da damar kyakkyawar haɗin gwiwa tsakanin waɗannan ginshiƙai guda biyu. Ya fahimci hanyoyin tsara aikin ta ƙungiyoyi da sarrafa tsammanin abokin ciniki.
Don yin irin wannan aikin da alhakin, wannan mutumin dole ne ya sami hanyar sarrafa ba kawai ci gaba da hanyoyin gwaji ba, har ma da sarrafa kayan aikin samfurin, da kuma tsara kayan aiki. DevOps a cikin wannan fahimtar ba za a iya kasancewa ko dai a cikin IT, ko a cikin R&D, ko ma a cikin PMO; dole ne ya sami tasiri a duk waɗannan fannoni - darektan fasaha na kamfanin, Babban Jami'in Fasaha.
Shin wannan gaskiya ne a cikin kamfanin ku? - Ina shakka. A mafi yawan lokuta, wannan shine ko dai IT ko R&D.
Rashin kuɗi da ikon yin tasiri aƙalla ɗaya daga cikin waɗannan fagage uku na ayyuka zai canza nauyin matsalolin zuwa inda waɗannan canje-canjen suka fi sauƙi don amfani, kamar aikace-aikacen ƙuntatawa na fasaha game da sakewa dangane da lambar "datti" bisa ga a tsaye. tsarin nazari. Wato, lokacin da PMO ya saita ƙayyadaddun ƙayyadaddun lokaci don sakin ayyuka, R&D ba zai iya samar da sakamako mai inganci a cikin waɗannan ƙayyadaddun ƙayyadaddun lokaci ba kuma ya samar da shi yadda ya kamata, yana barin sake fasalin daga baya, DevOps da ke da alaƙa da IT suna toshe sakin ta amfani da hanyoyin fasaha. . Rashin ikon canza halin da ake ciki, a cikin yanayin ma'aikata masu alhakin, yana haifar da bayyanar hyper-alhaki ga abin da ba za su iya tasiri ba, musamman ma idan waɗannan ma'aikata sun fahimci kuma sun ga kuskure, da kuma yadda za a gyara su - "Ni'ima ita ce jahilci". kuma sakamakon konewa da asarar wadannan ma'aikata.
Kasuwancin albarkatun DevOps
Bari mu kalli guraben guraben aiki da yawa don mukaman DevOps daga kamfanoni daban-daban.
Muna shirye mu gana da ku idan kun:
- Kuna da Zabbix kuma ku san abin da Prometheus yake;
- Iptables;
- BASH PhD dalibi;
- Farfesa Mai yiwuwa;
- Linux Guru;
- Sanin yadda ake amfani da gyara kurakurai kuma nemo matsalolin aikace-aikace tare da masu haɓakawa (php/java/python);
- Hanyar hanya ba ta sa ku zama mai hazo ba;
- Kula da hankali sosai ga tsarin tsaro;
- Ajiyayyen "komai da komai", da kuma nasarar dawo da wannan "komai da komai";
- Kun san yadda ake saita tsarin ta hanyar da za ku sami matsakaicin mafi ƙarancin;
- Saita kwafi kafin ka kwanta akan Postgres da MySQL;
- Saita da daidaita CI/CD ya zama dole a gare ku kamar karin kumallo / abincin rana / abincin dare.
- Yi kwarewa tare da AWS;
- Shirye don haɓakawa tare da kamfanin;
Saboda haka:
- daga 1 zuwa 6 - tsarin gudanarwa
- 7 – ‘yar karamar gudanarwar hanyar sadarwa, wacce kuma ta dace da mai kula da tsarin, matakin tsakiya
- 8- tsaro kadan, wanda ya wajaba ga mai kula da tsarin matakin tsakiya
- 9-11 - Mai Gudanar da Tsarin Tsari
- 12 - Dangane da ayyukan da aka ba su, ko dai Mai Gudanar da Tsarin Mulki ko Gina Injiniya
- 13 - Ƙwararren Ƙwararren Ƙwararren Ƙwararren Ƙwararren Ƙwararren Ƙwararren Ƙwararren Ƙwararren Ƙwararren Ƙwararren Ƙwararren Ƙwararren Ƙwararren Ƙwararren Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararrun Ƙwararru na Ƙarfafawa na Ƙaƙwalwa na Ƙaƙwalwar Ƙaƙwalwa .
Taƙaice wannan guraben, za mu iya cewa Babban Mai Gudanar da Tsari / Tsara ya isa ga samari.
Af, bai kamata ku rarraba masu gudanarwa da ƙarfi akan Linux/Windows ba. Tabbas na fahimci hidimomi da tsarin wadannan duniyoyi guda biyu sun banbanta, amma tushen kowa daya ne kuma duk wani admin mai mutunta kansa ya saba da daya da daya, kuma ko da bai saba ba, zai yi. ba zai zama da wahala ga wani ƙwararren admin ya saba da shi ba.
Bari mu yi la'akari da wani guraben aiki:
- Kwarewa a cikin gina tsarin kayan aiki mai girma;
- Kyakkyawan ilimin Linux OS, software na tsarin gabaɗaya da tari na yanar gizo (Nginx, PHP/Python, HAProxy, MySQL/PostgreSQL, Memcached, Redis, RabbitMQ, ELK);
- Kwarewa tare da tsarin haɓakawa (KVM, VMWare, LXC/Docker);
- Ƙwarewa a cikin harsunan rubutun rubutu;
- Fahimtar ƙa'idodin aiki na cibiyoyin sadarwar ka'idar;
- Fahimtar ka'idodin gina tsarin da ba daidai ba;
- 'Yanci da himma;
Mu duba:
- 1 – Babban Mai Gudanar da Tsari
- 2 - Ya danganta da ma'anar da aka sanya a cikin wannan tari - Babban Mai Gudanar da Tsari / Tsari
- 3 - Kwarewar aiki, gami da, na iya nufin - "Tarin bai ɗaga ba, amma ya ƙirƙira da sarrafa injunan kama-da-wane, akwai mai masaukin Docker guda ɗaya, ba a samun damar shiga kwantena" - Mai Gudanar da Tsari na Tsakiya
- 4 - Junior System Administrator - eh, admin wanda bai san yadda ake rubuta rubutun atomatik ba, ba tare da la'akari da yare ba, ba admin - enikey.
- 5-Mai Gudanar da Tsare-tsare
- 6 – Babban Mai Gudanar da Tsari
Don taƙaitawa - Babban Mai Gudanar da Tsari na Tsakiya/Senior
Wani kuma:
- Devops kwarewa;
- Ƙwarewa cikin amfani da ɗaya ko fiye samfura don ƙirƙirar hanyoyin CI/CD. Gitlab CI zai zama fa'ida;
- Yin aiki tare da kwantena da haɓakawa; Idan kun yi amfani da docker, mai kyau, amma idan kun yi amfani da k8s, mai girma!
- Ƙwarewar aiki a cikin ƙungiyar agile;
- Ilimin kowane harshe na shirye-shirye;
Mu gani:
- 1 - Hmm... Me mutanen suke nufi? =) Wataƙila su kansu ba su san abin da ke ɓoye a bayansa ba
- 2 - Gina Injiniya
- 3-Mai Gudanar da Tsare-tsare
- 4 - Ƙwarewa mai laushi, ba za mu yi la'akari da shi ba a yanzu, ko da yake Agile wani abu ne wanda aka fassara ta hanyar da ta dace.
- 5-Mafi yawan magana - yana iya zama yaren rubutu ko kuma wanda aka haɗa. Ina mamakin ko rubutu a Pascal da Basic a makaranta zai dace da su? =)
Ina so in bar bayanin kula game da batu na 3 don ƙarfafa fahimtar dalilin da yasa mai kula da tsarin ke rufe wannan batu. Kubernetes ƙungiyar makaɗa ce kawai, kayan aiki ne wanda ke kunshe umarnin kai tsaye zuwa direbobin hanyar sadarwa da rundunonin haɓakawa / keɓewa a cikin wasu umarni guda biyu kuma yana ba ku damar yin sadarwa tare da su, shi ke nan. Misali, bari mu dauki 'ginin tsarin' Make, wanda, ta hanya, ban yi la'akari da tsarin ba. Ee, Na san game da salon shoving Make a ko'ina, inda ya zama dole kuma ba a buƙata - nade Maven a Make, alal misali, da gaske?
Mahimmanci, Make kawai abin rufewa ne akan harsashi, yana sauƙaƙe tattarawa, haɗawa, da umarnin mahalli, kamar k8s.
Da zarar, na yi hira da wani mutumin da ya yi amfani da k8s a cikin aikinsa a saman OpenStack, kuma ya yi magana game da yadda ya tura ayyuka a kai, duk da haka, lokacin da na tambayi OpenStack, ya zama cewa an gudanar da shi, da kuma tashe ta hanyar tsarin. masu gudanarwa. Shin kuna tunanin cewa mutumin da ya shigar da OpenStack, ko da wane dandamali yake amfani da shi a bayansa, ba zai iya amfani da k8s ba? =)
Wannan mai nema ba ainihin DevOps bane, amma Mai Gudanar da Tsari ne kuma, don zama madaidaici, Mai Gudanar da Kubernetes.
Bari mu sake taƙaice - Babban Manajan Tsari na Tsakiya/Senior zai ishe su.
Nawa za a auna a cikin grams
Matsakaicin albashin da aka gabatar don guraben da aka nuna shine 90k-200k
Yanzu ina so in zana daidaici tsakanin ladan kuɗi na Masu Gudanar da Tsari da Injiniyoyi na DevOps.
A ka'ida, don sauƙaƙe abubuwa, zaka iya watsar da maki bisa ga kwarewar aiki, ko da yake wannan ba zai zama daidai ba, amma don dalilai na labarin zai isa.
Kwarewa:
- har zuwa shekaru 3 - Junior
- har zuwa shekaru 6 - Tsakiya
- fiye da 6 - Babban
Gidan binciken ma'aikaci yana ba da:
Masu Gudanar da Tsari:
- Junior - shekaru 2 - 50k rub.
- Tsakiyar - 5 shekaru - 70k rub.
- Babban - shekaru 11 - 100k rub.
Injiniyoyin DevOps:
- Junior - shekaru 2 - 100k rub.
- Tsakiyar - shekaru 3 - 160k rub.
- Babban - shekaru 6 - 220k rub.
Dangane da ƙwarewar "DevOps", an yi amfani da ƙwarewa wanda aƙalla ko ta yaya ya shafi SDLC.
Daga abin da ke sama ya biyo bayan cewa a zahiri kamfanoni ba sa buƙatar DevOps, haka kuma za su iya adana aƙalla kashi 50 na kuɗin da aka tsara na farko ta hanyar ɗaukar Ma’aikaci; haka ma, za su iya ƙara fayyace nauyin mutumin da suke nema. da kuma cika bukata da sauri. Har ila yau, kada mu manta cewa rarraba nauyin nauyi yana ba mu damar rage bukatun ma'aikata, da kuma haifar da yanayi mafi kyau a cikin tawagar, saboda rashin daidaituwa. Yawancin guraben guraben aiki cike suke da abubuwan amfani da alamun DevOps, amma ba su dogara ne akan ainihin buƙatun Injiniya na DevOps ba, buƙatun kawai ga mai gudanar da kayan aiki.
Tsarin horar da injiniyoyin DevOps kuma yana iyakance ne kawai ga takamaiman takamaiman ayyuka, abubuwan amfani, kuma baya ba da cikakkiyar fahimtar hanyoyin da dogaro da su. Tabbas yana da kyau lokacin da mutum zai iya tura AWS EKS ta amfani da Terraform, tare da haɗin gwiwa tare da Fluentd sidecar a cikin wannan gungu da tarin AWS ELK don tsarin shiga cikin mintuna 10, ta amfani da umarni ɗaya kawai a cikin na'ura wasan bidiyo, amma idan bai gane ba. ka'idar sarrafa kanta rajistan ayyukan da abin da ake bukata domin, idan ba ka san yadda za a tattara awo a kan su da kuma bin diddigin lalacewar da sabis, sa'an nan zai zama har yanzu wannan enikey wanda ya san yadda za a yi amfani da wasu utilities.
Bukatar, duk da haka, yana haifar da wadata, kuma muna ganin kasuwa mai zafi sosai don matsayi na DevOps, inda buƙatun ba su dace da ainihin rawar ba, amma kawai ƙyale masu gudanar da tsarin su sami ƙarin.
To su waye? DevOps ko masu gudanar da tsarin hadama? =)
Yadda za a ci gaba da rayuwa?
Ya kamata masu ɗaukan ma'aikata su tsara abubuwan buƙatu daidai gwargwado kuma su nemo ainihin waɗanda ake buƙata, kuma kada su jefa takalmi. Ba ku san abin da DevOps ke yi ba - ba kwa buƙatar su a wannan yanayin.
Ma'aikata - Koyi. Koyaushe inganta ilimin ku, duba cikakken hoton tafiyar matakai kuma ku bi hanyar zuwa burin ku. Kuna iya zama duk wanda kuke so, kawai ku gwada.
source: www.habr.com