Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

ALA Cloud Computing Introduction 2015


Published on

Presented Nov 18, 2015
Brief introduction to the types of cloud services, how libraries are using the cloud and the future of the cloud in libraries.
Includes presentation notes

Published in: Education
  • Be the first to comment

  • Be the first to like this

ALA Cloud Computing Introduction 2015

  2. 2. WHAT IS THE CLOUD? pretty familiar now applications do not run on single computer but spread over distributed cluster, using storage space and computing resources from many available machines as needed
  3. 3. adoption of cloud now common place - obligatory gartner hype cycle for emerging tech showing last year and this cloud computing still in trough of disillusionment
  4. 4. now no longer an issue, all comfortable with it
  6. 6. FROM PROCURING TO MANAGING TECH - shift priorities from managing IT to service oriented goals
  7. 7. FEATURES ▸ ON-DEMAND SELF-SERVICE ▸ BROAD NETWORKING ACCESS ▸ RESOURCE POOLING ▸ RAPID ELASTICITY ▸ MEASURED SERVICE - from National Institute of Standards and Technology (NIST)- - on-demand demand self service - access when you want, get more when you need it easily - broad network access - need/use internet to access, use with any internet ready device - resource pooling - resources easily shared, adjust for peak times - rapid elasticity - automatically scale as needed. grows as you need it; great for pilot projects. start small, grow as required rather than overbuy for potential growth or refigure infrastructure when move to actual project - measured service - like electricity; pay for what you use - multi tenancy - one of the other terms often associated with cloud computing is multi-tenancy - single software instance that runs on a server, which many access. one instance of the software for an discovery layer that many libraries access, may be able to customize a little, but the main is one software
  8. 8. CLOUD TYPES ▸ PUBLIC ▸ PRIVATE ▸ COMMUNITY ▸ HYBRID - public most common, sign up and go - private 1 institution only - community specific community, shared interests/concerns - government is good ex. higher education might have. like minded people share, consortiums - hybrid combo of the others
  10. 10. INFRASTRUCTURE AS A SERVICE (IAAS) - buying space/time on external servers. dealing with parts that are key to IT - servers, hardware, networking - staff prepared for high level of involvement
  11. 11. PLATFORM AS A SERVICE (PAAS) - existing sw platform to build your own applications on, uses provider’s infrastructure.
  12. 12. SOFTWARE AS A SERVICE (SAAS) - most common - - sign up and go
  14. 14. OUR PATRONS - used to it, want it, expect it
  15. 15. GOALS to provide best access, best service, reduce costs, campus or city initiative to consolidate services, etc
  16. 16. BUDGET - cuts, need to make changes - can’t afford IT dept, so use the cloud to support services instead
  17. 17. PERSONNEL - losing people, can’t replace (retirements, etc) - new skills needed
  18. 18. MOBILE DEVICES - mobile devices thrive on the cloud
  19. 19. POLICIES & REGULATIONS - major reason not to - provincial or state regulations may prohibit - privacy - data storage - legal is confusing to say the least
  21. 21. INFRASTRUCTURE AS A SERVICE (IAAS) - amazon web services (EC2 - elastic compute cloud & S3 - simple storage service) - can use open source software on such services for digital archives, etc - requires most tech know how - closest to having servers on site
  22. 22. PLATFORM AS A SERVICE (PASS) - for developing, testing, deploying, updating, hosting services - google app engine - windows azure - heroku - some ILS
  23. 23. SOFTWARE AS A SERVICE (SAAS) - most common - discovery layers (EDS, Primo, Summon) - ils - library services platforms (OCLC Worldshare, Ex Libris Alma, Proquest Intota) - citation managers - openurl resolvers - libguides - flickr - social media - stackmap
  24. 24. LIBRARY SERVICES - discovery layers - LSP/URM (Alma, Worldshare) - built from ground up - multitenant - allow for move to service oriented architecture, new agility to innovate & include new services - cataloguing - LibraryThing, biblios, book where
  25. 25. REFERENCE & INSTRUCTION - get out from ref desk - libguides - gforms, gdocs - poll everywhere - youtube, jing
  26. 26. MARKETING & OUTREACH -social media
  27. 27. QUESTIONS
  29. 29. SHARING - share metadata - share resources - share data
  30. 30. COLLABORATION - save time - metadata - Haithi Trust - bX Recommender - LibraryCloud (Harvard library innovation lab)
  31. 31. SERVICE - support - vendor side updates - in turn, focus on our own service rather than tech support
  32. 32. ACCESS any time, any where
  33. 33. COST no longer need to but servers that cost $1000s
  34. 34. SCALABILITY - grows as you need it - good during exam times when servers often busy, offloads to other servers to continue service; ideally less downtime - great for projects - start a pilot with a cloud service. if successfully, easily transition to full service; adjust needs only when needed
  35. 35. INNOVATION less time on maintenance = more time on innovation
  36. 36. DIGITIZATION - less time on maintenance, more time for digitizing our unique collections - can use the cloud to build digital collections, with less cost and IT maintenance
  37. 37. ASSESSMENT - new systems being built to make it easier to assess our collections - cloud is ideally about being open and sharing data - can compare our libraries with like libraries - build unique collections - save collections money - make sure we’re doing what our users need/want
  38. 38. GREEN - potential to be better for environ - fewer servers eating up energy - bigger companies can set up more efficiently
  40. 40. CHANGE - new skills, new focus - service rather than IT - new workflows, give up old practices
  41. 41. SUPPORT - being in a cloud means learning new things - support staff in learning - need to support users as learn new tools - need to deal with BYOD culture - how train our staff to handle questions or should they even support all devices?
  42. 42. COST - move to subscription based, recurring fees rather than one time fees - features can cost more - customizations can cost more
  43. 43. CONTROL - can’t do things when we want - reliant on others - customizations may be harder to implement
  44. 44. FORCED UPDATES - can cause issues for any customizations we may make - usually sandbox to help with that but change is coming regardless
  45. 45. DATA OWNERSHIP - a primary concern for libraries - ie. if sharing your metadata, do you retain it?
  46. 46. SECURITY - usually better but can still be an issue - threats: data leaks, breaches, or loss; denial of service attacks, - risks: service termination/failure, data protection, etc
  47. 47. RELIABILITY - nothing’s perfect - often part of an SLA (more soon) - issue can be with provider or with broadband provider - can be bought out by bigger companies or fail
  48. 48. PRIVACY - number 1 concern of libraries and many patrons - library data must be kept private -needs of larger organization/institution/province/state/nation can affect if you can use cloud
  49. 49. TEXT DO YOU TRUST YOUR DATA/INFO TO THE CLOUD ▸ A. Yes, I trust my data in the cloud ▸ B. Yes, I put some of my data in the cloud but I don’t really trust it ▸ C. No, I don’t trust the cloud at all
  51. 51. BUDGET - often start free and then costs increase - customizations can cost - one time to subscription fee - cost of data storage - cost by number of users
  52. 52. PERSONNEL - often used as an excuse to reduce IT - not necessary - may change but need someone who is well versed to deal with SLA, etc. IaaS still needs high level skills, just not on own servers. security issues to deal with. it won’t run itself. integration with other systems. apis, etc - new set of skills to implement and manages complex cloud services, to see how systems relate, make them work together
  53. 53. TRAINING & SUPPORT ‣ realign jobs ‣ support & training of byod
  54. 54. DIGITAL DIVIDE - not gone yet
  55. 55. BANDWIDTH - do you have bandwidth in area/institution to support a cloud service - what happens if it goes down? - we’re not at ubiquitous connectivity, not cheap enough, outages still happen. interruptions means loss of productivity
  56. 56. SERVICE LEVEL AGREEMENTS (SLA) When looking at a cloud based service, consider the following ‣ security (firewalls, web app protection, etc) ‣ storage space ‣ cost (subscription, IP/bandwidth costs, etc) ‣ ease of use/training/support ‣ data backup ‣ data restoration ‣ what features are paid vs free ‣ autoscaling/load balancing ‣ monitoring ‣ compatibility ‣ speed (processor, bandwidth, etc) ‣ control ‣ 3rd party app support ‣ consider security, scalability, availability, reliability
  57. 57. W H A T H A P P E N S I F T H E R E ’ S A B R E E C H ? W H A T H A P P E N S I F T H E Y F O L D ? W H A T I S T H E U P T I M E ? W H A T S E C U R I T Y I S O F F E R E D ? H O W M A N Y S I M U LTA N E O U S U S E R S ? W H A T A R E Y O U R P E R F O R M A N C E B E N C H M A R K S ? W H A T S U P P O R T I S O F F E R E D ? M A I N T E N A N C E S C H E D U L E S W H A T I S T H E R E S P O N S E T I M E ? - good checklist of questions from Jessica Bushey et al - Cloud Service Conracts, an issue of trust in Canadian journal of information and library science
  58. 58. LOCK IN - what happens when license terms change for the worse, or costs increase excessively, or a better system comes along?
  59. 59. QUESTIONS
  62. 62. PRODUCTIVITY & STORAGE - lots out there - gdocs, gforms, storage (gdrive, dropbox, box), wunderlist, remember the milk, kanban boards, bookmarking (delicious), evernote
  63. 63. COLLABORATION - gdocs, dropbox, etc
  65. 65. OPEN ARCHITECTURE & SERVICE ORIENTED ARCHITECTURE (SOA) - more open - apis to work between, share data - move beyond library silos
  66. 66. ASSESSMENT - more we share, the better we assess - new systems being designed with assessment in mind
  67. 67. DEMAND DRIVEN ACQUISITION (DDA) better DDA as we can assess better
  68. 68. LINKED DATA -potential to move towards linked data as we share the work of metadata together - move towards the semantic web - open our data up beyond library systems
  69. 69. WEB DRIVEN - move to linked data means that more traffic will come from outside our library services
  70. 70. BIG DATA - with all this information in the cloud, we’re seeing a rise in big data - open, sharing data
  71. 71. DATA AS A SERVICE - we can start exploring what libraries should do with data as a service - leverage the cloud to support the data needs of our institutions or cities
  72. 72. DATA VISUALIZATION start doing more with data visualization - our own or supporting others
  73. 73. DIGITAL PUBLICATION - digitize our own publication, open them up to the world - cloud can help accomplish this, at least in storage
  74. 74. DIGITAL PRESERVATION - of our own digitized products - of our researchers - of cloud data
  76. 76. THANKS!