[OPEN-ILS-GENERAL] Upgrading OpenSRF

Demian Katz demian.katz at villanova.edu
Fri May 13 15:54:20 EDT 2011


Great, thanks for the clarification!  Perhaps step 6 should state more explicitly that this is only necessary for testing purposes.

So what does it take to get a link to the Upgrading docs from the OpenSRF download page?

- Demian

> -----Original Message-----
> From: Anoop Atre [mailto:anoop.atre at mnsu.edu]
> Sent: Friday, May 13, 2011 3:20 PM
> To: Demian Katz
> Cc: Evergreen Discussion Group
> Subject: Re: [OPEN-ILS-GENERAL] Upgrading OpenSRF
> 
> Demian
> OpenSRF 2.0.0 is compatible with 2.0.x and above (it might even be fine
> with Evergreen 1.6.*)
> 
> Yes you can skip that step. I note in the instructions to create
> backups
> of those files (step 6) if you want to test the bare bones OpenSRF
> configuration and then roll back to the Evergreen configuration files
> (last part of the instructions).
> 
> I've updated the instructions after Dan Scott made some comments on
> IRC,
> it now includes a short version and a cleaned up longer version. Also
> included a warning that Thomas Berezansky thought might be a good idea
> about having to re-compile Evergreen once an OpenSRF upgrade was
> completed. In my test I didn't have to but there maybe cases where it
> might be required.
> 
> Cheers
> 
> On 05/13/2011 01:36 PM, Demian Katz wrote:
> > Thanks for sharing this.  Just one point that is a little unclear:
> since the Evergreen installation overwrites opensrf.xml and
> opensrf_core.xml, how should those files be treated during upgrading?
> Presumably if I overwrite the xml files with the xml.example files
> generated by the OpenSRF compilation process, that will cause problems
> when I go to upgrade Evergreen (since the Evergreen upgrade
> instructions don't address opensrf.xml at all).  Is there any way this
> can be streamlined?  Can we simply skip this step in the OpenSRF
> upgrade if we are later upgrading Evergreen anyway?
> >
> > Also, regarding OpenSRF 2.0.0, is this compatible with the Evergreen
> 2.0.x line, or is it not appropriate to use it until 2.1.x comes along?
> >
> > thanks,
> > Demian
> >
> >> -----Original Message-----
> >> From: Anoop Atre [mailto:anoop.atre at mnsu.edu]
> >> Sent: Tuesday, May 10, 2011 7:35 PM
> >> To: Evergreen Discussion Group
> >> Cc: Demian Katz
> >> Subject: Re: [OPEN-ILS-GENERAL] Upgrading OpenSRF
> >>
> >> Demian
> >> I'd been meaning to write upgrade instructions for sometime so here
> you
> >> go: http://evergreen-ils.org/dokuwiki/doku.php?id=opensrf:upgrading
> >>
> >> You basically don't need to recreate the ejabberd accounts and you
> >> could
> >> probably skip step 6 through 9 which are to test a bare-bones
> OpenSRF
> >> config/install.
> >>
> >> I'm sure I missed something or there is a better way of doing the
> >> upgrade but on a standalone server I've had no problems (yet) with
> >> these
> >> directions.
> >>
> >> Depending on what version of Evergreen you are working with I would
> >> recommend you move to the latest 2.0.0 that was released on Sunday
> >> (thanks to Dan Scott).
> >>
> >> Cheers
> >>
> >> On 05/10/2011 02:26 PM, Demian Katz wrote:
> >>> Hello,
> >>>
> >>> Just curious if there are upgrade instructions for OpenSRF that I'm
> >> missing.  I'm currently running 1.6.2, and I see that the newest
> >> version is 1.6.3 - it would be nice to upgrade without having to
> repeat
> >> the whole complex install process.  Is there a shortcut, or should I
> >> just bite the bullet and dig in?
> >>>
> >>> - Demian
> >>>
> >>
> >>
> >> --
> >>
> >> Anoop Atre
> >> IS Developer&  Integrator, MnPALS
> >> PH: 507.389.5060
> >> OF: 3022 Memorial Library (Office-ML 3022)
> >> --
> >> "Mit der Dummheit kämpfen Götter selbst vergebens"
> >>    ~ Johann Christoph Friedrich von Schiller
> 
> 
> --
> 
> Anoop Atre
> IS Developer & Integrator, MnPALS
> PH: 507.389.5060
> OF: 3022 Memorial Library (Office-ML 3022)
> --
> "Mit der Dummheit kämpfen Götter selbst vergebens"
>   ~ Johann Christoph Friedrich von Schiller


More information about the Open-ils-general mailing list