LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  April 2013

CODE4LIB April 2013

Subject:

Job: DevOps System Administrator at Stanford University

From:

[log in to unmask]

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Sun, 21 Apr 2013 12:50:35 -0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (55 lines)

Stanford University Libraries (SUL) is seeking a talented systems
administrator to support the management, preservation and access of digital
library content. This is a four-year term position, with the possibility of
extension. This position is part of the Application Development team in the
Digital Library Systems and Services (DLSS) unit of SUL.

  
The DevOps System Administrator will be primarily focused on defining,
documenting and supporting application deployment best practices, including
systems configuration, and on maintaining and supporting production DLSS
services. Specifically, the DevOps System Administrator will provide expertise
and ongoing support for DLSS's software deployment and maintenance procedures
in order to ensure high availability, consistency, and adherence to best
practices for network and application security. The DevOps System
Administrator will play a key role between other DLSS software developers and
the Libraries' system administrators.

  
As a member of SUL's digital library application development team, the DevOps
System Administrator will also contribute to the overall development of the
Stanford Library's web and digital library infrastructure, and help plan,
specify, and build the technologies needed to support the University's goal of
ubiquitous access to scholarly information.

  
Primary Responsibilities:

  * Maintain, refine, and support DLSS's application deployment process. (40%) Define puppet manifests to configure servers and write Capistrano recipes to automate application deploy processes. Load test applications before they go live. Provide data and metrics to support hardware sizing requirements and performance tuning decisions. Document procedures, and keep documentation updated.
  * Maintain and support DLSS's production environment. (40%) Perform updates to deployed applications and supporting software libraries. Define and maintain nagios checks for DLSS applications; respond to system-level incidents, and application-level events when possible. In cooperation with project stakeholders, codify service level agreements and uptime expectations. Perform periodic auditing and upgrades to our monitoring service. Help provision and maintain testing infrastructure, including integration and load testing. Respond to production emergencies. Monitor and perform regular audits of DLSS security practices. Stay abreast of new security threats relevant to the DLSS environment, and ensure timely response to security holes.
  * Perform systems administration tasks as needed. (20%) This will include management of virtual machines, NFS mounts, DNS updates, load balancer configuration, SSL certificates, etc. Act as a liaison between DLSS software developers and DLSS systems team.
  
Required Qualifications and Demonstrated Experience:

  * Demonstrated expertise with Linux systems administration.
  * Expert level knowledge of network and application security best practices.
  * Knowledge of application development best practices and ability to support related infrastructure such as continuous integration, monitoring, version control, automated builds, etc.
  * Demonstrated ability to develop new skills quickly, and to grasp unfamiliar architectures and application designs quickly.
  * Experience maintaining network firewall zones and iptables configuration
  * Demonstrated ability to work independently on a project from specification to launch; communicate effectively, orally and in writing; and work with all levels of staff, vendors, and consultants.
  * Four-year college degree or equivalent with at least three years demonstrated experience required.
  * At the 4P3 level, at least five years demonstrated experience required.
  
Desired Knowledge and Skills:

  * Experience with puppet, chef, or other system configuration management system
  * Demonstrated success participating in community-based open source projects, specifically those relevant to the Stanford Libraries' Digital Library architecture, such as Fedora, Blacklight, Solr or Hydra.
  * Demonstrated success participating in and contributing to open source software development projects.
  * Demonstrated experience with library applications and technology, including experience participating in relevant library open source efforts.
  * In-depth knowledge of library policies and practice, metadata standards and the scholarly communication framework
  * Familiarity with the process of digitizing images, text, audio and video in cultural heritage institutions.
  * Prior, successful experience working as a professional in an academic and/or library environment.



Brought to you by code4lib jobs: http://jobs.code4lib.org/job/7557/

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager