{"id":32217,"date":"2019-10-31T21:45:43","date_gmt":"2019-10-31T18:45:43","guid":{"rendered":"https:\/\/prohoster.info\/blog\/net-core-na-linux-devops-na-kone\/"},"modified":"2019-10-31T21:45:43","modified_gmt":"2019-10-31T18:45:43","slug":"net-core-na-linux-devops-na-kone","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/net-core-na-linux-devops-na-kone","title":{"rendered":".NET Core n\u00eb Linux, DevOps n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Ne zhvilluam DevOps si\u00e7 mund\u00ebm. Ishim 8 persona, dhe Vasia ishte m\u00eb i miri n\u00eb Windows. Papritmas, Vasia u largua, dhe un\u00eb mora detyr\u00ebn p\u00ebr t\u00eb sjell\u00eb nj\u00eb projekt t\u00eb ri, i cili ofron zhvillim p\u00ebr Windows. Kur i shp\u00ebrndava t\u00eb gjith\u00eb stek-un e zhvillimit p\u00ebr Windows mbi tryez\u00eb, e kuptova se situata ishte e v\u00ebshtir\u00eb...<\/p>\n

K\u00ebshtu fillon historia Aleksand\u00ebr Sin\u00e7inov<\/b> n\u00eb DevOpsConf<\/a><\/noindex>. Kur specialisti kryesor i Windows u largua nga kompania, Aleksandri u pyet se \u00e7far\u00eb duhet t\u00eb b\u00ebnte tani. T\u00eb kalonte n\u00eb Linux, sigurisht! Aleksandri do t\u00eb tregoj\u00eb se si arriti t\u00eb krijoj\u00eb nj\u00eb precedent dhe t\u00eb transferoj\u00eb nj\u00eb pjes\u00eb t\u00eb zhvillimit p\u00ebr Windows n\u00eb Linux p\u00ebrmes nj\u00eb projekti t\u00eb realizuar me 100,000 p\u00ebrdorues t\u00eb fundit.<\/p>\n

\".NET
\n
\nSi e leht\u00eb dhe e natyrshme t\u00eb dor\u00ebzosh nj\u00eb projekt n\u00eb RPM duke p\u00ebrdorur TFS, Puppet, Linux .NET core? Si t\u00eb mbash versionimin e DB-s\u00eb s\u00eb projektit, n\u00ebse zhvilluesit p\u00ebr her\u00eb t\u00eb par\u00eb d\u00ebgjojn\u00eb fjal\u00ebt Postgres dhe Flyway, dhe afati \u00ebsht\u00eb pasnes\u00ebr? Si t\u00eb integrosh me Docker? Si t'i motivosh zhvilluesit .NET t\u00eb heqin dor\u00eb nga Windows dhe smoothies p\u00ebr Puppet dhe Linux? Si t\u00eb zgjidh\u00ebsh konfliktet ideologjike n\u00ebse nuk ka energji, d\u00ebshira ose burime p\u00ebr t\u00eb mbajtur Windows n\u00eb prodhim? N\u00eb lidhje me k\u00ebt\u00eb, si dhe rreth Web Deploy, testimit, CI, praktikave t\u00eb p\u00ebrdorimit t\u00eb TFS n\u00eb projektet ekzistuese, dhe sigurisht, p\u00ebr k\u00ebmbanat e thyera dhe zgjidhjet q\u00eb funksionojn\u00eb, n\u00eb transkriptin e raportit t\u00eb Aleksandrit.
\n<\/a><\/noindex>
\n

\r\n \"Luaj\r\n
<\/div>\r\n <\/div><\/center>
\nPra, Vasya u largua, detyra \u00ebsht\u00eb p\u00ebr mua, zhvilluesit presin me tulla me padurim. Kur kuptova p\u00ebrfundimisht se nuk mund ta ktheja Vasya - fillova pun\u00ebn. Fillimisht, vler\u00ebsova p\u00ebrqindjen e VM Windows n\u00eb parku ton\u00eb. Numri ishte n\u00eb d\u00ebm t\u00eb Windows.<\/p>\n

\".NET
\n
\nDuke qen\u00eb se ne po zhvillojm\u00eb aktivisht DevOps, kuptova se duhej t\u00eb ndryshoja di\u00e7ka n\u00eb qasjen p\u00ebr nxjerrjen e nj\u00eb aplikacioni t\u00eb ri. Zgjidhja ishte nj\u00eb - sa m\u00eb shum\u00eb q\u00eb \u00ebsht\u00eb e mundur, t\u00eb kalojm\u00eb gjith\u00e7ka n\u00eb Linux. Google m\u00eb ndihmoi - n\u00eb at\u00eb koh\u00eb .Net ishte portuar n\u00ebn Linux, dhe kuptova se kjo ishte zgjidhja!<\/p>\n

Pse .NET core n\u00eb lidhje me Linux?<\/h2>\n

\nKjo kishte disa arsye. Nd\u00ebrmjet 't\u00eb paguash' dhe 't\u00eb mos paguash' shumica do t\u00eb zgjedhin t\u00eb dyt\u00ebn \u2014 si dhe un\u00eb. Licenca p\u00ebr MSDB kushton rreth 1 000 $, mir\u00ebmbajtja e parkut t\u00eb makinave virtuale Windows matet n\u00eb qindra dollar\u00eb. P\u00ebr nj\u00eb kompani t\u00eb madhe, k\u00ebto jan\u00eb shpenzime t\u00eb m\u00ebdha. Prandaj, kursimi\u00a0<\/b>\u2014 arsyeja e par\u00eb<\/b>. Nuk \u00ebsht\u00eb m\u00eb e r\u00ebnd\u00ebsishmja, por nj\u00eb nga ato t\u00eb r\u00ebnd\u00ebsishme.<\/p>\n

Makinat virtuale Windows konsumojn\u00eb m\u00eb shum\u00eb burime se sa homolog\u00ebt e tyre Linux \u2014 ato jan\u00eb t\u00eb r heavy<\/b>. Duke marr\u00eb parasysh madh\u00ebsin\u00eb e nj\u00eb kompanie t\u00eb madhe, ne zgjodh\u00ebm Linux.<\/p>\n

Sistemi thjesht integret n\u00eb CI ekzistues<\/b>. Ne e konsiderojm\u00eb veten DevOps progresiv\u00eb, p\u00ebrdorim Bamboo, Jenkins dhe GitLab CI, prandaj pjesa m\u00eb e madhe e pun\u00ebs son\u00eb b\u00ebhet n\u00eb Linux.<\/p>\n

Arsyeja e fundit \u00ebsht\u00eb mir\u00ebmbajtja e leht\u00eb. <\/b>Na duhej t\u00eb ulja e pragut t\u00eb hyrjes p\u00ebr 'mir\u00ebmbajt\u00ebsit' \u2014 djemt\u00eb q\u00eb kuptojn\u00eb pjes\u00ebn teknike, sigurojn\u00eb vazhdim\u00ebsin\u00eb dhe mbajn\u00eb sh\u00ebrbimet nga linja e dyt\u00eb. Ata tashm\u00eb ishin t\u00eb njohur me stakun Linux, k\u00ebshtu q\u00eb u ishte shum\u00eb m\u00eb e leht\u00eb t\u00eb kuptonin produktin e ri, ta mb\u00ebshtesin dhe ta mir\u00ebmbajn\u00eb, sesa t\u00eb shpenzonin burime shtes\u00eb p\u00ebr t\u00eb kuptuar nj\u00eb funksionalitet t\u00eb ngjash\u00ebm t\u00eb softuerit p\u00ebr platform\u00ebn Windows.<\/p>\n

K\u00ebrkesat<\/h2>\n

\nE para dhe m\u00eb e r\u00ebnd\u00ebsishmja \u00ebsht\u00eb leht\u00ebsia e zgjidhjes s\u00eb re p\u00ebr zhvilluesit<\/b>. Jo t\u00eb gjith\u00eb ishin t\u00eb gatsh\u00ebm p\u00ebr ndryshime, ve\u00e7an\u00ebrisht pas p\u00ebrmendjes s\u00eb fjal\u00ebs Linux. Zhvilluesit duan Visual Studio t\u00eb tyre t\u00eb dashur, TFS me teste automatike p\u00ebr nd\u00ebrtimet dhe smoothie. Si ndodh dor\u00ebzimi n\u00eb prodhim - p\u00ebr ta nuk ka r\u00ebnd\u00ebsi. K\u00ebshtu, ne vendos\u00ebm t\u00eb mos ndryshojm\u00eb procesin e zakonsh\u00ebm dhe t\u00eb l\u00ebm\u00eb gjith\u00e7ka t\u00eb paprekur p\u00ebr zhvillimin n\u00eb Windows. <\/p>\n

Projekti i ri duhet t\u00eb integrohet n\u00eb CI ekzistuese<\/b>. Rails ishin tashm\u00eb n\u00eb vend dhe gjith\u00eb puna duhej t\u00eb kryhej duke pasur parasysh parametrat e sistemit t\u00eb menaxhimit t\u00eb konfigurimit, standardet e pranueshme t\u00eb dor\u00ebzimit dhe sistemet e monitorimit.<\/p>\n

Thjesht\u00ebsia n\u00eb mb\u00ebshtetje dhe operim<\/b>, si kushte p\u00ebr nj\u00eb prag minimal hyrjeje p\u00ebr t\u00eb gjith\u00eb pjes\u00ebmarr\u00ebsit e rinj nga departamente t\u00eb ndryshme dhe departamenti i mb\u00ebshtetjes.<\/p>\n

Afati - dje<\/b>.<\/p>\n

Grupi i zhvillimit t\u00eb Win<\/h2>\n

\nMe \u00e7far\u00eb po punonte ekipi i Windows?<\/p>\n

\".NET
\n
\nTani mund t\u00eb them me siguri se IdentityServer4<\/b>\u00a0\u00ebsht\u00eb nj\u00eb alternativ\u00eb e shk\u00eblqyer falas p\u00ebr ADFS me funksionalitete t\u00eb ngjashme, ose se Entity Framework Core<\/b>\u00a0\u2014 nj\u00eb parajs\u00eb p\u00ebr zhvilluesit, ku mund t\u00eb mos shqet\u00ebsoheni p\u00ebr shkruarjen e skripteve SQL, por t\u00eb p\u00ebrshkruani k\u00ebrkesat n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave n\u00eb terma OOP. Por at\u00ebher\u00eb, gjat\u00eb diskutimit t\u00eb planit t\u00eb veprimit, e shikoja k\u00ebt\u00eb stiv\u00eb si nj\u00eb shkrim t\u00eb lasht\u00eb sumerian duke njohur vet\u00ebm PostgreSQL dhe Git.<\/p>\n

N\u00eb at\u00eb koh\u00eb ne po p\u00ebrdornim aktivisht Puppet<\/b> si sistem p\u00ebr menaxhimin e konfiguracionit. N\u00eb shumic\u00ebn e projekteve tona ne p\u00ebrdornim GitLab CI<\/b>, Elastic<\/b>, balanconim sh\u00ebrbime me ngarkes\u00eb t\u00eb lart\u00eb duke p\u00ebrdorur HAProxy,<\/b> v\u00ebzhgonim gjith\u00e7ka me Zabbix<\/b>, lidh\u00ebsi Grafana<\/b> dhe\u00a0Prometheus<\/b>, Jaeger<\/b>, dhe gjith\u00e7ka kjo funksiononte n\u00eb\u00a0HP<\/b> me\u00a0ESXi<\/b> n\u00eb\u00a0VMware<\/b>. T\u00eb gjith\u00eb e njohin \u2014 klasika e zhanrit.<\/p>\n

\".NET
\n
\nLe t\u00eb shohim dhe t\u00eb p\u00ebrpiqemi t\u00eb kuptojm\u00eb se \u00e7far\u00eb ndodhi p\u00ebrpara se t\u00eb nisnim t\u00eb gjitha k\u00ebto nd\u00ebrhyrje.<\/p>\n

\u00c7far\u00eb ishte<\/h2>\n

\nTFS \u2014 \u00ebsht\u00eb nj\u00eb sistem mjaft i fuqish\u00ebm, i cili jo vet\u00ebm q\u00eb d\u00ebrgon kodin nga zhvilluesi n\u00eb makin\u00eb p\u00ebrfundimtare t\u00eb prodhimit, por gjithashtu ka nj\u00eb grup p\u00ebr integrim shum\u00eb fleksib\u00ebl me sh\u00ebrbime t\u00eb ndryshme \u2014 p\u00ebr t\u00eb siguruar CI n\u00eb nivel multipllatform.<\/p>\n

\".NET
\nM\u00eb par\u00eb, k\u00ebto ishin vet\u00ebm dritare t\u00eb thjeshta. TFS p\u00ebrdorte disa agjent\u00eb t\u00eb nd\u00ebrtimit, mbi t\u00eb cil\u00ebt mblidheshin shum\u00eb projekte. \u00c7do agjent kishte 3-4 pun\u00ebtor\u00eb, p\u00ebr t\u00eb ndar\u00eb detyrat dhe optimizuar procesin. Pastaj, sipas planeve t\u00eb l\u00ebshimit, TFS d\u00ebrgonte nd\u00ebrtimin e ri n\u00eb serverin Windows t\u00eb aplikacioneve.<\/p>\n

\u00c7far\u00eb d\u00ebshironim t\u00eb arrijm\u00eb<\/h2>\n

\nP\u00ebr d\u00ebrgimin dhe zhvillimin p\u00ebrdorim TFS, nd\u00ebrsa aplikacioni ekzekutohet n\u00eb serverin e aplikacioneve Linux, dhe ndodhet ndonj\u00eb magji mes tyre. Ky Magic Box<\/b> \u00ebsht\u00eb thelbi i pun\u00ebs s\u00eb ardhshme. Para se ta analizojm\u00eb at\u00eb n\u00eb pjes\u00eb, do t\u00eb b\u00ebj nj\u00eb hap n\u00eb an\u00eb dhe do t\u00eb them disa fjal\u00eb rreth aplikacionit.<\/p>\n

Projekt<\/h2>\n

\nAplikacioni ofron funksionalitet p\u00ebr menaxhimin e kartave t\u00eb parapaguara. <\/p>\n

\".NET
\n<\/p>\n

Klienti<\/h3>\n

\nEkzistonte dy lloje p\u00ebrdoruesish. I par\u00eb<\/b> ka qasje, duke u autorizuar me nj\u00eb certifikat\u00eb SSL SHA-2. Nj\u00eb\u00a0i dyt\u00eb<\/b> kishte qasje me p\u00ebrdorues dhe fjal\u00ebkalim.<\/p>\n

HAProxy<\/h3>\n

\nPas k\u00ebsaj, k\u00ebrkesa e klientit kalonte n\u00eb HAProxy, e cila vendoste detyrat vijues:<\/p>\n