Making your it skills virtual
Upcoming SlideShare
Loading in...5
×
 

Making your it skills virtual

on

  • 1,062 views

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

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

Statistics

Views

Total Views
1,062
Views on SlideShare
753
Embed Views
309

Actions

Likes
0
Downloads
11
Comments
0

3 Embeds 309

http://www.erikmitchell.info 306
http://translate.googleusercontent.com 2
http://erikmitchell.info 1

Accessibility

Categories

Upload Details

Uploaded via as Apple Keynote

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • <br />
  • Library services through cloud computing <br /> Share experience from WFU <br /> Relate examples from ALA session <br />
  • <br />
  • The Crisis is not unique to libraries, Academic IT departments all feel this pressure <br /> &#xA0; <br /> motivations <br /> 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 <br /> 2 second change for us - lots of red tape, any changes to php.ini, changes to apache config, changes to mysql databases <br /> Lack of access makes it more difficult to debug errors <br /> You have to setup your own server to know how things work <br /> Stable production environment vs rapid upgrade cycle - how do you maintain both of those. &#xA0; <br /> Amazon makes this easier - <br /> Being able to run multiple instances of an application <br /> &#xA0; <br /> Resonated because of Digitalforsyth experience <br /> Cloud allows you to form partnerships without involving local IT resources, allows you to find neutral playing field <br /> Sometimes regulations help, sometimes provide unnecessary barriers <br />
  • How has library IT changed in the last decade? What does this change mean in relation to librarianship in general? <br /> Librarianship is becoming more interdisciplinary, more specialized <br /> Problems are growing in complexity <br /> Expected speed of adoption is changing <br /> <br /> What is the IT crisis? <br /> For WFU it was the realization that library systems faced a shorter implementation and life cycle than IS was used to <br /> Services in the wing were waiting to be implemented <br /> Open source comes with great opportunities but the need to be more involved with your systems <br /> It is not enough to be an application user if you cannot direct the system configuration <br />
  • How did we address this crisis? <br /> Realizing that we had an opportunity to move - cost comparison <br /> Laying the policial framework - Preserve partnerships, establish autonomy, demonstrate success <br /> Know your limits - It was a long discovery process <br /> <br /> 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 <br />
  • Service catalog - WFU case study - decided that subscription computing was more attractive than ownership models <br /> Over course of 4 years moved everything - really focused for last 18 months <br /> some elements had steep learing curve -talking more about that at LITA <br /> Lynch pin - needed all new servers - looked at cost vs cloud <br /> <br />
  • Hybrid models - Decided to move everything, used mix of models <br /> SAAS - help save staff time/expertise <br /> PAAS - When you want someone to manage the platform (ILS, ILL) <br /> IAAS - when you need customizabiltiy, scalability (Dspace, Vufind) <br /> <br />
  • Techical skills - a focus on server administration and application mangement <br /> Group work - learned together over the course of 6 months <br /> ITSM - help desk, know when to take a technical role, when to play a managment role <br /> Political - burning bridges does not help :) - we need our IT to play with us more than ever. <br />
  • Main point - talk about definintions of the cloud <br /> It is subscription based <br /> There are three types of models -Saas, Paas, Iaas,&#xA0; <br /> Opportunities <br /> Scalable, outsourced, lower cost? <br /> Challenges&#xA0; <br /> security/privacy, <br /> How do you run a cloud-based server - what makes it unique? <br /> Understanding size & subscription on cloud vs local hardware <br /> Choosing your platform (SAAS, PAAS, IAAS) <br /> Mediatemple - worked great as a simpleplatform - lots of autoconfig made it difficult to run more advanced apps. <br /> hard to attach lots of disk space <br /> ExLibris hosting - off load as much as you could <br /> Google Apps Engine - great, cheap but you have to do things &#x2018;their way&#x2019; <br />
  • Types <br /> service - delivered as an &#x2018;end-user&#x2019; application - serialssolutions <br /> platform - space for hosting custom services - application hosting - duracloud <br /> Infrastructure - open capacity - servers, disks - amazon <br />
  • <br />
  • Techical skills - a focus on server administration and application mangement <br /> Group work - learned together over the course of 6 months <br /> ITSM - help desk, know when to take a technical role, when to play a managment role <br /> Political - burning bridges does not help :) - we need our IT to play with us more than ever. <br />
  • Techical skills - a focus on server administration and application mangement <br /> Group work - learned together over the course of 6 months <br /> ITSM - help desk, know when to take a technical role, when to play a managment role <br /> Political - burning bridges does not help :) - we need our IT to play with us more than ever. <br />
  • IT service management <br /> Elements of IT service management <br /> Ensuring service uptime <br /> Monitoring - nagios, system backups <br /> Second monitoring server - <br /> Documenting services and platforms <br /> Systematic troubleshooting <br /> Public and private documentation (wiki vs confluence) <br /> help desk software - jira, <br /> keeping track of the complicated stuff <br /> Keep documentation about your server on another server <br /> Providing help to your users <br /> SLAs? <br /> Who has acces to your server? <br /> Sizing and managing servers <br /> One-Server-per-service model vs. mega-server model? <br /> Disk space <br /> Cost and upgrades <br /> Amazon cost calculator - costs tend to fluctuate and grow <br /> Being proactive in partnering with IT - know the cloud issues (security, sla, cost).&#xA0; be willing to take the lead with your IT partnership <br />
  • Techical skills - a focus on server administration and application mangement <br /> Group work - learned together over the course of 6 months <br /> ITSM - help desk, know when to take a technical role, when to play a managment role <br /> Political - burning bridges does not help :) - we need our IT to play with us more than ever. <br />
  • IT service management <br /> Elements of IT service management <br /> Ensuring service uptime <br /> Monitoring - nagios, system backups <br /> Second monitoring server - <br /> Documenting services and platforms <br /> Systematic troubleshooting <br /> Public and private documentation (wiki vs confluence) <br /> help desk software - jira, <br /> keeping track of the complicated stuff <br /> Keep documentation about your server on another server <br /> Providing help to your users <br /> SLAs? <br /> Who has acces to your server? <br /> Sizing and managing servers <br /> One-Server-per-service model vs. mega-server model? <br /> Disk space <br /> Cost and upgrades <br /> Amazon cost calculator - costs tend to fluctuate and grow <br />
  • Managing complexity <br /> Expertise is an issue - the more you take on CC, the closer you come to an IT department <br /> Server cost models and sizing <br /> Sizing and managing servers <br /> One-Server-per-service model vs. mega-server model? <br /> Disk space <br /> Cost and upgrades <br /> Amazon cost calculator - costs tend to fluctuate and grow <br /> <br /> <br />
  • Managing complexity <br /> Expertise is an issue - the more you take on CC, the closer you come to an IT department <br /> Server cost models and sizing <br /> Sizing and managing servers <br /> One-Server-per-service model vs. mega-server model? <br /> Disk space <br /> Cost and upgrades <br /> Amazon cost calculator - costs tend to fluctuate and grow <br /> <br /> <br />
  • Amazon s3 firefox plug in - working with speical collections to evaluate <br /> <br />
  • VPN is a key aspect here <br /> allows you to monitor / manage resources from anywhere <br />
  • <br />
  • VPN is a key aspect here <br /> allows you to monitor / manage resources from anywhere <br />
  • How do you get there from here? &#xA0;learning & help? <br /> how we did it <br /> Started with wide levels of knowledge <br /> Team-wide effort, everyone learned everything at first, specialized later <br /> Used meetings, free training, self training as key methods <br /> Some valuable resources <br /> ITSM <br /> Sun tutorials <br /> Linux administration handbook Evi Nemeth <br /> What came out of the tutorials & learning sessions <br /> Core linux & system skills (firewall, apache config, starting & managing servers, app install & configuration, sudo & users) <br /> Everyone installed vufind on a l <br /> Everyone migrated blog site from wfu (mysql tools, file transfer) <br /> People tended to specialize - server management is distributed (about 10% of job). <br />
  • <br />
  • <br />
  • Ranked our services & mapped out a timeline <br /> - what had to move first <br /> - what was easy to move <br /> - what was hard&#xA0; <br /> - What needed to go last <br /> <br /> Path to production <br /> - Setup production server, monitoring server, etc. <br /> -- get ready for services <br /> -- nagios, backups, etc. <br /> - Vufind first&#xA0; <br /> -- easy to move back - we used apache level redirects to go into production (april 14th) <br /> -- No migration was required <br /> -- Started over with a new server (large server on May 13th) before we did anything else. <br /> - Blogs & wikis were second <br /> -- (may 14, & 19 repsectively) <br /> - Website was tougher than we thought <br /> -- had to do dns so it was good to have done some other stuff first <br /> -- Old applications with lots of different requriements (sam wait collection) <br /> -- Ldap auth was problematic <br /> -- https was problematic <br /> --- 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. &#xA0;that handshake happens before apache sends teh name based virtual host stuff. &#xA0;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) <br /> --- 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 <br /> - Firewall rules <br /> -- voyager, campus&#xA0; <br /> - Dspace was last - mostly becuase it was hard to get data out of. (early july) <br /> - PCL came in mid summer (late july) <br />
  • <br />
  • <br />
  • Observations <br /> Tutorials are a starting point <br /> Lessons learned & things we would do differently <br /> hard to know where to look - &#x2018;dont know what you dont know&#x2019; <br /> Its true ITSM takes time - <br /> Customizations <br /> Our local IT department was heavily localized & customized (cfengine, local policies) - we found that we had to make our own decisions here. &#xA0;Tough to be on the outside. &#xA0; <br /> Tough problems don&apos;t go away on their own <br /> find workarounds / solutions <br /> &#xA0; <br /> is this outsourcing? <br /> depends on if you have local expertise, need to keep it, - <br />

Making your it skills virtual Making your it skills virtual Presentation Transcript

  • “Grandpa’s up there somewhere.”
  • 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
  • Overview The WFU experience Motivations, outcomes What we learned and what you should know Ideas for getting started
  • 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
  • Support for Demand for Capacity to core library + new services - manage services = IT crisis
  • The EC2 is with you Why would you move your library IT to the cloud?”
  • 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
  • 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
  • Themes for today Running services in the cloud IT service management for librarians What we learned and what next
  • Views of cloud computing Definitions Gartner, NIST Contexts Public vs. private, Own vs. subscription Models Services, Platforms, Infrastructure
  • 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
  • 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
  • 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
  • Case study - Vufind
  • 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
  • Learning Curve Technical skills IT Management skills Political & organizational skills
  • Balance server stability and service delivery
  • Service life-cycle install EC2 services configure secure backup document deploy monitor Server images administer upgrade remove
  • IT Management tools
  • Access for everyone
  • Mobile IT management
  • how do you get there from here?
  • here's how we did it.
  • 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...
  • the path to a nest of spiders.
  • ahem...the path to production.
  • 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...
  • so...what did we need to know?
  • more than we knew.
  • 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