{"id":87467,"date":"2020-07-08T13:42:11","date_gmt":"2020-07-08T11:42:11","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/rukovodstvo-dlya-nachinayushhih-sozdaem-devops-pajplajn"},"modified":"2020-07-08T13:42:11","modified_gmt":"2020-07-08T11:42:11","slug":"rukovodstvo-dlya-nachinayushhih-sozdaem-devops-pajplajn","status":"publish","type":"post","link":"https:\/\/prohoster.info\/lv\/blog\/administrirovanie\/rukovodstvo-dlya-nachinayushhih-sozdaem-devops-pajplajn","title":{"rendered":"S\u0101c\u0113ju rokasgr\u0101mata: veidojot DevOps cauru\u013cvadu","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Ja esat jauns DevOps jom\u0101, apskatiet \u0161o rokasgr\u0101matu, kas pal\u012bdz\u0113s izveidot j\u016bsu pirmo piecu posmu cauruli.<\/i><\/p>\n

\"S\u0101c\u0113ju<\/p>\n

DevOps ir k\u013cuvis par standarta risin\u0101jumu, lai labotu l\u0113nus, izklied\u0113tus vai neefekt\u012bvus programmat\u016bras izstr\u0101des procesus. Probl\u0113ma ir t\u0101da, ka, ja esat jauns DevOps jom\u0101 un nezin\u0101t, no kurienes s\u0101kt, jums var tr\u016bkt izpratnes par \u0161iem pa\u0146\u0113mieniem. \u0160aj\u0101 rakst\u0101 tiks apspriesta DevOps caurules defin\u012bcija un sniegta rokasgr\u0101mata t\u0101s izveido\u0161anai piecos so\u013cos. Lai gan \u0161is m\u0101c\u012bbu l\u012bdzeklis nav izsme\u013co\u0161s, tam vajadz\u0113tu dot jums pamatu, lai uzs\u0101ktu savu ce\u013cu un papla\u0161in\u0101tu savas zin\u0101\u0161anas n\u0101kotn\u0113. S\u0101ksim ar v\u0113sturi.<\/p>\n

Mana DevOps ce\u013cojums<\/h3>\n

\nAgr\u0101k es str\u0101d\u0101ju Citi Group m\u0101kon\u012b, izstr\u0101d\u0101jot Infrastructure-as-a-Service (IaaS) t\u012bmek\u013ca lietotni Citi m\u0101konis infrastrukt\u016bras p\u0101rvald\u012b\u0161anai, ta\u010du man vienm\u0113r bija interese par to, k\u0101 padar\u012bt att\u012bst\u012bbas procesu efekt\u012bv\u0101ku un ieviest pozit\u012bvas kult\u016bras izmai\u0146as izstr\u0101d\u0101t\u0101ju komand\u0101. Atbildi es atradu gr\u0101mat\u0101, kas tika ieteikta Gregam Lavenderam, Citi m\u0101kon\u012b arhitekt\u016bras un infrastrukt\u016bras tehniskajam direktoram. Gr\u0101mata sauc\u0101s \u201eFeniksa projekts\u201c (The Phoenix Project<\/a><\/noindex>), un taj\u0101 skaidro DevOps principus, un t\u0101 tiek las\u012bta k\u0101 rom\u0101ns.<\/p>\n

Gr\u0101matas aizmugur\u0113 redzamaj\u0101 tabul\u0101 ir par\u0101d\u012bts, cik bie\u017ei da\u017e\u0101das komp\u0101nijas izv\u0113r\u0161 savus sist\u0113mas izlaidumu vid\u0113:<\/p>\n

Amazon: 23 000 dien\u0101
\nGoogle: 5 500 dien\u0101
\nNetflix: 500 dien\u0101
\nFacebook: reizi dien\u0101
\nTwitter: 3 reizes ned\u0113\u013c\u0101
\nTipiska komp\u0101nija: reizi 9 m\u0113ne\u0161os<\/p>\n

K\u0101 visp\u0101r ir iesp\u0113jamas t\u0101das frekvences k\u0101 Amazon, Google un Netflix? Viss ir t\u0101d\u0113\u013c, ka \u0161\u012bs komp\u0101nijas ir izdom\u0101ju\u0161as, k\u0101 izveidot gandr\u012bz ide\u0101lu DevOps cauruli.
\n<\/a><\/noindex>
\nM\u0113s bij\u0101m t\u0101lu no t\u0101, l\u012bdz ievie\u0161am DevOps Citi. Taj\u0101 laik\u0101 man\u0101 komand\u0101 bija da\u017e\u0101das vides, bet izsnieg\u0161ana izstr\u0101des server\u012b bija piln\u012bgi manu\u0101la. Visi izstr\u0101d\u0101t\u0101ji piek\u013cuva tikai vienam izstr\u0101des serverim, kas balst\u012bts uz IBM WebSphere Application Server Community Edition. Probl\u0113ma bija t\u0101da, ka serveris izsl\u0113dz\u0101s, kad vair\u0101ki lietot\u0101ji vienlaikus m\u0113\u0123in\u0101ja veikt izsnieg\u0161anu, t\u0101p\u0113c izstr\u0101d\u0101t\u0101jiem bija j\u0101zi\u0146o viens otram par saviem nodomiem, kas bija diezgan s\u0101p\u012bgi. Turkl\u0101t past\u0101v\u0113ja probl\u0113mas ar zemu l\u012bme\u0146a koda test\u0113\u0161anas segumu, apjom\u012bgajiem manu\u0101l\u0101s izsnieg\u0161anas procesiem un iesp\u0113ju izsekot koda izsnieg\u0161anai, kas saist\u012bta ar konkr\u0113tu uzdevumu vai lietot\u0101ja st\u0101stu.<\/p>\n

Es sapratu, ka j\u0101veic kaut kas, un atradu kol\u0113\u0123i- l\u012bdz\u012bgi dom\u0101jo\u0161u partneri. M\u0113s nol\u0113m\u0101m sadarboties, lai izveidotu pirmo DevOps konveijeru \u2013 vi\u0146\u0161 uzst\u0101d\u012bja virtu\u0101lo ma\u0161\u012bnu un Tomcat lietojumserveri, kam\u0113r es str\u0101d\u0101ju pie Jenkins, integr\u0113ju Atlassian Jira un BitBucket, k\u0101 ar\u012b str\u0101d\u0101ju pie koda test\u0113\u0161anas seguma. \u0160is s\u0101nu projekts bija \u013coti veiksm\u012bgs: m\u0113s gandr\u012bz piln\u012bb\u0101 automatiz\u0113j\u0101m daudzas darb\u012bbas, pan\u0101c\u0101m gandr\u012bz 100% m\u016bsu izstr\u0101des servera darb\u012bbu, nodro\u0161in\u0101j\u0101m izsekojam\u012bbu un uzlaboj\u0101m koda test\u0113\u0161anas segumu, k\u0101 ar\u012b pievienoj\u0101m iesp\u0113ju saist\u012bt zarus Git ar uzdevumiem Jira vai izsnieg\u0161anu. Liel\u0101k\u0101 da\u013ca r\u012bku, ko m\u0113s izmantoj\u0101m, veidojot m\u016bsu DevOps konveijeru, bija atv\u0113rta koda.<\/p>\n

Tagad es saprotu, cik vienk\u0101r\u0161s bija m\u016bsu DevOps konveijers: m\u0113s neizmantoj\u0101m papla\u0161in\u0101jumus, piem\u0113ram, Jenkins failus vai Ansible. Tom\u0113r \u0161is vienk\u0101r\u0161ais konveijers darboj\u0101s labi, iesp\u0113jams, pateicoties Pareto principam (paz\u012bstams ar\u012b k\u0101 80\/20 likums).<\/p>\n

\u012ass ievads DevOps un CI\/CD konveijer\u0101<\/h3>\n

\nJa, ja jaut\u0101jat vair\u0101kiem cilv\u0113kiem: \u201eKas ir DevOps?\u201d, tad, visticam\u0101k, j\u016bs sa\u0146emsiet vair\u0101kas da\u017e\u0101das atbildes. DevOps, t\u0101pat k\u0101 Agile, ir att\u012bst\u012bjies, lai aptvertu daudz da\u017e\u0101du discipl\u012bnu, bet liel\u0101k\u0101 da\u013ca cilv\u0113ku piekrit\u012bs da\u017e\u0101m liet\u0101m: DevOps ir programmat\u016bras izstr\u0101des prakse vai programmat\u016bras izstr\u0101des cikls (SDLC), kura centr\u0101lais princips ir kult\u016bras mai\u0146a, kur\u0101 izstr\u0101d\u0101t\u0101ji un neizstr\u0101d\u0101t\u0101ji past\u0101v vid\u0113, kas:<\/p>\n

Automatiz\u0113 oper\u0101cijas, kuras iepriek\u0161 veica manu\u0101li;
\nKatrs dara to, kas vi\u0146am vislab\u0101k padodas;
\nIevie\u0161anas skaits noteikt\u0101 laika period\u0101 palielin\u0101s; caurlaidsp\u0113ja palielin\u0101s;
\nPalielin\u0101s izstr\u0101des elast\u012bba.<\/p>\n

Lai ar\u012b pareizo programmat\u016bras r\u012bku esam\u012bba ir ne tikai tas, kas nepiecie\u0161ams, lai izveidotu DevOps vidi, da\u017ei r\u012bki ir nepiecie\u0161ami. Galvenais r\u012bks ir nep\u0101rtraukta integr\u0101cija un nep\u0101rtraukta izvieto\u0161ana (CI\/CD). \u0160aj\u0101 konveijer\u012b vid\u0113m ir da\u017e\u0101das f\u0101zes (piem\u0113ram, DEV, INT, TST, QA, UAT, STG, PROD), daudzas oper\u0101cijas ir automatiz\u0113tas, un izstr\u0101d\u0101t\u0101ji var rakst\u012bt kvalitat\u012bvu kodu, pan\u0101kt izstr\u0101des elast\u012bbu un bie\u017e\u0101ku izvieto\u0161anu.<\/p>\n

\u0160aj\u0101 rakst\u0101 tiek aprakst\u012bts piecu posmu pieejas izveido\u0161anai DevOps konveijeram, k\u0101 par\u0101d\u012bts n\u0101kamaj\u0101 diagramm\u0101, izmantojot atv\u0113rt\u0101 koda r\u012bkus.<\/p>\n

Posms 1: CI\/CD metodes<\/h3>\n

\nVispirms jums nepiecie\u0161ams r\u012bks CI\/CD. Jenkins, atv\u0113rt\u0101 koda r\u012bks, kas balst\u012bts uz Java un tiek izplat\u012bts saska\u0146\u0101 ar MIT licenci, ir tas instruments, kas populariz\u0113ja DevOps pieeju un k\u013cuvis par de facto standartu.<\/p>\n

T\u0101tad, kas ir Jenkins? Uzskatiet to par k\u0101du ma\u0123isku univers\u0101lu t\u0101lvad\u012bbas pulti, kas var run\u0101t ar da\u017e\u0101d\u0101m pakalpojumu un r\u012bku sist\u0113m\u0101m un organiz\u0113t t\u0101s. CI\/CD r\u012bks, piem\u0113ram, Jenkins, pats par sevi ir bezj\u0113dz\u012bgs, ta\u010du tas k\u013c\u016bst jaud\u012bg\u0101ks, kad tas pievienojas da\u017e\u0101diem r\u012bkiem un pakalpojumiem.<\/p>\n

Jenkins ir tikai viens no daudziem atv\u0113rt\u0101 koda CI\/CD r\u012bkiem, ko varat izmantot, lai izveidotu DevOps cauru\u013cu.<\/p>\n

Jenkins: Creative Commons un MIT
\nTravis CI: MIT
\nCruiseControl: BSD
\nBuildbot: GPL
\nApache Gump: Apache 2.0
\nCabie: GNU<\/p>\n

T\u0101 izskat\u0101s DevOps procesi ar CI\/CD r\u012bku:<\/p>\n

\"S\u0101c\u0113ju<\/p>\n

Jums ir CI\/CD r\u012bks, kas darbojas j\u016bsu lok\u0101laj\u0101 t\u012bkl\u0101, bet patlaban j\u016bs varat dar\u012bt maz. P\u0101riesim pie n\u0101kam\u0101 so\u013ca ce\u013cojum\u0101 DevOps pasaul\u0113.<\/p>\n

2. solis: Koda versiju kontroles p\u0101rvald\u012bba<\/h3>\n

\nLab\u0101kais (un, iesp\u0113jams, visvienk\u0101r\u0161\u0101kais) veids, k\u0101 p\u0101rbaud\u012bt, vai j\u016bsu CI\/CD r\u012bks sp\u0113j rad\u012bt ma\u0123iju \u2013 integr\u0113ties ar versiju kontroles r\u012bku (SCM). K\u0101p\u0113c jums nepiecie\u0161ams kodu kontrole? Pie\u0146emsim, ka izstr\u0101d\u0101jat lietotni. Kad j\u016bs izstr\u0101d\u0101jat lietotni, j\u016bs kod\u0113jat, un nav noz\u012bmes, vai j\u016bs izmantojat Java, Python, C++, Go, Ruby, JavaScript vai k\u0101du no daudziem citiem programm\u0113\u0161anas valod\u0101m. Kods, ko j\u016bs rakst\u0101t, tiek saukts par avota kodu. Ies\u0101kum\u0101, it \u012bpa\u0161i, kad str\u0101d\u0101jat viens, iesp\u0113jams, to varat ievietot visus lok\u0101l\u0101 direktorij\u0101. Bet, kad projekts k\u013c\u016bst liel\u0101ks un j\u016bs uzaicin\u0101t citus uz sadarb\u012bbu, jums nepiecie\u0161ams veids, k\u0101 nov\u0113rst konfliktus efekt\u012bvas modifik\u0101ciju apmai\u0146as laik\u0101. Jums ar\u012b nepiecie\u0161ams veids, k\u0101 atjaunot iepriek\u0161\u0113j\u0101s versijas, jo dubl\u0113\u0161ana un kop\u0113\u0161ana\/iel\u012bm\u0113\u0161ana jau ir novecojusi. Jums (un j\u016bsu komandai) nepiecie\u0161ams kaut kas lab\u0101ks.<\/p>\n

Tie\u0161i \u0161eit koda versiju kontroles r\u012bks k\u013c\u016bst praktiski neaizst\u0101jam\u012bba. \u0160is r\u012bks saglab\u0101 j\u016bsu kodu repozitorijos, uzskaita versijas un koordin\u0113 projekta dal\u012bbnieku darbu.<\/p>\n

Lai gan past\u0101v daudzi koda versiju kontroles r\u012bki, Git ir standarts, un tas ir taisn\u012bgi. Es \u013coti ieteiktu izmantot Git, lai gan, ja v\u0113laties, ir ar\u012b citi atv\u0113rt\u0101 koda varianti.<\/p>\n

Git: GPLv2 un LGPL v2.1
\nSubversion: Apache 2.0
\nConcurrent Versions System (CVS): GNU
\nVesta: LGPL
\nMercurial: GNU GPL v2+<\/p>\n

T\u0101 izskat\u0101s DevOps cauru\u013cvads, pievienojot versiju kontroles r\u012bkus.<\/p>\n

\"S\u0101c\u0113ju<\/p>\n

CI\/CD r\u012bks var automatiz\u0113t p\u0101rbaudes, avota koda ieg\u016b\u0161anas un sadarb\u012bbas procesus starp dal\u012bbniekiem. Labi? Bet k\u0101 padar\u012bt to par str\u0101d\u0101jo\u0161u lietotni, lai miljardiem cilv\u0113ku to var\u0113tu izmantot un nov\u0113rt\u0113t?<\/p>\n

3. solis: Automatiz\u0101cijas r\u012bka izveide<\/h3>\n

\nLieliski! J\u016bs varat p\u0101rbaud\u012bt kodu un veikt izmai\u0146as versiju kontrol\u0113, k\u0101 ar\u012b iel\u016bgt savus draugus sadarboties izstr\u0101d\u0113. Ta\u010du j\u016bs v\u0113l neesat izveidojis lietotni. Lai izveidotu t\u012bmek\u013ca lietotni, to j\u0101kompil\u0113 un j\u0101pako izplat\u0101m\u0101 pakot\u0146u form\u0101t\u0101 vai j\u0101palai\u017e k\u0101 izpild\u0101mu failu. (L\u016bdzu, \u0146emiet v\u0113r\u0101, ka interpret\u0113jamai programm\u0113\u0161anas valodai, piem\u0113ram, JavaScript vai PHP, nav nepiecie\u0161ama kompil\u0101cija).<\/p>\n

Izmantojiet b\u016bvniec\u012bbas autom\u0101tiz\u0101cijas r\u012bku. Neatkar\u012bgi no t\u0101, kuru b\u016bvniec\u012bbas autom\u0101tiz\u0101cijas r\u012bku j\u016bs izv\u0113l\u0113sities, visi tie tiecas uz vienu un to pa\u0161u m\u0113r\u0137i: sav\u0101kt avota kodu k\u0101d\u0101 v\u0113lamaj\u0101 form\u0101t\u0101 un automatiz\u0113t uzdevumus, piem\u0113ram, t\u012br\u012b\u0161anu, kompil\u0113\u0161anu, test\u0113\u0161anu un izvieto\u0161anu konkr\u0113t\u0101 vid\u0113. B\u016bvniec\u012bbas r\u012bki at\u0161\u0137irsies atkar\u012bb\u0101 no j\u016bsu programm\u0113\u0161anas valodas, bet \u0161eit ir da\u017ei visp\u0101r\u012bgi atv\u0113rt\u0101 koda varianti.<\/p>\n

Nosaukums
\nLicence
\nProgramm\u0113\u0161anas valoda<\/p>\n

Maven
\nApache 2.0
\n Java<\/p>\n

BIND
\nApache 2.0
\nJava<\/p>\n

Gradle
\nApache 2.0
\nJava<\/p>\n

Bazel
\nApache 2.0
\nJava<\/p>\n

Make
\nGNU
\nN\/A<\/p>\n

Grunt
\nMIT
\nJavaScript<\/p>\n

Gulp
\nMIT
\nJavaScript<\/p>\n

Buildr
\nApache
\nRuby<\/p>\n

Rake
\nMIT
\nRuby<\/p>\n

A-A-P
\nGNU
\nPython<\/p>\n

SCons
\nMIT
\nPython<\/p>\n

BitBake
\nGPLv2
\nPython<\/p>\n

Cake
\nMIT
\nC#<\/p>\n

ASDF
\nExpat (MIT)
\nLISP<\/p>\n

Cabal
\nBSD
\nHaskell<\/p>\n

For\u0161i! J\u016bs varat ievietot autom\u0101tiz\u0101cijas r\u012bka konfigur\u0101cijas failus avota kontroles sist\u0113m\u0101 un \u013caut j\u016bsu CI\/CD r\u012bkam savienot visu kop\u0101.<\/p>\n

\"S\u0101c\u0113ju<\/p>\n

Viss ir labi, vai ne? Bet kur izvietot j\u016bsu lietotni?<\/p>\n

4. solis: T\u012bmek\u013ca lietot\u0146u serveris<\/h3>\n

\nPag\u0101ju\u0161aj\u0101 laik\u0101 jums ir iepakots fails, kas var b\u016bt gan izpild\u0101ms, gan instal\u0113jams. Lai jebkura lietotne b\u016btu patie\u0161\u0101m noder\u012bga, tai j\u0101sniedz k\u0101da pakalpojuma vai interfeisa funkcionalit\u0101te, bet jums ir nepiecie\u0161ams konteinera, kur ievietot j\u016bsu lietotni.<\/p>\n

T\u012bmek\u013ca lietot\u0146u serveris ir tie\u0161i t\u0101ds konteiners. Serveris nodro\u0161ina vidi, kur\u0101 var defin\u0113t izvietojam\u0101 pakot\u0146a lo\u0123iku. Ar\u012b serveris nodro\u0161ina interfeisu un pied\u0101v\u0101 t\u012bmek\u013ca pakalpojumus, atverot piesl\u0113gumus \u0101r\u0113jai pasaulei. Jums nepiecie\u0161ams HTTP serveris, k\u0101 ar\u012b k\u0101da vide (piem\u0113ram, virtu\u0101l\u0101 ma\u0161\u012bna) t\u0101 instal\u0113\u0161anai. Bet pagaid\u0101m pie\u0146emiet, ka j\u016bs par to uzzin\u0101siet t\u0101l\u0101k (lai gan es zem\u0101k run\u0101\u0161u par konteineriem).<\/p>\n

Past\u0101v vair\u0101ki atv\u0113rt\u0101 koda t\u012bmek\u013ca lietot\u0146u serveri.<\/p>\n

Nosaukums
\nLicence
\nProgramm\u0113\u0161anas valoda<\/p>\n

Tomcat
\nApache 2.0
\nJava<\/p>\n

Jetty
\nApache 2.0
\nJava<\/p>\n

WildFly
\nGNU Lesser Public
\nJava<\/p>\n

GlassFish
\nCDDL & GNU Less Public
\nJava<\/p>\n

Django
\n3-Clause BSD
\nPython<\/p>\n

Tornado
\nApache 2.0
\nPython<\/p>\n

Gunicorn
\nMIT
\nPython<\/p>\n

Python
\nMIT
\nPython<\/p>\n

Rails
\nMIT
\nRuby<\/p>\n

Node.js
\nMIT
\nJavascript<\/p>\n

J\u016bsu DevOps cauru\u013cvads dr\u012bz b\u016bs gatavs lieto\u0161anai. Lielisks darbs!<\/p>\n

\"S\u0101c\u0113ju<\/p>\n

Lai gan \u0161eit var\u0113tu apst\u0101ties un veikt integr\u0101ciju patst\u0101v\u012bgi, koda kvalit\u0101te ir svar\u012bgs faktors lietojumprogrammu izstr\u0101d\u0101t\u0101jiem, un par to ir j\u0101r\u016bp\u0113jas.<\/p>\n

5. solis: Koda test\u0113\u0161anas segums<\/h3>\n

\nTestu \u012bsteno\u0161ana var b\u016bt v\u0113l viens apgr\u016btin\u0101jums, ta\u010du izstr\u0101d\u0101t\u0101jiem ir j\u0101atkl\u0101j jebk\u0101das k\u013c\u016bdas lietojumprogramm\u0101 jau agri un j\u0101uzlabo koda kvalit\u0101te, lai garant\u0113tu, ka gala lietot\u0101ji b\u016bs apmierin\u0101ti. Par laimi, past\u0101v daudz atv\u0113rt\u0101 koda r\u012bku, lai test\u0113tu savu kodu un izveidotu ieteikumus t\u0101 kvalit\u0101tes uzlabo\u0161anai. V\u0113l lab\u0101k, ka vairums CI\/CD r\u012bku var pievienoties \u0161iem r\u012bkiem un automatiz\u0113t procesu.<\/p>\n

Koda test\u0113\u0161ana sast\u0101v no div\u0101m da\u013c\u0101m: koda test\u0113\u0161anas ietvariem, kas pal\u012bdz rakst\u012bt un palaist testus, un ieteikumu veido\u0161anas r\u012bkiem, kas pal\u012bdz uzlabot koda kvalit\u0101ti.<\/p>\n

Koda test\u0113\u0161anas sist\u0113mas<\/b><\/p>\n

Nosaukums
\nLicence
\nProgramm\u0113\u0161anas valoda<\/p>\n

JUnit
\nEclipse Public License
\nJava<\/p>\n

EasyMock
\nApache
\nJava<\/p>\n

Mockito
\nMIT
\nJava<\/p>\n

PowerMock
\nApache 2.0
\nJava<\/p>\n

Pytest
\n MIT
\nPython<\/p>\n

Hypothesis
\nMozilla
\nPython<\/p>\n

Tox
\nMIT
\nPython<\/p>\n

Ieteikumu sist\u0113mas koda uzlabo\u0161anai<\/b><\/p>\n

Nosaukums
\nLicence
\nProgramm\u0113\u0161anas valoda<\/p>\n

Cobertura
\nGNU
\nJava<\/p>\n

CodeCover
\nEclipse Public (EPL)
\nJava<\/p>\n

Coverage.py
\n Apache 2.0
\nPython<\/p>\n

Emma
\nCommon Public License
\nJava<\/p>\n

JaCoCo
\n Eclipse Public License
\nJava<\/p>\n

Hypothesis
\n Mozilla
\nPython<\/p>\n

Tox
\nMIT
\nPython<\/p>\n

Jasmine
\nMIT
\nJavaScript<\/p>\n

Karma
\nMIT
\nJavaScript<\/p>\n

Mocha
\n MIT
\nJavaScript<\/p>\n

Jest
\nMIT
\nJavaScript<\/p>\n

Piev\u0113rsiet uzman\u012bbu, ka liel\u0101k\u0101 da\u013ca iepriek\u0161 min\u0113to r\u012bku un ietvaru ir uzrakst\u012bti Java, Python un JavaScript valod\u0101, jo C++ un C# ir propriet\u0101ras programm\u0113\u0161anas valodas (lai gan GCC ir atv\u0113rt\u0101 koda).<\/p>\n

Tagad, kad esat \u012bstenojis koda p\u0101rkl\u0101juma r\u012bkus, j\u016bsu DevOps pl\u016bsmai b\u016btu j\u0101izskat\u0101s k\u0101 diagrammai, kas par\u0101d\u012bta \u0161\u012b ce\u013cve\u017ea s\u0101kum\u0101.<\/p>\n

Papildu so\u013ci<\/h3>\n

\nTvertnes<\/b><\/p>\n

K\u0101 jau teicu, j\u016bs varat izvietot savu serveri virtu\u0101l\u0101 ma\u0161\u012bn\u0101 vai server\u012b, bet konteineri ir popul\u0101ra lieta.<\/p>\n

Kas ir konteineri? \u012ass paskaidrojums ir t\u0101ds, ka virtu\u0101lajai ma\u0161\u012bnai ir nepiecie\u0161ams iev\u0113rojams oper\u0113t\u0101jsist\u0113mas atmi\u0146as apjoms, kas p\u0101rsniedz lietojumprogrammas izm\u0113ru, savuk\u0101rt konteineram nepiecie\u0161amas tikai da\u017eas bibliot\u0113kas un konfigur\u0101cijas, lai palaistu lietojumprogrammu. Ac\u012bmredzot virtu\u0101lajai ma\u0161\u012bnai joproj\u0101m ir svar\u012bgas pielieto\u0161anas jomas, ta\u010du konteiners ir viegla lieto\u0161anas risin\u0101jums, tostarp lietojumprogrammu serveriem.<\/p>\n

Lai gan past\u0101v ar\u012b citi konteineru varianti, vispopul\u0101r\u0101kie ir Docker un Kubernetes.<\/p>\n

Docker: Apache 2.0
\nKubernetes: Apache 2.0<\/p>\n

Starpprogrammat\u016bras automatiz\u0101cijas r\u012bki<\/b><\/p>\n

M\u016bsu DevOps cauru\u013cvads galvenok\u0101rt ir v\u0113rsts uz kop\u012bgu lietojumprogrammu izstr\u0101di un izvieto\u0161anu, ta\u010du ar DevOps r\u012bkiem ir iesp\u0113jams paveikt daudz citas lietas. Viens no veidiem ir infrastrukt\u016bras k\u0101 koda (IaC) r\u012bku izmanto\u0161ana, kas ir paz\u012bstami ar\u012b k\u0101 starpprogrammat\u016bras automatiz\u0101cijas r\u012bki. \u0160ie r\u012bki pal\u012bdz automatiz\u0113t instal\u0101ciju, p\u0101rvald\u012bbu un citas uzdevumu veik\u0161anas funkcijas starpprogrammat\u016brai. Piem\u0113ram, automatiz\u0101cijas r\u012bks var ieg\u016bt lietojumprogrammas, piem\u0113ram, t\u012bmek\u013ca lietojumprogrammu serverus, datu b\u0101zes un uzraudz\u012bbas r\u012bkus, ar pareizaj\u0101m konfigur\u0101cij\u0101m un izvietot t\u0101s lietojumprogrammu server\u012b.<\/p>\n

\u0160eit ir da\u017ei atv\u0113rt\u0101 koda starpprogrammat\u016bras automatiz\u0101cijas r\u012bki:<\/p>\n

Ansible: GNU Public
\nSaltStack: Apache 2.0
\nChef: Apache 2.0
\nPuppet: Apache vai GPL<\/p>\n

\"S\u0101c\u0113ju<\/p>\n

Uzziniet detaliz\u0113ti, k\u0101 ieg\u016bt piepras\u012btu profesiju no nulles vai uzlabot savas prasmes un algas, apg\u016bstot maksas tie\u0161saistes kursus SkillFactory:<\/p>\n