{"id":80289,"date":"2020-05-05T01:42:36","date_gmt":"2020-05-04T23:42:36","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/ansible-migracziya-konfiguraczii-120-vm-c-coreos-na-centos-za-18-mesyaczev"},"modified":"2020-05-05T01:42:36","modified_gmt":"2020-05-04T23:42:36","slug":"ansible-migracziya-konfiguraczii-120-vm-c-coreos-na-centos-za-18-mesyaczev","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/ansible-migracziya-konfiguraczii-120-vm-c-coreos-na-centos-za-18-mesyaczev","title":{"rendered":"Ansible: Migrimi i konfiguracionit t\u00eb 120 VM nga CoreOS n\u00eb CentOS brenda 18 muajve","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Ansible:<\/p>\n

<\/p>\n

Kjo \u00ebsht\u00eb transcripti i fjalimit n\u00eb DevopsConf 2019-10-01<\/a><\/noindex> dhe SPbLUG 2019-09-25<\/a><\/noindex>.<\/p>\n

<\/p>\n

Kjo \u00ebsht\u00eb historia e projektit, ku u p\u00ebrdor nj\u00eb sistem i personalizuar p\u00ebr menaxhimin e konfiguracioneve dhe pse kalimi n\u00eb Ansible zgjati 18 muaj.<\/p>\n

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

Dita \u2116 -XXX: Para fillimit<\/h2>\n

<\/p>\n

\"Ansible:<\/p>\n

<\/p>\n

Fillimisht infrastruktura p\u00ebrb\u00ebhej nga shum\u00eb hoste t\u00eb ve\u00e7anta n\u00ebn menaxhimin e Hyper-V. Krijimi i nj\u00eb makine virtuale k\u00ebrkonte shum\u00eb veprime: vendosjen e disqeve n\u00eb vendin e duhur, konfigurimin e DNS, rezervimin e DHCP, vendosjen e konfiguracionit t\u00eb VM n\u00eb nj\u00eb depo git. Ky proces ishte pjes\u00ebrisht mekanizuar, por p\u00ebr shembull, VM-t\u00eb shp\u00ebrndaheshin mes hosteve me duar. Megjithat\u00eb, zhvilluesit mund t\u00eb aplikonin ndryshimet n\u00eb konfiguracionin e VM n\u00eb git duke e rib\u00ebr\u00eb at\u00eb pas nj\u00eb rindezjeje t\u00eb VM.<\/p>\n

<\/p>\n

Zgjidhje e Personalizuar p\u00ebr Menaxhimin e Konfiguracioneve<\/h3>\n

<\/p>\n

\"Ansible:<\/p>\n

<\/p>\n

Ideja fillestare, besoj, ishte menduar si IaC: shum\u00eb VM stateless, t\u00eb cilat pas rindezjes resetonin gjendjen e tyre. \u00c7far\u00eb p\u00ebrfshinte menaxhimi i konfiguracioneve t\u00eb VM? Duket e thjesht\u00eb n\u00eb katror:<\/p>\n

<\/p>\n

    \n
  1. P\u00ebr VM-t\u00eb ishte vendosur MAC statik.<\/li>\n
  2. VM-t\u00eb ishin lidhur me ISO me CoreOS dhe diskun e ngarkes\u00ebs.<\/li>\n
  3. CoreOS ekzekuton skripti i personalizimit duke e shkarkuar at\u00eb nga serveri WEB n\u00eb baz\u00eb t\u00eb IP-s\u00eb s\u00eb tij.<\/li>\n
  4. Skripti shkarkon p\u00ebrmes SCP konfigurimin e VM duke u bazuar n\u00eb adres\u00ebn IP.<\/li>\n
  5. Aktivizohet nj\u00eb s\u00ebr\u00eb skedar\u00ebsh unit systemd dhe nj\u00eb s\u00ebr\u00eb skriptesh bash.<\/li>\n<\/ol>\n

    <\/p>\n

    \"Ansible:<\/p>\n

    <\/p>\n

    Ky zgjidhje kishte shum\u00eb probleme t\u00eb dukshme:<\/p>\n

    <\/p>\n

      \n
    1. ISO n\u00eb CoreOS ishte e hequr.<\/li>\n
    2. Shum\u00eb veprime t\u00eb komplikuara automatizimi dhe magji gjat\u00eb migrimit\/krijimit t\u00eb VM.<\/li>\n
    3. V\u00ebshtir\u00ebsi me p\u00ebrdit\u00ebsimin dhe kur k\u00ebrkohej nj\u00eb version i caktuar t\u00eb softuerit. Akoma m\u00eb arg\u00ebtuese me modulet e b\u00ebrtham\u00ebs.<\/li>\n
    4. VM-t\u00eb nuk rezultonin aq t\u00eb pa t\u00eb dh\u00ebna, dmth. u shfaq\u00ebn VM me nj\u00eb disk t\u00eb montuar me t\u00eb dh\u00ebna p\u00ebrdoruesi p\u00ebrve\u00e7.<\/li>\n
    5. Dikush gjithmon\u00eb gabonte me var\u00ebsit\u00eb e unit systemd dhe n\u00eb ri-nisjen CoreOS ngadal\u00ebsohej. Ishte problem p\u00ebr t\u00eb zbuluar k\u00ebt\u00eb me mjetet ekzistuese n\u00eb CoreOS.<\/li>\n
    6. Menaxhimi i sekreteve.<\/li>\n
    7. CM nuk ekzistonte faktikisht. Kishim bash dhe konfigurimet YML t\u00eb CoreOS.<\/li>\n<\/ol>\n

      <\/p>\n

      P\u00ebr t\u00eb aplikuar konfigurimin e VM-s\u00eb duhet ta ri-nisim, por ajo mund t\u00eb mos ri-niset. Megjith\u00ebse dukej si nj\u00eb problem i duksh\u00ebm, nuk kishte disqe persistente - nuk kishte ku t\u00eb ruheshin log-et. Po mire, le t\u00eb p\u00ebrpiqemi t\u00eb shtojm\u00eb opsionet e ngarkimit t\u00eb b\u00ebrtham\u00ebs p\u00ebr t\u00eb d\u00ebrguar log-et. Por jo, sa e v\u00ebshtir\u00eb \u00ebsht\u00eb gjith\u00e7ka.<\/p>\n

      <\/p>\n

      Dita e par\u00eb: Pranimi i problemit<\/h2>\n

      <\/p>\n

      \"Ansible:<\/p>\n

      <\/p>\n

      Ishte nj\u00eb infrastruktur\u00eb e zakonshme zhvillimi: jenkins, mjedise testimi, monitorime, registry. CoreOS ishte menduar p\u00ebr hostimin e klastereve k8s, dometh\u00ebn\u00eb, problemi ishte se si p\u00ebrdorej CoreOS. Hapi i par\u00eb ishte se\u00e7ja e stek\u00ebs. Ne vendos\u00ebm p\u00ebr:<\/p>\n

      <\/p>\n

        \n
      1. CentOS<\/strong> si distribucionin baz\u00eb, pasi \u00ebsht\u00eb distribucioni m\u00eb i af\u00ebrt me mjediset e prodhimit.<\/li>\n
      2. Ansible<\/strong> p\u00ebr menaxhimin e konfiguracioneve, pasi kishte nj\u00eb ekspertiz\u00eb t\u00eb gjer\u00eb.<\/li>\n
      3. Jenkins<\/strong> si nj\u00eb korniz\u00eb automatizimi t\u00eb proceseve ekzistuese, pasi ishte p\u00ebrdorur tashm\u00eb aktivisht p\u00ebr proceset e zhvillimit.<\/li>\n
      4. Hyper-V<\/strong> si platform\u00eb virtualizimi. Ka disa arsye q\u00eb shkojn\u00eb p\u00ebrtej tregimit, por n\u00eb m\u00ebnyr\u00eb t\u00eb shkurt\u00ebr \u2014 ne nuk mund t\u00eb p\u00ebrdorim cloud, duhet t\u00eb p\u00ebrdorim hardware-in ton\u00eb.<\/li>\n<\/ol>\n

        <\/p>\n

        Dita \u211630: Fiksimi i marr\u00ebveshjeve ekzistuese \u2014 Agreements as Code<\/h3>\n

        <\/p>\n

        \"Ansible:<\/p>\n

        <\/p>\n

        Kur u kuptua steka, filloi p\u00ebrgatitja p\u00ebr kalimin. Fiksimi i marr\u00ebveshjeve ekzistuese n\u00eb form\u00ebn e kodit (Agreements as Code<\/strong>!). Kalimi pun\u00eb parap\u00ebrgatitore<\/em> -> mekanizimi<\/em> -> automatizimi<\/em>.<\/p>\n

        <\/p>\n

        1. Konfiguroni VM-t\u00eb<\/h4>\n

        <\/p>\n

        \"Ansible:<\/p>\n

        <\/p>\n

        Ansible e menaxhon k\u00ebt\u00eb detyr\u00eb shum\u00eb mir\u00eb. Me pak p\u00ebrpjekje, mund t\u00eb nxjerrim n\u00ebn kontroll konfiguracionet e VM-ve:<\/p>\n

        <\/p>\n

          \n
        1. Krijoni nj\u00eb repozitor git.<\/li>\n
        2. Krijtojm\u00eb list\u00ebn e VM-ve n\u00eb inventory, konfigurimet n\u00eb playbooks dhe role.<\/li>\n
        3. Konfigurojm\u00eb nj\u00eb slave t\u00eb ve\u00e7ant\u00eb t\u00eb jenkins nga i cili mund t\u00eb ekzekutojm\u00eb ansible.<\/li>\n
        4. Krijojm\u00eb nj\u00eb pun\u00eb, konfigurojm\u00eb Jenkins.<\/li>\n<\/ol>\n

          <\/p>\n

          Procesi i par\u00eb \u00ebsht\u00eb gati. Marr\u00ebveshjet jan\u00eb fixuar.<\/p>\n

          <\/p>\n

          2. Krijo VM t\u00eb re<\/h4>\n

          <\/p>\n

          \"Ansible:<\/p>\n

          <\/p>\n

          Isha paksa i pak\u00ebnaqur. Nga Linux nuk ishte shum\u00eb e leht\u00eb t\u00eb krijoheshin VM n\u00eb Hyper-V. Nj\u00eb nga p\u00ebrpjekjet p\u00ebr t\u00eb mekanizuar k\u00ebt\u00eb proces ishte:<\/p>\n

          <\/p>\n

            \n
          1. Ansible lidhet p\u00ebrmes WinRM me hostin windows.<\/li>\n
          2. Ansible ekzekuton skenarin powershell.<\/li>\n
          3. Skenari powershell krijon nj\u00eb VM t\u00eb re.<\/li>\n
          4. Me mjetet Hyper-V\/ScVMM gjat\u00eb krijimit t\u00eb VM-s\u00eb n\u00eb sistemin e ftuar, konfigurohet hostname.<\/li>\n
          5. VM-ja, gjat\u00eb p\u00ebrdit\u00ebsimit t\u00eb DHCP lease, d\u00ebrgon hostname-n e saj.<\/li>\n
          6. Integrimi i standardizuar i ddns & dhcp n\u00eb an\u00ebn e Domain Controller konfiguron regjistrimin DNS.<\/li>\n
          7. Mund t\u00eb shtoni VM n\u00eb inventory dhe ta konfiguroni at\u00eb me Ansible.<\/li>\n<\/ol>\n

            <\/p>\n

            3. Krijo template VM<\/h4>\n

            <\/p>\n

            \"Ansible:<\/p>\n

            <\/p>\n

            K\u00ebtu nuk b\u00ebm\u00eb asgj\u00eb origjinale \u2014 p\u00ebrdor\u00ebm packer.<\/p>\n

            <\/p>\n

              \n
            1. N\u00eb depozit\u00ebn git vendosim konfigurimin e packer, kickstart.<\/li>\n
            2. Konfigurojm\u00eb nj\u00eb slave t\u00eb ve\u00e7ant\u00eb t\u00eb jenkins me hyper-v dhe Packer.<\/li>\n
            3. Krijojm\u00eb nj\u00eb pun\u00eb, konfigurojm\u00eb Jenkins.<\/li>\n<\/ol>\n

              <\/p>\n

              Si funksionon kjo lidhje:<\/p>\n

              <\/p>\n

                \n
              1. Packer krijon nj\u00eb VM t\u00eb zbraz\u00ebt, lidh ISO-n.<\/li>\n
              2. VM-ja ngarkohet, Packer jep komand\u00ebn p\u00ebr t\u00eb p\u00ebrdorur skedarin ton\u00eb kickstart nga disku ose http.<\/li>\n
              3. Anaconda nis me konfigurimin ton\u00eb, b\u00ebhet konfigurimi fillestar i OS.<\/li>\n
              4. Packer pret deri sa VM-ja t\u00eb b\u00ebhet e aksesueshme.<\/li>\n
              5. Packer brenda VM \u0437\u0430\u043f\u0443\u0441\u043a\u0430 ansible n\u00eb modalitetin lokal.<\/li>\n
              6. Ansible p\u00ebrdor t\u00eb nj\u00ebjtat role si n\u00eb hapin nr. 1.<\/li>\n
              7. Packer eksporton modelin e VM.<\/li>\n<\/ol>\n

                <\/p>\n

                Dita nr. 75: Ristrukturojm\u00eb marr\u00ebveshjet pa thyer = Testo ansible + Testkitchen.<\/h3>\n

                <\/p>\n

                \"Ansible:<\/p>\n

                <\/p>\n

                T\u00eb fiksohesh marr\u00ebveshjet n\u00eb kod mund t\u00eb mos mjaftoj\u00eb. Sepse n\u00ebse n\u00eb prapasken\u00eb d\u00ebshiron t\u00eb ndryshosh di\u00e7ka \u2014 mund t\u00eb thysh di\u00e7ka. Prandaj n\u00eb rastin e infrastruktur\u00ebs, testimi i k\u00ebsaj infrastrukture paraqitet. P\u00ebr t\u00eb sinkronizuar njohurit\u00eb brenda ekipit filluam t\u00eb testojm\u00eb rolet Ansible. Nuk do t\u00eb thellojm\u00eb, pasi ka nj\u00eb artikull q\u00eb p\u00ebrshkruan ngjarjet n\u00eb at\u00eb moment. M\u00eb testoni n\u00ebse mund t\u00eb porositeni ose a \u00ebnd\u00ebrrojn\u00eb programuesit YML p\u00ebr testimin ansible?<\/a><\/noindex>(spoiler, ky nuk ishte versioni p\u00ebrfundimtar dhe m\u00eb von\u00eb gjith\u00e7ka u b\u00eb m\u00eb e komplikuar). Si t\u00eb fillosh t\u00eb testosh Ansible, t\u00eb ristrukturosh projektin p\u00ebr nj\u00eb vit dhe t\u00eb mos b\u00ebsh \u00e7menduri.<\/a><\/noindex>).<\/p>\n

                <\/p>\n

                Dita nr. 130: Ndoshta CentOS + ansible nuk \u00ebsht\u00eb i nevojsh\u00ebm? ndoshta openshift?<\/h3>\n

                <\/p>\n

                Duhet t\u00eb kuptohet se procesi i integrimit t\u00eb infrastruktur\u00ebs nuk ishte e vetmja dhe kishte projekte an\u00ebsore. P\u00ebr shembull, erdhi nj\u00eb k\u00ebrkes\u00eb p\u00ebr ta drejtuar aplikacionin ton\u00eb n\u00eb openshift dhe kjo rezultoi n\u00eb k\u00ebrkime p\u00ebr m\u00eb shum\u00eb se nj\u00eb jav\u00eb. Nisim nj\u00eb aplikacion n\u00eb Openshift dhe krahasojm\u00eb mjetet ekzistuese.<\/a><\/noindex> \u00c7ka vonoi procesin e migrimit. Si rezultat, doli se Openshift nuk i plot\u00ebson t\u00eb gjitha nevojat, na nevojitet harduer i v\u00ebrtet\u00eb, ose t\u00eb pakt\u00ebn mund\u00ebsia p\u00ebr t\u00eb luajtur me kernelin.<\/p>\n

                <\/p>\n

                Dita \u2116170: Openshift nuk \u00ebsht\u00eb i p\u00ebrshtatsh\u00ebm, a do t\u00eb rrezikojm\u00eb me Windows Azure Pack?<\/h3>\n

                <\/p>\n

                \"Ansible:<\/p>\n

                <\/p>\n

                Hyper-V nuk \u00ebsht\u00eb shum\u00eb miq\u00ebsor, SCVMM nuk e b\u00ebn at\u00eb shum\u00eb m\u00eb t\u00eb mir\u00eb. Por ekziston nj\u00eb gj\u00eb e till\u00eb, Windows Azure Pack, e cila \u00ebsht\u00eb nj\u00eb shtres\u00eb mbi SCVMM dhe i ngjan Azure. Por n\u00eb realitet, produkti duket si i braktisur: dokumentacioni me lidhje t\u00eb prishura dhe mjaft i varf\u00ebr. Megjithat\u00eb, brenda hulumtimit t\u00eb mund\u00ebsive p\u00ebr t\u00eb leht\u00ebsuar jet\u00ebn ton\u00eb n\u00eb cloud, e kemi shqyrtuar edhe at\u00eb.<\/p>\n

                <\/p>\n

                Dita \u2116250: Windows Azure Pack nuk \u00ebsht\u00eb shum\u00eb. Q\u00ebndrojm\u00eb me SCVMM.<\/h3>\n

                <\/p>\n

                \"Ansible:<\/p>\n

                <\/p>\n

                Windows Azure Pack dukej premtues, por u vendos t\u00eb mos sjellim WAP me kompleksitetet e tij n\u00eb sistem p\u00ebr shkak t\u00eb ve\u00e7orive t\u00eb panevojshme dhe mbet\u00ebm me SCVMM.<\/p>\n

                <\/p>\n

                Dita \u2116360: Hame elefantin pjes\u00eb-pjes\u00eb.<\/h3>\n

                <\/p>\n

                \"Ansible:<\/p>\n

                <\/p>\n

                Vet\u00ebm nj\u00eb vit m\u00eb von\u00eb platforma ku duhej t\u00eb migronim ishte gati dhe filloi procesi i migrimit. P\u00ebr k\u00ebt\u00eb, u vendos nj\u00eb detyr\u00eb S.M.A.R.T. Shkruam t\u00eb gjitha VM-t\u00eb dhe filluam t\u00eb merremi me konfiguracionin, ta p\u00ebrshkruajm\u00eb at\u00eb n\u00eb Ansible, ta mbulojm\u00eb me teste.<\/p>\n

                <\/p>\n

                Dita \u2116450: \u00c7far\u00eb sistemi \u00ebsht\u00eb arritur?<\/h3>\n

                <\/p>\n

                \"Ansible:<\/p>\n

                <\/p>\n

                Procesi nuk \u00ebsht\u00eb interesant. Ai \u00ebsht\u00eb rutin\u00eb; mund t\u00eb theksohet se shumica e konfigurimeve ishin relativisht t\u00eb thjeshta ose izomorfe, dhe sipas parimit t\u00eb Pareto, 80% e konfigurimeve k\u00ebrkuan 20% t\u00eb koh\u00ebs. Po ashtu, 80% e koh\u00ebs u shpenzuan p\u00ebr p\u00ebrgatitjen e transferimit dhe vet\u00ebm 20% p\u00ebr vet\u00eb transferimin. <\/p>\n

                <\/p>\n

                Dita \u2116540: Finale<\/h2>\n

                <\/p>\n

                \"Ansible:<\/p>\n

                <\/p>\n

                \u00c7far\u00eb ndodhi gjat\u00eb 18 muajve?<\/p>\n

                <\/p>\n

                  \n
                1. Marr\u00ebveshjet u b\u00ebn\u00eb kod.<\/li>\n
                2. Pun\u00eb manuale<\/em> -> Mekanizim<\/em> -> Automatizimi<\/em>.<\/li>\n<\/ol>\n

                  <\/p>\n

                  Links<\/h2>\n

                  <\/p>\n