Deploy Stargate nodes #181
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ossarga
force-pushed
the
alex/stargate-updates
branch
from
d36f0ce to
93f4ff1
Compare
ossarga
force-pushed
the
alex/stargate-updates
branch
from
ec89d2b to
59782b9
Compare
adejanovski
force-pushed
the
alex/stargate-updates
branch
from
1bd5de8 to
29fc44f
Compare
adejanovski
force-pushed
the
alex/stargate-updates
branch
from
5c7f8b8 to
1b8b450
Compare
* Added ability to provision specific Stargate instances. * Add support for sg nodes in build_cluster.sh * Fix env.sh issue with Stargate nodes naming * Fix instance provisioning and disk mounts * Stargate gets pulled from the latest github release and stargate nodes are properly started during the start phase. * First of all Cassandra nodes will start, then the first stargate nodes using a Cassandra node as seed, and lastly the remaining stargate nodes using the first stargate node as seed. * If the cluster contains stargate nodes, then the stress instance contact point env variable will be the first stargate node instead of the Cassandra nodes.
* Remove Client and Ticket arguments and replaced with Cluster Name in init command * Moved env file creation from Up command to Use command * Refactored Use command so that there is a function to write out each env or config file * Updated Use command to get Cassandra version if using a custom build * Updated Use command to check Cassandra version when using Stargate * Updated Docker Cassandra build container to retrieve Cassandra version from build.xml and write it to a version file * Updated Starget install script to determine stargate contact node during installation and assign to an evironment variable * Started migrating Stargate to service.d * Updated Start command to use the same start function for Stargate (assumes service.d works) * Moved NodeFileter class to its own file * Added TFJson class to retrieve cluster name from Terraform JSON file * Updated Stop command to stop stargate service (assume service.d works) TODO: * Test Stargate install script * Test Stargate service.d file * Test Use command when no Stargate nodes in cluster * Test Start and Stop commands * Update monitoring to capture Stargate metrics * Update documentation
Fix Medusa install after Stargate related changes Move Cassandra debian package build to use python3
ossarga
force-pushed
the
alex/stargate-updates
branch
from
1b8b450 to
84b1925
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added ability to provision specific Stargate instances.
Add support for sg nodes in build_cluster.sh
Fix env.sh issue with Stargate nodes naming
Fix instance provisioning and disk mounts
Stargate gets pulled from the latest github release and stargate nodes are properly started during the start phase.
First of all Cassandra nodes will start, then the first stargate nodes using a Cassandra node as seed, and lastly the remaining stargate nodes using the first stargate node as seed.
If the cluster contains stargate nodes, then the stress instance contact point env variable will be the first stargate node instead of the Cassandra nodes.