Chris tonjes cloud computing

Uploaded on

Cloud computing presentation for ALA 2010

Cloud computing presentation for ALA 2010

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide
  • Drupal based site, customized workflow and calendar


  • 1. Cloud Computing at DCPL
    Chris Tonjes
    LITA Cloud Computing Session
    June 25, 10
  • 2. What does DCPL have in the cloud? – an Amazon EC2 hosted site, with redundancy and a separate development cloud
    Digital Image Archive – an open source enterprise content management system (Alfresco) also hosted using Amazon EC2
    Google Documents for staff
    Central Desktop - cloud-based collaboration tool (similar to sharepoint)
    Web services – ILS data exchange web services used by our mobile apps, and by the District government’s identity management system
    Flickr Commons site – rare photo archive
  • 3. Why did we choose the cloud?
    Speed – we were under very tight deadlines to create a new web site. The alternative service provider could not guarantee rapid setup, redundancy, or multiple environments
    Cost – Our annual hosting bill (for both the web and our digital archive) is $4,800. Comparable costs from the alternative provider would be $54,000 per year (note that 80% of our Amazon hosting costs are reimbursed via Erate)
    Performance – Distributing assets through the cloud conserves bandwidth, and allows us to maximize infrastructure. Our site and applications are also architected for optimum load balancing.
    Technology - we are able to use the components we want, test them, and configure them according to our needs
    Compliance – we’ve sidestepped our alternative providers security and change management requirments, using instead ours and those contained in the Amazon SLA
  • 4.
  • 5. –Architecture!
  • 6. Digital Archive
    Uses Alfresco 3.2
    Designed/Architected for Amazon EC2
    Includes customized metada (Dublin Core)
    Images will be geocoded
    DrupalAlfreso module and CMIS ensure smooth data exchange
  • 7. Digital Archive – Home
  • 8. Digital Archive – Search Results
  • 9. How do staff and customers benefit?
    Enhanced collaboration – over 40 people are active contributors to (previously there were 2)
    Vertical and Horizontal expansion – we quickly create new “sub sites” for programs and organizations
    Focus on content and media - staff are experimenting with podcasts, and thinking of ways to create and leverage content
    Technology is everyone’s job – we can spend more time training and consulting, less time supporting apps!
    Experimentation and practical discovery – we enhance and improve site components using drupal-based programs, such as open atrium (
  • 10. What’s next?
    Migrating our OPAC (Vufind) to the cloud
    Upcoming partnership with Google (whereby cardholders automatically receive Gmail and Google Docs accounts)
    Our own direct download open source books (downloaded to aforementioned customer Google accounts)
    Home made self check machines! (code and interface live at Amazon)
    Cloud based pxe server containing images
    Increased use of backup/restore functions
    Further adventures in virtualization!
    Tableau server data visualization tool