Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Many DSpace stakeholders are not developers.  If it was easier to deploy a snapshot instance of DSpace to the cloud, these stakeholders could play a more active role in system testing.

Deployment Options

The following grid documents some of the potential ways DSpace Docker images could be deployed.  Currently, only the first option is supported by the published DSpace images.

This grid has been designed to help recommend how our images will need to evolve to support multiple deployment options.

Deployment OptionsUptimePersistenceCLI AccessNotesChanges needed
Local workstation/test server deployment with Docker Compose - single nodeLimited Duration for TestingDocker Compose Volumesdocker exechttps://github.com/DSpace-Labs/DSpace-Docker-Images
Server deployment with Docker Compose - single node (shell access to server and network drives)Extended AvailabilityDocker Compose Volumes bound to file system storageSSH + docker exec

Dockerfiles
Use dockerfiles without test access

Insert custom dspace.cfg settings into distrib
Docker Compose
Remove test tools and scripts from the docker compose files.

Docker swarm optionsExtended Availability

https://docs.docker.com/v17.09/get-started/part6/
Local workstation/test server deployment with Kubernetes - single nodeLimited Duration for Testing



Server deployment with Kubernetes - single node (shell access to server and network drives)Extended Availability



Server deployment with Portainer management



https://www.portainer.io
Public cloud deployment using vendor-specific deployment option - single node (such as Amazon ECS or Fargate)




Public cloud deployment using Kubernetes - single node




Public cloud deployment using vendor-specific deployment option - multi node (such as Amazon ECS or Fargate)




Public cloud deployment using Kubernetes - multi node










Deploying to Production / to the Cloud with Docker

...