Remove hardcoded config files and use component defaults #572
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
Previously in
4.xwe had our own configuration files for both indexer and dashboard, as well as a predefined config file for AIO installations.This had the problem that if something in the component's own file changed, having the files hardcoded meant they would become outdated with these changes, potentially causing the installation to fail.
In this PR these files have been removed and we now modify the actual files that come with the installation of each component, so if something changes in the file at any point, it will be up to date. For the AIO
config.ymlpart, since we have it inartifact_urls.yml, we download it via URL.Tests 🧪
AIO deployment
The AIO has been tested separately on a VM:
AIO installation logs
Distributed deployment
On the other hand, a distributed deployment with 3 machines in total:
VM 1: 1 indexer, 1 master manager
VM 2: 1 indexer, 1 worker manager
VM 3: 1 indexer, 1 dashboard
Indexers installation
VM 1
VM 2
VM 3
Managers installation
VM 1
VM 2
Dashboard installation
VM 3