-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
Not defined
We should have a docker-compose file that incorporates Opensearch as a database instead of Elasticsearch. Note this could be done by conditions within the same docker file, but could also be a separate file.
This was fixed with the OPT-7226 PR
Testing Notes:
- When the new docker-compose file is run with the opensearch profile (docker-compose -f docker-compose.yml --profile opensearch up -d), Opensearch is started and requests can be sent manually to the opensearch database
This is the controller panel for Smart Panels app
[OPT-7197] Create docker-compose file for Opensearch
| Status | Original: Triage [ 10612 ] | New: Ready [ 10005 ] |
| Status | Original: Ready [ 10005 ] | New: In Development [ 10312 ] |
| Description | Original: We should have a docker-compose file that incorporates Opensearch as a database instead of Elasticsearch. Note this could be done by conditions within the same docker file, but could also be a separate file |
New:
We should have a docker-compose file that incorporates Opensearch as a database instead of Elasticsearch. Note this could be done by conditions within the same docker file, but could also be a separate file
*Testing Notes:* * When the new docker-compose file is run, Opensearch is started and Optimize can connect to it |
| Status | Original: In Development [ 10312 ] | New: Ready [ 10005 ] |
| Assignee | New: Giuliano Rodrigues Lima [ giuliano.rodrigues-lima ] |
| Status | Original: Ready [ 10005 ] | New: In Development [ 10312 ] |
| Description |
Original:
We should have a docker-compose file that incorporates Opensearch as a database instead of Elasticsearch. Note this could be done by conditions within the same docker file, but could also be a separate file
*Testing Notes:* * When the new docker-compose file is run, Opensearch is started and Optimize can connect to it |
New:
We should have a docker-compose file that incorporates Opensearch as a database instead of Elasticsearch. Note this could be done by conditions within the same docker file, but could also be a separate file
*Testing Notes:* * When the new docker-compose file is run, Opensearch is started and requests can be sent manually to the opensearch database |
| Description |
Original:
We should have a docker-compose file that incorporates Opensearch as a database instead of Elasticsearch. Note this could be done by conditions within the same docker file, but could also be a separate file
*Testing Notes:* * When the new docker-compose file is run, Opensearch is started and requests can be sent manually to the opensearch database |
New:
We should have a docker-compose file that incorporates Opensearch as a database instead of Elasticsearch. Note this could be done by conditions within the same docker file, but could also be a separate file.
This was fixed with the *Testing Notes:* * When the new docker-compose file is run, Opensearch is started and requests can be sent manually to the opensearch database |
| Description |
Original:
We should have a docker-compose file that incorporates Opensearch as a database instead of Elasticsearch. Note this could be done by conditions within the same docker file, but could also be a separate file.
This was fixed with the *Testing Notes:* * When the new docker-compose file is run, Opensearch is started and requests can be sent manually to the opensearch database |
New:
We should have a docker-compose file that incorporates Opensearch as a database instead of Elasticsearch. Note this could be done by conditions within the same docker file, but could also be a separate file.
This was fixed with the *Testing Notes:* * When the new docker-compose file is run with the opensearch profile (docker-compose -f docker-compose.yml --profile opensearch up -d), Opensearch is started and requests can be sent manually to the opensearch database |