Fwd: question about koha versions
-------- Forwarded Message -------- Subject: question about koha versions Date: Thu, 3 Nov 2016 16:21:20 -0600 From: Jose Manuel Campechano <jmcp18@gmail.com> To: kohanews@gmail.com Hi Koha team, can you help me with a question? what's the difference between koha 16 and 3.22 versions?
There was a change in numbering schemes. 16.05 means that it is the May release in 2016. Where the old scheme was just version 3 with sub-release 22. Ed On Fri, Nov 4, 2016 at 6:13 PM, kohanews <kohanews@gmail.com> wrote:
-------- Forwarded Message -------- Subject: question about koha versions Date: Thu, 3 Nov 2016 16:21:20 -0600 From: Jose Manuel Campechano <jmcp18@gmail.com> To: kohanews@gmail.com
Hi Koha team, can you help me with a question? what's the difference between koha 16 and 3.22 versions? _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- *Edward Veal* email: edward.m.veal@gmail.com Cell: 806-445-6867
Hi, We are looking for a solution to build a redundant infrastructure for Koha. What we want to do is shown in the diagram http://adminkuhn.ch/download/Redundant.png The main objective of such a solution is: If one of the Application Servers goes down the other will take over the job without losing any time. If the DB-Server Master goes down we will be able to build the Master out of the Slave and create a new Slave next to the new Master. Has anyone ever built such an infrastructure with Koha and can give us some advice how to proceed? Is this possible with Koha anyway? Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik@adminkuhn.ch · W www.adminkuhn.ch
On 8 November 2016 at 08:50, Michael Kuhn <mik@adminkuhn.ch> wrote:
Hi,
We are looking for a solution to build a redundant infrastructure for Koha.
What we want to do is shown in the diagram http://adminkuhn.ch/download/Redundant.png
The main objective of such a solution is: If one of the Application Servers goes down the other will take over the job without losing any time. If the DB-Server Master goes down we will be able to build the Master out of the Slave and create a new Slave next to the new Master.
Has anyone ever built such an infrastructure with Koha and can give us some advice how to proceed? Is this possible with Koha anyway?
Will shift this to Koha-devel Yes this is possible and quite easy to do. What makes it tricky is Zebra, which you have left out of your diagram. You either need to have the full zebra index on both your application servers (which means modifying rebuild_zebraqueue to make sure it gets built by each machine) Or you need to use something like nfs or another distributed filesystem. Or use rsync etc. It becomes a lot easier with elasticsearch of course, because you just have your elastic cluster and they talk to that. Hope this helps Chris
Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik@adminkuhn.ch · W www.adminkuhn.ch _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
participants (4)
-
Chris Cormack -
Edward Veal -
kohanews -
Michael Kuhn