{"id":37745,"date":"2019-10-31T22:19:28","date_gmt":"2019-10-31T19:19:28","guid":{"rendered":"https:\/\/prohoster.info\/blog\/balansirovka-nagruzki-v-openstack-chast-2\/"},"modified":"2019-10-31T22:19:28","modified_gmt":"2019-10-31T19:19:28","slug":"balansirovka-nagruzki-v-openstack-chast-2","status":"publish","type":"post","link":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/balansirovka-nagruzki-v-openstack-chast-2","title":{"rendered":"Koormuse tasakaalustamine Openstackis (Osa 2)","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Uues <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/rostelecom\/blog\/461483\/\">eelmisel artiklil<\/a><\/noindex> Oleme r\u00e4\u00e4kinud Watcher'i kasutamise katsetest ja esitanud katsetuste aruande. Selliseid katseid teeme regulaarselt k\u00f5rgema ettev\u00f5tte v\u00f5i teenusepakkuja pilve tasakaalustamiseks ja muude kriitiliste funktsioonide jaoks.<\/p>\n<p>\u00dclesande k\u00f5rge keerukus v\u00f5ib n\u00f5uda meie projekti kirjeldamiseks mitmeid artikleid. T\u00e4na avaldame teise artikli ts\u00fcklist, mis on p\u00fchendatud virtuaalmasinate tasakaalustamisele pilves. <\/p>\n<h3>Veidi terminoloogiat<\/h3>\n<p>\nEttev\u00f5te VMware tutvustas DRS-i (Distributed Resource Scheduler), et tasakaalustada koormust nende v\u00e4lja t\u00f6\u00f6tatud ja pakutavates virtuaalisuse keskkondades. <\/p>\n<p>Nagu kirjutab <noindex><a rel=\"nofollow\" href=\"https:\/\/searchvmware.techtarget.com\/definition\/VMware-DRS\">searchvmware.techtarget.com\/definition\/VMware-DRS<\/a><\/noindex><br \/>\n<i>\u201eVMware DRS (jaotatud ressursi planeerija) on t\u00f6\u00f6riist, mis tasakaalustab arvutuskoormust kergesti kergesti kergelt kergesti kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt kergelt.<\/p>\n<p>VMware DRS-i abil saavad kasutajad seadistada reegleid f\u00fc\u00fcsiliste ressursside jaotamiseks virtuaalmasinate vahel. T\u00f6\u00f6riista saab seadistada k\u00e4sitsi v\u00f5i automaatse juhtimise jaoks. VMware ressursigrupid v\u00f5ivad olla h\u00f5lpsasti lisatud, eemaldatud v\u00f5i \u00fcmber korraldatud. Soovi korral v\u00f5ivad ressursigrupid olla erinevate \u00e4ri\u00fcksuste vahel isoleeritud. Kui mingil virtuaalmasinal on koormus j\u00e4rsult muutumas, siis VMware DRS jaotab virtuaalmasinad f\u00fc\u00fcsiliste serverite vahel \u00fcmber. Kui kogu koormus v\u00e4heneb, v\u00f5ivad m\u00f5ned f\u00fc\u00fcsilised serverid ajutiselt v\u00e4lja l\u00fclitada ja koormus v\u00f5ib konsolideerida.<\/i><\/p>\n<h3>Miks on tasakaalustamine vajalik?<\/h3>\n<p>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nMeie arvates on DRS kohustuslik pilve funktsioon, kuigi see ei t\u00e4henda, et DRS-i tuleb alati ja igal pool kasutada. K\u00f5ne alla v\u00f5ivad tulla erinevad n\u00f5uded DRS-ile ja tasakaalustamismeetoditele s\u00f5ltuvalt pilve otstarbeks ja vajadustest. V\u00f5ib-olla on olukordi, kus tasakaalustamine ei ole vajalik v\u00f5i isegi kahjulik.<\/p>\n<p>Et paremini m\u00f5ista, kus ja millistele klientidele on DRS vajalik, vaatame nende eesm\u00e4rke ja \u00fclesandeid. Pilved jagunevad avalikeks ja privaatseteks. Siin on peamised erinevused nende pilvede ja klientide eesm\u00e4rkide vahel.<\/p>\n<p>Privaatpilved \/ Suured ettev\u00f5tted<br \/>\nAvalikud pilved \/ Keskmine ja v\u00e4ike \u00e4ri, inimesed<\/p>\n<p>Peamine kriteerium ja operaatori eesm\u00e4rgid<br \/>\nUsaldusv\u00e4\u00e4rse teenuse v\u00f5i toote pakkumine<br \/>\nTeenuste kogumismoega tegelemine konkurentsitihedal turul<\/p>\n<p>Teenuse n\u00f5uded<br \/>\nUsaldusv\u00e4\u00e4rsus k\u00f5igil tasanditel ja s\u00fcsteemi k\u00f5ikides elementides<\/p>\n<p>Tagatud j\u00f5udlus<\/p>\n<p>Virtuaalmasinate prioritiseerimine mitmesse kategooriasse\u00a0<\/p>\n<p>Teabe ja f\u00fc\u00fcsiline andmete turvalisus<\/p>\n<p>SLA ja \u00f6\u00f6p\u00e4evaringne tugi<br \/>\nTeenuse saamise maksimaalne lihtsus<\/p>\n<p>Suhteliselt lihtsad teenused<\/p>\n<p>Andmete eest vastutab klient<\/p>\n<p>Virtuaalmasinate prioritiseerimine ei ole vajalik<\/p>\n<p>Teabe turvalisus standardteenuste tasemel, vastutus kliendil<\/p>\n<p>S\u00fcsteemi t\u00f5rkeid v\u00f5ib esineda<\/p>\n<p>SLA-d ei ole, kvaliteeti ei garanteerita<\/p>\n<p>Tugi e-posti teel<\/p>\n<p>Varundamine ei ole kohustuslik<\/p>\n<p>Kliendi erip\u00e4ra<br \/>\nV\u00e4ga lai rakenduste spekter.<\/p>\n<p>P\u00e4randrakendused, mis on ettev\u00f5ttes edasi antud.<\/p>\n<p>Kliendi jaoks keerukad kohandatud arhitektuurid.<\/p>\n<p>Affiniteedi reeglid.<\/p>\n<p>Tarkvara t\u00f6\u00f6tab katkestusteta 7x24 re\u017eiimis.\u00a0<\/p>\n<p>Varundamisseadmed \"reaalajas\".<\/p>\n<p>Klientide prognoositav ts\u00fckliline koormus.<br \/>\nStandardrakendused \u2013 v\u00f5rgu tasakaalustamine, Apache, WEB, VPN, SQL<\/p>\n<p>Rakenduse peatamine on v\u00f5imalik teatud ajaks<\/p>\n<p>V\u00f5imalik on virtuaalmasinate suvaline jaotus pilves<\/p>\n<p>Varundamine kliendi poolt<\/p>\n<p>Prognoositav statistiliselt keskmine koormus suure hulga klientide korral.<\/p>\n<p>Tagaj\u00e4rjed arhitektuurile<br \/>\nGeoklusterdamine<\/p>\n<p>Keskne v\u00f5i jaotatud andmesalvestus<\/p>\n<p>Reserveeritud DR<br \/>\nAndmete kohalik talletamine arvutuspunktides<\/p>\n<p>Tasakaalustamise eesm\u00e4rgid<br \/>\nKoormuse \u00fchtlane jaotamine<\/p>\n<p>Rakenduste maksimaalne reageerimisv\u00f5ime\u00a0<\/p>\n<p>Minimaalne viivitus tasakaalustamisel<\/p>\n<p>Tasakaalustamine ainult selgelt vajaliku korral<\/p>\n<p>Osade seadmete v\u00e4lja viimine hooldust\u00f6\u00f6d teostama<br \/>\nTeenuse ja operaatori kulude v\u00e4hendamine\u00a0<\/p>\n<p>Osade ressursside v\u00e4ljal\u00fclitamine madala koormuse korral<\/p>\n<p>Energiakulu kokkuhoid<\/p>\n<p>Kulude v\u00e4hendamine personalile<\/p>\n<h3> J\u00f5udsime j\u00e4rgmistele j\u00e4reldustele:<\/h3>\n<p>\n<b>Privaatsete pilvede jaoks<\/b>, mida pakuvad suured korporatiivsed kliendid, DRS v\u00f5ib rakenduda j\u00e4rgmiste piirangute kohaselt:<\/p>\n<ul>\n<li>teabe turvalisus ja affiniteedi reeglite arvesse v\u00f5tmine tasakaalustamisel;<\/li>\n<li>reservis peab olema piisav ressursside maht h\u00e4daolukordade korral;<\/li>\n<li>virtuaalmasinate andmed paiknevad kesksetes v\u00f5i jaotatud andmesalvestustes;<\/li>\n<li>ajastatud haldust\u00f6\u00f6de, varukoopiate ja koormuse jaotamise lahtiseletamine;<\/li>\n<li>koormuse jaotamine ainult kliendi hostide r\u00fchmas;<\/li>\n<li>koormuse jaotamine ainult siis, kui tasakaal on tugevasti h\u00e4iritud, k\u00f5ige t\u00f5husamad ja turvalisemad VM-i migreerimised (sest migreerimine v\u00f5ib l\u00f5ppeda eba\u00f5nnestumisena);<\/li>\n<li>koormuse jaotamine 'rahulike' virtuaalmasinate p\u00f5hjal (igal juhul 'm\u00fcrarikka' virtuaalmasina migreerimine v\u00f5ib v\u00f5tta kaua aega);<\/li>\n<li>koormuse jaotamine 'kulude' p\u00f5hjal \u2014 koormus salvestusseadmetele ja v\u00f5rgule (kohandatud arhitektuuride puhul suurematele klientidele);<\/li>\n<li>koormuse jaotamine arvestades iga VM-i individuaalseid k\u00e4itumismustreid;<\/li>\n<li>koormuse jaotamine oleks soovitatav teha t\u00f6\u00f6v\u00e4lisel ajal (\u00f6\u00f6sel, n\u00e4dalavahetustel, p\u00fchadel).<\/li>\n<\/ul>\n<p>\n<b>Avalike pilvede jaoks<\/b>, mis pakuvad teenuseid v\u00e4ikestele klientidele, v\u00f5ivad DRS-i rakendused olla palju sagedamad, laiemate v\u00f5imalustega:<\/p>\n<ul>\n<li>turvas\u00e4tete ja affiniteedieeskirjade puudumine; <\/li>\n<li>koormuse jaotamine pilve piires;<\/li>\n<li>koormuse jaotamine igal m\u00f5istlikul ajal;<\/li>\n<li>koormuse jaotamine igasuguste VM-ide vahel; <\/li>\n<li>koormuse jaotamine 'm\u00fcrarikka' virtuaalmasina p\u00f5hjal (et mitte segada teisi); <\/li>\n<li>virtuaalmasinate andmed asuvad sageli kohalikul kettal;<\/li>\n<li>arvestades salvestusseadmete ja v\u00f5rgu keskmist j\u00f5udlust (pilve arhitektuur on \u00fchtne);<\/li>\n<li>koormuse jaotamine \u00fcldiste reeglite ja olemasoleva keskkonna k\u00e4itumise statistika p\u00f5hjal.<\/li>\n<\/ul>\n<p><\/p>\n<h2>Probleemi keerukus<\/h2>\n<p>\nKoormuse jaotamise keerukus seisneb selles, et DRS peab t\u00f6\u00f6tama suure arvu m\u00e4\u00e4ramatute teguritega:<\/p>\n<ul>\n<li>kliendi info s\u00fcsteemide iga\u00fche kasutajate k\u00e4itumine;<\/li>\n<li>infosis\u00fcsteemide serverite t\u00f6\u00f6 algoritmid;<\/li>\n<li>andmebaasi serverite k\u00e4itumine;<\/li>\n<li>koormus arvutusressurssidele, salvestusseadmetele, v\u00f5rgule; <\/li>\n<li>serverite omavaheline suhtlemine ressursside p\u00e4rast v\u00f5itlemisel.<\/li>\n<\/ul>\n<p>\nPaljude virtuaalserverite rakenduste ja andmebaaside koormus avaldub ajas, tagaj\u00e4rjed v\u00f5ivad ilmneda ja kattuda \u00fcksteisega ettearvamatute m\u00f5judega ettearvamatul ajal. Isegi suhteliselt lihtsate protsesside (nt mootori juhtimine, kodu veesoojenduss\u00fcsteem) juhtimise jaoks peab automaatikaettev\u00f5ttes olema kasutada keerulisi <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/%D0%9F%D0%98%D0%94-%D1%80%D0%B5%D0%B3%D1%83%D0%BB%D1%8F%D1%82%D0%BE%D1%80\">proportsionaalne-integraalne-differentseerivad <\/a><\/noindex>tagasiside algoritme. <\/p>\n<p><img decoding=\"async\" alt=\"Koormuse tasakaalustamine Openstackis (Osa 2)\" src=\"\/wp-content\/uploads\/2019\/09\/5270ddb943db9b4921a887e67c4f2a8f.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nMeie \u00fclesanne on mitmeid j\u00e4rke keerulisem ja on oht, et s\u00fcsteem ei suuda m\u00f5istliku aja jooksul koormust tasakaalustada seatud v\u00e4\u00e4rtustele, isegi kui kasutajaid ei esine v\u00e4list m\u00f5ju. <\/p>\n<p><img decoding=\"async\" alt=\"Koormuse tasakaalustamine Openstackis (Osa 2)\" src=\"\/wp-content\/uploads\/2019\/09\/5214b3af233e7c718fd40e6336472903.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h2>Meie arenduste ajalugu<\/h2>\n<p>\nSelle probleemiga tegelemiseks otsustasime mitte alustada nullist, vaid tugineda olemasolevale kogemusele ja hakkasime suhtlema alal kogenud spetsialistidega. \u00d5nneks kattus meie arusaam probleemist t\u00e4ielikult. <\/p>\n<h3>Etapp 1<\/h3>\n<p>\nKasutame s\u00fcsteemi, mis p\u00f5hineb n\u00e4rviv\u00f5rkude tehnoloogial, ja proovime selle alusel meie ressursse optimeerida.<\/p>\n<p>Selle etapi huvi seisnes uue tehnoloogia katsetamises ning selle olulisus seisnes mittestandardses l\u00e4henemisviisis \u00fclesande lahendamisel, kus sarnastes tingimustes on standardsed l\u00e4henemisviisid praktiliselt ammendunud.<\/p>\n<p>K\u00e4ivitame s\u00fcsteemi ja meil t\u00f5esti hakkas tasakaalustus t\u00f6\u00f6le. Meie pilve ulatus ei lubanud meil saada optimistlikke tulemusi, nagu arendajad olid v\u00e4itnud, kuid oli n\u00e4ha, et tasakaalustus t\u00f6\u00f6tab. <\/p>\n<p>Selle juures olid meil t\u00f5sised piirangud:<\/p>\n<ul>\n<li>N\u00e4rviv\u00f5rgu koolitamiseks on vajalik, et virtuaalmasinad t\u00f6\u00f6taksid ilma m\u00e4rkimisv\u00e4\u00e4rsete muutusteta n\u00e4dalaid v\u00f5i kuid.<\/li>\n<li>Algoritm on m\u00f5eldud optimeerimiseks l\u00e4htudes varasemate \"ajalooliste\" andmete anal\u00fc\u00fcsist.<\/li>\n<li>N\u00e4rviv\u00f5rgu koolitamiseks on vajalik piisavalt suur andmehulk ja arvutusv\u00f5ime. <\/li>\n<li>Optimeerimist ja tasakaalustamist saab teha suhteliselt harva \u2013 paar korda tunnis, mis on ilmselgelt ebapiisav. <\/li>\n<\/ul>\n<p><\/p>\n<h3>Etapp 2<\/h3>\n<p>\nKuna meid ei rahuldanud olukord, otsustasime s\u00fcsteemi modifitseerida ja sellele vastata <b>peamisele k\u00fcsimusele<\/b> \u2013 kellele me seda valmistame?<\/p>\n<p>Esmalt \u2013 ettev\u00f5tte klientidele. See t\u00e4hendab, et vajame s\u00fcsteemi, mis t\u00f6\u00f6tab kiiresti, koos nende ettev\u00f5tte piirangutega, mis ainult lihtsustavad elluviimist.<\/p>\n<p><b>Teine k\u00fcsimus<\/b> \u2013 mida m\u00f5ista s\u00f5na \"kiiresti\" all? L\u00fchikeste arutelude tulemusena otsustasime, et saame l\u00e4htuda reageerimise ajast 5 \u2013 10 minutit, et l\u00fchiajalised h\u00fcpped ei h\u00e4iriks s\u00fcsteemi.<\/p>\n<p><b>Kolmas k\u00fcsimus<\/b> \u2013 kui palju servereid tuleks tasakaalustada?<br \/>\nSee, this issue resolved itself. Typically, clients do not make server aggregates very large, and this aligns with the recommendations in the article to limit aggregates to 30-40 servers.<\/p>\n<p>Furthermore, by segmenting the server pool, we simplify the task for the balancing algorithm.<\/p>\n<p><b>The fourth issue<\/b> \u2013 how suitable is the neural network for us with its long training process and infrequent balancing? We decided to opt out of it in favor of simpler operational algorithms, to achieve results in seconds. <\/p>\n<p><img decoding=\"async\" alt=\"Koormuse tasakaalustamine Openstackis (Osa 2)\" src=\"\/wp-content\/uploads\/2019\/09\/73fb927b304ca5d61090a5c045568931.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nYou can learn about the system that uses such algorithms and its drawbacks <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/416391\/\">siit <\/a><\/noindex><\/p>\n<p>We implemented and launched this system and received promising results \u2013 it now regularly analyzes the cloud load and provides recommendations for moving virtual machines, which are largely correct. Even now, it's clear that we can achieve a 10-15% resource release for new virtual machines while improving the performance of existing ones.<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habrastorage.org\/webt\/ie\/ky\/wa\/iekywainupnidp_73j55hc1dbnw.png\"><img decoding=\"async\" alt=\"Koormuse tasakaalustamine Openstackis (Osa 2)\" src=\"\/wp-content\/uploads\/2019\/09\/f1f0919ae653dc9b8c78b4d32d839313.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/p>\n<p>Upon detecting an imbalance in RAM or CPU, the system sends commands to the Tionix scheduler to perform live migration of the required virtual machines. As seen in the monitoring system, a virtual machine moved from one (upper) host to another (lower) host and freed memory on the upper host (highlighted in yellow circles), occupying it accordingly on the lower one (highlighted in white circles).<\/p>\n<p>Currently, we are trying to evaluate the effectiveness of the existing algorithm more accurately and are looking for possible errors within it.<\/p>\n<h3>Etapp 3<\/h3>\n<p>\nIt would seem that we could relax at this point, wait for proven efficiency, and close the topic.<br \/>\nBut we are pushed towards conducting a new phase by the following clear optimization opportunities<\/p>\n<ol>\n<li>Statistics, for example, <noindex><a rel=\"nofollow\" href=\"https:\/\/www.cpubenchmark.net\/multi_cpu.html\">siit <\/a><\/noindex>ja <noindex><a rel=\"nofollow\" href=\"https:\/\/www.cpubenchmark.net\/high_end_cpus.html\">siit <\/a><\/noindex>show that dual- and quad-processor systems are significantly lower in performance compared to single-processor systems. This means that all users receive much lower returns from purchased multi-processor systems in terms of CPU, RAM, SSD, LAN, FC, compared to single-processor ones. <\/li>\n<li>The resource schedulers themselves can operate with serious errors, <noindex><a rel=\"nofollow\" href=\"https:\/\/www.ece.ubc.ca\/~sasha\/papers\/eurosys16-final29.pdf\">here is one of the articles<\/a><\/noindex> sellel teemal. <\/li>\n<li>Intel ja AMD pakuvad RAM ja vahem\u00e4lu j\u00e4lgimise tehnoloogiaid, mis v\u00f5imaldavad uurida virtuaalmasinate k\u00e4itumist ja paigutada neid nii, et \"m\u00fcra\" naabrid ei segaks \"rahulikke\" virtuaalmasinaid. <\/li>\n<li>Parameetrite komplekti laienemine (v\u00f5rk, salvestusseade, virtuaalmasina prioriteet, migratsiooni maksumus, migratsiooni valmisolek).<\/li>\n<\/ol>\n<p><\/p>\n<h2>Kokkuv\u00f5ttes<\/h2>\n<p>\nMeie t\u00f6\u00f6 tulemuseks tasakaalustamisalgoritmide t\u00e4iustamisel on selge j\u00e4reldus, et t\u00e4nu kaasaegsetele algoritmidele on v\u00f5imalik saavutada olulisi ressursside (25-30%) optimeerimist andmekeskustes ja samal ajal parandada klienditeeninduse kvaliteeti.<\/p>\n<p>Neuraalv\u00f5rkudel p\u00f5hinev algoritm on kahtlemata huvitav, kuid vajab edasist arendamist ning olemasolevate piirangute t\u00f5ttu ei sobi see selliste \u00fclesannete lahendamiseks, mis on iseloomulikud privaatsetele pilvedele. Samas on avalikes suurtes pilvedes n\u00e4idanud algoritm h\u00e4id tulemusi.<\/p>\n<p>Protsessorite, planeerijate ja k\u00f5rgema taseme tasakaalustamise v\u00f5imaluste kohta r\u00e4\u00e4gime j\u00e4rgnevates artiklites.<br \/>\n<br \/>Allikas: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/rostelecom\/blog\/465715\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0412 \u043f\u0440\u043e\u0448\u043b\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435 \u043c\u044b \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u0430\u043b\u0438 \u043e \u043f\u043e\u043f\u044b\u0442\u043a\u0430\u0445 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c Watcher \u0438 \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u0438\u043b\u0438 \u043e\u0442\u0447\u0435\u0442 \u0438\u0441\u043f\u044b\u0442\u0430\u043d\u0438\u0439. \u0422\u0430\u043a\u0438\u0435 \u0438\u0441\u043f\u044b\u0442\u0430\u043d\u0438\u044f \u043c\u044b \u043f\u0435\u0440\u0438\u043e\u0434\u0438\u0447\u0435\u0441\u043a\u0438 \u043f\u0440\u043e\u0432\u043e\u0434\u0438\u043c \u0434\u043b\u044f \u0431\u0430\u043b\u0430\u043d\u0441\u0438\u0440\u043e\u0432\u043a\u0438 \u0438 \u0434\u0440\u0443\u0433\u0438\u0445 \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0445 \u0444\u0443\u043d\u043a\u0446\u0438\u0439 \u0431\u043e\u043b\u044c\u0448\u043e\u0433\u043e \u043a\u043e\u0440\u043f\u043e\u0440\u0430\u0442\u0438\u0432\u043d\u043e\u0433\u043e \u0438\u043b\u0438 \u043e\u043f\u0435\u0440\u0430\u0442\u043e\u0440\u0441\u043a\u043e\u0433\u043e \u043e\u0431\u043b\u0430\u043a\u0430. \u0412\u044b\u0441\u043e\u043a\u0430\u044f \u0441\u043b\u043e\u0436\u043d\u043e\u0441\u0442\u044c \u0440\u0435\u0448\u0430\u0435\u043c\u043e\u0439 \u0437\u0430\u0434\u0430\u0447\u0438, \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e, \u043f\u043e\u0442\u0440\u0435\u0431\u0443\u0435\u0442 \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u0438\u0445 \u0441\u0442\u0430\u0442\u0435\u0439 \u0434\u043b\u044f \u043e\u043f\u0438\u0441\u0430\u043d\u0438\u044f \u043d\u0430\u0448\u0435\u0433\u043e \u043f\u0440\u043e\u0435\u043a\u0442\u0430. \u0421\u0435\u0433\u043e\u0434\u043d\u044f \u043c\u044b \u043f\u0443\u0431\u043b\u0438\u043a\u0443\u0435\u043c \u0432\u0442\u043e\u0440\u0443\u044e \u0441\u0442\u0430\u0442\u044c\u044e \u0446\u0438\u043a\u043b\u0430, \u043f\u043e\u0441\u0432\u044f\u0449\u0435\u043d\u043d\u0443\u044e \u0431\u0430\u043b\u0430\u043d\u0441\u0438\u0440\u043e\u0432\u043a\u0435 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u044b\u0445 \u043c\u0430\u0448\u0438\u043d \u0432 \u043e\u0431\u043b\u0430\u043a\u0435. \u041d\u0435\u043c\u043d\u043e\u0433\u043e \u0442\u0435\u0440\u043c\u0438\u043d\u043e\u043b\u043e\u0433\u0438\u0438 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":28330,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-37745","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.1.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0412 \u043f\u0440\u043e\u0448\u043b\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435 \u043c\u044b \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u0430\u043b\u0438 \u043e \u043f\u043e\u043f\u044b\u0442\u043a\u0430\u0445 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c Watcher \u0438 \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u0438\u043b\u0438 \u043e\u0442\u0447\u0435\u0442 \u0438\u0441\u043f\u044b\u0442\u0430\u043d\u0438\u0439.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/balansirovka-nagruzki-v-openstack-chast-2\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.1.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"et_EE\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u0411\u0430\u043b\u0430\u043d\u0441\u0438\u0440\u043e\u0432\u043a\u0430 \u043d\u0430\u0433\u0440\u0443\u0437\u043a\u0438 \u0432 Openstack (\u0427\u0430\u0441\u0442\u044c 2) | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0412 \u043f\u0440\u043e\u0448\u043b\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435 \u043c\u044b \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u0430\u043b\u0438 \u043e \u043f\u043e\u043f\u044b\u0442\u043a\u0430\u0445 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c Watcher \u0438 \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u0438\u043b\u0438 \u043e\u0442\u0447\u0435\u0442 \u0438\u0441\u043f\u044b\u0442\u0430\u043d\u0438\u0439.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/balansirovka-nagruzki-v-openstack-chast-2\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-10-31T19:19:28+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T19:19:28+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Lastesurve tasakaalustamine OpenStackis (osa 2) | ProHoster","description":"Eelmises artiklis r\u00e4\u00e4kisime katsetest kasutada Watcherit ja esitasime testimise aruande.","canonical_url":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/balansirovka-nagruzki-v-openstack-chast-2","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"et_EE","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0411\u0430\u043b\u0430\u043d\u0441\u0438\u0440\u043e\u0432\u043a\u0430 \u043d\u0430\u0433\u0440\u0443\u0437\u043a\u0438 \u0432 Openstack (\u0427\u0430\u0441\u0442\u044c 2) | ProHoster","og:description":"\u0412 \u043f\u0440\u043e\u0448\u043b\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435 \u043c\u044b \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u0430\u043b\u0438 \u043e \u043f\u043e\u043f\u044b\u0442\u043a\u0430\u0445 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c Watcher \u0438 \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u0438\u043b\u0438 \u043e\u0442\u0447\u0435\u0442 \u0438\u0441\u043f\u044b\u0442\u0430\u043d\u0438\u0439.","og:url":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/balansirovka-nagruzki-v-openstack-chast-2","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T19:19:28+00:00","article:modified_time":"2019-10-31T19:19:28+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37745","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-23 19:08:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:21:23","updated":"2026-01-23 19:08:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/37745","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/comments?post=37745"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/37745\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media\/28330"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media?parent=37745"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/categories?post=37745"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/tags?post=37745"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}