NET Core akan Linux, DevOps akan doki

Mun haɓaka DevOps gwargwadon iyawarmu. Mu 8 ne, kuma Vasya ya kasance mafi kyawu a cikin Windows. Ba zato ba tsammani Vasya ya tafi, kuma ina da aikin ƙaddamar da sabon aikin wanda ci gaban Windows ya kawo. Lokacin da na jefar da duka tarin ci gaban Windows akan tebur, na gane cewa lamarin yana da zafi...

Haka labarin ya fara Alexandra Sinchinova a kan DevOpsConf. Lokacin da babban masanin Windows ya bar kamfanin, Alexander ya yi mamakin abin da zai yi yanzu. Canja zuwa Linux, ba shakka! Alexander zai gaya muku yadda ya gudanar ya ƙirƙiri wani misali da canja wurin wani ɓangare na ci gaban Windows zuwa Linux ta amfani da misalin aikin da aka kammala don masu amfani da ƙarshen 100.

NET Core akan Linux, DevOps akan doki

Yadda ake isar da aiki cikin sauƙi da wahala zuwa RPM ta amfani da TFS, Puppet, Linux .NET core? Yadda ake tallafawa sigar bayanan bayanan aikin idan ƙungiyar haɓaka ta ji kalmomin Postgres da Flyway a karon farko, kuma ranar ƙarshe shine jibi? Yadda ake haɗawa tare da Docker? Yadda za a kwadaitar da masu haɓaka NET su watsar da Windows da smoothies don goyon bayan Puppet da Linux? Yadda za a warware rikice-rikice na akida idan babu ƙarfi, ko sha'awar, ko albarkatun don kula da Windows a cikin samarwa? Game da wannan, da kuma game da Yanar Gizo na Yanar Gizo, gwaji, CI, game da ayyuka na yin amfani da TFS a cikin ayyukan da ake ciki, kuma, ba shakka, game da fashewar crutches da mafita aiki, a cikin rubutun rahoton Alexander.


Don haka, Vasya ya bar, aikin yana kan ni, masu haɓakawa suna jira ba tare da jinkiri ba tare da farar fata. Sa’ad da na fahimci cewa ba za a iya mayar da Vasya ba, sai na fara kasuwanci. Da farko, na tantance yawan Win VMs a cikin jiragen ruwan mu. Makin bai goyi bayan Windows ba.

NET Core akan Linux, DevOps akan doki

Tun da muna haɓaka DevOps sosai, na gane cewa akwai buƙatar canza wani abu ta hanyar isar da sabon aikace-aikacen. Akwai mafita ɗaya kawai - idan zai yiwu, canja wurin komai zuwa Linux. Google ya taimake ni - a wancan lokacin .Net an riga an tura shi zuwa Linux, kuma na gane cewa wannan shine mafita!

Me yasa NET core tare da Linux?

Akwai dalilai da yawa na wannan. Tsakanin "biyan kuɗi" da "ba biya", yawancin za su zaɓi na biyu - kamar ni. Lasisi na MSDB ya kai kusan $1; kiyaye rundunonin injunan kwatancen Windows yana biyan daruruwan daloli. Ga babban kamfani wannan babban kuɗi ne. Shi ya sa tanadi - dalili na farko. Ba wai kawai mafi mahimmanci ba, amma daya daga cikin mafi mahimmanci.

Injin kwamfyuta na Windows suna ɗaukar albarkatu fiye da ƴan uwansu Linux - suna da nauyi. Idan aka ba da sikelin babban kamfani, mun zaɓi Linux.

An haɗa tsarin kawai cikin CI data kasance. Muna ɗaukar kanmu DevOps masu ci gaba, muna amfani da Bamboo, Jenkins da GitLab CI, don haka yawancin ayyukanmu suna gudana akan Linux.

Dalili na ƙarshe shine dace rakiya. Muna buƙatar rage shingen shigarwa don "masu rakiya" - mutanen da suka fahimci ɓangaren fasaha, tabbatar da sabis ɗin da ba a yanke ba, da kuma kula da ayyuka daga layi na biyu. Sun riga sun saba da tarin Linux, don haka yana da sauƙi a gare su su fahimta, tallafawa da kuma kula da sabon samfur fiye da kashe ƙarin albarkatu don fahimtar aikin software iri ɗaya na dandalin Windows.

bukatun

Na farko kuma mafi - saukaka sabon bayani ga masu haɓakawa. Ba duka ba ne a shirye don canji, musamman bayan kalmar Linux. Masu haɓakawa suna son Kayayyakin Kayayyakin Kayayyakin da suka fi so, TFS tare da autotests don taro da santsi. Yadda isar da kayayyaki ke faruwa ba shi da mahimmanci a gare su. Sabili da haka, mun yanke shawarar kada mu canza tsarin da aka saba kuma mu bar duk abin da bai canza ba don ci gaban Windows.

Sabon aikin da ake bukata shiga cikin CI data kasance. Rails sun riga sun kasance a can kuma duk aikin dole ne a yi la'akari da ma'auni na tsarin gudanarwa, yarda da tsarin bayarwa da tsarin kulawa.

Sauƙin tallafi da aiki, a matsayin sharadi don mafi ƙarancin shigarwa ga duk sabbin mahalarta daga sassa daban-daban da sashen tallafi.

Ranar ƙarshe - jiya.

Win Development Group

Menene ƙungiyar Windows ke aiki dashi a lokacin?

NET Core akan Linux, DevOps akan doki

Yanzu zan iya faɗin hakan da ƙarfin gwiwa IdentityServer4 madadin kyauta ne mai kyau ga ADFS tare da irin wannan damar, ko menene Tsarin Tsarin Halittu Core - aljanna ga mai haɓakawa, inda ba lallai ne ku damu da rubuta rubutun SQL ba, amma ku bayyana tambayoyi a cikin bayanan cikin sharuddan OOP. Amma sai, yayin tattaunawar shirin aiki, na kalli wannan tari kamar dai cuneiform na Sumerian ne, na gane kawai PostgreSQL da Git.

A lokacin muna amfani sosai 'Yar tsana a matsayin tsarin gudanarwa na sanyi. A yawancin ayyukanmu da muka yi amfani da su GitLab CI, na roba, daidaitattun ayyuka masu ɗaukar nauyi ta amfani da su HAProxy lura da komai da Zabbix, ligaments Grafana и Prometheus, Mafarauci, kuma duk wannan yana jujjuya akan guntun ƙarfe HPESXi a kan VMware. Kowa ya san shi - classic na nau'in.

NET Core akan Linux, DevOps akan doki

Bari mu duba kuma mu yi ƙoƙari mu fahimci abin da ke faruwa kafin mu fara duk waɗannan ayyukan.

Me ya faru

TFS tsari ne mai ƙarfi mai ƙarfi wanda ba wai kawai yana ba da lambar daga mai haɓakawa zuwa injin samarwa na ƙarshe ba, har ma yana da saiti don daidaitawa sosai tare da ayyuka daban-daban - don samar da CI a matakin giciye.

NET Core akan Linux, DevOps akan doki
A baya can, waɗannan tagogi ne masu ƙarfi. TFS ta yi amfani da wakilai na Gina da yawa, waɗanda aka yi amfani da su don haɗa ayyuka da yawa. Kowane wakili yana da ma'aikata 3-4 don daidaita ayyuka da inganta tsarin. Sannan, bisa ga tsare-tsaren sakin, TFS ta isar da sabon ginin Gine zuwa uwar garken aikace-aikacen Windows.

Me muka so mu cimma?

Muna amfani da TFS don bayarwa da haɓakawa, kuma muna gudanar da aikace-aikacen akan uwar garken aikace-aikacen Linux, kuma akwai wani nau'in sihiri a tsakanin su. Wannan Akwatin Sihiri kuma akwai gishirin aikin gaba. Kafin in rabu, zan ɗauki wani mataki a gefe in faɗi wasu kalmomi game da aikace-aikacen.

Wannan aikin

Aikace-aikacen yana ba da ayyuka don sarrafa katunan da aka riga aka biya.

NET Core akan Linux, DevOps akan doki

Abokin ciniki

Akwai nau'ikan masu amfani guda biyu. Na farko sami dama ta hanyar shiga ta amfani da takardar shaidar SSL SHA-2. U na biyu akwai damar yin amfani da login da kalmar sirri.

HAProxy

Sa'an nan buƙatar abokin ciniki ya tafi HAProxy, wanda ya warware matsalolin masu zuwa:

  • izini na farko;
  • Ƙarshen SSL;
  • daidaita buƙatun HTTP;
  • buƙatun watsa shirye-shirye.

An tabbatar da takardar shaidar abokin ciniki tare da sarkar. Mu - dalĩli kuma za mu iya samun wannan, tunda mu kanmu muna ba da takaddun shaida ga abokan cinikin sabis.

Kula da batu na uku, za mu koma gare shi kadan kadan.

backend

Sun shirya yin baya akan Linux. Ƙarshen baya yana hulɗa tare da bayanan bayanai, yana ɗora jerin abubuwan da suka dace na gata sannan, ya danganta da irin gatan da mai amfani da izini ke da shi, yana ba da damar sanya hannu kan takaddun kuɗi da aika su don aiwatarwa, ko samar da wani nau'in rahoto.

Ajiye tare da HAProxy

Baya ga mahallin guda biyu da kowane abokin ciniki ya kewaya, akwai kuma mahallin ainihi. IdentityServer4 kawai yana ba ku damar shiga, wannan analog ɗin kyauta ne mai ƙarfi don ADFS - Adireshin Tarayya na Sabis na Aiki.

An aiwatar da buƙatar ainihi ta matakai da yawa. Mataki na farko - abokin ciniki ya shiga baya, wanda ya yi magana da wannan uwar garken kuma ya bincika kasancewar alamar ga abokin ciniki. Idan ba a samo shi ba, an mayar da buƙatar zuwa yanayin da ta fito, amma tare da turawa, kuma tare da turawa ta tafi zuwa ga ainihi.

Mataki na biyu - an karɓi buƙatar zuwa shafin izini a cikin IdentityServer, inda abokin ciniki ya yi rajista, kuma alamar da aka daɗe ana jira ta bayyana a cikin bayanan IdentityServer.

Mataki na uku - abokin ciniki ya koma baya ga mahallin da ya fito.

NET Core akan Linux, DevOps akan doki

IdentityServer4 yana da fasali: yana mayar da martani ga buƙatun dawowa ta hanyar HTTP. Duk yadda muka yi fama da kafa uwar garken, komai nawa muka haskaka kanmu da takardun, duk lokacin da muka sami buƙatun abokin ciniki na farko tare da URL wanda ya zo ta hanyar HTTPS, kuma IdentityServer ya dawo da mahallin guda ɗaya, amma tare da HTTP. Mun yi mamaki! Kuma mun canza duk wannan ta hanyar mahallin ainihi zuwa HAProxy, kuma a cikin kanun labarai dole ne mu canza ka'idar HTTP zuwa HTTPS.

Menene cigaba kuma a ina kuka ajiye?

Mun adana kuɗi ta amfani da mafita kyauta don ba da izini ga ƙungiyar masu amfani, albarkatu, tunda ba mu sanya IdentityServer4 a matsayin kulli na dabam a cikin wani yanki na daban ba, amma mun yi amfani da shi tare da bayan baya akan sabar guda ɗaya inda ƙarshen aikace-aikacen ke gudana. .

Yadda yakamata yayi aiki

Don haka, kamar yadda na yi alkawari - Akwatin sihiri. Mun riga mun fahimci cewa an ba mu tabbacin matsawa zuwa Linux. Bari mu tsara takamaiman ayyuka waɗanda ke buƙatar mafita.

NET Core akan Linux, DevOps akan doki

Yar tsana bayyana. Don isar da sarrafa sabis da tsarin aikace-aikacen, dole ne a rubuta girke-girke masu kyau. Nadi na fensir yana nuna yadda aka yi cikin sauri da inganci.

Hanyar bayarwa. Ma'auni shine RPM. Kowa ya fahimci cewa a cikin Linux ba za ku iya yin ba tare da shi ba, amma aikin da kansa, bayan taro, saitin fayilolin DLL ne masu aiwatarwa. Akwai kusan 150 daga cikinsu, aikin yana da wahala sosai. Maganin jituwa ɗaya kawai shine haɗa wannan binary cikin RPM kuma tura aikace-aikacen daga gare ta.

Siffar. Dole ne mu saki sau da yawa, kuma dole ne mu yanke shawarar yadda za mu samar da sunan kunshin. Wannan tambaya ce ta matakin haɗin kai tare da TFS. Muna da wakili na gini akan Linux. Lokacin da TFS ta aika aiki zuwa ga ma'aikaci - ma'aikaci - ga Wakilin Gina, kuma yana ba da shi gungun masu canji waɗanda ke ƙarewa a cikin yanayin aikin mai sarrafa. Waɗannan masu canjin yanayi sun ƙunshi sunan Gina, sunan sigar, da sauran masu canji. Kara karantawa game da wannan a cikin sashin "Ginin Kunshin RPM".

Saita TFS ya sauko don kafa Pipeline. A baya, mun tattara duk ayyukan Windows akan ma'aikatan Windows, amma yanzu wakili na Linux ya bayyana - wakili na Gina, wanda ke buƙatar haɗa shi cikin rukunin ginin, wadatar da wasu kayan tarihi, kuma ya faɗi irin ayyukan da za a gina akan wannan ginin ginin. , kuma ko ta yaya canza Pipeline.

IdentityServer. ADFS ba shine hanyarmu ba, muna zuwa Buɗe Source.

Bari mu je ta cikin sassan.

Akwatin Sihiri

Ya ƙunshi sassa huɗu.

NET Core akan Linux, DevOps akan doki

Wakilin Gina Linux. Linux, saboda mun gina shi - yana da ma'ana. An yi wannan bangare a matakai uku.

  • Sanya ma'aikata kuma ba shi kaɗai ba, tunda ana tsammanin aikin rarraba kan aikin.
  • Shigar da NET Core 1.x. Me yasa 1.x lokacin da 2.0 ya riga ya kasance a cikin daidaitaccen ma'ajin? Domin lokacin da muka fara ci gaba, sigar kwanciyar hankali ta kasance 1.09, kuma an yanke shawarar yin aikin bisa shi.
  • Git 2.x.

RPM-majiya. Ana buƙatar adana fakitin RPM a wani wuri. An ɗauka cewa za mu yi amfani da ma'ajin RPM na kamfani guda ɗaya wanda ke samuwa ga duk rundunonin Linux. Abin da suka yi ke nan. An saita uwar garken ma'ajiya ƙugiya wanda ya zazzage fakitin RPM da ake buƙata daga ƙayyadadden wuri. Wakilin Gina ya bayar da rahoton sigar fakitin zuwa gidan yanar gizon.

GitLab. Hankali! GitLab anan ana amfani da shi ba ta masu haɓakawa ba, amma ta sashin ayyuka don sarrafa nau'ikan aikace-aikacen, nau'ikan fakiti, saka idanu da matsayin duk injunan Linux, kuma yana adana girke-girke - duk Puppet yana bayyana.

'Yar tsana - yana warware duk batutuwa masu rikitarwa kuma yana ba da daidai tsarin da muke so daga Gitlab.

Mun fara nutsewa. Ta yaya isar da DLL zuwa RPM ke aiki?

Isar da DDL zuwa RPM

Bari mu ce muna da tauraruwar dutsen ci gaba ta NET. Yana amfani da Visual Studio kuma yana ƙirƙirar reshen saki. Bayan haka, yana loda shi zuwa Git, kuma Git anan shine mahallin TFS, wato, wurin ajiyar aikace-aikacen da mai haɓaka ke aiki dashi.

NET Core akan Linux, DevOps akan doki

Bayan haka TFS ya ga cewa sabon alkawari ya zo. Wace app? A cikin saitunan TFS akwai lakabin da ke nuna irin albarkatun da wani wakilin Gina ke da shi. A wannan yanayin, yana ganin cewa muna gina aikin NET Core kuma ya zaɓi wakili na Gina Linux daga tafkin.

Wakilin Gina yana karɓar kafofin kuma yana zazzage abin da ake bukata abin dogaro daga ma'ajiyar NET, npm, da sauransu. kuma bayan gina aikace-aikacen kanta da marufi na gaba, aika fakitin RPM zuwa ma'ajiyar RPM.

A daya bangaren kuma, abin yana faruwa. Injiniyan sashen ayyuka yana da hannu kai tsaye a cikin ƙaddamar da aikin: yana canza nau'ikan fakiti a ciki Hiera a cikin ma'ajiya inda aka adana girke-girke na aikace-aikacen, bayan haka Puppet yana jawo Yum, yana ɗauko sabon fakitin daga maajiyar, kuma sabon sigar aikace-aikacen yana shirye don amfani.

NET Core akan Linux, DevOps akan doki

Komai yana da sauƙi a cikin kalmomi, amma menene ke faruwa a cikin wakilin Gina kanta?

Marufi DLL RPM

Sami tushen aikin da gina ɗawainiya daga TFS. Gina wakili ya fara gina aikin da kansa daga tushe. Aikin da aka haɗa yana samuwa azaman saiti DLL fayiloli, wanda aka tattara a cikin ma'ajiyar zip don rage nauyin da ke kan tsarin fayil.

An jefar da rumbun ajiyar ZIP zuwa ga tsarin ginin fakitin RPM. Bayan haka, rubutun Bash yana fara canza canjin yanayi, ya nemo sigar Gina, sigar aikin, hanyar zuwa ginin directory, kuma yana gudanar da RPM-gina. Da zarar ginin ya cika, ana buga fakitin zuwa wurin ajiyar gida, wanda ke kan Wakilin Gina.

Na gaba, daga Wakilin Gina zuwa uwar garken a cikin ma'ajin RPM An aika buƙatar JSON yana nuna sunan sigar da ginawa. Webhook, wanda na yi magana game da shi a baya, yana zazzage wannan fakitin daga ma'ajiyar gida akan wakili na Gina kuma yana sa sabon taron ya kasance don shigarwa.

NET Core akan Linux, DevOps akan doki

Me yasa wannan takamaiman tsarin isar da fakiti zuwa ma'ajiyar RPM? Me yasa ba zan iya aika fakitin da aka haɗa nan da nan zuwa wurin ajiya ba? Gaskiyar ita ce wannan sharadi ne don tabbatar da aminci. Wannan yanayin yana iyakance yuwuwar mutane marasa izini suna loda fakitin RPM zuwa sabar da ke isa ga duk injunan Linux.

Sigar Database

A cikin shawarwari tare da ƙungiyar ci gaba, ya nuna cewa mutanen sun fi kusa da MS SQL, amma a yawancin ayyukan da ba na Windows ba mun riga mun yi amfani da PostgreSQL da dukan ƙarfinsu. Tun da mun riga mun yanke shawarar yin watsi da duk abin da aka biya, mun fara amfani da PostgreSQL anan ma.

NET Core akan Linux, DevOps akan doki

A cikin wannan ɓangaren ina so in gaya muku yadda muka tsara ma'ajin bayanai da kuma yadda muka zaɓa tsakanin Flyway da Cibiyar Tsarin Mulki. Bari mu dubi riba da rashin amfaninsu.

Минусы

Flyway yana tafiya daya kawai, mu ba za mu iya mirgina baya ba - wannan babban hasara ne. Kuna iya kwatanta shi tare da Tsarin Tsarin Halittu ta wasu hanyoyi - dangane da saukakawa masu haɓakawa. Kuna tuna cewa mun sanya wannan a kan gaba, kuma babban ma'auni shine kada a canza wani abu don ci gaban Windows.

Don Flyway mu an bukaci wani nau'i na nannadedon kada samarin su rubuta Tambayoyin SQL. Sun fi kusanci da aiki a cikin sharuɗɗan OOP. Mun rubuta umarni don aiki tare da abubuwan bayanai, mun ƙirƙiri tambayar SQL kuma muka aiwatar da shi. Sabuwar sigar bayanan tana shirye, an gwada - komai yana da kyau, komai yana aiki.

Tsarin Tsarin Halittu Core yana da ragi - ƙarƙashin nauyi mai nauyi yana gina ƙananan tambayoyin SQL, kuma raguwa a cikin bayanan bayanai na iya zama mahimmanci. Amma tun da ba mu da sabis mai kayatarwa, ba mu ƙididdige nauyin a ɗaruruwan RPS ba, mun yarda da waɗannan haɗari kuma mun ba da matsala ga mu nan gaba.

Плюсы

Tsarin Tsarin Halittu Core yana aiki daga cikin akwatin kuma yana da sauƙin haɓakawa, da kuma Flyway Sauƙi yana haɗawa cikin CI data kasance. Amma muna sanya shi dacewa ga masu haɓakawa :)

Hanyar mirgine

Puppet yana ganin canji a cikin sigar fakitin yana zuwa, gami da wanda ke da alhakin ƙaura. Na farko, yana shigar da fakitin da ya ƙunshi rubutun ƙaura da ayyuka masu alaƙa da bayanai. Bayan wannan, aikace-aikacen da ke aiki tare da bayanan bayanan yana sake farawa. Na gaba yana zuwa shigar da sauran abubuwan da suka rage. An bayyana tsarin da aka shigar da fakiti da kuma ƙaddamar da aikace-aikace a cikin bayyanar tsana.

Aikace-aikacen suna amfani da mahimman bayanai, kamar tokens, kalmomin sirri na bayanai, duk waɗannan ana jan su zuwa cikin config daga Puppet master, inda ake adana su a cikin ɓoye.

Matsalolin TFS

Bayan da muka yanke shawara kuma muka gane cewa duk abin yana aiki da mu, sai na yanke shawarar duba abin da ke faruwa tare da majalisai a cikin TFS gaba ɗaya don sashen ci gaba na Win akan wasu ayyuka - ko muna ginawa / sakewa da sauri ko a'a, kuma gano matsaloli masu mahimmanci tare da sauri .

Ɗaya daga cikin manyan ayyukan yana ɗaukar mintuna 12-15 don haɗuwa - wannan shine lokaci mai tsawo, ba za ku iya rayuwa haka ba. Bincike mai sauri ya nuna mummunar faduwa a cikin I/O, kuma wannan yana kan tsararru.

Bayan na yi nazarinsa bangaran ta bangaren, sai na gano abubuwa guda uku. Na farko - "Kaspersky riga-kafi", wanda ke bincika tushe akan duk wakilan Gina Windows. Na biyu - Windows Indexer. Ba a kashe shi ba, kuma duk abin da aka ƙididdige shi a ainihin lokacin akan wakilan Gina yayin aikin turawa.

Na uku - Npm shigar. Ya zama cewa a yawancin Bututun bututu mun yi amfani da wannan ainihin yanayin. Me ya sa ba shi da kyau? Ana gudanar da hanyar shigar Npm lokacin da aka kafa bishiyar dogaro a ciki kunshin-kulle.json, inda ake rubuta nau'ikan fakitin da za a yi amfani da su don gina aikin. Abin da ya rage shi ne shigar Npm yana fitar da sabbin nau'ikan fakiti daga Intanet kowane lokaci, kuma wannan yana ɗaukar lokaci mai yawa a cikin yanayin babban aiki.

Masu haɓakawa wani lokaci suna gwaji akan injin gida don gwada yadda wani yanki ko gaba ɗaya aikin ke aiki. Wani lokaci ya zama cewa komai yana da sanyi a cikin gida, amma sun haɗa shi, suna fitar da shi, kuma babu abin da ya faru. Mun fara gano menene matsalar - eh, nau'ikan fakiti daban-daban tare da dogaro.

yanke shawara

  • Sources a cikin keɓancewar AV.
  • Kashe ƙididdiga.
  • Canji zuwa npm ci.

Amfanin npm ci shine mu Muna tattara itacen dogaro sau ɗaya, kuma muna samun damar samar da mai haɓakawa jerin fakiti na yanzu, wanda zai iya yin gwaji a cikin gida gwargwadon yadda yake so. Wannan yana ceton lokaci developers suka rubuta code.

Kanfigareshan

Yanzu kadan game da daidaitawar ma'ajin. A tarihi muna amfani Nexus don sarrafa wuraren ajiya, gami da REPO na ciki. Wannan ma'ajiya na ciki ya ƙunshi duk abubuwan da muke amfani da su don dalilai na ciki, misali, sa ido na rubutu da kansa.

NET Core akan Linux, DevOps akan doki

Muna kuma amfani NuGet, kamar yadda yana da mafi kyawun caching idan aka kwatanta da sauran manajan kunshin.

sakamakon

Bayan mun inganta Ma'aikatan Gina, an rage matsakaicin lokacin ginawa daga mintuna 12 zuwa 7.

Idan muka ƙidaya duk injunan da za mu iya amfani da su don Windows, amma mun canza zuwa Linux a cikin wannan aikin, mun adana kusan $ 10. Kuma wannan yana kan lasisi kawai, da ƙari idan muka yi la'akari da abubuwan da ke ciki.

Shirye-shirye

A kwata na gaba, mun shirya yin aiki don inganta isar da lambar.

Juyawa zuwa hoton Docker da aka riga aka gina. TFS abu ne mai sanyi tare da plugins da yawa waɗanda ke ba ka damar haɗawa cikin Pipeline, gami da taron tushen faɗakarwa, ka ce, hoton Docker. Muna so mu sanya wannan fararwa don guda ɗaya kunshin-kulle.json. Idan abubuwan abubuwan da aka yi amfani da su don gina aikin ko ta yaya sun canza, za mu gina sabon hoton Docker. Ana amfani da shi daga baya don tura akwati tare da aikace-aikacen da aka haɗa. Wannan ba haka lamarin yake ba a yanzu, amma muna shirin canzawa zuwa gine-ginen microservice a Kubernetes, wanda ke haɓakawa sosai a cikin kamfaninmu kuma yana ba da mafita na samarwa na dogon lokaci.

Takaitaccen

Ina ƙarfafa kowa ya jefar da Windows, amma ba don ban san yadda ake dafa shi ba. Dalili shine yawancin hanyoyin magance Opensource sune Linux tari. kana lafiya ajiye albarkatun. A ra'ayina, gaba ta kasance na Buɗe tushen mafita akan Linux tare da al'umma mai ƙarfi.

Bayanan Bayani na Alexander Sinchinov ku GitHub.

DevOps Conf taro ne game da haɗin kai na ci gaba, gwaji da tsarin aiki don masu sana'a ta hanyar kwararru. Shi ya sa aikin da Alexander yayi magana akai? aiwatar da aiki, kuma a ranar wasan kwaikwayon an sami nasarar sakewa guda biyu. Kunna DevOps Conf a RIT++ A ranar 27 da 28 ga Mayu za a sami ƙarin irin wannan shari'o'in daga likitoci. Har yanzu kuna iya tsalle cikin karusar ƙarshe da gabatar da rahoto ko dauki lokacin ku don littafin tikitin. Haɗu da mu a Skolkovo!

source: www.habr.com

Add a comment