Generalizing from discussions within the GIS Data Modeling Working Group, this talk aims to address the potential benefits and risks involved in attempting to integrate Vagrant Boxes (virtual machine images) into software development and service deployment life cycles. An audio recording of the session is available for download below. and A lightning talk presentation at Hydra Connect 2016, described thus
Keyword:
Deployment, Connect 2016, Hydra, and Lightning talk
Subject:
Hydra Project
Creator:
Griffin, James
Contributor:
Lafayette College Libraries and GIS Data Modeling Working Group
A presentation at Hydra Connect 2016 described thus, In this presentation, we will present a software development and deployment process that we have developed at Virginia Tech. We have used this procedure to develop several Hydra projects for University Libraries services at Virginia Tech and have also used it to conduct interviews for Ruby and Rails developers. We implemented a central vagrant box to facilitate the development and deployment processes. Using this vagrant box gives us many benefits, and 1. Code immediately. Our software engineers can focus on coding without worrying about software installation. 2. Unified development environment. All developers do their work in the same, consistent development environment. 3. Development of multiple projects simultaneously. Developers can work on multiple projects in parallel, switching between project environments in just a few minutes. 4. Minimal differences between development environments and production environment. After we finish implementation, we can quickly deploy our applications into a cloud environment (e.g. AWS and OpenStack) that is highly consistent with our development environments. We will present and demonstrate our hands-on experience on how we use a single vagrant box with different GitHub repositories to develop multiple Hydra applications in detail, including Sufia, GeoBlacklight, Fedora, Solr, Vagrant, AWS, and OpenStack. An audio recording of the session is available for download below.
At Stanford libraries we've run hundreds of virtual machines to support dozens of applications. We've found the cost and complexity of patching and maintaining these machines to be untenable. We believe that a serverless infrastructure is our future and so we are using AWS Fargate (Elastic Container Services) and Lambda architecture to reduce our maintenance burden. We will explain the AWS offerings in this space, explain how we can set up a simple distributed system, and point out pitfalls that we've experienced. and A video recording of a presentation at Samvera Connect 2018 described thus
Keyword:
Deployment, Connect 2018, and Samvera
Subject:
Samvera Community
Creator:
Coyne, Justin
Contributor:
Stanford University Libraries and University of Utah
A presentation at the Open Repositories conference in 2014. There are those who perceive that implementing, running and maintaining a Fedora-based digital repository is a daunting task suited only to institutions with a significant team of developers and support staff. This paper offers a different perspective. The University of Hull in the UK, the Rock and Roll Hall of Fame and Museum in Cleveland, Ohio, and the Chinese Historical Society of Southern California (CHSSC) provide three case studies of Hydra-based repositories that are centred on a single developer working with small, limited or no support. This talk will compare and contrast their experiences and explain why the developers concerned feel that creating and maintaining these successful repositories has been worth their time and effort.
Keyword:
Deployment, Case study, Hydra, and Open Repositories 2014
Subject:
Hydra Project
Creator:
Wead, Adam, Awre, Christopher L, Green, Richard A, Ng, Steven, and Lamb, Simon W
Contributor:
University of Hull, Chinese Historical Society of Southern California (CHSSC), and Rock and Roll Hall of Fame and Museum