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

\"Ansible:<\/p>\n

<\/p>\n

Ky \u00ebsht\u00eb nj\u00eb p\u00ebrmbledhje e 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, n\u00eb t\u00eb cilin u p\u00ebrdor nj\u00eb sistem i shkruar nga vet\u00eb p\u00ebr menaxhimin e konfigurimeve dhe si u zgjat kalimi n\u00eb Ansible p\u00ebr 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\u00ebnte nj\u00eb num\u00ebr hostesh t\u00eb ve\u00e7uar 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 i mekanizuar, por p\u00ebr shembull, makinat virtuale shp\u00ebrndaheshin midis hosteve manualisht. Megjithat\u00eb, p\u00ebr shembull, zhvilluesit mund t\u00eb modificonin konfigurimin e VM n\u00eb git dhe ta aplikonin duke rinisur VM.<\/p>\n

<\/p>\n

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

<\/p>\n

\"Ansible:<\/p>\n

<\/p>\n

Ideja fillestare, e dyshoj, ishte menduar si IaC: shum\u00eb VM pa gjendje, t\u00eb cilat, pas rinisjes, e rikthenin gjendjen e tyre n\u00eb null. Si dukej menaxhimi i konfigurimeve t\u00eb VM? Schematisht duket thjesht\u00eb:<\/p>\n

<\/p>\n

    \n
  1. P\u00ebr VM, u vendos nj\u00eb MAC statik.<\/li>\n
  2. VM-at u lidh\u00ebn me ISO me CoreOS dhe diskun e b\u00ebr\u00eb p\u00ebr t'u ngarkuar.<\/li>\n
  3. CoreOS nis nj\u00eb skript personalizimi duke e shkarkuar at\u00eb nga nj\u00eb server 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. Nisin nj\u00eb s\u00ebr\u00eb skedar\u00ebsh systemd unit 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 deprecated.<\/li>\n
    2. Shum\u00eb veprime dhe magji t\u00eb nd\u00ebrlikuara gjat\u00eb migrimit\/krijimi t\u00eb VM.<\/li>\n
    3. V\u00ebshtir\u00ebsi n\u00eb p\u00ebrdit\u00ebsim dhe kur \u00ebsht\u00eb e nevojshme t\u00eb ket\u00eb nj\u00eb version t\u00eb caktuar t\u00eb softuerit. Edhe m\u00eb zbavit\u00ebse me modulet e b\u00ebrtham\u00ebs.<\/li>\n
    4. VM-t\u00eb nuk ishin aq pa t\u00eb dh\u00ebna, pra, dol\u00ebn VM q\u00eb pat\u00ebn disqe t\u00eb montuara me t\u00eb dh\u00ebna nga p\u00ebrdoruesit p\u00ebrve\u00e7 k\u00ebsaj.<\/li>\n
    5. P\u00ebrher\u00eb dikush b\u00ebnte gabime me var\u00ebsit\u00eb e unit systemd dhe n\u00eb rinisjen e CoreOS ngeciste. Ishte problematike t\u00eb kapje k\u00ebt\u00eb me mjetet ekzistuese n\u00eb CoreOS.<\/li>\n
    6. Menaxhimi i sekreteve.<\/li>\n
    7. CM pothuajse nuk kishte. Kishim bash dhe konfigurime YML t\u00eb CoreOS.<\/li>\n<\/ol>\n

      <\/p>\n

      P\u00ebr t\u00eb aplikuar konfigurimin e VM, ishte e nevojshme ta rinisje, por ajo mund t\u00eb mos rinisej. Dukej si nj\u00eb problem i qart\u00eb, por nuk kishte disqe t\u00eb vazhdueshme \u2014 nuk kishte ku t\u00eb ruhej logun. Mir\u00eb, le t\u00eb p\u00ebrpiqemi t\u00eb shtojm\u00eb opsione t\u00eb ngarkes\u00ebs s\u00eb b\u00ebrtham\u00ebs q\u00eb logjet t\u00eb d\u00ebrgoheshin. Por jo, sa e komplikuar ishte gjith\u00e7ka.<\/p>\n

      <\/p>\n

      Dita \u21160: Pranimi i problemit<\/h2>\n

      <\/p>\n

      \"Ansible:<\/p>\n

      <\/p>\n

      Ishte nj\u00eb infrastruktur\u00eb e zakonshme zhvillimi: jenkins, ambientet testuese, monitorimet, registry. CoreOS ishte menduar p\u00ebr hostimin e klastereve k8s, pra problemi ishte se si p\u00ebrdorej CoreOS. Hapi i par\u00eb ishte zgjedhja e stack-ut. Ne u ndal\u00ebm tek:<\/p>\n

      <\/p>\n

        \n
      1. CentOS<\/strong> si distribucion bazik, pasi \u00ebsht\u00eb distribuicioni m\u00eb i af\u00ebrt me ambientet e prodhimit.<\/li>\n
      2. Ansible<\/strong> p\u00ebr menaxhimin e konfigurimeve, pasi kishte nj\u00eb ekspertiz\u00eb t\u00eb gjer\u00eb p\u00ebr t\u00eb.<\/li>\n
      3. Jenkins<\/strong> si nj\u00eb framework automatik p\u00ebr proceset ekzistuese, pasi ishte tashm\u00eb aktivisht i p\u00ebrdorur p\u00ebr proceset e zhvillimit.<\/li>\n
      4. Hyper-V<\/strong> si platform\u00eb virtualizimi. Ka disa arsye, t\u00eb cilat dalin p\u00ebrtej tregimit, por n\u00ebse e p\u00ebrmbledhim \u2014 nuk mund t\u00eb p\u00ebrdorim cloud, duhet t\u00eb p\u00ebrdorim harduerin ton\u00eb.<\/li>\n<\/ol>\n

        <\/p>\n

        Dita \u211630: Fiksojm\u00eb marr\u00ebveshjet ekzistuese \u2014 Agreements as Code<\/h3>\n

        <\/p>\n

        \"Ansible:<\/p>\n

        <\/p>\n

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

        <\/p>\n

        1. Konfiguro VMs<\/h4>\n

        <\/p>\n

        \"Ansible:<\/p>\n

        <\/p>\n

        Ansible e b\u00ebn k\u00ebt\u00eb detyr\u00eb mjaft mir\u00eb. Me minimumin e l\u00ebvizjeve mund t\u00eb marrim n\u00eb menaxhim konfigurimet e VM-ve:<\/p>\n

        <\/p>\n

          \n
        1. Krijojm\u00eb nj\u00eb repository git.<\/li>\n
        2. Vendosim list\u00ebn e VM-ve n\u00eb inventory, konfigurimet n\u00eb playbooks dhe role.<\/li>\n
        3. Konfigurojm\u00eb nj\u00eb jenkins slave t\u00eb ve\u00e7ant\u00eb nga e cila mund t\u00eb nisnim ansible.<\/li>\n
        4. Krijojm\u00eb nj\u00eb job, konfigurojm\u00eb Jenkins.<\/li>\n<\/ol>\n

          <\/p>\n

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

          <\/p>\n

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

          <\/p>\n

          \"Ansible:<\/p>\n

          <\/p>\n

          K\u00ebtu nuk ishte shum\u00eb e leht\u00eb. Nga Linux nuk \u00ebsht\u00eb shum\u00eb e leht\u00eb t\u00eb krijosh VM n\u00eb Hyper-V. Nj\u00eb nga p\u00ebrpjekjet p\u00ebr t\u00eb makinizuar k\u00ebt\u00eb proces ishte:<\/p>\n

          <\/p>\n

            \n
          1. Ansible lidhet p\u00ebrmes WinRM me hostin windows.<\/li>\n
          2. Ansible ekzekuton skriptin powershell.<\/li>\n
          3. Skripti Powershell krijon nj\u00eb VM t\u00eb re.<\/li>\n
          4. Me mjete Hyper-V\/ScVMM gjat\u00eb krijimit t\u00eb VM-s\u00eb n\u00eb OS t\u00eb mysafir\u00ebve, konfiguroni hostname.<\/li>\n
          5. VM n\u00eb azhurnimin e DHCP lease d\u00ebrgon hostname-in e saj.<\/li>\n
          6. Integrimi i zakonsh\u00ebm ddns & dhcp n\u00eb an\u00ebn e Domain Controller konfiguron regjistrin DNS.<\/li>\n
          7. Mund t\u00eb shtoni VM n\u00eb inventar dhe t\u00eb konfiguroni Ansible p\u00ebr t\u00eb.<\/li>\n<\/ol>\n

            <\/p>\n

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

            <\/p>\n

            \"Ansible:<\/p>\n

            <\/p>\n

            K\u00ebtu nuk u shpik asgj\u00eb \u2014 mor\u00ebm packer.<\/p>\n

            <\/p>\n

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

              <\/p>\n

              Si funksionon ky bashk\u00ebpunim:<\/p>\n

              <\/p>\n

                \n
              1. Packer krijon nj\u00eb VM bosh, lidh ISO.<\/li>\n
              2. VM ngarkohet, Packer fut n\u00eb ngarkues komand\u00ebn p\u00ebr t\u00eb p\u00ebrdorur skedarin ton\u00eb kickstart nga disku ose http.<\/li>\n
              3. Anaconda me konfigurimin ton\u00eb nis inicializimin e OS.<\/li>\n
              4. Packer pret n\u00eb dispozicionin e VM-s\u00eb.<\/li>\n
              5. Packer brenda VM-s\u00eb nis ansible n\u00eb modin lokal.<\/li>\n
              6. Ansible p\u00ebrdor t\u00eb nj\u00ebjtat role si n\u00eb hapin \u21161.<\/li>\n
              7. Packer eksporton \u0448\u0430\u0431\u043b\u043e\u043din e VM.<\/li>\n<\/ol>\n

                <\/p>\n

                Dita \u211675: Riorganizojm\u00eb marr\u00ebveshjet pa prishur = Testo ansible + Testkitchen<\/h3>\n

                <\/p>\n

                \"Ansible:<\/p>\n

                <\/p>\n

                T\u00eb ngulisim marr\u00ebveshjet n\u00eb kod mund t\u00eb mos jet\u00eb e mjaftueshme. N\u00eb fund t\u00eb fundit, n\u00ebse n\u00eb thell\u00ebsi t\u00eb procesit d\u00ebshiron t\u00eb ndryshosh di\u00e7ka, mund t\u00eb prish\u00ebsh di\u00e7ka. Prandaj, n\u00eb rastin e infrastruktur\u00ebs kemi nevoj\u00eb p\u00ebr testimin e k\u00ebsaj infrastrukture. P\u00ebr t\u00eb sinkronizuar njohurit\u00eb brenda ekipit filluam t\u00eb testonim rolet e Ansible. Nuk do t\u00eb thellohem sepse ekziston nj\u00eb artikel q\u00eb p\u00ebrshkruan ngjarjet n\u00eb at\u00eb koh\u00eb. M\u00eb testo n\u00ebse mundesh ose \u00ebnd\u00ebrrojn\u00eb YML programuesit p\u00ebr testimin e ansible?<\/a><\/noindex>(spoiler, kjo nuk ishte versione p\u00ebrfundimtare dhe m\u00eb von\u00eb gjith\u00e7ka u b\u00eb m\u00eb komplekse) Si t\u00eb fillojm\u00eb t\u00eb testojm\u00eb Ansible, t\u00eb riorganizojm\u00eb projektin pas nj\u00eb viti dhe t\u00eb mos dalim nga mendja.<\/a><\/noindex>).<\/p>\n

                <\/p>\n

                Dita \u2116130: A \u00ebsht\u00eb CentOS + ansible i panevojsh\u00ebm? Ndoshta openshift?<\/h3>\n

                <\/p>\n

                Duhet t\u00eb kuptojm\u00eb se procesi i integrimit t\u00eb infrastruktur\u00ebs nuk ishte i vetmi dhe kishte projekte an\u00ebsore. P\u00ebr shembull, erdhi nj\u00eb k\u00ebrkes\u00eb p\u00ebr t\u00eb lan\u00e7uar aplikacionin ton\u00eb n\u00eb Openshift dhe kjo shkaktoi hulumtime q\u00eb zgjat\u00ebn m\u00eb shum\u00eb se nj\u00eb jav\u00eb. Loksionojm\u00eb aplikacionin n\u00eb Openshift dhe krahasojm\u00eb mjetet ekzistuese.<\/a><\/noindex> \u00e7far\u00eb e ngadal\u00ebsoi procesin e migrimit. Rezultati doli se openshift nuk mbulon t\u00eb gjitha nevojat, \u00ebsht\u00eb e nevojshme nj\u00eb hardware real, ose t\u00eb pakt\u00ebn t\u00eb kemi mund\u00ebsin\u00eb t\u00eb luajm\u00eb me kernelin.<\/p>\n

                <\/p>\n

                Dita \u2116170: Openshift nuk \u00ebsht\u00eb i p\u00ebrshtatsh\u00ebm, a 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 shum\u00eb m\u00eb t\u00eb mir\u00eb. Por ka nj\u00eb gj\u00eb t\u00eb till\u00eb si Windows Azure Pack, e cila \u00ebsht\u00eb nj\u00eb shtres\u00eb mbi SCVMM dhe imiton Azure. Por realisht produkti duket i braktisur: dokumentacioni me lidhje t\u00eb prishura dhe shum\u00eb i varf\u00ebr. Por n\u00eb kuad\u00ebr t\u00eb hulumtimit t\u00eb mund\u00ebsive p\u00ebr t\u00eb leht\u00ebsuar jet\u00ebn e cloud-it ton\u00eb 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 shum\u00eb premtues, por u vendos q\u00eb 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: Ham\u00eb elefantin n\u00eb copa.<\/h3>\n

                <\/p>\n

                \"Ansible:<\/p>\n

                <\/p>\n

                Vet\u00ebm pas nj\u00eb viti platforma ku do t\u00eb migronim ishte gati dhe filloi procesi i migrimit. P\u00ebr k\u00ebt\u00eb ishte vendosur nj\u00eb detyr\u00eb S.M.A.R.T. P\u00ebrshkruam t\u00eb gjitha VM-t\u00eb dhe filluam t\u00eb merremi me konfigurimin nj\u00eb nga nj\u00eb, ta p\u00ebrshkruajm\u00eb at\u00eb n\u00eb Ansible dhe ta mbulojm\u00eb me teste.<\/p>\n

                <\/p>\n

                Dita \u2116450: \u00c7far\u00eb sistemi u krijua?<\/h3>\n

                <\/p>\n

                \"Ansible:<\/p>\n

                <\/p>\n

                Procesi vet\u00eb nuk \u00ebsht\u00eb i interesant. Ai \u00ebsht\u00eb rutin\u00eb, mund t\u00eb theksojm\u00eb se shumica e konfigurimeve ishin relativisht t\u00eb thjeshta ose izomorfe dhe sipas parimit t\u00eb Pareto, 80% e konfigurimeve k\u00ebrkoi 20% t\u00eb koh\u00ebs. N\u00eb t\u00eb nj\u00ebjtin parim, 80% e koh\u00ebs kaloi p\u00ebr p\u00ebrgatitjen e shp\u00ebrnguljes dhe vet\u00ebm 20% p\u00ebr shp\u00ebrnguljen vet\u00eb. <\/p>\n

                <\/p>\n

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

                <\/p>\n

                \"Ansible:<\/p>\n

                <\/p>\n

                \u00c7far\u00eb ndodhi p\u00ebr 18 muajt?<\/p>\n

                <\/p>\n

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

                  <\/p>\n

                  Links<\/h2>\n

                  <\/p>\n