{"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 maj\u00eb","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Ne kemi zhvilluar DevOps sa kemi mundur. Ishim 8 persona, dhe Vasja ishte m\u00eb i shk\u00eblqyeri p\u00ebr Windows. Papritmas Vasja iku, dhe un\u00eb mora nj\u00eb sfid\u00eb p\u00ebr t\u00eb nxjerr\u00eb n\u00eb pah nj\u00eb projekt t\u00eb ri q\u00eb ofron zhvillim p\u00ebr Windows. Kur hodha n\u00eb tryez\u00eb t\u00eb gjith\u00eb grack\u00ebn e zhvillimit p\u00ebr Windows, e kuptova se situata ishte e dhimbshme...<\/p>\n

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

\".NET
\n
\nSi t\u00eb d\u00ebrgosh leht\u00ebsisht dhe n\u00eb m\u00ebnyr\u00eb pa stres projektin n\u00eb RPM, duke p\u00ebrdorur TFS, Puppet, Linux .NET core? Si t\u00eb mbash versionimin e DB t\u00eb projektit, kur zhvilluesit e par\u00eb d\u00ebgjojn\u00eb fjal\u00ebt Postgres dhe Flyway, dhe data e fundit \u00ebsht\u00eb nes\u00ebr? Si t\u00eb integrosh me Docker? Si t\u00eb motivojn\u00eb zhvilluesit .NET t\u00eb braktisin Windows-in dhe smoothies p\u00ebr Puppet dhe Linux? Si t\u00eb zgjidh\u00ebsh konflikte ideologjike, kur nuk ke as forc\u00eb, as d\u00ebshir\u00eb dhe as burime p\u00ebr t\u00eb mb\u00ebshtetur Windows n\u00eb prodhim? P\u00ebr k\u00ebt\u00eb, si dhe p\u00ebr Web Deploy, testimin, CI, praktikat e p\u00ebrdorimit t\u00eb TFS n\u00eb projektet ekzistuese, dhe natyrisht, p\u00ebr k\u00ebmb\u00ebt e thyera dhe zgjidhjet q\u00eb funksionojn\u00eb, n\u00eb transkriptin e fjalimit t\u00eb Aleksandrit.
\n<\/a><\/noindex>
\n

\r\n \"Luaj\r\n
<\/div>\r\n <\/div><\/center>
\nPra, Vasja iku, detyra \u00ebsht\u00eb n\u00eb duar t\u00eb mia, zhvilluesit presin me kazma me padurim. Kur e kuptova p\u00ebrfundimisht se Vasja nuk do t\u00eb kthehej, fillova pun\u00ebn. S\u00eb pari vler\u00ebsova p\u00ebrqindjen e Win VM n\u00eb paradin ton\u00eb. Numri nuk ishte n\u00eb favor t\u00eb Windows.<\/p>\n

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

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

\nP\u00ebr k\u00ebt\u00eb kishte disa arsye. Nd\u00ebrmjet \"t\u00eb paguash\" dhe \"t\u00eb mos paguash\" shumica do t\u00eb zgjedhin t\u00eb dyt\u00ebn - si un\u00eb. Licenca p\u00ebr MSDB kushton rreth 1,000 $, mb\u00ebshtetje e parkut t\u00eb makinave virtuale Windows arrin 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 \u00ebsht\u00eb arsyeja e par\u00eb<\/b>. Nuk \u00ebsht\u00eb m\u00eb e r\u00ebnd\u00ebsishmja, por \u00ebsht\u00eb nj\u00eb nga m\u00eb t\u00eb r\u00ebnd\u00ebsishmet.<\/p>\n

Makinat virtuale Windows ndjekin m\u00eb shum\u00eb burime se v\u00ebllez\u00ebrit e tyre nga Linux - jan\u00eb m\u00eb t\u00eb rheavy<\/b>. Duke marr\u00eb parasysh shkall\u00ebn e madhe t\u00eb kompanis\u00eb, ne zgjodh\u00ebm Linux.<\/p>\n

Sistemi thjesht integrohet n\u00eb CI-n\u00eb ekzistuese<\/b>. Ne e shohim veten si DevOps progresiv, p\u00ebrdorim Bamboo, Jenkins dhe GitLab CI, prandaj pjesa m\u00eb e madhe funksionon n\u00eb Linux.<\/p>\n

Arsyeja e fundit \u00ebsht\u00eb shoq\u00ebrimi i leht\u00eb. <\/b>Na nevojitej t\u00eb ulte pragun e hyrjes p\u00ebr \"shoq\u00ebruesit\" - djemt\u00eb q\u00eb kuptojn\u00eb pjes\u00ebn teknike, sigurojn\u00eb vazhdim\u00ebsin\u00eb dhe mb\u00ebshtesin sh\u00ebrbimet nga niveli i dyt\u00eb. Ata tashm\u00eb ishin t\u00eb njohur me stakun Linux, prandaj ishte shum\u00eb m\u00eb e leht\u00eb p\u00ebr ta t\u00eb kuptonin produktin e ri, ta mbanin dhe ta shoq\u00ebronin, sesa t\u00eb shpenzonin burime t\u00eb tjera p\u00ebr t\u00eb kuptuar funksionalitetin e 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 prej tyre ishin t\u00eb gatsh\u00ebm p\u00ebr ndryshime, ve\u00e7an\u00ebrisht pas fjal\u00ebs Linux. Zhvilluesit duan Visual Studio t\u00eb tyren, TFS me teste automatike p\u00ebr nd\u00ebrtimet dhe smuzi. Si ndodh shp\u00ebrndarja n\u00eb prodhim - nuk \u00ebsht\u00eb e r\u00ebnd\u00ebsishme p\u00ebr ta. Prandaj vendos\u00ebm t\u00eb mos ndryshonim procesin e zakonsh\u00ebm dhe t\u00eb l\u00ebm\u00eb gjith\u00e7ka pa ndryshime p\u00ebr zhvillimin Windows. <\/p>\n

Projekti i ri duhet t\u00eb integrohet n\u00eb CI-n\u00eb ekzistuese<\/b>. Railsat ishin tashm\u00eb atje dhe e gjith\u00eb puna duhej t\u00eb kryhej duke marr\u00eb parasysh parametrat e sistemit t\u00eb menaxhimit t\u00eb konfigurimit, standardet e pranueshme t\u00eb shp\u00ebrndarjes dhe sistemet e monitorimit.<\/p>\n

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

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

Grupi i zhvillimit Windows<\/h2>\n

\nMe \u00e7far\u00eb ka punuar ekipi 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 mund\u00ebsi t\u00eb ngjashme, ose q\u00eb Entity Framework Core<\/b>\u00a0\u00ebsht\u00eb nj\u00eb parajs\u00eb p\u00ebr zhvilluesin, ku mund t\u00eb shkruaj\u00eb k\u00ebrkesa n\u00eb DB n\u00eb termat e OOP pa u shqet\u00ebsuar p\u00ebr shkruajtjen e skripteve SQL. Por at\u00ebher\u00eb, gjat\u00eb diskutimit t\u00eb planit t\u00eb veprimit, e shikoja k\u00ebt\u00eb Stak si shkrim t\u00eb vjet\u00ebr, duke njohur vet\u00ebm PostgreSQL dhe Git.<\/p>\n

N\u00eb at\u00eb koh\u00eb, ne aktivisht p\u00ebrdornim Puppet<\/b> si sistem menaxhimi t\u00eb konfiguracionit. N\u00eb shumic\u00ebn e projekteve tona p\u00ebrdorim GitLab CI<\/b>, Elastic<\/b>, balancojm\u00eb sh\u00ebrbimet me ngarkesa t\u00eb larta me ndihm\u00ebn e HAProxy,<\/b> monitorojm\u00eb gjith\u00e7ka me ndihm\u00ebn e Zabbix<\/b>, lidhjeve N\u00ebse tashm\u00eb e dini se \u00e7far\u00eb \u00ebsht\u00eb analiza e grupeve dhe se si ta b\u00ebni n\u00eb SQL, kaloni menj\u00ebher\u00eb n\u00eb seksionin e fundit.<\/b> dhe\u00a0Prometheus<\/b>, Jaeger<\/b>, dhe e gjith\u00eb kjo funksionon n\u00eb harduerin\u00a0HP<\/b> c\u00a0ESXi<\/b> n\u00eb\u00a0VMware<\/b>. T\u00eb gjith\u00eb e njohin - klasika e zhanrit.<\/p>\n

\".NET
\n
\nLe t\u00eb shohim dhe t\u00eb p\u00ebrpiqemi t\u00eb kuptojm\u00eb se \u00e7far\u00eb ndodhi para se t\u00eb nisim k\u00ebto p\u00ebrzierje.<\/p>\n

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

\nTFS \u00ebsht\u00eb nj\u00eb sistem mjaft i fuqish\u00ebm, i cili jo vet\u00ebm q\u00eb d\u00ebrgon kodin nga zhvilluesi n\u00eb makinerin\u00eb p\u00ebrfundimtare t\u00eb prodhimit, por gjithashtu ka nj\u00eb paket\u00eb p\u00ebr nj\u00eb integrim shum\u00eb fleksib\u00ebl me sh\u00ebrbime t\u00eb ndryshme \u2013 p\u00ebr t\u00eb siguruar CI n\u00eb nivelin multi-platform\u00eb.<\/p>\n

\".NET
\nNj\u00eb her\u00eb, kishte vet\u00ebm dritare t\u00eb pafundme. TFS p\u00ebrdorte disa agjent\u00eb Build, mbi t\u00eb cil\u00ebt grumbulloheshin shum\u00eb projekte. N\u00eb \u00e7do agjent kishte 3-4 pun\u00ebtor\u00eb p\u00ebr t\u00eb b\u00ebr\u00eb paralelizmin e detyrave dhe p\u00ebr t\u00eb optimizuar procesin. M\u00eb pas, sipas planeve t\u00eb l\u00ebshimit, TFS dor\u00ebzonte nj\u00eb Build t\u00eb sapogatuar n\u00eb serverin e aplikacioneve Windows.<\/p>\n

\u00c7far\u00eb donim t\u00eb arrinim<\/h2>\n

\nP\u00ebr d\u00ebrgimin dhe zhvillimin p\u00ebrdorim TFS, nd\u00ebrsa aplikacionin e aktivizojm\u00eb n\u00eb serverin e aplikacioneve Linux, dhe nd\u00ebrmjet tyre ndodhin disa magji. Ky Magic Box<\/b> \u00ebsht\u00eb thelbi i pun\u00ebs s\u00eb ardhshme. Para se ta ndajm\u00eb at\u00eb n\u00eb pjes\u00eb, do t\u00eb b\u00ebj nj\u00eb hap m\u00ebnjan\u00eb dhe do t\u00eb them dy fjal\u00eb mbi aplikacionin.<\/p>\n

Projekti<\/h2>\n

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

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

Client<\/h3>\n

\nEkzistuan dy lloje p\u00ebrdoruesish. First<\/b> kishte akses duke u autorizuar me nj\u00eb certifikat\u00eb SSL SHA-2. T\u00eb\u00a0t\u00eb dyt\u00eb<\/b> kishte akses me emrin e p\u00ebrdoruesit dhe fjal\u00ebkalimin.<\/p>\n

HAProxy<\/h3>\n

\nM\u00eb pas, k\u00ebrkesa e klientit shkonte n\u00eb HAProxy, i cili zgjidhte detyrat e m\u00ebposhtme:<\/p>\n