{"id":33075,"date":"2019-10-31T21:50:35","date_gmt":"2019-10-31T18:50:35","guid":{"rendered":"https:\/\/prohoster.info\/blog\/besprostojnaya-migratsiya-rabbitmq-v-kubernetes\/"},"modified":"2019-10-31T21:50:35","modified_gmt":"2019-10-31T18:50:35","slug":"besprostojnaya-migratsiya-rabbitmq-v-kubernetes","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/besprostojnaya-migratsiya-rabbitmq-v-kubernetes","title":{"rendered":"Migrimi i pap\u00ebrmbajtsh\u00ebm i RabbitMQ n\u00eb Kubernetes","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Migrimi
\n
\nRabbitMQ \u2013 nj\u00eb broker mesazhesh i shkruar n\u00eb gjuh\u00ebn Erlang, q\u00eb mund\u00ebson organizimin e nj\u00eb klasteri q\u00eb ka q\u00ebndrueshm\u00ebri ndaj d\u00ebshtimeve me replika t\u00eb plot\u00eb t\u00eb t\u00eb dh\u00ebnave n\u00eb disa nyje, ku secila nyje mund t\u00eb sh\u00ebrbej\u00eb k\u00ebrkesat p\u00ebr lexim dhe shkwrite. Duke pasur n\u00eb prodhim shum\u00eb klastera Kubernetes, mb\u00ebshtesim nj\u00eb num\u00ebr t\u00eb madh instalimesh RabbitMQ dhe kemi hasur nevoj\u00ebn p\u00ebr migrimin e t\u00eb dh\u00ebnave nga nj\u00eb klaster n\u00eb tjetrin pa ndalim.<\/a><\/noindex><\/p>\n

Kjo operacion ishte e nevojshme p\u00ebr ne t\u00eb pakt\u00ebn n\u00eb dy raste:<\/p>\n

    \n
  1. Transferimi i t\u00eb dh\u00ebnave nga nj\u00eb klaster RabbitMQ, q\u00eb nuk ndodhet n\u00eb Kubernetes, n\u00eb nj\u00eb t\u00eb ri \u2014 tashm\u00eb \u00abkubernetizuar\u00bb (dmth. q\u00eb funksionon n\u00eb pod\u2019 a K8s) \u2014 klaster.<\/li>\n
  2. Migrimi i RabbitMQ brenda Kubernetes nga nj\u00eb namespace n\u00eb tjetrin (p\u00ebr shembull, n\u00ebse kufijt\u00eb jan\u00eb t\u00eb ndara nga hap\u00ebsirat e emrave, at\u00ebher\u00eb p\u00ebr t\u00eb transferuar infrastruktur\u00ebn nga nj\u00eb kufi n\u00eb tjetrin).<\/li>\n<\/ol>\n

    \nReceta e propozuar n\u00eb k\u00ebt\u00eb artikull \u00ebsht\u00eb orientuar n\u00eb situata (por aspak e kufizuar n\u00eb to), ku ka nj\u00eb klaster t\u00eb vjet\u00ebr RabbitMQ (p\u00ebr shembull, prej 3 nyjesh), q\u00eb ndodhet ose tashm\u00eb n\u00eb K8s, ose n\u00eb ndonj\u00eb server t\u00eb vjet\u00ebr. Me t\u00eb punon nj\u00eb aplikacion, i vendosur n\u00eb Kubernetes (tashm\u00eb atje ose n\u00eb perspektiv\u00eb):<\/p>\n

    \"Migrimi
    \n
    \n\u2026 dhe para nesh q\u00ebndron detyra e migrimit t\u00eb tij n\u00eb production t\u00eb ri n\u00eb Kubernetes.<\/p>\n

    M\u00eb par\u00eb do t\u00eb p\u00ebrshkruhet qasja e p\u00ebrgjithshme p\u00ebr migrimin, dhe m\u00eb pas do t\u00eb vijn\u00eb detajet teknike p\u00ebr implementimin e saj.<\/p>\n

    Algoritmi i migrimit<\/h2>\n

    \nHapi i par\u00eb, paraprak, para \u00e7do veprimi \u2014 verifikimi q\u00eb n\u00eb instalimin e vjet\u00ebr t\u00eb RabbitMQ \u00ebsht\u00eb aktivizuar moda e disponibilitetit t\u00eb lart\u00eb (HA<\/a><\/noindex>). Arsyeja \u00ebsht\u00eb e qart\u00eb \u2014 ne nuk duam t\u00eb humbim asnj\u00eb t\u00eb dh\u00ebn\u00eb. P\u00ebr t\u00eb realizuar k\u00ebt\u00eb verifikim, mund t\u00eb hyni n\u00eb panelin administrativ t\u00eb RabbitMQ dhe n\u00eb skedarin Admin \u2192 Policies t\u00eb siguroheni q\u00eb vlera e vendosur \u00ebsht\u00eb ha-mode: all<\/code>:<\/p>\n

    \"Migrimi
    \n
    \nHapi tjet\u00ebr \u2014 ngritja e nj\u00eb klasteri t\u00eb ri t\u00eb RabbitMQ n\u00eb pod-at e Kubernetes (n\u00eb rastin ton\u00eb, p\u00ebr shembull, duke p\u00ebrfshir\u00eb 3 node, por numri i tyre mund t\u00eb jet\u00eb ndryshe).<\/p>\n

    Pas k\u00ebsaj, ne bashkojm\u00eb klasterin e vjet\u00ebr dhe at\u00eb t\u00eb ri t\u00eb RabbitMQ, duke marr\u00eb nj\u00eb klaster t\u00eb vet\u00ebm (nga 6 node):<\/p>\n

    \"Migrimi
    \n
    \nIniciuhet procesi i sinkronizimit t\u00eb t\u00eb dh\u00ebnave midis klastereve t\u00eb vjet\u00ebr dhe t\u00eb ri t\u00eb RabbitMQ. Pas p\u00ebrfundimit t\u00eb sinkronizimit t\u00eb t\u00eb gjitha t\u00eb dh\u00ebnave midis t\u00eb gjith\u00eb node-ve n\u00eb klaster, ne mund t\u00eb kalojm\u00eb aplikacionin n\u00eb p\u00ebrdorimin e klasterit t\u00eb ri:<\/p>\n

    \"Migrimi
    \n
    \nPas k\u00ebtyre operacioneve, mjafton t\u00eb nxjerrim nga klasteri t\u00eb vjetrit t\u00eb RabbitMQ, dhe kalimi mund t\u00eb konsiderohet i p\u00ebrfunduar:<\/p>\n

    \"Migrimi
    \n
    \nK\u00ebt\u00eb skem\u00eb e kemi aplikuar disa her\u00eb n\u00eb produkcion. Megjithat\u00eb, p\u00ebr komoditetin ton\u00eb, e realizuam at\u00eb brenda nj\u00eb sistemi t\u00eb specializuar, q\u00eb shp\u00ebrndan konfigurime standart RMQ n\u00eb shum\u00eb klaster\u00eb Kubernetes. (p\u00ebr ata q\u00eb jan\u00eb kurioz: po flasim p\u00ebr     addon-operator<\/a><\/noindex>, p\u00ebr t\u00eb cilin ne m\u00eb s\u00eb fundmi fol\u00ebm<\/a><\/noindex>)<\/i>. M\u00eb posht\u00eb do t\u00eb paraqiten udh\u00ebzime t\u00eb ve\u00e7anta q\u00eb secili mund t\u00eb aplikoj\u00eb n\u00eb instalimet e tij p\u00ebr t\u00eb provuar zgjidhjen e propozuar n\u00eb veprim.<\/p>\n

    T\u00eb provojm\u00eb n\u00eb praktik\u00eb<\/h2>\n

    <\/p>\n

    K\u00ebrkesat<\/h3>\n

    \nDetajet jan\u00eb shum\u00eb t\u00eb thjeshta:<\/p>\n

      \n
    1. Kluster Kubernetes (minikube \u00ebsht\u00eb gjithashtu n\u00eb rregull);<\/li>\n
    2. Kluster RabbitMQ (mund t\u00eb vendoset gjithashtu n\u00eb bare metal, si edhe t\u00eb b\u00ebhet si nj\u00eb kluster i zakonsh\u00ebm n\u00eb Kubernetes nga Helm-chart zyrtar).<\/li>\n<\/ol>\n

      \nP\u00ebr shembullin e p\u00ebrshkruar m\u00eb posht\u00eb, un\u00eb kam vendosur RMQ n\u00eb Kubernetes dhe e quajta rmq-old<\/code>.<\/p>\n

      P\u00ebrgatitja e sken\u00ebs<\/h3>\n

      \n1. Do t\u00eb shkarkojm\u00eb Helm-chart dhe pak do ta redaktojm\u00eb at\u00eb:<\/p>\n

      helm fetch --untar stable\/rabbitmq-ha<\/code><\/pre>\n
      \nP\u00ebr leht\u00ebsim, do t\u00eb caktuam fjal\u00ebkalimin, ErlangCookie<\/code> dhe do t\u00eb krijojm\u00eb politik\u00ebn ha-all<\/code>, n\u00eb m\u00ebnyr\u00eb q\u00eb rreshtat t\u00eb sinkronizohen automatikisht midis t\u00eb gjitha nyjeve t\u00eb klustrit RMQ:<\/p>\n
      rabbitmqPassword: guest\nrabbitmqErlangCookie: mae9joopaol7aiVu3eechei2waiGa2we\ndefinitions:\npolicies: |-\n  {\n    \"name\": \"ha-all\",\n    \"pattern\": \".*\",\n    \"vhost\": \"\/\",\n    \"definition\": {\n      \"ha-mode\": \"all\",\n      \"ha-sync-mode\": \"automatic\",\n      \"ha-sync-batch-size\": 81920\n    }\n  }<\/code><\/pre>\n
      \n2. Instaloni grafik\u00ebn:<\/p>\n
      helm install . --name rmq-old --namespace rmq-old<\/code><\/pre>\n
      \n3. Hyni n\u00eb panelin administrativ t\u00eb RabbitMQ, krijoni nj\u00eb radh\u00eb t\u00eb re dhe shtoni disa mesazhe. Ato do t\u00eb nevojiten p\u00ebr t\u00eb siguruar q\u00eb, pas migrimit, t\u00eb gjitha t\u00eb dh\u00ebnat t\u00eb ruhen dhe asgj\u00eb t\u00eb mos humbas\u00eb:<\/p>\n
      \"Migrimi
      \n
      \nStendi i testit \u00ebsht\u00eb gati: kemi nj\u00eb RabbitMQ \"t\u00eb vjet\u00ebr\" me t\u00eb dh\u00ebna q\u00eb duhet t\u00eb transferohen.<\/p>\n
      Migrimi i grupit t\u00eb RabbitMQ<\/h3>\n
      \n1. Fillimisht, do t\u00eb vendosim nj\u00eb RabbitMQ t\u00eb ri n\u00eb nj\u00eb tjet\u00ebr<\/b> hap\u00ebsir\u00eb emri me t\u00eb nj\u00ebjtat<\/b> ErlangCookie<\/code> dhe fjal\u00ebkalim p\u00ebr p\u00ebrdoruesin. Prandaj, do t\u00eb kryejm\u00eb operacionet e p\u00ebrshkruara m\u00eb sip\u00ebr, duke ndryshuar komand\u00ebn p\u00ebrfundimtare t\u00eb instalimit t\u00eb RMQ n\u00eb k\u00ebt\u00eb:<\/p>\n
      helm install . --name rmq-new --namespace rmq-new<\/code><\/pre>\n
      \n2. Tani \u00ebsht\u00eb e nevojshme t\u00eb kombinohet grupi i ri me at\u00eb t\u00eb vjet\u00ebr. P\u00ebr t\u00eb b\u00ebr\u00eb k\u00ebt\u00eb, hyni n\u00eb secilin nga pod\u00ebt e reja<\/b> RabbitMQ dhe kryeni komandat:<\/p>\n
      export OLD_RMQ=rabbit@rmq-old-rabbitmq-ha-0.rmq-old-rabbitmq-ha-discovery.rmq-old.svc.cluster.local && \n  rabbitmqctl stop_app && \n  rabbitmqctl join_cluster $OLD_RMQ && \n  rabbitmqctl start_app<\/code><\/pre>\n
      \nN\u00eb variabl\u00ebn OLD_RMQ<\/code> \u00ebsht\u00eb adresa e nj\u00ebrit nga node-t e vjet\u00ebr<\/b> grupi RMQ.<\/p>\n
      K\u00ebto komandat do t\u00eb ndalojn\u00eb nodin aktual e reja<\/b> e grupit RMQ, do ta bashkojn\u00eb at\u00eb me grupin e vjet\u00ebr dhe do ta fillojn\u00eb p\u00ebrs\u00ebri.<\/p>\n
      3. Grupe RMQ me 6 node \u00ebsht\u00eb gati:<\/p>\n
      \"Migrimi
      \n
      \nDuhet t\u00eb prisni, derisa mesazhet t\u00eb sinkronizohen midis t\u00eb gjith\u00eb nyjeve. Nuk \u00ebsht\u00eb e v\u00ebshtir\u00eb t\u00eb kuptohet se koha e sinkronizimit t\u00eb mesazheve varet nga kapacitetet e harduerit mbi t\u00eb cilin \u00ebsht\u00eb vendosur klusteri, si dhe nga numri i mesazheve. N\u00eb skenarin e p\u00ebrshkruar, ka vet\u00ebm 10, prandaj t\u00eb dh\u00ebnat u sinkronizuan menj\u00ebher\u00eb, por me nj\u00eb num\u00ebr t\u00eb mjaftuesh\u00ebm mesazhesh, sinkronizimi mund t\u00eb zgjas\u00eb p\u00ebr or\u00eb t\u00eb t\u00ebra.<\/p>\n
      Pra, statusi i sinkronizimit:<\/p>\n
      \"Migrimi
      \n
      \nK\u00ebtu +5<\/code> do t\u00eb thot\u00eb se mesazhet jan\u00eb tashm\u00eb ende<\/b> n\u00eb 5 nyje (p\u00ebrve\u00e7 asaj q\u00eb \u00ebsht\u00eb e specifikuar n\u00eb fush\u00ebn Node<\/code>). K\u00ebshtu, sinkronizimi kaloi me sukses.<\/p>\n
      4. Vet\u00ebm duhet t\u00eb nd\u00ebrroni n\u00eb aplikacion adres\u00ebn RMQ n\u00eb klusterin e ri (veprimet specifike k\u00ebtu varet nga pena e teknologjis\u00eb q\u00eb p\u00ebrdorni dhe specifika t\u00eb tjera t\u00eb aplikacionit), pas s\u00eb cil\u00ebs mund t\u00eb despedoni nga i vjetri.<\/p>\n
      P\u00ebr operacionin e fundit (dmth tashm\u00eb pas<\/b> nd\u00ebrrimin e aplikacionit n\u00eb klusterin e ri) hyjm\u00eb n\u00eb \u00e7do nyj\u00eb e vjet\u00ebr<\/b> t\u00eb klusterit dhe ekzekutojm\u00eb komandat:<\/p>\n
      rabbitmqctl stop_app\nrabbitmqctl reset<\/code><\/pre>\n
      \nKlusteri \u00abe ka harruar\u00bb nyjet e vjetra: mund t\u00eb largoni RMQ-n\u00eb e vjet\u00ebr, duke p\u00ebrfunduar k\u00ebshtu migrimin.<\/p>\n
      Sh\u00ebnim<\/b>: N\u00ebse po p\u00ebrdorni RMQ me certifikata, at\u00ebher\u00eb asgj\u00eb nuk ndryshon thelb\u00ebsisht \u2014 procesi i migrimit do t\u00eb zhvillohet pik\u00ebrisht ashtu si\u00e7 \u00ebsht\u00eb.<\/i><\/p>\n
      P\u00ebrfundimet<\/h2>\n
      \nSkema e p\u00ebrshkruar \u00ebsht\u00eb e p\u00ebrshtatshme praktikisht p\u00ebr t\u00eb gjitha rastet kur duhet t\u00eb transferojm\u00eb RabbitMQ ose thjesht t\u00eb kalojm\u00eb n\u00eb nj\u00eb klaster t\u00eb ri.<\/p>\n
      N\u00eb rastin ton\u00eb, v\u00ebshtir\u00ebsit\u00eb u shfaq\u00ebn vet\u00ebm nj\u00eb her\u00eb, kur RMQ u k\u00ebrkua nga shum\u00eb vende, dhe ne nuk kishim mund\u00ebsi t\u00eb ndryshonim adres\u00ebn e RMQ n\u00eb t\u00eb gjith\u00eb vendet. At\u00ebher\u00eb ne nis\u00ebm nj\u00eb RMQ t\u00eb ri n\u00eb t\u00eb nj\u00ebjtin hap\u00ebsir\u00eb emri me etiketat e nj\u00ebjta, n\u00eb m\u00ebnyr\u00eb q\u00eb t\u00eb p\u00ebrfshiheshin n\u00eb sh\u00ebrbimet dhe Ingress-at ekzistues, dhe kur nisim pod-in manualisht, manipuluam etiketat, duke i hequr ato n\u00eb fillim, p\u00ebr t\u00eb siguruar q\u00eb k\u00ebrkesat t\u00eb mos kalonin n\u00eb RMQ-n\u00eb e zbraz\u00ebt dhe duke i shtuar p\u00ebrs\u00ebri pas sinkronizimit t\u00eb mesazheve.<\/p>\n
      Ne kemi aplikuar t\u00eb nj\u00ebjt\u00ebn strategji kur azhurnuam RabbitMQ n\u00eb nj\u00eb version t\u00eb ri me konfigurim t\u00eb ndryshuar \u2014 gjith\u00e7ka funksionoi pa probleme.<\/p>\n
      P.S.<\/h2>\n
      \nSi nj\u00eb vazhdim logjik i k\u00ebtij materiali, ne po p\u00ebrgatisim artikuj p\u00ebr MongoDB (migrimi nga serveri fizik n\u00eb Kubernetes) dhe MySQL (si e p\u00ebrgatisim k\u00ebt\u00eb DBMS brenda Kubernetes). Ato do t\u00eb publikohen n\u00eb muajt e ardhsh\u00ebm.<\/p>\n
      P.P.S.<\/h2>\n
      \nLexoni gjithashtu n\u00eb blogun ton\u00eb:<\/p>\n