...
This grid has been designed to help recommend how our images will need to evolve to support multiple deployment options.
Deployment Options | Uptime | DSpace Nodes | DB Nodes | Persistence | CLI Access | Notes | Changes needed |
---|---|---|---|---|---|---|---|
Local workstation/test server deployment with Docker |
Compose | Limited Duration for Testing | 1 | 1 | Docker Compose Volumes | docker exec | https://github.com/DSpace-Labs/DSpace-Docker-Images | |
Server deployment with Docker Compose |
(shell access to server and network drives) | Extended Availability | 1 | 1 | Docker Compose Volumes bound to file system storage | SSH + docker exec | Dockerfiles Insert custom dspace.cfg settings into distrib | |
Docker swarm options | Extended Availability | ? | ? | https://docs.docker.com/v17.09/get-started/part6/ | |||
Local workstation/test server deployment with Kubernetes |
Limited Duration for Testing | 1 | 1 | |||||
Server deployment with Kubernetes |
(shell access to server and network drives) | Extended Availability | 1 | 1 | ||||
Server deployment with Portainer management | Extended Availability | ? | ? | https://www.portainer.io | |||
Public cloud deployment using vendor-specific deployment option |
(such as Amazon ECS or Fargate) | Extended Availability | 1 | 1 | No access | DSpace Enable all CLI functionality through the REST API. Some CLI functionality might need to be queued to a separate worker thread. | ||
Public cloud deployment using Kubernetes |
Extended Availability | 1 | 1 | |||||
Public cloud deployment using vendor-specific deployment option |
(such as Amazon ECS or Fargate) | Extended Availability | 1 or N | N | No access | DSpace Enable all CLI functionality through the REST API. Some CLI functionality might need to be queued to a separate worker thread. | ||
Public cloud deployment using Kubernetes |
Extended Availability | 1 or N | N | |||||
Deploying to Production / to the Cloud with Docker
...