Actions
Idea #18337
openEasy install via OS package
Start date:
Due date:
Story points:
-
Release:
Release relationship:
Auto
Description
Setting up a new single-node Arvados cluster should look something like
# add-apt-repository ... # apt-get install arvados-server # arvados-server init [some options] [answer some questions] OK, you can now log in to https://workbench2.example.com/ # arvados-server health OK
Scaling up by adding new system nodes should be just as easy.
It is okay if some installation environments (or sysadmin preferences) necessitate additional manual intervention. The idea is to make it extremely easy to start a production-quality cluster on a few suitable types of system that most people can get access to, like an on-prem server or publicly reachable cloud instance running Debian stable.
Things you don't currently get by installing arvados-server-easy on a cloud VM:- Cloud storage (currently it just stores on local disk by default, in /var/lib/arvados)
Diagnostics tool should use system root token from the config file when run on a server node, instead of requiring env vars#17344
Related issues
Updated by Tom Clegg over 2 years ago
- Related to Idea #16552: "arvados-server init" can get TLS certificates from Let's Encrypt added
Updated by Tom Clegg over 2 years ago
- Related to Idea #18338: "arvados-server init" can use a local root CA to sign certificates added
Updated by Tom Clegg over 2 years ago
- Related to Idea #18341: "arvados-server init" can set up a single-node production cluster added
Updated by Tom Clegg over 2 years ago
- Project changed from Arvados to Arvados Epics
Updated by Tom Clegg over 2 years ago
- Start date set to 01/01/2022
- Due date set to 07/01/2022
- Subject changed from [Epic] Easy install via OS package to Easy install via OS package
Updated by Peter Amstutz over 2 years ago
- Start date changed from 01/01/2022 to 03/01/2022
- Due date changed from 07/01/2022 to 09/30/2022
Updated by Peter Amstutz over 2 years ago
- Start date changed from 03/01/2022 to 05/01/2022
Updated by Peter Amstutz over 2 years ago
- Start date changed from 05/01/2022 to 09/01/2022
- Due date changed from 09/30/2022 to 12/31/2022
Updated by Tom Clegg almost 2 years ago
- Related to Idea #17344: [boot] Make arvados-server-easy package suitable for demo use case added
Updated by Peter Amstutz almost 2 years ago
- Start date changed from 09/01/2022 to 12/01/2022
- Due date changed from 12/31/2022 to 03/31/2023
Updated by Tom Clegg over 1 year ago
- Related to Bug #17345: [boot] handle dependency upgrades better in "arvados-package build" added
Updated by Tom Clegg over 1 year ago
- Status changed from New to In Progress
- Description updated (diff)
Updated by Tom Clegg over 1 year ago
- Related to Idea #18685: Synchronize configuration on multi-node cluster added
Updated by Tom Clegg over 1 year ago
- Related to Feature #19709: Apply database migrations if needed when starting arvados-server boot added
Updated by Tom Clegg over 1 year ago
- Related to Feature #16385: add prebuilt container images for Arvados releases added
Updated by Peter Amstutz over 1 year ago
- Start date changed from 12/01/2022 to 09/01/2023
- Due date changed from 03/31/2023 to 12/31/2023
Updated by Peter Amstutz about 1 year ago
- Start date changed from 09/01/2023 to 01/01/2024
- Due date changed from 12/31/2023 to 03/31/2024
Updated by Peter Amstutz 6 months ago
- Start date changed from 01/01/2024 to 01/01/2025
- Due date changed from 03/31/2024 to 03/31/2025
Actions