Mateusz Suski
39 lines
1.7 KiB
Markdown
39 lines
1.7 KiB
Markdown
# Roadmap
|
|
|
|
This file keeps future portfolio ideas in one place so empty folders do not look like finished work.
|
|
|
|
## Planned Lab Areas
|
|
|
|
- Docker: image build notes, container troubleshooting, and small service examples.
|
|
- Kubernetes: workload inspection, basic operations checks, and failure scenario notes.
|
|
- Terraform: small infrastructure-as-code examples with clear plan/apply separation.
|
|
- Networking: DNS, routing, firewall, and connectivity troubleshooting labs.
|
|
- CI/CD: validation pipelines for shell, YAML, and Ansible examples.
|
|
|
|
## Planned Platform Case Studies
|
|
|
|
- Storage: expansion planning, filesystem checks, and SAN handoff documentation.
|
|
- Clustering: service group checks, failover review, and operational checklists.
|
|
- Monitoring: Zabbix-oriented alert review and host onboarding notes.
|
|
- Virtualization: VM lifecycle and platform operations examples.
|
|
- Log analysis: optional ELK-style search case study under `platform-projects`, separate from current local Python helpers.
|
|
|
|
## Implemented Portfolio Additions
|
|
|
|
- Standalone Bash incident checks under `infra-run/scripts/bash/incident-checks/` for common Linux incident triage and ticket evidence.
|
|
- Python operational log analysis suite under `infra-run/scripts/python/`:
|
|
- `incident-log-summary`
|
|
- `log-diff-checker`
|
|
- `auth-log-audit`
|
|
- `jvm-log-analyzer`
|
|
- `journal-analyzer`
|
|
- `known-error-matcher`
|
|
|
|
## Future Python Tooling Ideas
|
|
|
|
- Real-world sample report examples using sanitized evidence.
|
|
- Integration examples that combine log summaries with change evidence collection.
|
|
- A shared Python helper library only if the standalone tools begin duplicating enough stable behavior to justify it.
|
|
|
|
Planned sections remain future work unless listed as implemented.
|