Reporting - DevOps Work for Reporting
Target release | |
|---|---|
Epic | |
Status | drafted |
Priority | High |
eLMIS Status | Unimplemented |
OpenLMIS Status | Unimplemented |
Ona | @Craig Appl (Unlicensed) |
OpenLMIS | - |
JSI | - |
Goals/Scope
Make it easy to standup the reporting infrastructure.
Background
Assumptions
User Stories
# | Title | User Story | Label | Importance | Notes | JIRA Tickets |
|---|---|---|---|---|---|---|
|
| Ansible to Docker images
|
|
|
|
|
|
| Docker images for each service
|
|
|
|
|
|
| Move Druid scripts to NiFi |
|
|
|
|
|
| Run BDW on Kubernetes and Consul |
|
|
|
|
|
| Documentation
|
|
|
|
|
|
| Auto-load flows |
|
|
|
|
|
| Auto-load Superset metrics |
|
|
|
|
|
| Server monitoring (Graylog, Grafana, Graphite?) What doe OpenLMIS use? |
|
|
|
|
Dependencies
Description | Link |
|---|---|
Jira Epics
Open Questions
Below is a list of questions to be addressed as a result of this requirements document:
# | Question | Outcome | Status |
|---|---|---|---|
1 | We probably want to provide setup for an additional database, like Postgres |
|
|
2 | We may want to provide an additional raw data store (like HDFS) in addition to Kafka |
|
|
3 | We may want to support backing up Kafka data in a more robust way |
|
|
4 | We may want to have greater support for authentication in NiFi |
|
|
5 | We may want to add more restricted security settings to Druid and Kafka |
|
|
Out of Scope
Tasks
Gap Estimation Notes 4/12/2018
Doesn't block or depend on other work
Required for Gap completion