You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should allow users to run a trunk/5.1 local cluster as there are some really interesting features coming in 5.1 and we can give people access to run it locally and play with it.
Call it cassandra-trunk we will periodically release new versions of this image.
3 - Have a pipeline set-up to automatically run this trunk build weekly and generate a new image regularly from trunk.
4 - Update workbench local clusters workflow
a) Add an option to select trunk
b) When a user selects trunk ** disable the ability to deploy axonops ** in this local cluster as AxonOps only supports releases, not development Cassandra builds.
c) When a user selects trunk before creating the local cluster, display a warning dialog explaining what it is:
You have opted to deploy a local cluster using an in-development trunk build of Apache Cassandra. This version is considered unstable and you may encounter issues. See: https://github.com/apache/cassandra/tree/trunk
5 - Allow user to pull the latest trunk container version
Before a user starts an trunk cluster, we need to (optionally) pull the latest version of the trunk image to use.
When a user clicks start on a local cluster connection always prompt them in a dialog to ask if they want to download the latest trunk image (default is true). If this is selected, then add the extra arguments to pull the container to the docker compose command when starting
docker compose up --pull always
6 - Add system setting to always pull trunk clusters before starting
Give users the option to always pull the latest version and not bother prompting them (as described in 5).
7 - Add a descriptive icon to the connection box for trunk local clusters
millerjp
changed the title
[feat]: Allow users to run in-development Cassandra 5.1 in a local cluster
[feat]: Allow users to run in-development Cassandra trunk builds in a local cluster
Oct 27, 2024
We should allow users to run a trunk/5.1 local cluster as there are some really interesting features coming in 5.1 and we can give people access to run it locally and play with it.
To do this we will need to
1 - Build Cassandra 5.1/trunk
To do that checkout trunk from https://github.com/apache/cassandra and run
ant artifacts
this will generate a tarball buildSee: https://cassandra.apache.org/_/development/ide.html
2 - Bundle it into a axonops docker image
Call it
cassandra-trunk
we will periodically release new versions of this image.3 - Have a pipeline set-up to automatically run this
trunk
build weekly and generate a new image regularly from trunk.4 - Update workbench local clusters workflow
a) Add an option to select
trunk
b) When a user selects
trunk
** disable the ability to deploy axonops ** in this local cluster as AxonOps only supports releases, not development Cassandra builds.c) When a user selects
trunk
before creating the local cluster, display a warning dialog explaining what it is:5 - Allow user to pull the latest
trunk
container versionBefore a user starts an
trunk
cluster, we need to (optionally) pull the latest version of thetrunk
image to use.When a user clicks start on a local cluster connection always prompt them in a dialog to ask if they want to download the latest
trunk
image (default is true). If this is selected, then add the extra arguments to pull the container to the docker compose command when starting6 - Add system setting to always pull
trunk
clusters before startingGive users the option to always pull the latest version and not bother prompting them (as described in 5).
7 - Add a descriptive icon to the connection box for
trunk
local clusterseg https://commons.wikimedia.org/wiki/File:Icon_DINA_Voraussetzungen_Digitale_Nachhaltigkeit_01_Ausgereift_Schwarz.svg
The text was updated successfully, but these errors were encountered: