{"id":96767,"date":"2020-10-14T14:43:02","date_gmt":"2020-10-14T12:43:02","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/hystax-cloud-migration-skachem-po-oblakam"},"modified":"2020-10-14T14:43:02","modified_gmt":"2020-10-14T12:43:02","slug":"hystax-cloud-migration-skachem-po-oblakam","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/hystax-cloud-migration-skachem-po-oblakam","title":{"rendered":"Hystax Cloud Migration: duke u zhvendosur n\u00ebp\u00ebrmjet reve","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Nj\u00eb nga lojtar\u00ebt e rinj n\u00eb tregun e zgjidhjeve t\u00eb Rim\u00ebk\u00ebmbjes nga Avaria \u00ebsht\u00eb kompan\u00eda Hystax \u2013 nj\u00eb startup rus i vitit 2016. Duke qen\u00eb se tema e rim\u00ebk\u00ebmbjes nga avaria \u00ebsht\u00eb shum\u00eb e popullarizuar, dhe konkurrenca n\u00eb treg \u00ebsht\u00eb jasht\u00ebzakonisht e lart\u00eb, startup-i vendosi t\u00eb p\u00ebrqendrohet n\u00eb migrimin midis infrastrukturave t\u00eb ndryshme cloud. Nj\u00eb produkt q\u00eb lejon organizimin e nj\u00eb migrimi t\u00eb thjesht\u00eb dhe t\u00eb shpejt\u00eb n\u00eb cloud do t\u00eb ishte shum\u00eb i dobish\u00ebm edhe p\u00ebr klient\u00ebt e kompanis\u00eb \"Onlanta\" \u2013 p\u00ebrdoruesit. Oncloud.ru<\/a><\/noindex>. K\u00ebshtu u njoha me Hystax dhe fillova t\u00eb testoj mund\u00ebsit\u00eb e tij. \u00c7far\u00eb doli nga kjo, do ta shpjegoj n\u00eb k\u00ebt\u00eb artikull.<\/p>\n

\"Hystax<\/a><\/noindex>
\nKarakteristika kryesore e Hystax \u00ebsht\u00eb se ka nj\u00eb funksionalitet t\u00eb gjer\u00eb p\u00ebr mb\u00ebshtetje t\u00eb platformave t\u00eb ndryshme t\u00eb virtualizimit, sistemeve operative mysafir dhe sh\u00ebrbimeve cloud, duke dh\u00ebn\u00eb mund\u00ebsin\u00eb p\u00ebr t\u00eb transferuar ngarkesat tuaja t\u00eb pun\u00ebs nga kudo dhe n\u00eb \u00e7do vend.<\/p>\n

Kjo mund\u00ebson krijimin e zgjidhjeve DR p\u00ebr t\u00eb rritur q\u00ebndrueshm\u00ebrin\u00eb e sh\u00ebrbimeve, por gjithashtu lejon q\u00eb t\u00eb migrohen burimet midis platformave dhe hiperskalier\u00ebve t\u00eb ndrysh\u00ebm p\u00ebr t\u00eb rritur kursimin e kostove dhe p\u00ebr t\u00eb zgjedhur zgjidhjen m\u00eb t\u00eb p\u00ebrshtatshme p\u00ebr sh\u00ebrbimin konkret n\u00eb at\u00eb moment. P\u00ebrve\u00e7 platformave t\u00eb p\u00ebrmendura n\u00eb imazhin kryesor, kompania gjithashtu bashk\u00ebpunon aktivisht me ofrues t\u00eb ndrysh\u00ebm t\u00eb sh\u00ebrbimeve cloud n\u00eb Rusi: Yandex.Cloud, KROK \u201cSh\u00ebrbimet Cloud\u201d, Mail.ru dhe shum\u00eb t\u00eb tjer\u00eb. Gjithashtu, vlen t\u00eb theksohet se n\u00eb vitin 2020 kompania hapi nj\u00eb qend\u00ebr R&D n\u00eb Skolkovo.\u00a0<\/p>\n

Zgjedhja e nj\u00ebz\u00ebshme nga nj\u00eb num\u00ebr i madh lojtar\u00ebsh n\u00eb treg d\u00ebshmon p\u00ebr nj\u00eb politik\u00eb t\u00eb mir\u00eb \u00e7mimi dhe aplikueshm\u00ebrin\u00eb e lart\u00eb t\u00eb produktit, \u00e7far\u00eb ne vendos\u00ebm ta verifikojm\u00eb n\u00eb praktik\u00eb.<\/p>\n

Pra, detyra jon\u00eb provuese do t\u00eb p\u00ebrb\u00ebhet nga migrimi nga platforma ime testuese VMware dhe makinat fizike n\u00eb platform\u00ebn e ofruesit gjithashtu n\u00ebn menaxhimin e VMware. Po, ka shum\u00eb zgjidhje q\u00eb mund t\u00eb realizojn\u00eb nj\u00eb migrim t\u00eb till\u00eb, por ne e shohim Hystax si nj\u00eb mjet universale, nd\u00ebrsa t\u00eb testosh migrimin n\u00eb t\u00eb gjitha kombinimet e mundshme \u00ebsht\u00eb thjesht nj\u00eb detyr\u00eb e pamundur. Po ashtu, cloud-i Oncloud.ru \u00ebsht\u00eb nd\u00ebrtuar pik\u00ebrisht mbi VMware, prandaj kjo platform\u00eb si objektiv na intereson m\u00eb shum\u00eb. M\u00eb pas do ta p\u00ebrshkruaj parimin kryesor t\u00eb funksionimit, i cili n\u00eb thelb nuk varet nga platforma, dhe VMware nga \u00e7do an\u00eb mund t\u00eb z\u00ebvend\u00ebsohet me platform\u00ebn e nj\u00eb ofruesi tjet\u00ebr.\u00a0<\/p>\n

N\u00eb faz\u00ebn e par\u00eb, \u00ebsht\u00eb e nevojshme t\u00eb implementoni Hystax Acura, e cila \u00ebsht\u00eb paneli i menaxhimit t\u00eb sistemit.<\/p>\n

\"Hystax<\/a><\/noindex>
\nAjo implementohet nga nj\u00eb shabllon. P\u00ebr nj\u00eb arsye, n\u00eb rastin ton\u00eb ai nuk ishte krejt\u00ebsisht i sakt\u00eb dhe p\u00ebrve\u00e7 8CPU, 16Gb t\u00eb rekomanduara, u implementua me burime dy her\u00eb m\u00eb t\u00eb vogla. Prandaj, mos e harroni t'i ndryshoni ato, p\u00ebrndryshe infrastruktura brenda VM, mbi t\u00eb cil\u00ebn \u00ebsht\u00eb nd\u00ebrtuar gjith\u00e7ka, thjesht nuk do t\u00eb nis\u00eb dhe porta do t\u00eb jet\u00eb e paqart\u00eb. N\u00eb K\u00ebrkesat p\u00ebr implementim<\/a><\/noindex> shpjegojn\u00eb n\u00eb detaje burimet e k\u00ebrkuara dhe portet p\u00ebr t\u00eb gjith\u00eb komponent\u00ebt e sistemit.\u00a0<\/p>\n

Dhe gjithashtu kishim v\u00ebshtir\u00ebsi me caktimin e adres\u00ebs IP p\u00ebrmes shabllonit, k\u00ebshtu q\u00eb e ndryshuam at\u00eb nga konsola. Pas k\u00ebsaj, mund t\u00eb kaloni n\u00eb nd\u00ebrfaqen web t\u00eb administrat\u00ebs dhe t\u00eb plot\u00ebsoni masterin e konfigurimit fillestar.\u00a0<\/p>\n

\"Hystax<\/a><\/noindex>
\n\"Hystax<\/a><\/noindex>
\nEndpoint \u2013 IP ose FQDN i vCenter ton\u00eb.\u00a0
\nLogin dhe Fjal\u00ebkalimi \u2013 k\u00ebtu \u00ebsht\u00eb e qart\u00eb.\u00a0
\nEmri i hostit t\u00eb synuar ESXi \u2013 nj\u00eb nga hostet e klasterit ton\u00eb, ku do t\u00eb b\u00ebhet replikimi.\u00a0
\nDepoja e synuar \u2013 nj\u00eb nga depojat e klasterit ton\u00eb, ku do t\u00eb b\u00ebhet replikimi.
\nIP publike e panelit t\u00eb kontrollit Hystax Acura \u2013 adresa, nga e cila do t\u00eb jet\u00eb e aksesueshme paneli i menaxhimit.<\/p>\n

K\u00ebrkohet nj\u00eb sqarim i vog\u00ebl p\u00ebr hostin dhe depot. \u00c7\u00ebshtja \u00ebsht\u00eb se replika Hystax funksionon n\u00eb nivelin e hostit dhe depot. M\u00eb von\u00eb do t'ju tregoj se si mund t\u00eb ndryshoni hostin dhe depotin p\u00ebr tenantin, por problemi \u00ebsht\u00eb se Hystax nuk mb\u00ebshtet pun\u00ebn me grumbuj burimesh, dmth. replikimi gjithmon\u00eb do t\u00eb ndodh\u00eb n\u00eb rr\u00ebnj\u00ebn e klasterit (n\u00eb koh\u00ebn e shkrimit t\u00eb k\u00ebtij materiali, ekipi i Hystax l\u00ebshoi nj\u00eb version t\u00eb azhurnuar, ku shpejt implementuan k\u00ebrkes\u00ebn time p\u00ebr mb\u00ebshtetje t\u00eb grumbujve t\u00eb burimeve). Gjithashtu, vCloud Director nuk mb\u00ebshtetet, dmth. n\u00ebse, si n\u00eb rastin tim, tenanti nuk ka t\u00eb drejta administratoriale p\u00ebr t\u00eb gjith\u00eb klasterin, por vet\u00ebm p\u00ebr nj\u00eb grumbull specifik burimesh, dhe ne i dham\u00eb akses Hystax, ai do t\u00eb mund t\u00eb replikoj\u00eb dhe t\u00eb nis\u00eb k\u00ebto VM vet\u00eb, por nuk do t\u00eb mund t'i shoh\u00eb ato n\u00eb infrastruktur\u00ebn VMware, n\u00eb t\u00eb cil\u00ebn ka akses dhe, p\u00ebr rrjedhoj\u00eb, nuk do t\u00eb mund t\u00eb menaxhoj\u00eb m\u00eb tej makinat virtuale. \u00cbsht\u00eb e nevojshme q\u00eb administratori i klasterit t\u00eb transferoj\u00eb VM n\u00eb grumbullin e duhur t\u00eb burimeve ose ta importoj\u00eb n\u00eb vCloud Director.<\/p>\n

Pse po i kushtoj kaq shum\u00eb r\u00ebnd\u00ebsi k\u00ebtyre momenteve? Sepse, sa m\u00eb kuptohet koncepti i produktit, klienti duhet t\u00eb ket\u00eb mund\u00ebsin\u00eb t\u00eb realizoj\u00eb \u00e7do migrim ose DR p\u00ebrmes panelit Acura. Por, deri tani, mb\u00ebshtetje p\u00ebr VMware \u00ebsht\u00eb pak prapa nivelit t\u00eb mb\u00ebshtetjes p\u00ebr OpenStack, ku mekanizmat e till\u00eb tashm\u00eb jan\u00eb realizuar.\u00a0<\/p>\n

Por le t\u00eb kthehemi te shp\u00ebrndarja. S\u00eb pari, pas konfigurimit fillestar t\u00eb panelit, na nevojitet t\u00eb krijojm\u00eb tenantin e par\u00eb n\u00eb sistemin ton\u00eb.<\/p>\n

\"Hystax<\/a><\/noindex>
\nT\u00eb gjitha fushat k\u00ebtu jan\u00eb t\u00eb qarta, do flas vet\u00ebm p\u00ebr fush\u00ebn Cloud. Ne tashm\u00eb kemi nj\u00eb \u00abcloud\u00bb \u00abdefault\u00bb q\u00eb e krijuam gjat\u00eb konfigurimit fillestar. Por n\u00ebse duam t\u00eb kemi mund\u00ebsin\u00eb t\u00eb vendosim \u00e7do tenant n\u00eb datastorin e vet dhe n\u00eb pool-in e vet t\u00eb burimeve, mund ta realizojm\u00eb k\u00ebt\u00eb duke krijuar \u2018cloud\u2019 t\u00eb ve\u00e7ant\u00eb p\u00ebr secilin nga klient\u00ebt tan\u00eb.<\/p>\n

\"Hystax<\/a><\/noindex>
\nN\u00eb formularin p\u00ebr shtimin e nj\u00eb \u2018cloud\u2019-i t\u00eb ri ne tregojm\u00eb t\u00eb nj\u00ebjtat parametra si gjat\u00eb konfigurimit fillestar (mund t\u00eb p\u00ebrdorim madje edhe hostin e nj\u00ebjt\u00eb), tregojm\u00eb datastorin e nevojsh\u00ebm p\u00ebr klientin specifik dhe tani n\u00eb parametrat shtes\u00eb mund t\u00eb tregojm\u00eb individualisht pool-in e burimeve t\u00eb nevojshme {\u00abresource_pool\u00bb: \u00abYOUR_POOL_NAME\u00bb}\u00a0<\/p>\n

Si\u00e7 e keni v\u00ebn\u00eb re, n\u00eb formularin e krijimit t\u00eb tenantit nuk ka asgj\u00eb p\u00ebr ndarjen e burimeve ose ndonj\u00eb kuot\u00eb \u2013 asgj\u00eb e till\u00eb nuk ekziston n\u00eb sistem. Nuk \u00ebsht\u00eb e mundur t\u00eb kufizojm\u00eb tenantin n\u00eb numrin e replika t\u00eb nj\u00ebkohshme, numrin e makinave p\u00ebr replikim ose sipas parametrave t\u00eb tjer\u00eb. K\u00ebshtu, ne krijuam tenantin e par\u00eb. Tani ka di\u00e7ka jo krejt logjike, por t\u00eb detyrueshme \u2013 instalimi i agentit Cloud. Nuk \u00ebsht\u00eb logjike, sepse agjenti shkarkohet n\u00eb faqen e klientit konkret.<\/p>\n

\"Hystax<\/a><\/noindex>
\nAi nuk \u00ebsht\u00eb i lidhur me tenantin e krijuar dhe p\u00ebrmes tij do t\u00eb punojn\u00eb t\u00eb gjith\u00eb klient\u00ebt tan\u00eb (ose disa, n\u00ebse i deploy-m). Nj\u00eb agjent mb\u00ebshtet 10 sesione t\u00eb nj\u00ebkohshme. Nj\u00eb sesion llogaritet si nj\u00eb makin\u00eb. N\u00eb k\u00ebt\u00eb rast, nuk ka r\u00ebnd\u00ebsi sa disqe ka ajo. N\u00eb dit\u00ebt e sotme, mekanizmi p\u00ebr shkall\u00ebzim t\u00eb agjent\u00ebve n\u00eb vet\u00eb Acura n\u00ebn VMware nuk ekziston. Ka edhe nj\u00eb \u00e7\u00ebshtje tjet\u00ebr t\u00eb pak\u00ebndshme \u2013 ne nuk kemi mund\u00ebsi nga paneli Acura t\u00eb shohim<\/p>\n

\"Hystax<\/a><\/noindex>
\nHapi tjet\u00ebr p\u00ebr t\u00eb aksesuar portalin e klientit ton\u00eb \u00ebsht\u00eb krijimi i nj\u00eb llogarie (dhe m\u00eb par\u00eb duhet t\u00eb krijojm\u00eb nj\u00eb rol q\u00eb do t\u00eb aplikohet p\u00ebr k\u00ebt\u00eb p\u00ebrdorues).<\/p>\n

\"Hystax<\/a><\/noindex>
\n\"Hystax<\/a><\/noindex>
\nTani klienti yn\u00eb mund t\u00eb p\u00ebrdor\u00eb portalin n\u00eb m\u00ebnyr\u00eb t\u00eb pavarur. E gjith\u00eb \u00e7far\u00eb duhet t\u00eb b\u00ebj\u00eb \u00ebsht\u00eb t\u00eb shkarkoj\u00eb agjent\u00ebt nga portali dhe t'i instaloj\u00eb n\u00eb an\u00ebn e tij. Ekzistojn\u00eb tre lloje agjent\u00ebsh: Linux, Windows dhe VMware.<\/p>\n

\"Hystax<\/a><\/noindex>
\nT\u00eb dy t\u00eb par\u00ebt instalohen n\u00eb fiziologjin\u00eb ose n\u00eb makinat virtuale n\u00eb \u00e7do hipervizor tjet\u00ebr p\u00ebrve\u00e7 VMware. Nuk k\u00ebrkohet t\u00eb konfigurohet asgj\u00eb shtes\u00eb, agjenti shkarkohet dhe tashm\u00eb di ku duhet t\u00eb trokas\u00eb, dhe brenda nj\u00eb minute makina do t\u00eb duket n\u00eb panelin Acura. Situata me agjentin VMware \u00ebsht\u00eb pak m\u00eb e nd\u00ebrlikuar. Problemi \u00ebsht\u00eb se agjenti p\u00ebr VMware gjithashtu shkarkohet nga portali tashm\u00eb i p\u00ebrgatitur dhe me konfigurimin e nevojsh\u00ebm. Por agjenti VMware, p\u00ebrve\u00e7 njohjes p\u00ebr portalin ton\u00eb Acura, duhet t\u00eb dij\u00eb gjithashtu p\u00ebr sistemin e virtualizimit, n\u00eb t\u00eb cilin do t\u00eb implementohet.<\/p>\n

\"Hystax<\/a><\/noindex>
\nP\u00ebr m\u00eb tep\u00ebr, k\u00ebto t\u00eb dh\u00ebna sistemi do t'i k\u00ebrkoj\u00eb t\u00eb specifikojm\u00eb gjat\u00eb shkarkimit t\u00eb par\u00eb t\u00eb agjentit VMware. Problemi \u00ebsht\u00eb se n\u00eb epok\u00ebn ton\u00eb t\u00eb dashuris\u00eb s\u00eb p\u00ebrgjithshme p\u00ebr sigurin\u00eb, shum\u00eb pak do t\u00eb duan t\u00eb specifikojn\u00eb fjal\u00ebkalimin e tyre t\u00eb administratorit n\u00eb nj\u00eb portal tjet\u00ebr, gj\u00eb q\u00eb \u00ebsht\u00eb mjaft e kuptueshme. Pas implementimit, agjenti nuk mund t\u00eb konfigurohet m\u00eb (mund t\u00eb ndryshosh vet\u00ebm parametrat e tij rrjetit). K\u00ebtu parashikoj v\u00ebshtir\u00ebsi me klient\u00ebt mjaft t\u00eb kujdessh\u00ebm.\u00a0<\/p>\n

Pra, pas instalimit t\u00eb agjent\u00ebve, mund t\u00eb kthehemi n\u00eb panelin Acura dhe t\u00eb shohim t\u00eb gjitha makinat tona.<\/p>\n

\"Hystax<\/a><\/noindex>
\nPasi un\u00eb tashm\u00eb kam punuar me sistemin p\u00ebr nj\u00eb koh\u00eb t\u00eb gjat\u00eb, kam makina n\u00eb gjendje t\u00eb ndryshme. T\u00eb gjitha ato jan\u00eb n\u00eb grupin Default, por ka mund\u00ebsi t\u00eb krijoni grupe t\u00eb ve\u00e7anta dhe t'i transferoni makinat sipas nevoj\u00ebs tuaj. Kjo nuk ndikon n\u00eb asgj\u00eb - \u00ebsht\u00eb thjesht nj\u00eb paraqitje logjike e t\u00eb dh\u00ebnave dhe grupimi i tyre p\u00ebr nj\u00eb pun\u00eb m\u00eb t\u00eb leht\u00eb. E para dhe m\u00eb e r\u00ebnd\u00ebsishmja q\u00eb duhet t\u00eb b\u00ebjm\u00eb pas k\u00ebsaj, \u00ebsht\u00eb t\u00eb nisim procesin e migrimit. Ne mund ta b\u00ebjm\u00eb k\u00ebt\u00eb si me forc\u00eb manualisht, ashtu edhe t\u00eb vendosim nj\u00eb orar, p\u00ebrfshir\u00eb nj\u00eb migrim masiv p\u00ebr t\u00eb gjitha makinat nj\u00ebher\u00ebsh.<\/p>\n

\"Hystax<\/a><\/noindex>
\nM\u00eb kujtohet q\u00eb Hystax \u00ebsht\u00eb pozicionuar si nj\u00eb produkt p\u00ebr migrim. Prandaj, nuk \u00ebsht\u00eb e habitshme q\u00eb p\u00ebr t\u00eb nisur makinat tona t\u00eb replikueshme, na nevojitet t\u00eb krijojm\u00eb nj\u00eb plan DR. Plani mund t\u00eb p\u00ebrgatitet p\u00ebr makinat q\u00eb tashm\u00eb jan\u00eb n\u00eb gjendjen Synced. Mund t\u00eb gjenerohet si p\u00ebr nj\u00eb VM t\u00eb ve\u00e7ant\u00eb, ashtu edhe p\u00ebr t\u00eb gjitha makinat nj\u00ebher\u00ebsh.<\/p>\n

\"Hystax<\/a><\/noindex>
\nGrupi i parametrave kur gjeneroni planin DR do t\u00eb ndryshoj\u00eb n\u00eb var\u00ebsi t\u00eb infrastruktur\u00ebs n\u00eb t\u00eb cil\u00ebn do t\u00eb migroni. P\u00ebr ambientin VMware, disponohet nj\u00eb grup minimal parametrash. Gjithashtu, Re-IP nuk mb\u00ebshtetet p\u00ebr makinat. N\u00eb k\u00ebt\u00eb plan, na interesojn\u00eb k\u00ebto pika: n\u00eb p\u00ebrshkrimin e VM parametrin \"subnet\": \"VMNetwork\", ku lidhim VM me nj\u00eb rrjet t\u00eb caktuar n\u00eb grumbull. Rank - \u00ebsht\u00eb i r\u00ebnd\u00ebsish\u00ebm kur migroni disa VM, p\u00ebrcakton renditjen e nisjes s\u00eb tyre. Flavor - p\u00ebrshkruan konfigurimin e VM, n\u00eb k\u00ebt\u00eb rast - 1CPU, 2GB RAM. N\u00eb seksionin subnets ne p\u00ebrcaktojm\u00eb se \"subnet\": \"VMNetwork\" \u00ebsht\u00eb e asociuar me rrjetin \"VM Network\" t\u00eb VMware.\u00a0<\/p>\n

Kur krijoni planin DR, nuk ka mund\u00ebsi t\u00eb \"ndar\u00eb\" disqet n\u00eb datastore t\u00eb ndryshme. Ato do t\u00eb q\u00ebndrojn\u00eb n\u00eb t\u00eb nj\u00ebjtin datastore q\u00eb \u00ebsht\u00eb p\u00ebrcaktuar p\u00ebr k\u00ebt\u00eb cloud klienti, dhe n\u00ebse keni disqe t\u00eb klasave t\u00eb ndryshme, kjo mund t\u00eb shkaktoj\u00eb disa v\u00ebshtir\u00ebsi gjat\u00eb nisjes s\u00eb makin\u00ebs, dhe pas nisjes dhe \"ndarjes\" s\u00eb VM nga Hystax, do t\u00eb k\u00ebrkoj\u00eb gjithashtu nj\u00eb migrim t\u00eb ve\u00e7ant\u00eb t\u00eb disqeve n\u00eb datastore t\u00eb nevojshme. M\u00eb pas na mbetet vet\u00ebm t\u00eb aktivizojm\u00eb planin ton\u00eb DR dhe t\u00eb presim deri sa t\u00eb ngrihen makinat tona. Procesi i konvertimit P2V\/V2V gjithashtu k\u00ebrkon koh\u00eb. N\u00eb makin\u00ebn time m\u00eb t\u00eb madhe p\u00ebr prov\u00eb me 100GB dhe tre disqe, kjo zuri maksimumi 10 minuta.<\/p>\n

\"Hystax<\/a><\/noindex>
\nPas k\u00ebsaj, duhet t\u00eb kontrolloni VM-n\u00eb e aktivizuar, sh\u00ebrbimet n\u00eb t\u00eb, koherenc\u00ebn e t\u00eb dh\u00ebnave dhe t\u00eb kryeni kontrolle t\u00eb tjera.\u00a0<\/p>\n

M\u00eb pas kemi dy rrug\u00eb:\u00a0<\/p>\n

    \n
  1. Fshij \u2013 fshi planin e DR-s\u00eb n\u00eb funksion. Ky veprim vet\u00ebm se do t\u00eb ndal\u00eb VM-n\u00eb e aktivizuar. T\u00eb dh\u00ebnat e replik\u00ebs nuk do t\u00eb humbasin.\u00a0<\/li>\n
  2. Shk\u00ebput \u2013 shk\u00ebput makin\u00ebn e replikimit nga Acura, dmth, n\u00eb thelb p\u00ebrfundon procesin e migrimit.\u00a0<\/li>\n<\/ol>\n

    \nAvantazhet e zgjidhjes:<\/strong>\u00a0<\/p>\n