Elastic search infrastructure
Story points: 5 SP
Estimated focus duration: 2 days
Estimated pessimistic duration: 3 days
Who
- @gabriel.chamon -- DevOps
- @kikokhaledu -- Interested party - Backend developer
What
Why
- To have a replicated elasticsearch instance under <telemetry.nunet.io>, separate from staging and test, which possibly are unused/deprecated.
- To implement a basic, barebones automation pipeline for deploying configuring elastic nodes for a cluster
- To extract information using the available query languages in kibana
When
-
after @gabriel.chamon get access to dev and test servers
Acceptance Criteria
Click to expand
There should be a minimum documentation describing this deployment.Work Breakdown Structure (WBS)
Task | Description | Duration | Status | Start Date | End Date | Comment |
---|---|---|---|---|---|---|
1 | Investigate current compute availability | 4 Hrs | Done | 2024-03-20 | 2024-03-21 | |
2 | Quick study of es topologies | 2 Hrs | Done | 2024-03-21 | 2024-03-21 | |
3 | Deploy single node | 4 Hrs | Doing | 2024-03-21 | ||
4 | Automate deployment | 4 Hrs | Todo | |||
5 | Deploy the second node | 2 Hrs | Todo |
Previous notes:
- It seems that elastic search is running from misc-experiments/observability repository. This is not how it should be; --> Done; moved to https://gitlab.com/nunet/observability
- Description for this issue in this comment below: #198 (comment 1823303760)
Edited by Gabriel Chamon