History

1. Unconference Session at Samvera Connect 2019

Scope & Objectives

1. There is much duplication when it comes to Docker containers for certain infrastructure/services
2. Primary Elements
   1. Deployment
   2. Runtime
   3. Dev. Practices
   4. Monitoring
   5. Observability
   6. Metrics
3. Topics for Inclusion
   1. Anything that is required for the application to run in a particular environment
   2. Everything from environment variables, documentation, containers, CI scripts...
   3. Anything in the deployment and runtime environment
   4. Much larger in scope than application
4. Gentle recommendations regarding software development best practices?
   1. A series of guardrails and referencing what those might be

Audience(s)

Deliverables & Timeframe

Deliverables

1. First Order
   1. DockerHub Organization for Samvera
   2. Dockerfiles for major stack components
   3. Example docker-compose structure for the full stack
   4. Vagrant image or other full-stack example
2. Aspirational
   1. Helm charts or guidance around other orchestration tools (e.g., Kubernetes)
   2. Other infrastructure-as-code templates/manifests/playbooks/examples (Puppet, Chef, Ansible, Terraform, CloudFormation)

Timeframe

The Samvera Infrastructure working group will begin its work in January 2019 and deliver a wrap-up report (with the goal of extending the work into a second cycle) at Samvera Connect 2020.

Meeting Times & Communication Channels

Blue Jeans (copy meeting info from one of the call Agenda/Notes pages)

Members

• Michael B. Klein (facilitator) – Northwestern University Libraries / Michael Klein/ michael dot klein at northwestern.edu

Resources