{"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\/sv\/blog\/administrirovanie\/southbridge-v-chelyabinske-i-bitriks-v-kubernetes","title":{"rendered":"Southbridge i Tjelyabinsk och Bitrix i Kubernetes","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

I Chelyabinsk, meetups for system administrators Sysadminka are taking place, and at the last one, I presented on our solution for running applications on 1C-Bitrix in Kubernetes.<\/p>\n

<\/p>\n

Bitrix, Kubernetes, Ceph \u2014 a great mix?<\/p>\n

<\/p>\n

I'll explain how we put all of this together into a working solution.<\/p>\n

<\/p>\n

L\u00e5t oss k\u00f6ra!<\/p>\n

<\/p>\n

\"Southbridge<\/p>\n

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

The meetup took place on April 18 in Chelyabinsk. You can read about our meetups in Timepad<\/a><\/noindex> and watch on YouTube<\/a><\/noindex>.<\/p>\n

<\/p>\n

If you want to join us as a speaker or as an attendee, feel free to write to vadim.isakanov@gmail.com and on Telegram t.me\/vadimisakanov. <\/p>\n

<\/p>\n

My presentation<\/h2>\n

<\/p>\n

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

<\/p>\n

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

<\/p>\n

Solution \"Bitrix in Kubernetes, version Southbridge 1.0\"<\/h2>\n

<\/p>\n

I will discuss our solution in a \"for beginners in Kubernetes\" format, as it was done at the meetup. However, I assume that you are at least familiar with the terms Bitrix, Docker, Kubernetes, and Ceph at the Wikipedia article level.<\/p>\n

<\/p>\n

What is actually available regarding Bitrix in Kubernetes?<\/h4>\n

<\/p>\n

There is very little information on the internet about running applications on Bitrix in Kubernetes.
\nI found only the following materials:<\/p>\n

<\/p>\n

Presentation by Alexander Serbul, 1C-Bitrix, and Anton Tuzlukov from Qsoft: <\/p>\n

\n

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

I recommend listening to it.<\/p>\n

<\/p>\n

Development of a solution from a user serkyron<\/a><\/noindex> I detta omr\u00e5de har ocks\u00e5 AI-system n\u00e5tt fram. Smarta algoritmer f\u00f6rutsp\u00e5r serverfel genom att analysera deras \"beteende\". Till exempel, f\u00f6retaget Litbit<\/a><\/noindex>.
\nI also found such a solution<\/a><\/noindex>.<\/p>\n

<\/p>\n

And... that's basically it.<\/p>\n

<\/p>\n

I warn you, we haven't checked the quality of the solutions linked above \ud83d\ude42
\nBy the way, while preparing our solution, I communicated with Alexander Serbul, and at that time his presentation wasn't available yet, so there is a point in my slides stating that \"Bitrix does not use Kubernetes.\"<\/p>\n

<\/p>\n

But there are already many ready-made Docker images for running Bitrix in Docker: https:\/\/hub.docker.com\/search?q=bitrix&type=image<\/a><\/noindex> <\/p>\n

<\/p>\n

Is this enough to create a full-fledged solution for Bitrix in Kubernetes?
\nNo. There are a lot of problems that need to be solved.<\/p>\n

<\/p>\n

What are the problems with Bitrix in Kubernetes?<\/h4>\n

<\/p>\n

The first is that the ready-made images from Dockerhub are not suitable for Kubernetes.<\/strong><\/p>\n

<\/p>\n

If we want to build a microservices architecture (which we usually want to do in Kubernetes), you need to break the application down into containers and ensure that each container performs one small function (and does it well). Why only one? In short \u2014 the simpler, the more reliable.
\nIf you want a longer explanation \u2014 please take a look at this article and video: https:\/\/habr.com\/ru\/company\/southbridge\/blog\/426637\/<\/a><\/noindex> <\/p>\n

<\/p>\n

Docker images on Dockerhub are mainly built on the principle of \"everything in one\", so we had to reinvent the wheel and even create images from scratch.<\/p>\n

<\/p>\n

The second is that the website code is modified from the admin panel.<\/strong><\/p>\n

<\/p>\n

Vi har skapat en ny sektion p\u00e5 webbplatsen - koden har uppdaterats (en katalog med namnet p\u00e5 den nya sektionen har lagts till).<\/p>\n

<\/p>\n

Egenskaperna f\u00f6r komponenten har \u00e4ndrats fr\u00e5n administrationspanelen - koden har f\u00f6r\u00e4ndrats.<\/p>\n

<\/p>\n

Kubernetes kan inte arbeta med det h\u00e4r som standard, containrar m\u00e5ste vara of\u00f6r\u00e4nderliga (Stateless).<\/p>\n

<\/p>\n

Orsaken: varje container (pod) i klustret hanterar endast en del av trafiken. Om koden \u00e4ndras endast i en container (pod), kommer koden att vara olika i olika pods, webbplatsen kommer att fungera olika, olika anv\u00e4ndare f\u00e5r se olika versioner av webbplatsen. S\u00e5 kan vi inte ha det.<\/p>\n

<\/p>\n

Det tredje - vi m\u00e5ste ta itu med fr\u00e5gan om utplacering.<\/strong><\/p>\n

<\/p>\n

Om vi har en monolit och en \"klassisk\" server \u00e4r allt ganska enkelt: vi rullar ut en ny kodbas, genomf\u00f6r databasmigrering, och dirigerar trafiken till den nya versionen av koden. Omkopplingen sker omedelbart.
\nOm vi har en webbplats i Kubernetes, uppdelad i mikrotj\u00e4nster, och det finns m\u00e5nga containrar med kod - oj. Vi m\u00e5ste bygga containrar med den nya versionen av koden, rulla ut dem ist\u00e4llet f\u00f6r de gamla, utf\u00f6ra databasmigreringen korrekt, och helst g\u00f6ra detta utan att bes\u00f6karna m\u00e4rker det. Lyckligtvis hj\u00e4lper Kubernetes oss med detta, med en m\u00e4ngd olika typer av utplacering.<\/p>\n

<\/p>\n

Det fj\u00e4rde - vi m\u00e5ste ta itu med fr\u00e5gan om lagring av statiska filer.<\/strong><\/p>\n

<\/p>\n

Om din webbplats \"bara\" v\u00e4ger 10 gigabyte och du rullar ut den helt i containrar, f\u00e5r du containrar som v\u00e4ger 10 gigabyte, som kommer att ta en evighet att distribuera.
\nDe tyngsta delarna av webbplatsen m\u00e5ste lagras utanf\u00f6r containrarna, och fr\u00e5gan \u00e4r hur man g\u00f6r detta p\u00e5 r\u00e4tt s\u00e4tt.<\/p>\n

<\/p>\n

Vad som saknas i v\u00e5r l\u00f6sning.<\/h4>\n

<\/p>\n

Hela koden f\u00f6r Bitrix \u00e4r inte uppdelad p\u00e5 mikro-funktioner\/mikrotj\u00e4nster (s\u00e5 att registrering \u00e4r separat, modulen f\u00f6r e-handeln separat, och s\u00e5 vidare). Vi lagrar hela kodbasen i varje container i sin helhet.<\/p>\n

<\/p>\n

Vi lagrar \u00e4ven inte databasen i Kubernetes (jag har anv\u00e4nt l\u00f6sningar med databasen i Kubernetes f\u00f6r utvecklarmilj\u00f6er, men inte f\u00f6r produktion).<\/p>\n

<\/p>\n

Webbplatsens administrat\u00f6rer kommer att m\u00e4rka att webbplatsen arbetar i Kubernetes. Funktionen \"systemkontroll\" fungerar inte korrekt, f\u00f6r att redigera koden p\u00e5 webbplatsen fr\u00e5n administrationspanelen m\u00e5ste man f\u00f6rst klicka p\u00e5 knappen \"jag vill redigera koden\".<\/p>\n

<\/p>\n

Problemmerne er blevet l\u00f8st, behovet for implementering af mikrotjenester er afklaret, m\u00e5let er klart - at f\u00e5 et fungerende system til anvendelse af Bitrix i Kubernetes, mens vi bevarer b\u00e5de Bitrix-funktionalitet og Kubernetes-fordele. Vi starter implementeringen.<\/p>\n

<\/p>\n

Arkitektur<\/h4>\n

<\/p>\n

M\u00e5nga \"arbets\" poddar med webserver (worker’er).
\nEn pod med cron-opgaver (kun \u00e9n kr\u00e6ves).
\nEn upgrade pod til redigering af hjemmesidens kode fra administrationspanelet (ogs\u00e5 kun \u00e9n kr\u00e6ves).<\/p>\n

<\/p>\n

\"Southbridge<\/p>\n

<\/p>\n

Vi l\u00f8ser sp\u00f8rgsm\u00e5lene:<\/p>\n

<\/p>\n