Arvados™ Docs
WARNING - you are viewing the documentation for an old version of Arvados. For the latest version, click here.
  1. Overview
    1. Installation options
  2. Docker quick start
    1. Arvados-in-a-box
  3. Arvados Installer
    1. Single host Arvados
    2. Multi-Host Arvados
  4. Manual installation
    1. Planning and prerequisites
    2. Arvados package repositories
  5. Configuration
    1. Configuration files
    2. InternalURLs and ExternalURL
    3. Configuration reference
  6. Maintenance and upgrading
    1. Arvados upgrade notes
    2. Maintenance and upgrading
  7. Core
    1. Install API server and Controller
    2. Cluster diagnostics tool
  8. Keep
    1. Install Keepstore servers
    2. Configure filesystem storage
    3. Configure S3 object storage
    4. Configure Azure Blob storage
    5. Install Keepproxy server
    6. Install Keep-web server
    7. Install Keep-balance
  9. User interface
    1. Set up web based login
    2. Install the websocket server
    3. Install Workbench
    4. Install Workbench 2
    5. Customizing Workbench
  10. Additional services
    1. Set up a shell node
    2. Configure webshell
    3. Install the Git server
  11. Containers API (cloud)
    1. Build a cloud compute node image
    2. Install the cloud dispatcher
  12. Compute nodes (Slurm or LSF)
    1. Set up a compute node with Docker
    2. Set up a compute node with Singularity
  13. Containers API (Slurm)
    1. Install the Slurm dispatcher
    2. Configure Slurm
    3. Test Slurm dispatch
  14. Containers API (LSF)
    1. Install the LSF dispatcher
  15. Additional configuration
    1. Configure container shell access
  16. External dependencies
    1. Install PostgreSQL 9.4+
    2. Install Ruby and Bundler
    3. Install Nginx
    4. Set up Docker

Arvados on Kubernetes

Arvados on Kubernetes is implemented as a Helm 3 chart.

Overview

This Helm chart provides a basic, small Arvados cluster.

Current limitations, to be addressed in the future:

  • An Arvados cluster created with this Helm chart is entirely ephemeral, and all data stored on the cluster will be deleted when it is shut down.
  • No dynamic scaling of compute nodes (but you can adjust values.yaml and reload the Helm chart)
  • All compute nodes are the same size
  • Compute nodes have no cpu/memory/disk constraints yet
  • No git server

Requirements

  • Minikube or Google Kubernetes Engine (Kubernetes 1.10+ with at least 3 nodes, 2+ cores per node)
  • kubectl and Helm 3 installed locally, and able to connect to your Kubernetes cluster

Please refer to Arvados on Minikube or Arvados on GKE for detailed installation instructions.

Previous: Set up Docker

The content of this documentation is licensed under the Creative Commons Attribution-Share Alike 3.0 United States licence.
Code samples in this documentation are licensed under the Apache License, Version 2.0.