{"id":52367,"date":"2019-11-07T00:00:00","date_gmt":"2019-11-06T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/pereshel-s-terraform-na-cloudformation-i-pozhalel"},"modified":"2020-02-18T14:00:04","modified_gmt":"2020-02-18T11:00:04","slug":"pereshel-s-terraform-na-cloudformation-i-pozhalel","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/pereshel-s-terraform-na-cloudformation-i-pozhalel","title":{"rendered":"Kalova nga Terraform n\u00eb CloudFormation \u2014 dhe e pash\u00eb se b\u00ebra gabim","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

T\u00eb paraqes\u00ebsh infrastruktur\u00ebn si kod n\u00eb nj\u00eb format tekstual t\u00eb rip\u00ebrs\u00ebritsh\u00ebm \u00ebsht\u00eb nj\u00eb praktik\u00eb e thjesht\u00eb dhe m\u00eb e mir\u00eb p\u00ebr sistemet, me t\u00eb cil\u00ebn nuk duhet t\u00eb merresh. Kjo praktik\u00eb ka marr\u00eb emrin \u2014 Infrastruktur\u00eb si Kod<\/a><\/noindex>, dhe deri m\u00eb tani, p\u00ebr ta realizuar at\u00eb, ve\u00e7an\u00ebrisht n\u00eb AWS, ekzistojn\u00eb dy mjete popullore: Terraform<\/a><\/noindex> dhe CloudFormation<\/a><\/noindex>.<\/p>\n

<\/p>\n

\"Kalova
\nPo krahason p\u00ebrvoj\u00ebn time me Terraform dhe CloudFormation<\/em><\/p>\n

<\/p>\n

Para se t\u00eb vija n\u00eb Twitch<\/a><\/noindex> (po ashtu Amazon Jr.<\/a><\/noindex>) kam punuar n\u00eb nj\u00eb startup<\/a><\/noindex> dhe p\u00ebr rreth tre vjet kam p\u00ebrdorur Terraform. N\u00eb vendin e ri, un\u00eb gjithashtu kam p\u00ebrdorur shum\u00eb Terraform, dhe m\u00eb pas kompania kaloi n\u00eb t\u00eb gjith\u00eb sistemin e Amazon, duke p\u00ebrfshir\u00eb CloudFormation. Un\u00eb punova me p\u00ebrkushtim p\u00ebr t\u00eb zhvilluar praktikat m\u00eb t\u00eb mira p\u00ebr t\u00eb dy ato, dhe p\u00ebrdorja t\u00eb dyja mjetet n\u00eb procese t\u00eb pun\u00ebs shum\u00eb t\u00eb komplikuara n\u00eb nivel organizate. M\u00eb von\u00eb, pas nj\u00eb vler\u00ebsimi t\u00eb kujdessh\u00ebm t\u00eb pasojave t\u00eb kalimit nga Terraform n\u00eb CloudFormation, arrita n\u00eb p\u00ebrfundimin se Terraform, ndoshta, \u00ebsht\u00eb zgjedhja m\u00eb e mir\u00eb p\u00ebr organizat\u00ebn.<\/p>\n

<\/a><\/noindex><\/p>\n

Terraform \u00ebsht\u00eb i tmerrsh\u00ebm<\/h2>\n

<\/p>\n

Beta-version e softuerit<\/h3>\n

<\/p>\n

Terraform ende nuk ka l\u00ebshuar as versionin 1.0, dhe kjo \u00ebsht\u00eb nj\u00eb arsye e fort\u00eb p\u00ebr ta mos p\u00ebrdorur. Q\u00eb nga hera e par\u00eb q\u00eb e provova, ka ndryshuar shum\u00eb, por at\u00ebher\u00eb terraform apply<\/code> shpesh prishtypte pas disa p\u00ebrdit\u00ebsimeve ose thjesht pas disa vjet\u00ebsh p\u00ebrdorimi. do t\u00eb thosha se \"tani gjith\u00e7ka \u00ebsht\u00eb ndryshe\", por... k\u00ebshtu duket se thon\u00eb t\u00eb gjith\u00eb, apo jo? Ka ndryshime, t\u00eb papajtueshme me versionet e m\u00ebparshme, megjith\u00ebse ato jan\u00eb t\u00eb arsyeshme, dhe madje ndjehet se sintaksa dhe abstraksionet e depozitave t\u00eb burimeve tani jan\u00eb aty ku duhet. Instrumenti duket se \u00ebsht\u00eb v\u00ebrtet b\u00ebr\u00eb m\u00eb i mir\u00eb, por... :-0<\/p>\n

<\/p>\n

Nga ana tjet\u00ebr, AWS ka b\u00ebr\u00eb nj\u00eb pun\u00eb t\u00eb mir\u00eb duke mb\u00ebshtetur pajtueshm\u00ebrin\u00eb me versionet e m\u00ebparshme. T\u00eb gjith\u00eb ndoshta p\u00ebr shkak se sh\u00ebrbimet e tyre shpesh testohen mir\u00eb brenda organizat\u00ebs dhe m\u00eb pas, pas rinaming, publikohen. Pra \"kan\u00eb b\u00ebr\u00eb mir\u00eb\" \u00ebsht\u00eb ende e paqart\u00eb p\u00ebr t\u00eb th\u00ebn\u00eb. T\u00eb mbash pajtueshm\u00ebrin\u00eb me versionet e m\u00ebparshme t\u00eb API-s\u00eb p\u00ebr nj\u00eb sistem kaq t\u00eb shum\u00ebllojsh\u00ebm dhe kompleks si AWS \u00ebsht\u00eb jasht\u00ebzakonisht e v\u00ebshtir\u00eb. \u00c7dokush q\u00eb ka pasur p\u00ebrvoj\u00eb n\u00eb mbajtjen e API-ve publike, t\u00eb p\u00ebrdorura gjithashtu kaq gjer\u00ebsisht, duhet t\u00eb kuptoj\u00eb se sa e v\u00ebshtir\u00eb \u00ebsht\u00eb t\u00eb b\u00ebsh k\u00ebt\u00eb p\u00ebr kaq shum\u00eb vite. E megjithat\u00eb, sjellja e CloudFormation nuk ka ndryshuar asnj\u00ebher\u00eb p\u00ebr aq sa e mbaj mend.<\/p>\n

<\/p>\n

Njoftohu, k\u00ebmb\u00eb... kjo \u00ebsht\u00eb nj\u00eb plumb<\/h3>\n

<\/p>\n

Sa di un\u00eb, p\u00ebr t\u00eb fshir\u00eb nj\u00eb burim t\u00eb jashtme<\/strong> Nj\u00eb stek CloudFormation nuk mund t\u00eb importohet nga steku im CF. Situata \u00ebsht\u00eb e ngjashme me Terraform. Ai lejon importimin e burimeve ekzistuese n\u00eb stekun tuaj. Funksioni, mund t\u00eb thuhet, \u00ebsht\u00eb mahnit\u00ebs, por me nj\u00eb forc\u00eb t\u00eb madhe vjen edhe nj\u00eb p\u00ebrgjegj\u00ebsi e madhe. Sapo t\u00eb shtosh nj\u00eb burim n\u00eb stek, gjat\u00eb koh\u00ebs q\u00eb punon me stekun t\u00ebnd, nuk mund ta fshish ose ndryshosh at\u00eb burim. Nj\u00eb her\u00eb kjo kishte pasoja. Disa her\u00eb n\u00eb faqen e Twitch, dikush, pa ndonj\u00eb q\u00ebllim t\u00eb keq, rast\u00ebsisht importoi nj\u00eb grup sigurie AWS n\u00eb stekun e tij Terraform. E futi disa komanda dhe... grupi i siguris\u00eb (bashk\u00eb me trafikun e ardhsh\u00ebm) zhduku.<\/p>\n

<\/p>\n

Terraform i Madh<\/h2>\n

<\/p>\n

Rikuperimi nga gjendje t\u00eb paplota<\/h3>\n

<\/p>\n

Ndonj\u00ebher\u00eb CloudFormation nuk mund t\u00eb kaloj\u00eb plot\u00ebsisht nga nj\u00eb gjendje n\u00eb tjet\u00ebr. P\u00ebrs\u00ebri do t\u00eb p\u00ebrpiqet t\u00eb kthehet n\u00eb gjendjen e m\u00ebparshme. Fatkeq\u00ebsisht, kjo nuk \u00ebsht\u00eb gjithmon\u00eb e mundur. T\u00eb rikuperosh at\u00eb q\u00eb \u00ebsht\u00eb shkat\u00ebrruar mund t\u00eb jet\u00eb frik\u00ebsuese \u2014 kurr\u00eb nuk e di n\u00ebse CloudFormation do t\u00eb g\u00ebzohet q\u00eb e thyejn\u00eb at\u00eb \u2014 edhe n\u00ebse \u00ebsht\u00eb p\u00ebr ta riparuar. Ai nuk di t\u00eb p\u00ebrcaktoj\u00eb n\u00ebse do t\u00eb kthehet apo jo n\u00eb gjendjen e m\u00ebparshme dhe si rregull ngec p\u00ebr or\u00eb, duke pritur nj\u00eb mrekulli.<\/p>\n

<\/p>\n

Terraform, nga ana tjet\u00ebr, ka prirjen t\u00eb rikuperohet pas kalimeve t\u00eb d\u00ebshtuara n\u00eb nj\u00eb m\u00ebnyr\u00eb m\u00eb t\u00eb eleganteshme dhe ofron nj\u00eb set t\u00eb zgjeruar alat\u00ebsh p\u00ebr debug.<\/p>\n

<\/p>\n

Ndryshime m\u00eb t\u00eb qarta n\u00eb gjendjet e dokumentit<\/h3>\n

<\/p>\n

\"B mir\u00eb, balancuesi i ngarkes\u00ebs, po ndryshon. Por si?\"<\/p>\n

\u2014inxhinier i shqet\u00ebsuar, i gatsh\u00ebm p\u00ebr t\u00eb shtypur butonin \"prano\".<\/p><\/blockquote>\n

Ndonj\u00ebher\u00eb m\u00eb nevojitet t\u00eb b\u00ebj disa manovra me balancuesin e ngarkes\u00ebs n\u00eb stekun CloudFormation \u2014 p\u00ebr shembull, t\u00eb shtoj numrin e portit ose t\u00eb ndryshoj grupin e siguris\u00eb. Ndryshimet ClouFormation i tregon dob\u00ebt. Un\u00eb, si n\u00eb gjilp\u00ebra, kontrolloj dhjet\u00eb her\u00eb skedarin yaml, p\u00ebr t'u siguruar q\u00eb nuk kam fshier asgj\u00eb t\u00eb nevojshme dhe as nuk kam shtuar di\u00e7ka t\u00eb tep\u00ebrt.<\/p>\n

<\/p>\n

Terraform n\u00eb k\u00ebt\u00eb drejtim \u00ebsht\u00eb shum\u00eb m\u00eb transparent. Ndonj\u00ebher\u00eb ai madje \u00ebsht\u00eb tep\u00ebr transparent (lexo: bezdissh\u00ebm). Fatmir\u00ebsisht, n\u00eb versionin e fundit u p\u00ebrfshi nj\u00eb p\u00ebrmir\u00ebsim n\u00eb paraqitjen e ndryshimeve - tani \u00ebsht\u00eb e qart\u00eb se \u00e7far\u00eb ndryshon.<\/p>\n

<\/p>\n

Fleksibiliteti<\/h3>\n

<\/p>\n

Shkruani softuerin nga prapavija.<\/p><\/blockquote>\n

Duke folur ndersh\u00ebm, dallimi m\u00eb i r\u00ebnd\u00ebsish\u00ebm i softuerit q\u00eb q\u00ebndron p\u00ebr nj\u00eb koh\u00eb t\u00eb gjat\u00eb \u00ebsht\u00eb aft\u00ebsia p\u00ebr t'u p\u00ebrshtatur me ndryshimet. \u00c7do softuer shkruani nga e kund\u00ebrta. M\u00eb shpesh kam gabuar n\u00eb at\u00eb q\u00eb kam marr\u00eb nj\u00eb sh\u00ebrbim \"t\u00eb thjesht\u00eb\" dhe pastaj filloja t\u00eb futja gjith\u00e7ka n\u00eb nj\u00eb stek t\u00eb vet\u00ebm CloudFormation ose Terraform. Dhe nj\u00eblloj, pas disa muajsh doli n\u00eb pah se un\u00eb e kuptova t\u00eb gjith\u00eb ndryshe, dhe sh\u00ebrbimi n\u00eb fakt nuk ishte i thjesht\u00eb! Dhe tani duhet t\u00eb ndara ndonj\u00eb m\u00ebnyr\u00eb stekun e madh n\u00eb pjes\u00ebt e vogla. Kur punoni me CloudFormation, kjo \u00ebsht\u00eb e mundur vet\u00ebm pasi t\u00eb riprodhoni stekun ekzistues, dhe un\u00eb, me bazat e t\u00eb dh\u00ebnave t\u00eb mia, nuk b\u00ebj k\u00ebt\u00eb. Terraformi lejonte ndarjen e stekut dhe p\u00ebrb\u00ebrjen e tij n\u00eb pjes\u00eb m\u00eb t\u00eb vogla dhe m\u00eb t\u00eb kuptueshme.<\/p>\n

<\/p>\n

Modulet n\u00eb git<\/h3>\n

<\/p>\n

T\u00eb ndash kodin Terraform nd\u00ebrmjet shum\u00eb stivave \u00ebsht\u00eb shum\u00eb m\u00eb e leht\u00eb sesa me kodin CloudFormation. Me Terraform mund t\u00eb vendosni kodin n\u00eb nj\u00eb depo git dhe ta referoni at\u00eb duke p\u00ebrdorur kontrollin semantik t\u00eb versioneve. Cilido q\u00eb ka akses n\u00eb k\u00ebt\u00eb depo mund ta p\u00ebrdor\u00eb s\u00ebrish kodin e p\u00ebrbashk\u00ebt. Ekuivalenti n\u00eb CloudFormation \u00ebsht\u00eb S3, por ai nuk ka t\u00eb nj\u00ebjtat avantazhe dhe nuk ka asnj\u00eb arsye p\u00ebr t\u00eb cil\u00ebn do t\u00eb duhej t\u00eb heqim dor\u00eb nga git n\u00eb favor t\u00eb S3.<\/p>\n

<\/p>\n

Organizata po rritej dhe aft\u00ebsia p\u00ebr t\u00eb ndar\u00eb stivat e p\u00ebrbashk\u00ebta arriti nivelin kritik. Me Terraform, kjo ndodh leht\u00ebsisht dhe natyrsh\u00ebm, nd\u00ebrsa CloudFormation do t'ju detyroj\u00eb t\u00eb kaloni disa ringa p\u00ebrpara se t\u00eb arrini di\u00e7ka t\u00eb ngjashme.<\/p>\n

<\/p>\n

Operacione si kod<\/h3>\n

<\/p>\n

\"T\u00eb scriptuara dhe mjaft\".<\/p>\n

\u2014inzhinieri 3 vjet para se t\u00eb shpik\u00eb bi\u00e7iklet\u00ebn Terraform.<\/p><\/blockquote>\n

Kur b\u00ebhet fjal\u00eb p\u00ebr zhvillimin e softuerit, Go ose nj\u00eb program n\u00eb Java nuk \u00ebsht\u00eb vet\u00ebm kod.<\/p>\n

<\/p>\n

\"Kalova
\nKod si Kod<\/em><\/p>\n

<\/p>\n

Sepse ka edhe infrastruktur\u00ebn n\u00eb t\u00eb cil\u00ebn ajo punon.<\/p>\n

<\/p>\n

\"Kalova
\nInfrastruktur\u00eb si Kod<\/em><\/p>\n

<\/p>\n

Por nga vjen ajo aty? Si e monitoroni? Ku \u00ebsht\u00eb kodi juaj? A kan\u00eb nevoj\u00eb zhvilluesit p\u00ebr leje p\u00ebr akses?<\/p>\n

<\/p>\n

\"Kalova
\nOperacione si Kod<\/em><\/p>\n

<\/p>\n

T\u00eb jesh zhvillues i softuerit nuk \u00ebsht\u00eb vet\u00ebm t\u00eb shkruash kod.<\/p><\/blockquote>\n

Jo vet\u00ebm AWS: sigurisht q\u00eb po p\u00ebrdorni sh\u00ebrbime nga ofrues t\u00eb tjer\u00eb. SignalFx, PagerDuty ose Github. Ndoshta keni nj\u00eb server t\u00eb brendsh\u00ebm Jenkins p\u00ebr CI\/CD ose nj\u00eb panel t\u00eb brendsh\u00ebm Grafana p\u00ebr monitorim. Infrastruktur\u00eb si Kod zgjidhet p\u00ebr arsye t\u00eb ndryshme, dhe \u00e7do arsyetim \u00ebsht\u00eb po aq i r\u00ebnd\u00ebsish\u00ebm p\u00ebr \u00e7do gj\u00eb q\u00eb lidhet me softuerin.<\/p>\n

<\/p>\n

Kur punoja n\u00eb Twitch, ne shpejtonim sh\u00ebrbimet brenda sistemeve t\u00eb p\u00ebrziera t\u00eb integruara dhe sistemeve t\u00eb AWS Amazon. Ne marksim dhe mb\u00ebshtesim shum\u00eb mikrosisteme, duke rritur shpenzimet operuese. Diskutimet ndodhnin rreth k\u00ebsaj tema:<\/p>\n

<\/p>\n