{"id":35581,"date":"2019-10-31T22:05:09","date_gmt":"2019-10-31T19:05:09","guid":{"rendered":"https:\/\/prohoster.info\/blog\/southbridge-v-chelyabinske-i-bitriks-v-kubernetes\/"},"modified":"2019-10-31T22:05:09","modified_gmt":"2019-10-31T19:05:09","slug":"southbridge-v-chelyabinske-i-bitriks-v-kubernetes","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/southbridge-v-chelyabinske-i-bitriks-v-kubernetes","title":{"rendered":"Southbridge n\u00eb Chelyabinsk dhe Bitrix n\u00eb Kubernetes","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

N\u00eb Chelyabinsk po mbahet takimi i administrator\u00ebve t\u00eb sistemeve Sysadminka, dhe n\u00eb takimin e fundit un\u00eb mbajta nj\u00eb ligj\u00ebrat\u00eb rreth zgjidhjes son\u00eb p\u00ebr funksionimin e aplikacioneve n\u00eb 1C-Bitrix n\u00eb Kubernetes.<\/p>\n

<\/p>\n

Bitrix, Kubernetes, Ceph \u2014 nj\u00eb kombinim i shk\u00eblqyer?<\/p>\n

<\/p>\n

Do t'ju tregoj se si ne e nd\u00ebrtuam nj\u00eb zgjidhje funksionale nga e gjith\u00eb kjo.<\/p>\n

<\/p>\n

Le t\u00eb shkojm\u00eb!<\/p>\n

<\/p>\n

\"Southbridge<\/p>\n

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

Takimi u mbajt m\u00eb 18 prill n\u00eb Chelyabinsk. Mund t\u00eb lexoni p\u00ebr takimet tona n\u00eb Timepad<\/a><\/noindex> dhe t'i shihni ato n\u00eb YouTube<\/a><\/noindex>.<\/p>\n

<\/p>\n

N\u00ebse d\u00ebshirani t\u00eb vini me nj\u00eb ligj\u00ebrat\u00eb ose si d\u00ebgjues \u2014 jeni t\u00eb mir\u00ebpritur, shkruani n\u00eb vadim.isakanov@gmail.com dhe n\u00eb Telegram t.me\/vadimisakanov. <\/p>\n

<\/p>\n

Ligj\u00ebrata ime<\/h2>\n

<\/p>\n

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

<\/p>\n

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

<\/p>\n

Zgjidhja \u00abBitrix n\u00eb Kubernetes, versioni Southbridge 1.0\u00bb<\/h2>\n

<\/p>\n

Do flas p\u00ebr zgjidhjen ton\u00eb n\u00eb formatin \u00abp\u00ebr fillestar\u00ebt n\u00eb Kubernetes\u00bb, si \u00ebsht\u00eb b\u00ebr\u00eb n\u00eb takim. Por supozit\u00eb se fjal\u00ebt Bitrix, Docker, Kubernetes, Ceph jan\u00eb t\u00eb njohura p\u00ebr ju t\u00eb pakt\u00ebn n\u00eb nivelin e artikujve n\u00eb Wikipedia.<\/p>\n

<\/p>\n

\u00c7far\u00eb informacioni ekziston rreth Bitrix n\u00eb Kubernetes?<\/h4>\n

<\/p>\n

N\u00eb t\u00eb gjith\u00eb internetin ka shum\u00eb pak informacion rreth funksionimit t\u00eb aplikacioneve n\u00eb Bitrix n\u00eb Kubernetes.
\nGjeta vet\u00ebm k\u00ebto materiale:<\/p>\n

<\/p>\n

Ligj\u00ebrata e Aleksandrit Serbul dhe Anton Tuzlukov nga Qsoft: <\/p>\n

\n

\r\n \"Luaj\r\n
<\/div>\r\n <\/div><\/center><\/p>\n

E rekomandoj t\u00eb d\u00ebgjoni at\u00eb.<\/p>\n

<\/p>\n

Zhvillimi i nj\u00eb zgjidhjeje t\u00eb vetme nga p\u00ebrdoruesi serkyron<\/a><\/noindex> n\u00eb Habr\u00eb<\/a><\/noindex>.
\nGjeta gjithashtu nj\u00eb zgjidhje t\u00eb till\u00eb<\/a><\/noindex>.<\/p>\n

<\/p>\n

Dhe\u2026 n\u00eb thelb, kjo \u00ebsht\u00eb gjith\u00e7ka.<\/p>\n

<\/p>\n

Ju paralajm\u00ebroj, nuk e kemi verifikuar cil\u00ebsin\u00eb e zgjidhjeve n\u00eb lidhjet e m\u00ebsip\u00ebrme \ud83d\ude42
\nP\u00ebr m\u00eb tep\u00ebr, gjat\u00eb p\u00ebrgatitjes s\u00eb zgjidhjes son\u00eb kam komunikuar me Aleksandrin Serbul, ligj\u00ebrata e tij nuk ishte ende publikuar, k\u00ebshtu q\u00eb n\u00eb slajdet e mia ka nj\u00eb pik\u00eb \u00abBitrix nuk p\u00ebrdor Kubernetes\u00bb.<\/p>\n

<\/p>\n

Por p\u00ebrkundrazi, tashm\u00eb ka shum\u00eb imazhe Docker t\u00eb gatshme p\u00ebr funksionimin e Bitrix n\u00eb Docker: https:\/\/hub.docker.com\/search?q=bitrix&type=image<\/a><\/noindex> <\/p>\n

<\/p>\n

A \u00ebsht\u00eb e mjaftueshme kjo p\u00ebr t\u00eb nd\u00ebrtuar nj\u00eb zgjidhje t\u00eb plot\u00eb p\u00ebr Bitrix n\u00eb Kubernetes?
\nJo. Ka nj\u00eb num\u00ebr t\u00eb madh problemesh q\u00eb duhet t\u00eb zgjidhen.<\/p>\n

<\/p>\n

Cilat jan\u00eb problemet me Bitrix n\u00eb Kubernetes?<\/h4>\n

<\/p>\n

E para \u2014 imazhet e gatshme nga Dockerhub nuk i p\u00ebrshtaten Kubernetes<\/strong><\/p>\n

<\/p>\n

N\u00ebse duam t\u00eb nd\u00ebrtojm\u00eb nj\u00eb arkitektur\u00eb mikrosh\u00ebrbimesh (dhe zakonisht n\u00eb Kubernetes duam), aplikacioni n\u00eb Kubernetes duhet t\u00eb ndahet n\u00eb kontejner\u00eb dhe duhet t\u00eb arrijm\u00eb q\u00eb \u00e7do kontejner t\u00eb ekzekutoj\u00eb nj\u00eb funksion t\u00eb vog\u00ebl (dhe ta b\u00ebj\u00eb at\u00eb mir\u00eb). Pse vet\u00ebm nj\u00eb? N\u00ebse e themi shkurt \u2014 sa m\u00eb e thjesht\u00eb, aq m\u00eb e besueshme.
\nN\u00ebse d\u00ebshironi m\u00eb n\u00eb detaje \u2014 ju lutem shikoni k\u00ebt\u00eb artikull dhe video: https:\/\/habr.com\/ru\/company\/southbridge\/blog\/426637\/<\/a><\/noindex> <\/p>\n

<\/p>\n

Imazhet e Docker n\u00eb Dockerhub n\u00eb p\u00ebrgjith\u00ebsi jan\u00eb nd\u00ebrtuar sipas parimit \u00abt\u00eb gjitha n\u00eb nj\u00eb\u00bb, prandaj na duhej t\u00eb b\u00ebnim nj\u00eb bi\u00e7iklet\u00eb ton\u00eb dhe madje t\u00eb krijonim imazhe nga e para.<\/p>\n

<\/p>\n

E dyta \u2014 kodi i sitit rregullohet nga paneli i adminit<\/strong><\/p>\n

<\/p>\n

Krijuam nj\u00eb seksion t\u00eb ri n\u00eb sajt - kodi \u00ebsht\u00eb p\u00ebrdit\u00ebsuar (u shtua nj\u00eb direktor i quajtur si seksioni i ri).<\/p>\n

<\/p>\n

Ndryshuam pron\u00ebsit\u00eb e komponentit nga paneli i administrat\u00ebs - kodi \u00ebsht\u00eb ndryshuar.<\/p>\n

<\/p>\n

Kubernetes \u00abdefault\u00bb nuk di t\u00eb punoj\u00eb me k\u00ebt\u00eb, kontejner\u00ebt duhet t\u00eb jen\u00eb t\u00eb pandryshuesh\u00ebm (Stateless).<\/p>\n

<\/p>\n

Arsyetimi: secili kontejner (pod) n\u00eb klaster p\u00ebrpunon vet\u00ebm nj\u00eb pjes\u00eb t\u00eb trafikut. N\u00ebse ndryshoni kodin vet\u00ebm n\u00eb nj\u00eb kontejner (pod), at\u00ebher\u00eb kode t\u00eb ndryshme do t\u00eb jen\u00eb n\u00eb pod-e t\u00eb ndrysh\u00ebm, sajt do t\u00eb funksionoj\u00eb ndryshe, p\u00ebrdorues t\u00eb ndrysh\u00ebm do t'u shfaqen versione t\u00eb ndryshme t\u00eb sajtit. K\u00ebshtu nuk \u00ebsht\u00eb e mundur t\u00eb vazhdohet.<\/p>\n

<\/p>\n

E treta - nevojitet t\u00eb zgjidhet \u00e7\u00ebshtja e deploy-it.<\/strong><\/p>\n

<\/p>\n

N\u00ebse kemi nj\u00eb monolit dhe nj\u00eb server \u00abklasik\u00bb, gjith\u00e7ka \u00ebsht\u00eb shum\u00eb e thjesht\u00eb: zbatojm\u00eb nj\u00eb baz\u00eb t\u00eb re kodi, kryejm\u00eb migrimin e DB, drejtojm\u00eb trafikun n\u00eb versionin e ri t\u00eb kodit. Kalimi ndodh menj\u00ebher\u00eb.
\nN\u00ebse kemi nj\u00eb sajt n\u00eb Kubernetes, t\u00eb shp\u00ebrndar\u00eb n\u00eb mikrosh\u00ebrbime, ka shum\u00eb kontejner\u00eb me kod - oj. Duhet t\u00eb mbledhim kontejner\u00ebt me versionin e ri t\u00eb kodit, ti z\u00ebvend\u00ebsojm\u00eb ata me t\u00eb vjetr\u00ebt, t\u00eb kryejm\u00eb migrimin e DB sakt\u00eb, dhe idealisht ta b\u00ebjm\u00eb k\u00ebt\u00eb pa i v\u00ebn\u00eb re vizitor\u00ebve. Fatmir\u00ebsisht, Kubernetes na ndihmon me k\u00ebt\u00eb, duke mb\u00ebshtetur nj\u00eb s\u00ebr\u00eb llojshm\u00ebrish t\u00eb ndryshme t\u00eb deploy-it.<\/p>\n

<\/p>\n

E kat\u00ebrta - duhet t\u00eb zgjidhet \u00e7\u00ebshtja e ruajtjes s\u00eb statik\u00ebs.<\/strong><\/p>\n

<\/p>\n

N\u00ebse saiti juaj peshon \u00abvet\u00ebm\u00bb 10 gigabajt dhe ju e implementoni at\u00eb krejt\u00ebsisht n\u00eb kontejner\u00eb, do t\u00eb merrni kontejner\u00eb pesha 10 gigabajt, t\u00eb cil\u00ebt do t\u00eb implementohen p\u00ebr nj\u00eb koh\u00eb t\u00eb gjat\u00eb.
\nDuhet t\u00eb ruajm\u00eb pjes\u00ebt m\u00eb \u00abt\u00eb m\u00ebdha\u00bb t\u00eb sajtit jasht\u00eb kontejner\u00ebve, dhe lind pyetja, si t\u00eb b\u00ebjm\u00eb k\u00ebt\u00eb sakt\u00ebsisht.<\/p>\n

<\/p>\n

\u00c7far\u00eb nuk ka n\u00eb zgjidhjen ton\u00eb.<\/h4>\n

<\/p>\n

T\u00eb gjith\u00eb kodi Bitrix nuk \u00ebsht\u00eb prer\u00eb n\u00eb mikrofunksione\/mikrosh\u00ebrbime (n\u00eb m\u00ebnyr\u00eb q\u00eb regjistrimi t\u00eb jet\u00eb ve\u00e7mas, moduli i dyqanit t\u00eb internetit ve\u00e7mas, etj.). Ne ruajm\u00eb t\u00ebr\u00eb baz\u00ebn e kodit n\u00eb \u00e7do kontejner n\u00eb m\u00ebnyr\u00eb t\u00eb plot\u00eb.<\/p>\n

<\/p>\n

Ne gjithashtu nuk ruajm\u00eb baz\u00ebn e t\u00eb dh\u00ebnave n\u00eb Kubernetes (kalim, un\u00eb gjithmon\u00eb kam implementuar zgjidhje me baz\u00ebn e t\u00eb dh\u00ebnave n\u00eb Kubernetes p\u00ebr mjediset e zhvilluesve, por jo p\u00ebr prodhim).<\/p>\n

<\/p>\n

Administrator\u00ebt e sajtit gjithsesi do ta ndjejn\u00eb se saiti funksionon n\u00eb Kubernetes. Funksioni \u00abkontrolli i sistemit\u00bb punon n\u00eb m\u00ebnyr\u00eb t\u00eb parregullt, p\u00ebr t\u00eb redaktuar kodin e saj do t\u00eb duhet s\u00eb pari t\u00eb shtypni butonin \u00abdua t\u00eb redaktoj kodin\u00bb.<\/p>\n

<\/p>\n

Kemi p\u00ebrballur me problemet, kemi r\u00ebn\u00eb dakord p\u00ebr nevoj\u00ebn p\u00ebr implementimin e mikrosh\u00ebrbimeve, dhe q\u00ebllimi \u00ebsht\u00eb i qart\u00eb \u2014 t\u00eb kemi nj\u00eb sistem funksional p\u00ebr pun\u00ebn e aplikacioneve n\u00eb Bitrix n\u00eb Kubernetes, duke ruajtur mund\u00ebsit\u00eb e Bitrix dhe avantazhet e Kubernetes. Fillojm\u00eb implementimin.<\/p>\n

<\/p>\n

Arkitektura<\/h4>\n

<\/p>\n

Shum\u00eb \u00abpunonj\u00ebs\u00bb pod\u00ebsh me server web (punonj\u00ebsit).
\nNj\u00eb pod me detyra cron (absolutisht vet\u00ebm nj\u00eb).
\nNj\u00eb pod upgrade p\u00ebr redaktimin e kodit t\u00eb faqes nga paneli administrativ (po ashtu, absolutisht vet\u00ebm nj\u00eb).<\/p>\n

<\/p>\n

\"Southbridge<\/p>\n

<\/p>\n

Po zgjidhim pyetje:<\/p>\n

<\/p>\n