You are propably right, when performing backup export/import we can even say its mandatory to stop the server.
Sebastian 2012/3/20 Maxim Solodovnik <[email protected]> > I'll examine what can be done in case of Om is up and running. > If nothing can be done #1 can be used in this case. > > For me it seems to be not a big deal to stop server since it's better to > have no active connections while backup/restore + it takes small amount of > timeif all operations are performed locally. > > On Tue, Mar 20, 2012 at 14:45, [email protected] < > [email protected]> wrote: > >> I would vote for #2 too. >> I only see here the problem with the Spring managed DB Session and >> possible caching issues. If OpenMeetings is already Up and running, it >> would mean a second Java instance is started to perform the cli tasks? How >> will that work for example with OpenJPA's sequence table? Do we have a >> chance to grab the session from an already running webapp? Or is there >> maybe a Spring extension point that we can use here? >> >> Sebastian >> >> >> 2012/3/20 Maxim Solodovnik <[email protected]> >> >>> The quick-and-easy way to implement it: >>> 1) import/export php-cli script based on REST calls >>> 2) Java command-line tool performing the code currently implemented in >>> JUnit tests (install/import/export can be easily implemented) >>> >>> I would vote for #2 >>> >>> >>> On Tue, Mar 20, 2012 at 10:03, Maxim Solodovnik <[email protected]>wrote: >>> >>>> Hello Sebastian >>>> >>>> I think command line import/export/install will be great idea! (There >>>> was old request for this feature) >>>> This will save time for the installation/update. >>>> Backup can be stored on the same server (will save time for >>>> download/upload and traffic) >>>> >>>> instead of unarchiving, installing, login and importing there will be >>>> just one step. >>>> I would like to implement that >>>> >>>> >>>> On Tue, Mar 20, 2012 at 02:20, [email protected] < >>>> [email protected]> wrote: >>>> >>>>> Hi Maxim, >>>>> >>>>> after you have successfully improved and set up our Nightly Build >>>>> System (Congrats!!) I would like to start some discussion about our update >>>>> mechanism: >>>>> >>>>> The current mechanism is fine as you can switch between from any old >>>>> version and import your data to another version. I would like to keep that >>>>> import/export mechanism via the web-interface. I think it is easy to use >>>>> also for non Sys-Administrators to re-import existing data that way. >>>>> >>>>> However there is no other way of updating the system (except you know >>>>> what you do). My idea was kind of inspired by Moodle: They have >>>>> implemented >>>>> some kind of command line interface to do backup actions in their latest >>>>> version. >>>>> I think having the possibility to do the backup import/export also via >>>>> command line would be great. >>>>> There might be also a possibility to do the initial install via this >>>>> command line interface instead of the web-installer via browser. >>>>> And for example to add a user to the openmeetings database with it. >>>>> This gives Sys admins much more flexibility for managing the system. >>>>> From my understanding the problem with that idea is that this command >>>>> line interface to OpenMeetings has to access the same Spring managed >>>>> openJPA DB session then the usual webapp, cause otherwise you would need >>>>> to >>>>> do a restart Red5 or some tricks to flush openJPA's cache. >>>>> The second big point about it would be security. I think to access the >>>>> command line interface it should be possible to auth with the same user >>>>> that you auth at the web-interface (admin level users only of course). >>>>> >>>>> What do you think about that? >>>>> I think a big plus for this feature would be also that this is a >>>>> perfect extension point for system integrators and for building packages >>>>> for various linux distributions. >>>>> >>>>> Sebastian >>>>> >>>>> -- >>>>> Sebastian Wagner >>>>> http://www.openmeetings.de >>>>> http://incubator.apache.org/openmeetings/ >>>>> http://www.webbase-design.de >>>>> http://www.wagner-sebastian.com >>>>> [email protected] >>>>> >>>> >>>> >>>> >>>> -- >>>> WBR >>>> Maxim aka solomax >>>> >>> >>> >>> >>> -- >>> WBR >>> Maxim aka solomax >>> >> >> >> >> -- >> Sebastian Wagner >> http://www.openmeetings.de >> http://incubator.apache.org/openmeetings/ >> http://www.webbase-design.de >> http://www.wagner-sebastian.com >> [email protected] >> > > > > -- > WBR > Maxim aka solomax > -- Sebastian Wagner http://www.openmeetings.de http://incubator.apache.org/openmeetings/ http://www.webbase-design.de http://www.wagner-sebastian.com [email protected]
