{"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":"U kalova nga Terraform n\u00eb CloudFormation \u2014 dhe u pendova","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Paraqitja e infrastruktur\u00ebs si kod n\u00eb nj\u00eb format tekstual t\u00eb rip\u00ebrs\u00ebritsh\u00ebm \u00ebsht\u00eb nj\u00eb praktik\u00eb e thjesht\u00eb m\u00eb e mir\u00eb p\u00ebr sistemet, me t\u00eb cil\u00ebn nuk \u00ebsht\u00eb nevoja t\u00eb lodhesh. Kjo praktik\u00eb ka marr\u00eb emrin \u2014 Infrastruktura si Kod<\/a><\/noindex>, dhe deri m\u00eb tani p\u00ebr realizimin e saj, ve\u00e7an\u00ebrisht n\u00eb AWS, ka dy mjete t\u00eb njohura: Terraform<\/a><\/noindex> dhe CloudFormation<\/a><\/noindex>.<\/p>\n

<\/p>\n

\"U
\nPo e krahasoni p\u00ebrvoj\u00ebn time me Terraform dhe CloudFormation<\/em><\/p>\n

<\/p>\n

Para se t\u00eb vija n\u00eb Twitch<\/a><\/noindex> (n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb Amazon Jr.<\/a><\/noindex>) kam punuar n\u00eb nj\u00eb startup<\/a><\/noindex> dhe p\u00ebr tre vjet kam p\u00ebrdorur Terraform. N\u00eb vendin e ri un\u00eb gjithashtu e kam p\u00ebrdorur Terraform, pastaj kompania e kaloi n\u00eb nj\u00eb form\u00eb t\u00eb gjitha p\u00ebr AWS, duke p\u00ebrfshir\u00eb CloudFormation. Un\u00eb kam punuar me p\u00ebrkushtim p\u00ebr t\u00eb zhvilluar praktikat m\u00eb t\u00eb mira p\u00ebr t\u00eb dy, dhe t\u00eb dy mjetet i kam p\u00ebrdorur n\u00eb procese t\u00eb pun\u00ebs tep\u00ebr t\u00eb komplikuara n\u00eb shkall\u00eb organizative. M\u00eb von\u00eb, pas nj\u00eb vler\u00ebsimi t\u00eb kujdessh\u00ebm t\u00eb pasojave t\u00eb kalimit nga Terraform n\u00eb CloudFormation, kam konstatruar se Terraform, ndoshta, \u00ebsht\u00eb zgjedhja m\u00eb e mir\u00eb p\u00ebr organizat\u00ebn.<\/p>\n

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

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

<\/p>\n

Versioni Beta i Software-it<\/h3>\n

<\/p>\n

Terraform ende nuk ka l\u00ebshuar versionin 1.0, dhe kjo \u00ebsht\u00eb nj\u00eb arsye e fort\u00eb p\u00ebr t\u00eb mos e p\u00ebrdorur. Q\u00eb nga koha kur e kam provuar p\u00ebr her\u00eb t\u00eb par\u00eb, ka ndryshuar shum\u00eb, por at\u00ebher\u00eb terraform apply<\/code> kaq\u00eb shpesh prishej pas disa p\u00ebrdit\u00ebsimesh ose thjesht pas disa viteve p\u00ebrdorimi. Do thosha se \"tani gjith\u00e7ka \u00ebsht\u00eb ndryshe\", por\u2026 k\u00ebshtu duket se t\u00eb gjith\u00eb flasin, apo jo? Ka ndryshime q\u00eb jan\u00eb t\u00eb papajtueshme me versionet e m\u00ebparshme, megjithat\u00eb jan\u00eb t\u00eb arsyeshme, madje ka nj\u00eb ndjesi se sintaksat dhe abstraksionet e depozitave t\u00eb burimeve tani jan\u00eb n\u00eb rregull. Instrumenti duket si\u00e7 n\u00eb t\u00eb v\u00ebrtet\u00eb \u00ebsht\u00eb p\u00ebrmir\u00ebsuar, por\u2026 :-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 e din\u00eb se sh\u00ebrbimet e tyre shpesh testohen mir\u00eb brenda organizat\u00ebs dhe vet\u00ebm pastaj, pasi jan\u00eb rinovuar, publikohen. Pra, \"kan\u00eb b\u00ebr\u00eb nj\u00eb pun\u00eb t\u00eb mir\u00eb\" \u00ebsht\u00eb pak sa e n\u00ebnkuptuar. T\u00eb mbash pajtueshm\u00ebrin\u00eb me versionet e m\u00ebparshme t\u00eb API p\u00ebr nj\u00eb sistem kaq t\u00eb larmish\u00ebm dhe t\u00eb nd\u00ebrlikuar si AWS \u00ebsht\u00eb jasht\u00ebzakonisht e v\u00ebshtir\u00eb. \u00c7do kush q\u00eb ka pasur p\u00ebrvoj\u00eb n\u00eb mbajtjen e API-ve publike, q\u00eb p\u00ebrdoren gjithashtu aq gjer\u00eb, duhet t\u00eb kuptoj\u00eb sa e v\u00ebshtir\u00eb \u00ebsht\u00eb ta b\u00ebsh k\u00ebt\u00eb p\u00ebr kaq shum\u00eb vite. Nd\u00ebrkoh\u00eb, sjellja e CloudFormation nuk ka ndryshuar asnj\u00ebher\u00eb p\u00ebr mua gjat\u00eb viteve.<\/p>\n

<\/p>\n

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

<\/p>\n

Sa di un\u00eb, t\u00eb fshish nj\u00eb burim t\u00eb jasht\u00ebm<\/strong> Nuk \u00ebsht\u00eb e mundur t\u00eb eksportoni nj\u00eb grup CloudFormation nga steka juaj CF. Rreth k\u00ebsaj situate jan\u00eb gj\u00ebrat me Terraform. Ai lejon importimin e burimeve ekzistuese n\u00eb stek\u00eb. Funksioni \u00ebsht\u00eb, mund t\u00eb thuhet, mbres\u00ebl\u00ebn\u00ebs, por me forc\u00eb t\u00eb madhe vjen edhe nj\u00eb p\u00ebrgjegj\u00ebsi e madhe. Sa her\u00eb q\u00eb e futni nj\u00eb burim n\u00eb stek, nd\u00ebrkoh\u00eb q\u00eb punoni me stekun tuaj, nuk mund ta fshini ose ta ndryshoni at\u00eb burim. Nj\u00eb her\u00eb, kjo ndodhi. Ndodhi q\u00eb n\u00eb faqen e Twitch dikush, pa ndonj\u00eb q\u00ebllim t\u00eb keq, p\u00ebrfundoi duke importuar grupin e siguris\u00eb s\u00eb dikujt n\u00eb stekun e tij Terraform. Fut disa komanda dhe... grupi i siguris\u00eb (n\u00eb bashk\u00ebpunim me trafikun e hyr\u00ebs) u zhduk.<\/p>\n

<\/p>\n

Terraform i Madh<\/h2>\n

<\/p>\n

Ribashkimi nga gjendjet e paplota<\/h3>\n

<\/p>\n

Ndonj\u00ebher\u00eb CloudFormation nuk mund t\u00eb kaloj\u00eb plot\u00ebsisht nga nj\u00eb gjendje n\u00eb nj\u00eb tjet\u00ebr. N\u00eb k\u00ebt\u00eb rast, ai do t\u00eb p\u00ebrpiqet t\u00eb rikthehet n\u00eb gjendjen e m\u00ebparshme. E trishtueshme, kjo nuk \u00ebsht\u00eb gjithmon\u00eb e mundur. T\u00eb riparosh at\u00eb q\u00eb rezulton, ndonj\u00ebher\u00eb \u00ebsht\u00eb frik\u00ebsuese - nuk dihet se si do ta pranoj\u00eb CloudFormation q\u00eb e ndjekin - ndon\u00ebse p\u00ebr t\u00eb p\u00ebrmir\u00ebsuar. N\u00ebse do t\u00eb jet\u00eb e mundur t\u00eb ktheheni n\u00eb gjendjen e m\u00ebparshme, ai nuk di ta p\u00ebrcaktoj\u00eb mir\u00eb dhe p\u00ebr default mund t\u00eb pres\u00eb p\u00ebr or\u00eb t\u00eb t\u00ebra p\u00ebr nj\u00eb mrekulli.<\/p>\n

<\/p>\n

Terraform, p\u00ebrkundrazi, \u00ebsht\u00eb m\u00eb i aft\u00eb t\u00eb rikuperohet pas kalimeve t\u00eb d\u00ebshtuara dhe ofron nj\u00eb grup t\u00eb p\u00ebrmir\u00ebsuar mjetesh debugimi.<\/p>\n

<\/p>\n

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

<\/p>\n

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

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

Ndonj\u00ebher\u00eb kam nevoj\u00eb t\u00eb b\u00ebj disa manipulime me balancuesin e ngarkes\u00ebs n\u00eb stekun CloudFormation - p\u00ebr shembull, t\u00eb shtoj numrin e portit ose t\u00eb ndryshoj grupin e siguris\u00eb. ClouFormation ndryshimet i tregon dob\u00ebt. Nd\u00ebrsa un\u00eb, si n\u00eb thik\u00eb, po e kontrolloj skedarin yaml nga dhjet\u00eb her\u00eb p\u00ebr t\u00eb siguruar q\u00eb asgj\u00eb e nevojshme nuk e kam fshir\u00eb, e as q\u00eb 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 \u00ebsht\u00eb madje shum\u00eb transparent (lexo: i bezdissh\u00ebm). P\u00ebr fat t\u00eb mir\u00eb, n\u00eb versionin m\u00eb t\u00eb fundit u p\u00ebrfshi nj\u00eb p\u00ebrmir\u00ebsim i paraqitjes s\u00eb ndryshimeve - tani shihet sakt\u00ebsisht se \u00e7far\u00eb po ndryshon.<\/p>\n

<\/p>\n

Fleksibiliteti<\/h3>\n

<\/p>\n

Shkruani softuer nga e kund\u00ebrta.<\/p><\/blockquote>\n

P\u00ebr t\u00eb th\u00ebn\u00eb drejtp\u00ebrdrejt, karakteristika m\u00eb e r\u00ebnd\u00ebsishme e softuerit me jet\u00ebgjat\u00ebsi \u00ebsht\u00eb aft\u00ebsia p\u00ebr t'u adaptuar n\u00eb ndryshime. \u00c7do softuer shkruani nga prapavija. Un\u00eb shpesh m\u00eb ka ndodhur q\u00eb t\u00eb marr nj\u00eb sh\u00ebrbim \"t\u00eb thjesht\u00eb\", dhe pastaj t\u00eb filloj t\u00eb p\u00ebrpiqem ta fus t\u00eb gjith\u00eb at\u00eb n\u00eb nj\u00eb stek t\u00eb vet\u00ebm CloudFormation ose Terraform. Dhe, padyshim, pas disa muajsh ishte zbuluar se un\u00eb nuk e kisha kuptuar si\u00e7 duhet, dhe sh\u00ebrbimi do ishte n\u00eb t\u00eb v\u00ebrtet\u00eb jo aq i thjesht\u00eb! Dhe k\u00ebshtu m\u00eb duhej ta \u00e7'montoj stekun e madh n\u00eb pjes\u00eb m\u00eb t\u00eb vogla. Kur punoni me CloudFormation, kjo \u00ebsht\u00eb e mundur vet\u00ebm n\u00ebse e rikrijoni p\u00ebrpara stekun ekzistues, gj\u00eb q\u00eb un\u00eb me bazat e mia t\u00eb t\u00eb dh\u00ebnave nuk e b\u00ebj. Terraform m\u00eb lejonte t\u00eb shk\u00ebputja stekun dhe ta ndaja at\u00eb 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 e Terraform-it midis grumbujve t\u00eb shumt\u00eb \u00ebsht\u00eb ndjesh\u00ebm m\u00eb e leht\u00eb se sa me kodin e CloudFormation. Me Terraform mund t\u00eb vendos\u00ebsh kodin n\u00eb nj\u00eb depo git dhe t\u00eb aksesosh at\u00eb duke p\u00ebrdorur kontrollin semantik t\u00eb versioneve. \u00c7do kush q\u00eb ka akses n\u00eb k\u00ebt\u00eb depo mund ta rip\u00ebrdor\u00eb kodin e zakonsh\u00ebm. Ekuivalenti n\u00eb CloudFormation \u00ebsht\u00eb S3, por nuk ka t\u00eb nj\u00ebjtin avantazh dhe nuk ka asnj\u00eb arsye p\u00ebr t\u00eb cil\u00ebn duhet 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 grumbujt e p\u00ebrbashk\u00ebt arriti nj\u00eb nivel kritik. Me Terraform, gjith\u00e7ka \u00ebsht\u00eb e leht\u00eb dhe natyrale, nd\u00ebrsa CloudFormation do t'ju nxiste t\u00eb luanit me disa rrethana p\u00ebrpara se t\u00eb arrini n\u00eb nj\u00eb rezultat t\u00eb ngjash\u00ebm.<\/p>\n

<\/p>\n

Operacione si kod<\/h3>\n

<\/p>\n

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

\u2014 inxhinier tre vjet p\u00ebrpara se t\u00eb shpik\u00eb bi\u00e7iklet\u00ebn Terraform.<\/p><\/blockquote>\n

Kur \u00ebsht\u00eb fjala p\u00ebr zhvillimin e softuerit, Go ose nj\u00eb program n\u00eb Java nuk jan\u00eb thjesht kod.<\/p>\n

<\/p>\n

\"U
\nKode si Kod<\/em><\/p>\n

<\/p>\n

Megjithat\u00eb, ekziston edhe infrastrukturen n\u00eb t\u00eb cil\u00ebn funksionon ajo.<\/p>\n

<\/p>\n

\"U
\nInfrastruktura si Kod<\/em><\/p>\n

<\/p>\n

Por nga e di ajo atje? Si ta monitorosh? Ku q\u00ebndron kodi yt? A kan\u00eb nevoj\u00eb zhvilluesit p\u00ebr leje p\u00ebr akses?<\/p>\n

<\/p>\n

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

<\/p>\n

T\u00eb jesh zhvillues i softuerit nuk \u00ebsht\u00eb thjesht nj\u00eb pun\u00eb kodimi.<\/p><\/blockquote>\n

Nuk \u00ebsht\u00eb vet\u00ebm AWS: sigurisht q\u00eb ju po p\u00ebrdorni sh\u00ebrbimet e ofruesve 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 kontrolli Grafana p\u00ebr monitorim. Infra si Kod zgjidhet p\u00ebr arsye t\u00eb ndryshme, dhe \u00e7do arsye \u00ebsht\u00eb po aq e r\u00ebnd\u00ebsishme 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 dhe sistemeve t\u00eb AWS Amazon. Ne krijonim dhe mb\u00ebshtetnim shum\u00eb mikrosherbime, duke rritur kostot e operacioneve. Diskutimet kalonin kryesisht k\u00ebshtu:<\/p>\n

<\/p>\n