History
Scope & Objectives
- There is much duplication when it comes to Docker containers for certain infrastructure/services
- Primary Elements
- Deployment
- Runtime
- Dev. Practices
- Monitoring
- Observability
- Metrics
- Topics for Inclusion
- Anything that is required for the application to run in a particular environment
- Everything from environment variables, documentation, containers, CI scripts...
- Anything in the deployment and runtime environment
- Much larger in scope than application
- Gentle recommendations regarding software development best practices?
- A series of guardrails and referencing what those might be
Audience(s)
Deliverables & Timeframe
Deliverables
- First Order
- DockerHub Organization for Samvera
- Dockerfiles for major stack components
- Fedora 4.x
- Apache Solr 7.x & Solr 8.x
- Example docker-compose structure for the full stack
- Vagrant image or other full-stack example
- Aspirational
- Helm charts or guidance around other orchestration tools (e.g., Kubernetes)
- 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 2020 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
- Ryan Ordway – Oregon State University Libraries / Ryan Ordway/ rordway at oregonstate dot edu