This presentation covers the work done by Erik Mitchell, Kevin Gilbertson, Jean Paul Bessou, Barry Davis and Tim Mitchell in moving the ZSR library to Amazon servers
2. Making your IT skills
virtual
What it takes to move your services to the cloud
Erik Mitchell | Kevin Gilbertson | Jean Paul Bessou
Z. Smith Reynolds Library Wake Forest University
4. Motivating factors
“ For shared development projects and services,
cloud based services offer libraries and their
partners the opportunity to move outside the
organization bureaucracy and into International
waters, where projects are able to function
unencumbered… ”
Terry Reese - Oregon State
University
http://oregonstate.edu
5. Support for
Demand for Capacity to
core library + new services - manage
services
=
IT crisis
6. The EC2 is with you
Why would you
move your library
IT to the cloud?”
7. Choose a solution
{
Approach Systems
OpenURL resolver, Stats
SaaS manager, research guides,
online reference
Service catalog Integrated library system,
PaaS Interlibrary loan, copyright
compliance systems
Discovery, digital repository,
archives management, website,
IaaS digital storage, institutional
repository
8. Hybrid approach
Amazon EC2
Infrastructure, Server
images, backup processes, Amazon S3
monitoring, service
deployment, code
management Data archiving, system
backups, file system SaaS
operations
Hosted end-point services,
Amazon EBS data subscriptions, 100%
outsourced options
Server disks, application and PaaS
data storage, platform for
EC2 systems Custom configurations,
single purpose applications
(ILS), proprietary systems
9. Themes for today
Running services in the cloud
IT service management for librarians
What we learned and what next
10. Views of cloud
computing
Definitions Gartner, NIST
Contexts Public vs. private, Own vs. subscription
Models Services, Platforms, Infrastructure
11. Types of cloud
computing services
Applications that provide ‘end-user’
Software experiences - SerialsSolutions,
Wordpress.com, WorldCat Local
An environment for delivering customized
Platforms
services - Site hosting, DuraSpace,
Open infrastructure that can be used for
Infrastructure any purpose, Amazon EC2, Microsoft
Azure
12. Contrasting views
Opportunities Challenges
Network foundation
Lower initial cost
adds complexity
Flexible, scalable as Collaboration with
needed partners is key
Solutions tailored to fit Security, connectivity,
specific service needs contingency plans are key
13. Deploying your
service
Service level agreements
Between provider and library, library and campus it, library and customers
Access and security
Firewall, DNS, VPN, LDAP, SSL, Public & private keys, authentication
Managing user access
15. ITSM for Librarians
Principles of IT Service management
Using people skills in addition to technical skills
Understanding your core services
Time and staff allocation for system support
24. we started with a definition. what do we need?
we did some assessment. where are you? where am I?
we ended with a plan. sysadmin in six weeks! ;)
and then we learned.
and tested...and learned some more...and tested...and learned some more...
27. we ranked our services. what would be first?
we built the production box. backups! monitoring!
we migrated our applications. let me tell you about the easy ones.
and then we waited...
30. we pulled together the documentation we created during our learning
sessions to form a set of introductory tutorials.
they are a starting point.
we offer them to anyone who is where we were.
zsr.wfu.edu/litacloud
Notas del editor
Library services through cloud computing
Share experience from WFU
Relate examples from ALA session
The Crisis is not unique to libraries, Academic IT departments all feel this pressure
 
motivations
political - internally it was increasingly difficult to get IT resources for library applications, compared to banner & other system, economic - we needed to buy new servers, technical - we needed to get some new services running
2 second change for us - lots of red tape, any changes to php.ini, changes to apache config, changes to mysql databases
Lack of access makes it more difficult to debug errors
You have to setup your own server to know how things work
Stable production environment vs rapid upgrade cycle - how do you maintain both of those.  
Amazon makes this easier -
Being able to run multiple instances of an application
 
Resonated because of Digitalforsyth experience
Cloud allows you to form partnerships without involving local IT resources, allows you to find neutral playing field
Sometimes regulations help, sometimes provide unnecessary barriers
How has library IT changed in the last decade? What does this change mean in relation to librarianship in general?
Librarianship is becoming more interdisciplinary, more specialized
Problems are growing in complexity
Expected speed of adoption is changing
What is the IT crisis?
For WFU it was the realization that library systems faced a shorter implementation and life cycle than IS was used to
Services in the wing were waiting to be implemented
Open source comes with great opportunities but the need to be more involved with your systems
It is not enough to be an application user if you cannot direct the system configuration
How did we address this crisis?
Realizing that we had an opportunity to move - cost comparison
Laying the policial framework - Preserve partnerships, establish autonomy, demonstrate success
Know your limits - It was a long discovery process
Theresa Rowe - Educause webinar - cost savings, resource availability, service agility. makes sense to move commodity services such as email and storage. recruitment and job application (not core service areas) harder to move CMS, things that add value to departments, LMS for example
Service catalog - WFU case study - decided that subscription computing was more attractive than ownership models
Over course of 4 years moved everything - really focused for last 18 months
some elements had steep learing curve -talking more about that at LITA
Lynch pin - needed all new servers - looked at cost vs cloud
Hybrid models - Decided to move everything, used mix of models
SAAS - help save staff time/expertise
PAAS - When you want someone to manage the platform (ILS, ILL)
IAAS - when you need customizabiltiy, scalability (Dspace, Vufind)
Techical skills - a focus on server administration and application mangement
Group work - learned together over the course of 6 months
ITSM - help desk, know when to take a technical role, when to play a managment role
Political - burning bridges does not help :) - we need our IT to play with us more than ever.
Main point - talk about definintions of the cloud
It is subscription based
There are three types of models -Saas, Paas, Iaas, 
Opportunities
Scalable, outsourced, lower cost?
Challenges 
security/privacy,
How do you run a cloud-based server - what makes it unique?
Understanding size & subscription on cloud vs local hardware
Choosing your platform (SAAS, PAAS, IAAS)
Mediatemple - worked great as a simpleplatform - lots of autoconfig made it difficult to run more advanced apps.
hard to attach lots of disk space
ExLibris hosting - off load as much as you could
Google Apps Engine - great, cheap but you have to do things ‘their way’
Types
service - delivered as an ‘end-user’ application - serialssolutions
platform - space for hosting custom services - application hosting - duracloud
Infrastructure - open capacity - servers, disks - amazon
Techical skills - a focus on server administration and application mangement
Group work - learned together over the course of 6 months
ITSM - help desk, know when to take a technical role, when to play a managment role
Political - burning bridges does not help :) - we need our IT to play with us more than ever.
Techical skills - a focus on server administration and application mangement
Group work - learned together over the course of 6 months
ITSM - help desk, know when to take a technical role, when to play a managment role
Political - burning bridges does not help :) - we need our IT to play with us more than ever.
IT service management
Elements of IT service management
Ensuring service uptime
Monitoring - nagios, system backups
Second monitoring server -
Documenting services and platforms
Systematic troubleshooting
Public and private documentation (wiki vs confluence)
help desk software - jira,
keeping track of the complicated stuff
Keep documentation about your server on another server
Providing help to your users
SLAs?
Who has acces to your server?
Sizing and managing servers
One-Server-per-service model vs. mega-server model?
Disk space
Cost and upgrades
Amazon cost calculator - costs tend to fluctuate and grow
Being proactive in partnering with IT - know the cloud issues (security, sla, cost).  be willing to take the lead with your IT partnership
Techical skills - a focus on server administration and application mangement
Group work - learned together over the course of 6 months
ITSM - help desk, know when to take a technical role, when to play a managment role
Political - burning bridges does not help :) - we need our IT to play with us more than ever.
IT service management
Elements of IT service management
Ensuring service uptime
Monitoring - nagios, system backups
Second monitoring server -
Documenting services and platforms
Systematic troubleshooting
Public and private documentation (wiki vs confluence)
help desk software - jira,
keeping track of the complicated stuff
Keep documentation about your server on another server
Providing help to your users
SLAs?
Who has acces to your server?
Sizing and managing servers
One-Server-per-service model vs. mega-server model?
Disk space
Cost and upgrades
Amazon cost calculator - costs tend to fluctuate and grow
Managing complexity
Expertise is an issue - the more you take on CC, the closer you come to an IT department
Server cost models and sizing
Sizing and managing servers
One-Server-per-service model vs. mega-server model?
Disk space
Cost and upgrades
Amazon cost calculator - costs tend to fluctuate and grow
Managing complexity
Expertise is an issue - the more you take on CC, the closer you come to an IT department
Server cost models and sizing
Sizing and managing servers
One-Server-per-service model vs. mega-server model?
Disk space
Cost and upgrades
Amazon cost calculator - costs tend to fluctuate and grow
Amazon s3 firefox plug in - working with speical collections to evaluate
VPN is a key aspect here
allows you to monitor / manage resources from anywhere
VPN is a key aspect here
allows you to monitor / manage resources from anywhere
How do you get there from here?  learning & help?
how we did it
Started with wide levels of knowledge
Team-wide effort, everyone learned everything at first, specialized later
Used meetings, free training, self training as key methods
Some valuable resources
ITSM
Sun tutorials
Linux administration handbook Evi Nemeth
What came out of the tutorials & learning sessions
Core linux & system skills (firewall, apache config, starting & managing servers, app install & configuration, sudo & users)
Everyone installed vufind on a l
Everyone migrated blog site from wfu (mysql tools, file transfer)
People tended to specialize - server management is distributed (about 10% of job).
Ranked our services & mapped out a timeline
- what had to move first
- what was easy to move
- what was hard 
- What needed to go last
Path to production
- Setup production server, monitoring server, etc.
-- get ready for services
-- nagios, backups, etc.
- Vufind first 
-- easy to move back - we used apache level redirects to go into production (april 14th)
-- No migration was required
-- Started over with a new server (large server on May 13th) before we did anything else.
- Blogs & wikis were second
-- (may 14, & 19 repsectively)
- Website was tougher than we thought
-- had to do dns so it was good to have done some other stuff first
-- Old applications with lots of different requriements (sam wait collection)
-- Ldap auth was problematic
-- https was problematic
--- Having more than one domain point to https - we use port 4430 for cloud.lib.wfu.edu - You cannot have more than one name based virtual host share an https connection on a single server.  that handshake happens before apache sends teh name based virtual host stuff.  One solution is to redirect all secure traffic to one name, another is to use multiple ports (cloud.lib.wfu.edu:4430 zsr.wfu.edu on 443)
--- We did not config apache running mods_augs_ldap - allwoed .htaccess files to produect and auth using univ ldap server - we did not fully appreciate how it was happening on boulder - once we were close enough we didnt try making that config change on teh apache server
- Firewall rules
-- voyager, campus 
- Dspace was last - mostly becuase it was hard to get data out of. (early july)
- PCL came in mid summer (late july)
Observations
Tutorials are a starting point
Lessons learned & things we would do differently
hard to know where to look - ‘dont know what you dont know’
Its true ITSM takes time -
Customizations
Our local IT department was heavily localized & customized (cfengine, local policies) - we found that we had to make our own decisions here.  Tough to be on the outside.  
Tough problems don't go away on their own
find workarounds / solutions
 
is this outsourcing?
depends on if you have local expertise, need to keep it, -