GDB-10418 Single Node Deployment #53
Merged
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
viktor-ribchev
force-pushed
the
GDB-10418_single_node_deployment
branch
4 times, most recently
from
8782970 to
3920e97
Compare
ghost
reviewed
Jul 3, 2024
ghost
self-requested a review
mihailradkov
reviewed
Jul 5, 2024
viktor-ribchev
force-pushed
the
GDB-10418_single_node_deployment
branch
2 times, most recently
from
bc1c3d1 to
1a6a048
Compare
mihailradkov
approved these changes
Jul 5, 2024
viktor-ribchev
force-pushed
the
GDB-10418_single_node_deployment
branch
from
1a6a048 to
05547c0
Compare
Removed hardcoded values for DNS zone in userdata scripts Updated the NSGs ports based on graphdb_node_count Updated user_data.tf Changed the name of the LB target group to avoid conflicts when scaling from 1 to 3 AZs Updated the monitoring, to not deploy cluster alarms when a single node is deployed Updated the availability_tests Updated how the VPC azs are calculated based on the graphdb_node_count Added calculations for the subnets based on the graphdb_node_count Removed route53_availability_content_match from modules\monitoring Moved route53_availability_http_string_type to root level. Changed the availability test to support single node deployment. Added dynamic change of the availability tests http string type based on tls_enabled Updated the README.md Updated CHANGELOG.md Made duplicate code into functions and moved it to 00_functions.sh Updated README.md example for existing subnets Renamed 10_start_graphdb_services.sh.tpl to 10_start_single_graphdb_services.sh.tpl
viktor-ribchev
force-pushed
the
GDB-10418_single_node_deployment
branch
from
05547c0 to
e4ae245
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.
Description
Added the ability to deploy a single node GraphDB
Related Issues
GDB-10418
Changes
Added support for single node deployment.
Removed hardcoded values for DNS zone in userdata scripts
Updated the NSGs ports based on graphdb_node_count
Updated user_data.tf
Changed the name of the LB target group to avoid conflicts when scaling from 1 to 3 AZs
Updated the monitoring, to not deploy cluster alarms when a single node is deployed
Updated the availability_tests
Updated how the VPC azs are calculated based on the graphdb_node_count
Added calculations for the subnets based on the graphdb_node_count
Screenshots (if applicable)
N/A
Checklist