[Koha-devel] Deploying Koha at scale

[Tomás]

Hi folks.

Theke Solutions has started a project some time ago, sponsored by ByWater
Solutions to generate the tools and pipelines to provide a reliable Docker
implementation for deploying Koha in production environments. We have just
finished the housekeeping a few days ago so we are not embarrassed by our
commit messages and leftovers :-D and want to propose it for community
adoption anytime soon.

The project lives here for now:
https://gitlab.com/thekesolutions/koha-docker

What you will find there is a Docker image that can be used to run any of
the different Koha services/pieces on separate containers, or all inside a
single one. We aimed to target different deployment scenarios, from a small
library running it on a desktop computer to a multi-cluster K8s setup. A
helm chart is part of the roadmap.

You will notice there are a couple issues to be addressed [1]. For
instance, the shipped docker-compose.yml is outdated regarding the
MySQL/MariaDB server and we definitely need more on the README.

Thanks to ByWater for supporting this effort, and now that people are
talking about this, let's start the conversation \o/

[1] https://gitlab.com/thekesolutions/koha-docker/-/issues


El jue., 11 jun. 2020 a las 4:52, <dcook at prosentient.com.au> escribió:

> Hi all,
>
> For a long time, I've been thinking about how Koha could scale better, and
> I'm wondering what other people are thinking about this topic. I think
> Mengu
> is probably the best expert on this topic that we have on Earth, so
> especially curious about his input.
>
> It's relatively easy to add more Apache web servers, more MySQL nodes, and
> more Elasticsearch nodes. but the same might not be said for other parts of
> Koha like the following:
>
> 1. Zebra
>         a. In theory, you could load balance queries to a cluster of Zebra
> listeners
>         b. But indexing updates to many Zebra databases could be tricky (I
> don't know if Zebra's database can support many readers). I suppose you
> could alter rebuild_zebra.pl to update multiple databases in a variety of
> different ways. I imagine Mengu could speak to this, as I recall him
> talking
> once about needing to do work to make Zebra scale?
>
> 2. I'm not familiar enough with the SIP server to say
>         a. Off the top of my head, I think a TCP load balancer would be
> good
> enough here
>
> 3. Z3950 Responder?
>         a. I'm not familiar with this daemon
>
> 4. What about cronjobs? Only 1 instance should execute the cronjobs.
>         a. I suppose a person could disable cronjobs on all Koha nodes
> except for 1? It wouldn't be very robust in terms of availability but it
> would technically work most of the time.
>
> Any other thoughts?
>
> David Cook
> Systems Librarian
> Prosentient Systems
> 72/330 Wattle St
> Ultimo, NSW 2007
> Australia
>
> Office: 02 9212 0899
> Online: 02 8005 0595
>
>
>

-- 
Tomás Cohen Arazi
Theke Solutions (http://theke.io)
✆ +54 9351 3513384
GPG: B2F3C15F
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20200611/d59171d7/attachment.htm>