Discussion:
Development/Test Server
Wimmer Christian
2014-10-06 11:02:02 UTC
Permalink
Dear all,

we currently do all our changes on our EZProxy production server, which is hardly ideal. I was wondering how the admins of this list handle this.

Do you have a development/test server where you test more complicated database or configuration changes?
How do you keep your production and test server in sync, when it comes to the configuration files like config.txt?
Did you request a seperate licence from OCLC or can you just use one licence fort two different systems?

Any input on this topic would be helpful.


--
Christian Wimmer
Ludwig-Maximilians-Universität München
University Library
IT-Department

Geschwister-Scholl-Platz 1, 80359 München, Germany
Phone: +49 89 2180-6141
Email: ***@ub.uni-muenchen.de



---
You are currently subscribed to ezproxy as: gee-***@m.gmane.org.
To unsubscribe, send request to ***@itec.suny.edu
Simon McLeish
2014-10-06 11:21:05 UTC
Permalink
Hi Christian,
Post by Wimmer Christian
Dear all,
we currently do all our changes on our EZProxy production server,
which is hardly ideal. I was wondering how the admins of this list
handle this.
Do you have a development/test server where you test more complicated
database or configuration changes?
Yes. They're linked to from different environments in our discovery
service. We're also intending to use it for testing software upgrades.
Post by Wimmer Christian
How do you keep your production and test server in sync, when it comes
to the configuration files like config.txt?
We don't, particularly. The general configuration is kept in sync
because we try out these changes in the development environment first.
Post by Wimmer Christian
Did you request a seperate licence from OCLC or can you just use one
licence fort two different systems?
We asked OCLC and were told that a single license would cover both.

Cheers,
Simon
Post by Wimmer Christian
Any input on this topic would be helpful.
--
Christian Wimmer
Ludwig-Maximilians-Universität München
University Library
IT-Department
Geschwister-Scholl-Platz 1, 80359 München, Germany
Phone: +49 89 2180-6141
--
Dr Simon McLeish
Resource Discovery Architect
Bodleian Libraries
University of Oxford
***@bodleian.ox.ac.uk | (+44)1865 283818


---
You are currently subscribed to ezproxy as: gee-***@m.gmane.org.
To unsubscribe, send request to ***@itec.suny.edu
Alex Birchall
2014-10-06 11:25:30 UTC
Permalink
Hi Christian,

We have an EZProxy development/test server for exactly the purposes you specify. My understanding is that OCLC allows this - what we are not allowed is two production instances of EZProxy.

I make no attempt to keep production and test in sync - apart from ensuring they are running the same version of EZProxy.

Regards,

Alex



Alex Birchall
Library Systems Manager
Middlesex University
The Sheppard Library
The Burroughs
London NW4 4BT

Tel: +44 (0) 208 411 5235
Mob: 07765 237 570

[cid:***@01CFE160.9E372D80]

From: Wimmer Christian [mailto:***@ub.uni-muenchen.de]
Sent: 06 October 2014 12:02
To: EZProxy discussion list
Subject: [ezproxy] Development/Test Server

Dear all,

we currently do all our changes on our EZProxy production server, which is hardly ideal. I was wondering how the admins of this list handle this.

Do you have a development/test server where you test more complicated database or configuration changes?
How do you keep your production and test server in sync, when it comes to the configuration files like config.txt?
Did you request a seperate licence from OCLC or can you just use one licence fort two different systems?

Any input on this topic would be helpful.


--
Christian Wimmer
Ludwig-Maximilians-Universität München
University Library
IT-Department

Geschwister-Scholl-Platz 1, 80359 München, Germany
Phone: +49 89 2180-6141
Email: ***@ub.uni-muenchen.de<mailto:***@ub.uni-muenchen.de>



You are currently subscribed to ezproxy as: ***@mdx.ac.uk<mailto:***@mdx.ac.uk>.
To unsubscribe, send request to ***@itec.suny.edu<mailto:***@itec.suny.edu>



---------------------------------------------------------------------------


Please note that Middlesex University's preferred way of receiving all correspondence is via email in line with our Environmental Policy. All incoming post to Middlesex University is opened and scanned by our digital document handler, CDS, and then emailed to the recipient.

If you do not want your correspondence to Middlesex University processed in this way please email the recipient directly. Parcels, couriered items and recorded delivery items will not be opened or scanned by CDS. There are items which are "exceptions" which will be opened by CDS but will not be scanned a full list of these can be obtained by contacting the University.


---
You are currently subscribed to ezproxy as: gee-***@m.gmane.org.
To unsubscribe, send request to ***@itec.suny.edu
Brian A Helstien
2014-10-06 11:49:05 UTC
Permalink
Christian,
I've a local test server. In the config.txt file for it, I've an includefile directive for a file called newtargets.txt. All development work is done in that file before new/modified targets are pushed into the production config file. Our staff are the only ones with accounts/access to the test instance, so we don't violate license nor is there any possibility of any untested addition/modification fouling up patrons.

Brian A. Helstien, SISD, MLS,
Director, Special Technologies Initiatives,
Library IT, University Libraries, x06913
University of Southern California, (213) 740-6913
Los Angeles, California, 90089 ***@usc.edu<mailto:***@usc.edu>
Information is independent of media or format

From: Wimmer Christian [mailto:***@ub.uni-muenchen.de]
Sent: Monday, October 06, 2014 4:02 AM
To: EZProxy discussion list
Subject: [ezproxy] Development/Test Server

Dear all,

we currently do all our changes on our EZProxy production server, which is hardly ideal. I was wondering how the admins of this list handle this.

Do you have a development/test server where you test more complicated database or configuration changes?
How do you keep your production and test server in sync, when it comes to the configuration files like config.txt?
Did you request a seperate licence from OCLC or can you just use one licence fort two different systems?

Any input on this topic would be helpful.


--
Christian Wimmer
Ludwig-Maximilians-Universität München
University Library
IT-Department

Geschwister-Scholl-Platz 1, 80359 München, Germany
Phone: +49 89 2180-6141
Email: ***@ub.uni-muenchen.de<mailto:***@ub.uni-muenchen.de>



You are currently subscribed to ezproxy as: ***@usc.edu<mailto:***@usc.edu>.
To unsubscribe, send request to ***@itec.suny.edu<mailto:***@itec.suny.edu>

---
You are currently subscribed to ezproxy as: gee-***@m.gmane.org.
To unsubscribe, send request to ***@itec.suny.edu
Stephan Rosenke
2014-10-06 11:51:01 UTC
Permalink
Post by Wimmer Christian
How do you keep your production and test server in sync, when it comes
to the configuration files like config.txt?
We are using git: after testing the changes are merged to the testing
master branch and the testing master branch is merged to the production
master branch.
Testing and production differs in some configuration options like
hostname and SSL certificates.
--
Stephan Rosenke M.A.

***********Universitäts- und Landesbibliothek Darmstadt**********
***********Abteilung Elektronische Informationsdienste***********
**Magdalenenstraße 8 * 64289 Darmstadt ** Fon +49 6151 16-76221**


---
You are currently subscribed to ezproxy as: gee-***@m.gmane.org.
To unsubscribe, send request to ***@itec.suny.edu
Sébastien Nadeau
2014-10-06 13:04:08 UTC
Permalink
I have a test server. Once in a while I copy my production config files to the test server manually. Licencewise, we've been allowed to run a test server without acquiring a separate licence for it.

Sébastien Nadeau
Analyste informatique
Technologies et systemes d'information
Bibliothèque de l'Université Laval
418 656-2131 poste 6815


De : Wimmer Christian [mailto:***@ub.uni-muenchen.de]
Envoyé : 6 octobre 2014 07:02
À : EZProxy discussion list
Objet : [ezproxy] Development/Test Server

Dear all,

we currently do all our changes on our EZProxy production server, which is hardly ideal. I was wondering how the admins of this list handle this.

Do you have a development/test server where you test more complicated database or configuration changes?
How do you keep your production and test server in sync, when it comes to the configuration files like config.txt?
Did you request a seperate licence from OCLC or can you just use one licence fort two different systems?

Any input on this topic would be helpful.


--
Christian Wimmer
Ludwig-Maximilians-Universität München
University Library
IT-Department

Geschwister-Scholl-Platz 1, 80359 München, Germany
Phone: +49 89 2180-6141
Email: ***@ub.uni-muenchen.de<mailto:***@ub.uni-muenchen.de>



You are currently subscribed to ezproxy as: ***@bibl.ulaval.ca<mailto:***@bibl.ulaval.ca>.
To unsubscribe, send request to ***@itec.suny.edu<mailto:***@itec.suny.edu>

---
You are currently subscribed to ezproxy as: gee-***@m.gmane.org.
To unsubscribe, send request to ***@itec.suny.edu
Michel de la Rambelje
2014-10-06 13:35:15 UTC
Permalink
Hi Christian,

License wise we also got permission from OCLC to run a test instance.

As the running footprint for ezproxy is low, we installed the test
instance on the same server.
We changed the listening ports for the test instance and made sure that
only allowed ip addresses can connect to those ports. We also changed
the name of the executable from "ezproxy" to "testezproxy" This way we
can monitor deamon behaviour.

This setup has a couple of benefits. Only one server to maintain and pay
for, test and production have the same ip address, production and test
run on exactly the same platform and configuration files can be easily
copied or even shared/included.
Test instance has its own configuration file. No synchronisation is
done. If the configuration runs on test we do the same thing in the
production config.

Hope this helps,

Michel de la Rambelje

--
Michel de la Rambelje
Radboud Universiteit Nijmegen
ICT Servicecentrum
www.ru.nl/isc
024-3611584
Post by Wimmer Christian
Dear all,
we currently do all our changes on our EZProxy production server,
which is hardly ideal. I was wondering how the admins of this list
handle this.
Do you have a development/test server where you test more complicated
database or configuration changes?
How do you keep your production and test server in sync, when it comes
to the configuration files like config.txt?
Did you request a seperate licence from OCLC or can you just use one
licence fort two different systems?
Any input on this topic would be helpful.
--
Christian Wimmer
Ludwig-Maximilians-Universität München
University Library
IT-Department
Geschwister-Scholl-Platz 1, 80359 München, Germany
Phone: +49 89 2180-6141
---
You are currently subscribed to ezproxy as: gee-***@m.gmane.org.
To unsubscribe, send request to ***@itec.suny.edu
Andrew Anderson
2014-10-06 14:01:19 UTC
Permalink
We use a separate EZproxy instance for testing, but this could be done with a 2nd instance running on the same machine with different bound interfaces or ports.

I developed a puppet module to manage our ezproxy servers, and use that to build the configurations for all of our proxy servers, both internal and hosted. When it comes time for changes, I disable puppet on the test server, iterate through the changes I need until they work to my satisfaction, and then commit those changes into the ezproxy module for the rest of our servers to pick up. Thanks to the automation, I don’t have to worry about anything after that, as the proxies are reloaded to pick up the new configurations the next time puppet runs, and I know that all of our proxies are in sync.
--
Andrew Anderson, Director of Development, Library and Information Resources Network, Inc.
http://www.lirn.net/ | http://www.twitter.com/LIRNnotes | http://www.facebook.com/LIRNnotes
Post by Wimmer Christian
Dear all,
we currently do all our changes on our EZProxy production server, which is hardly ideal. I was wondering how the admins of this list handle this.
Do you have a development/test server where you test more complicated database or configuration changes?
How do you keep your production and test server in sync, when it comes to the configuration files like config.txt?
Did you request a seperate licence from OCLC or can you just use one licence fort two different systems?
Any input on this topic would be helpful.
--
Christian Wimmer
Ludwig-Maximilians-Universität München
University Library
IT-Department
Geschwister-Scholl-Platz 1, 80359 München, Germany
Phone: +49 89 2180-6141
---
You are currently subscribed to ezproxy as: gee-***@m.gmane.org.
To unsubscribe, send request to ***@itec.suny.edu
Dominic Benson
2014-10-06 17:37:46 UTC
Permalink
Dear Christian,

We create or amend stanzas on our test instance. Each stanza is saved as a separate text file and referred to in config.txt with an IncludeFile directive. We commit or revert a change using Tortoise SVN. If testing works out then the change is tagged and applied to the live instance.

Kind regards,

Dominic Benson
E-Resources Librarian
Brunel University London
Library

T +44 (0)1895 266143 | www.brunel.ac.uk/library<http://www.brunel.ac.uk/library>
Bannerman Centre, Brunel University London, Uxbridge, UB8 3PH, UK

From: Wimmer Christian [mailto:***@ub.uni-muenchen.de]
Sent: 06 October 2014 12:02
To: EZProxy discussion list
Subject: [ezproxy] Development/Test Server

Dear all,

we currently do all our changes on our EZProxy production server, which is hardly ideal. I was wondering how the admins of this list handle this.

Do you have a development/test server where you test more complicated database or configuration changes?
How do you keep your production and test server in sync, when it comes to the configuration files like config.txt?
Did you request a seperate licence from OCLC or can you just use one licence fort two different systems?

Any input on this topic would be helpful.


--
Christian Wimmer
Ludwig-Maximilians-Universität München
University Library
IT-Department

Geschwister-Scholl-Platz 1, 80359 München, Germany
Phone: +49 89 2180-6141
Email: ***@ub.uni-muenchen.de<mailto:***@ub.uni-muenchen.de>







---
You are currently subscribed to ezproxy as: gee-***@m.gmane.org.
To unsubscribe, send request to ***@itec.suny.edu

Loading...