2014-07-18 10:06 GMT+02:00 Cédric Krier <[email protected]>: > On 18 Jul 09:09, Dominique Chabord wrote: > > Le 17/07/2014 10:00, Cédric Krier a écrit : > > > On 17 Jul 08:51, Dominique Chabord wrote: > > >> If you restore db_archive_A, save it, and then restore db-archive_B, > you > > >> donr'need to restart the server. This would become impossible. > > > > > > You will have to restart. > > > > You need to access the server for this and if you access the server you > > get access to all instances. As a side effect, the "restore" function > > can be suppressed, as well as the master password. > > Yes of course, this has always been a security concern. > > > >> This is off-topic, but single database would be uncompatible with > > >> education requirements. > > > > > > Can not understand why education will need server provisioning in the > > > ERP instead of general provisioning solution. > > > > I don't understand what you mean above. > > Education requirement is to manage several hundreds of databases, and > > create tens of new ones (typically 30 for a classroom) at a time. > > Creating/Deleting new instances require complex port management. The > > teacher also has to manage connection profiles accordingly. > > This is called provisioning: https://en.wikipedia.org/wiki/Provisioning > > > Running > > hundreds of instances is also a waste in resources (disk and memory). > > I disagree about disk waste. > For memory, the gain of using one process for all DB vs one process per > DB doesn't seem so much I measure it of ~40Mb with the full set of > module when starting a DB takes ~25Mb. > So in some way, it will double the require memory for such case but > still it should fit in one common server configuration.
I think this part of discussion is out of thread topic. It has been discussed in this thread [1] where you can find the arguments for the change to a single-database per instance. As I commented in that thread, I think that with Circus [2] will be posible (Out of the box or developing some plugin) to serve multiple instances/databases selected by subdomain (all of theme using the same external port). With this and a flask application (for example) for the Instance/Database reated functions (create, drop, restore...) we can have a better provisioning system. I understand that now, the Education use case is supported easyly, but a very good solution will be posible and, as you can find here [1], there are good reasons for the change. If you want, we can create a blueprint in the Tryton's wiki for this provisioning system and try to design it and develop with the collaboration of community. [1] https://groups.google.com/d/msg/tryton-dev/jrLyPxHMzeA/7TeqMzoo6sQJ [2] http://circus.readthedocs.org/en -- Guillem Barba http://www.guillem.alcarrer.net
