4. Solutions { Service catalog Approach Systems SaaS OpenURL resolver, Stats manager, research guides, online reference PaaS Integrated library system, Interlibrary loan, copyright compliance systems IaaS Discovery, digital repository, archives management, website, digital storage, institutional repository
5. Current configuration Infrastructure, Server images, backup processes, monitoring, service deployment, code management Amazon EC2 Hosted end-point services, data subscriptions, 100% outsourced options SaaS Custom configurations, single purpose applications (ILS), proprietary systems PaaS Data archiving, system backups, file system operations Amazon S3 Server disks, application and data storage, platform for EC2 systems Amazon EBS
6. Service management install configure secure backup document deploy monitor administer upgrade remove Server images EC2 services
7.
8.
Notes de l'éditeur
Goals: discuss our process and current approach to using cloud services, platforms, and infrastructure to serve our IT needs
Cloud is cool - so we hear What does it mean to actually do this? Where were we coming from?
Need: Implement and manage library systems faster and more flexibly than local solutions would allow Turn infrastructure into a service Turn recurring projects into scalable solutions (vufind, community training) Administrators dont understand why technology ‘expires but they do understand subscriptions
Background WFU - sports, liberal arts, student and faculty focus in library Move to the cloud based on need to provide IT services more quickly Library IT changing rapidly Questions If library IT is changing so fast, does traditional approaches to providing infrastructure still work? Can subscription models be more effective? has been effective in other areas What perils exist? What do you need to know? Is it a viable option for your staff? Pathways There are many options - even more now than when we started - PaaS options, Duraspace, co-located preservation Contiumum from individual cloud to community hosted (lockss) These are some of the challenges we faced Chose amazon because it gave us open stable services Story - Realizing what it took - training, marketing, adapting Solutions Library was positioned to make the full move by previously adopting Saas and Paas solutions IaaS approaches had been limited by local infrastructure options Current configuration Use Amazon EBS instnaces - define Use S3 for backup & storage Use browser based and command line tools for management Use open source tools (zmanda, nagios, svn) and some proprietary tools (confluence, jira) Dual server approach - production & monitoring Issues - server size options, fair pricing model - affordable (in the hundreds of dollars per month) vs Paas solutions - in the thousands per month EC2 services server images, backups ec2 services - ip addresses, volumes, snapshots, security groups Means IT has to do DNS, security certs, firewall Intersted in more? We have documented some of our 'tutorials' Good books, websites