Re: [CODE4LIB] OCLC Service Outage Update

2010-05-11 Thread Don Hamparian
Jonathan, I'll check this out this morning.

Don Hamparian
OCLC



On Mon, May 10, 2010 at 4:54 PM, Jonathan Rochkind rochk...@jhu.edu wrote:

 I _believe_ that the OCLC FirstSearch shibboleth server is still down, for
 anyone who tries to send their users to FirstSearch via Shibboleth.


 Simon Spero wrote:

 At least it wasn't  a totally transparent  UPS test scheduled for the
 Thursday of Thanksgiving weekend.  My personal philosophy is that every
 rack
 should have its own UPS separate from the data center one, with enough
 capacity to keep going through blips,and handle a clean shutdown if
 necessary.  That way,  when the ops team messes up, far fewer sysadmins
 get
 their weekend ruined.

 Of course, the real problem is that too many people are writing
 unoptimized
 code in energy-inefficient languages like ruby and PHP, which require far
 more servers, and far more cooling, to do the same work as properly
 written
 code.  If carbon emissions should turn out to be a  strong forcer  of
 global
 warming, then we can clearly say that every time you write  PHP, Phil
 Jones
 kills a polar bear. Please, think of the polar bears.

 Simon






Re: [CODE4LIB] OCLC Service Outage Update

2010-05-11 Thread Don Hamparian
Jonathan and others who use Shibboleth access to First Search - access
looks up and normal so if anyone has any problems - email us at
shibbol...@oclc.org.

Don


On Tue, May 11, 2010 at 6:28 AM, Don Hamparian don.hampar...@gmail.com wrote:
 Jonathan, I'll check this out this morning.
 Don Hamparian
 OCLC


 On Mon, May 10, 2010 at 4:54 PM, Jonathan Rochkind rochk...@jhu.edu wrote:

 I _believe_ that the OCLC FirstSearch shibboleth server is still down, for
 anyone who tries to send their users to FirstSearch via Shibboleth.

 Simon Spero wrote:

 At least it wasn't  a totally transparent  UPS test scheduled for the
 Thursday of Thanksgiving weekend.  My personal philosophy is that every
 rack
 should have its own UPS separate from the data center one, with enough
 capacity to keep going through blips,and handle a clean shutdown if
 necessary.  That way,  when the ops team messes up, far fewer sysadmins
 get
 their weekend ruined.

 Of course, the real problem is that too many people are writing
 unoptimized
 code in energy-inefficient languages like ruby and PHP, which require far
 more servers, and far more cooling, to do the same work as properly
 written
 code.  If carbon emissions should turn out to be a  strong forcer  of
 global
 warming, then we can clearly say that every time you write  PHP, Phil
 Jones
 kills a polar bear. Please, think of the polar bears.

 Simon






[CODE4LIB] OCLC Service Outage Update

2010-05-10 Thread Roy Tennant
Since this topic came up on the list yesterday, here is an official update.
Roy

Service outage update

On Sunday, May 9, the primary OCLC data center in Dublin lost power during
required internal facilities maintenance activity.  OCLC staff worked
diligently to restore services as quickly as possible.  All systems are
fully recovered and operational.

OCLC schedules maintenance activities at typically low usage times.  We
regret any interruption of service, and apologize for any inconvenience to
our users.  We are confident that we have put in place systems that address
these issues for services today, and we continue to build on those systems
to plan for the future.

Additionally, in July, OCLC will implement the use of its secondary data
center for active/passive service configurations, which can fail-over and
back in minutes with minimal manual intervention.  In the future, we will be
able to use the secondary data center for active/active service
configurations, where services are load balanced in both data centers.


Re: [CODE4LIB] OCLC Service Outage Update

2010-05-10 Thread Simon Spero
At least it wasn't  a totally transparent  UPS test scheduled for the
Thursday of Thanksgiving weekend.  My personal philosophy is that every rack
should have its own UPS separate from the data center one, with enough
capacity to keep going through blips,and handle a clean shutdown if
necessary.  That way,  when the ops team messes up, far fewer sysadmins get
their weekend ruined.

Of course, the real problem is that too many people are writing unoptimized
code in energy-inefficient languages like ruby and PHP, which require far
more servers, and far more cooling, to do the same work as properly written
code.  If carbon emissions should turn out to be a  strong forcer  of global
warming, then we can clearly say that every time you write  PHP, Phil Jones
kills a polar bear. Please, think of the polar bears.

Simon


Re: [CODE4LIB] OCLC Service Outage Update

2010-05-10 Thread Casey Bisson
Or be like Google, give up on UPSs, and just attached a battery to the DC side 
of each server's power supply.

http://arstechnica.com/hardware/news/2009/04/the-beast-unveiled-inside-a-google-server.ars


On May 10, 2010, at 4:41 PM, Simon Spero wrote:

 At least it wasn't  a totally transparent  UPS test scheduled for the
 Thursday of Thanksgiving weekend.  My personal philosophy is that every rack
 should have its own UPS separate from the data center one, with enough
 capacity to keep going through blips,and handle a clean shutdown if
 necessary.  That way,  when the ops team messes up, far fewer sysadmins get
 their weekend ruined.
 
 Of course, the real problem is that too many people are writing unoptimized
 code in energy-inefficient languages like ruby and PHP, which require far
 more servers, and far more cooling, to do the same work as properly written
 code.  If carbon emissions should turn out to be a  strong forcer  of global
 warming, then we can clearly say that every time you write  PHP, Phil Jones
 kills a polar bear. Please, think of the polar bears.
 
 Simon


Re: [CODE4LIB] OCLC Service Outage Update

2010-05-10 Thread Jonathan Rochkind
I _believe_ that the OCLC FirstSearch shibboleth server is still down, 
for anyone who tries to send their users to FirstSearch via Shibboleth.


Simon Spero wrote:

At least it wasn't  a totally transparent  UPS test scheduled for the
Thursday of Thanksgiving weekend.  My personal philosophy is that every rack
should have its own UPS separate from the data center one, with enough
capacity to keep going through blips,and handle a clean shutdown if
necessary.  That way,  when the ops team messes up, far fewer sysadmins get
their weekend ruined.

Of course, the real problem is that too many people are writing unoptimized
code in energy-inefficient languages like ruby and PHP, which require far
more servers, and far more cooling, to do the same work as properly written
code.  If carbon emissions should turn out to be a  strong forcer  of global
warming, then we can clearly say that every time you write  PHP, Phil Jones
kills a polar bear. Please, think of the polar bears.

Simon

  


Re: [CODE4LIB] OCLC Service Outage Update

2010-05-10 Thread Simon Spero
The unix hackers at the Technion did that to the Vaxen 11/7XXes;   didn't
trust the walk-in UPS, because the mainframe and Vax 9000 would drain it to
the dregs. Couldn't do the same thing for the Sun 4/XXX because no source
license.

Up hill, both ways, in the sand.
Simon

On Mon, May 10, 2010 at 4:47 PM, Casey Bisson cbis...@plymouth.edu wrote:

 Or be like Google, give up on UPSs, and just attached a battery to the DC
 side of each server's power supply.


 http://arstechnica.com/hardware/news/2009/04/the-beast-unveiled-inside-a-google-server.ars


 On May 10, 2010, at 4:41 PM, Simon Spero wrote:

  At least it wasn't  a totally transparent  UPS test scheduled for the
  Thursday of Thanksgiving weekend.  My personal philosophy is that every
 rack
  should have its own UPS separate from the data center one, with enough
  capacity to keep going through blips,and handle a clean shutdown if
  necessary.  That way,  when the ops team messes up, far fewer sysadmins
 get
  their weekend ruined.
 
  Of course, the real problem is that too many people are writing
 unoptimized
  code in energy-inefficient languages like ruby and PHP, which require far
  more servers, and far more cooling, to do the same work as properly
 written
  code.  If carbon emissions should turn out to be a  strong forcer  of
 global
  warming, then we can clearly say that every time you write  PHP, Phil
 Jones
  kills a polar bear. Please, think of the polar bears.
 
  Simon



Re: [CODE4LIB] OCLC Service Outage Update

2010-05-10 Thread Simon Spero
On Mon, May 10, 2010 at 4:54 PM, Jonathan Rochkind rochk...@jhu.edu wrote:

 I _believe_ that the OCLC FirstSearch shibboleth server is still down, for
 anyone who tries to send their users to FirstSearch via Shibboleth


Are you sure you're saying it right?

Simon


Re: [CODE4LIB] OCLC Service Outage Update

2010-05-10 Thread stuart yeates

Simon Spero wrote:


Of course, the real problem is that too many people are writing unoptimized
code in energy-inefficient languages like ruby and PHP, which require far
more servers, and far more cooling, to do the same work as properly written
code.  


No, the real problem is with trolls sending flamebait.

cheers
stuart
--
Stuart Yeates
http://www.nzetc.org/   New Zealand Electronic Text Centre
http://researcharchive.vuw.ac.nz/ Institutional Repository


Re: [CODE4LIB] OCLC Service Outage Update

2010-05-10 Thread Alexander Johannesen
On Tue, May 11, 2010 at 06:59, stuart yeates stuart.yea...@vuw.ac.nz wrote:
 No, the real problem is with trolls sending flamebait.

Friggin' AMEEN!

Alex
-- 
 Project Wrangler, SOA, Information Alchemist, UX, RESTafarian, Topic Maps
--- http://shelter.nu/blog/ --
-- http://www.google.com/profiles/alexander.johannesen ---


Re: [CODE4LIB] OCLC Service Outage Update

2010-05-10 Thread Andrew Hankinson
Writing code in energy efficient languages is the funniest thing  
I've heard in a while. It ranks up there with setting my desktop  
wallpaper to black because it uses less energy.


More servers are required because more people are writing webapps  
because Ruby and PHP make it easier for more people to do it. Is there  
even a C webapp framework available?


-A

On 2010-05-10, at 16:59, stuart yeates stuart.yea...@vuw.ac.nz wrote:


Simon Spero wrote:

Of course, the real problem is that too many people are writing  
unoptimized
code in energy-inefficient languages like ruby and PHP, which  
require far
more servers, and far more cooling, to do the same work as properly  
written

code.


No, the real problem is with trolls sending flamebait.

cheers
stuart
--
Stuart Yeates
http://www.nzetc.org/   New Zealand Electronic Text Centre
http://researcharchive.vuw.ac.nz/ Institutional Repository


Re: [CODE4LIB] OCLC Service Outage Update

2010-05-10 Thread Michael J. Giarlo
... people took Simon's comment seriously?

C'mon, failsters.  Stop making it so easy.

-Mike



On Mon, May 10, 2010 at 18:49, Andrew Hankinson
andrew.hankin...@gmail.com wrote:
 Writing code in energy efficient languages is the funniest thing I've
 heard in a while. It ranks up there with setting my desktop wallpaper to
 black because it uses less energy.

 More servers are required because more people are writing webapps because
 Ruby and PHP make it easier for more people to do it. Is there even a C
 webapp framework available?

 -A

 On 2010-05-10, at 16:59, stuart yeates stuart.yea...@vuw.ac.nz wrote:

 Simon Spero wrote:

 Of course, the real problem is that too many people are writing
 unoptimized
 code in energy-inefficient languages like ruby and PHP, which require far
 more servers, and far more cooling, to do the same work as properly
 written
 code.

 No, the real problem is with trolls sending flamebait.

 cheers
 stuart
 --
 Stuart Yeates
 http://www.nzetc.org/       New Zealand Electronic Text Centre
 http://researcharchive.vuw.ac.nz/     Institutional Repository



Re: [CODE4LIB] OCLC Service Outage Update

2010-05-10 Thread Alexander Johannesen
Michael J. Giarlo leftw...@alumni.rutgers.edu wrote:
 ... people took Simon's comment seriously?

Language is a funny thing ; some times the things that are being said
is taken seriously. And the script-haters are spread far and wide, so
there was no reason not to take him seriously. Should the default be
not to take anyone seriously? Srsly?


Alex
-- 
 Project Wrangler, SOA, Information Alchemist, UX, RESTafarian, Topic Maps
--- http://shelter.nu/blog/ --
-- http://www.google.com/profiles/alexander.johannesen ---


Re: [CODE4LIB] OCLC Service Outage Update

2010-05-10 Thread Kyle Banerjee
  Is there even a C webapp framework available?


C is for wussy. Real hombres only need assembly.


Re: [CODE4LIB] OCLC Service Outage Update

2010-05-10 Thread Kyle Banerjee
That had occurred to me. However, they tend not to participate in p*ssing
contests (i.e. they're less inclined to do dumb things than guys) so they
weren't listed.

But this is a big tent where all are welcome :)

On Mon, May 10, 2010 at 6:22 PM, Lynne Lysiak lysia...@appstate.edu wrote:

 ahem, y mujeres sir!!

 - Original Message -
 From: Kyle Banerjee baner...@uoregon.edu
 Date: Monday, May 10, 2010 9:18 pm
 Subject: Re: [CODE4LIB] OCLC Service Outage Update
 To: CODE4LIB@LISTSERV.ND.EDU

Is there even a C webapp framework available?
 
 
  C is for wussy. Real hombres only need assembly.
 




-- 
--
Kyle Banerjee
Digital Services Program Manager
Orbis Cascade Alliance
baner...@uoregon.edu / 503.999.9787


Re: [CODE4LIB] OCLC Service Outage Update

2010-05-10 Thread Chris Cormack
On 11 May 2010 14:19, Kyle Banerjee baner...@uoregon.edu wrote:
 That had occurred to me. However, they tend not to participate in p*ssing
 contests (i.e. they're less inclined to do dumb things than guys) so they
 weren't listed.

Oh wow, want a shovel to help dig you out of the gross generalisations hole?

Chris

 But this is a big tent where all are welcome :)

 On Mon, May 10, 2010 at 6:22 PM, Lynne Lysiak lysia...@appstate.edu wrote:

 ahem, y mujeres sir!!

 - Original Message -
 From: Kyle Banerjee baner...@uoregon.edu
 Date: Monday, May 10, 2010 9:18 pm
 Subject: Re: [CODE4LIB] OCLC Service Outage Update
 To: CODE4LIB@LISTSERV.ND.EDU

    Is there even a C webapp framework available?
 
 
  C is for wussy. Real hombres only need assembly.
 




 --
 --
 Kyle Banerjee
 Digital Services Program Manager
 Orbis Cascade Alliance
 baner...@uoregon.edu / 503.999.9787



Re: [CODE4LIB] OCLC Service Outage Update

2010-05-10 Thread Kyle Banerjee


 Oh wow, want a shovel to help dig you out of the gross generalisations
 hole?


Nah -- I'm totally secure in my idiocy.

If I really step in it, I'll get loads of hate mail. If I'm really unlucky
and it takes on a life of it's own, I may even be forced to issue a
groveling public apology. Been there done that ;)

kyle

Note to self: Never make light of important technical discussions. Also
change wallpaper to black


Re: [CODE4LIB] OCLC Service Outage Update

2010-05-10 Thread Sean Hannan
After poking around, it seems that there is: Wt (http://www.webtoolkit.eu/wt).  
After looking through the source of the Hello World example[1], I'm not sure 
why anyone would go through the trouble, but then again, I feel that way about 
a lot of lower-level compiled languages.

-Sean

[1] http://www.webtoolkit.eu/wt#/src/hello

From: Code for Libraries [code4...@listserv.nd.edu] On Behalf Of Andrew 
Hankinson [andrew.hankin...@gmail.com]
Sent: Monday, May 10, 2010 6:49 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] OCLC Service Outage Update

Is there even a C webapp framework available?

-A

On 2010-05-10, at 16:59, stuart yeates stuart.yea...@vuw.ac.nz wrote:

 Simon Spero wrote:

 Of course, the real problem is that too many people are writing
 unoptimized
 code in energy-inefficient languages like ruby and PHP, which
 require far
 more servers, and far more cooling, to do the same work as properly
 written
 code.

 No, the real problem is with trolls sending flamebait.

 cheers
 stuart
 --
 Stuart Yeates
 http://www.nzetc.org/   New Zealand Electronic Text Centre
 http://researcharchive.vuw.ac.nz/ Institutional Repository