[Koha-devel] Koha 3.2 in virtualization or with several database : Is it effective ?

[Brice Sanchez]

Thank you for your reply,

I've already done several installations of Koha in DEV and Single mode. 
But when we have multiple installations on one server we have problems 
with the Zebra indexing engine.

This is why we try to virtualize (with Xen), or to install a single Koha 
running with several databases.

We are therefore looking for feedback and help to build the right 
architecture : that is the most easily maintainable for 20 School and 
can easily accommodate 500 simultaneous users.

Brice


On 02/08/2010 12:18, Joe Atzberger wrote:
> Koha can be effectively virtualized for production in VMware, 
> Virtualbox or xen.  It is quite common and helpful.
>
> And yes, you can use the same codebase with different Koha instances. 
>  You will have to do edit your $KOHA_CONF files accordingly.  But 
> start with one instance and get familiar with it first before trying 
> to add additional ones.
>
> --Joe
>
> 2010/8/2 Brice Sanchez <brice.sanchez at sys-tech.net 
> <mailto:brice.sanchez at sys-tech.net>>
>
>     Hello everyone,
>
>     I'm preparing to install Koha 3.2 for 20 schools and I was
>     wondering if some of you had used the method of virtualization
>     (VMWare or Virtualbox). If yes, is it effective? What are the
>     problems you encountered? Have you done any benchmarks?
>
>     I am also looking for a method with one Koha and several databases
>     and Zebras : Is this a successful method?
>
>     Thank you for your answers!
>
>     *Brice Sanchez*
>     Programmeur Web
>
>     brice.sanchez at sys-tech.net <mailto:brice.sanchez at sys-tech.net>
>     418 520-0739 poste 136
>     514 907-0036 / 1-877-969-8324
>
>     *SYS-TECH / Technologies de l'information libres*
>     6700 BOUL PIERRE-BERTRAND BUREAU 209
>     QUÉBEC QC G2J 0B4
>     http://www.sys-tech.net
>
>     /Membre supporteur de l'Association TYPO3 <http://typo3.org>/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20100802/5ca8d15c/attachment-0001.htm>