Dev ops in the Digital Repository of Ireland - Stuart Kenny
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Dev ops in the Digital Repository of Ireland - Stuart Kenny

on

  • 412 views

 

Statistics

Views

Total Views
412
Views on SlideShare
412
Embed Views
0

Actions

Likes
0
Downloads
5
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

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

Dev ops in the Digital Repository of Ireland - Stuart Kenny Presentation Transcript

  • 1. DevOps in the Digital Repository of Ireland
  • 2. About DRI (http://www.dri.ie/) ● DRI is an interactive trusted digital repository for contemporary and historical, social and cultural data held by Irish institutions ● Exchequer funded; HEA PRTLI 5, €5.2M ● RIA (lead), NUIM, TCD, DIT, NUIG, NCAD ● Partners: academic, cultural, social, government ● Duration - Sep 2011 – Sep 2015
  • 3. Objectives ● Trusted Digital Repository (TDR) ○ Provide reliable, long-term access to managed digital resources  Open Archival Information System (OAIS)  ISO16363 Trusted Digital Repository (TDR) Checklist  Certification (DSA) ● Central internet access point o Interactive multimedia tools
  • 4. Organisation User Interface configurable bi-lingual multi-modal accessible Data Management software architecture tool-set curation preservation Storage federated secure scalable resilient
  • 5. Requirements ● Stakeholder interviews ○ Requirements ○ Policy ● Core DRI requirements ○ Multiple data types ○ Multiple metadata standards ○ Access controls ● Mapped to Cucumber features
  • 6. Technology Choices ● ● ● ● ● ● ● ● Ruby on Rails (http://rubyonrails.org/) Git (http://git-scm.com/) Jenkins (http://jenkins-ci.org/) Cucumber (http://cukes.info/) Project Hydra (http://projecthydra.org/) Ansible (Dev/Test/Prod) (http://www.ansibleworks.com/) Vagrant (Dev) (http://www.vagrantup.com/) OpenNebula (Test/Prod) (http://opennebula.org/) ○ Originally FP7 Funded
  • 7. Hydra • • • Open-source repository solution Open architecture o Common core o Solution bundles Community o Developers and adopters
  • 8. OpenNebula ● Open-source IaaS ○ Private cloud o Hybrid cloud support Lightweight o Management interface o VM hosts o Storage Community support • •
  • 9. Development Practices ● Communication ○ ‘Stand-ups’ ○ Teleconference ○ Face-to-Face ● Collaboration ○ Issue tracking ○ Version control ○ Continuous integration ● Consistent environment ○ Virtualisation
  • 10. Development Environment ● Development scaffold ○ Automated ○ Repeatable ● Production like environment ○ OS ○ Package versions ● System dependencies ○ Fedora ○ Solr ○ Redis/Resque ○ MySQL ○ Ceph S3 ○ Passenger ○ ClamAV, ffmpeg….
  • 11. Deployment ● Local test suite ○ Cucumber/RSpec ● Continuous integration ○ Automated build and test ● Deployment ○ Automated with Ansible ○ Development/production
  • 12. Deployment
  • 13. Operations ● Preservation and disaster recovery ○ File fixity ○ Replication ● Auditing ○ Security (authorisation and authentication) ○ Malware scanning ○ Characterization ● DOIs ○ Minting, Takedowns, Updates ● User support
  • 14. Issues ● Translating requirements to specification ○ Maintaining Cucumber steps ● Initial stakeholder interaction ● Hydra rapid development ● Institutional networking restrictions ● RHEL (rvm/ruby, ceph, haproxy...) ● Performance issues ○ Many moving parts
  • 15. Questions? Team ● TCD - Jimmy Tang, Kathryn Cassidy, Peter Tiernan, Stuart Kenny ● NUIM - Damien Gallagher, Sinéad Redmond ● DIT - Eoin Kilfeather, Monica Harasimiuk, Anna Deegan