Mateusz Suski
35e6b139fc
ci / validate (push) Failing after 1m8s
Rework portfolio around Linux operations, Zabbix monitoring, migration validation, and ELK/Grafana log observability. Add AAP-style LVM resize workflow, Zabbix server/proxy/agent automation assets, Linux/AIX monitoring templates, and updated validation CI.
62 lines
2.0 KiB
Markdown
62 lines
2.0 KiB
Markdown
# AI Context File - CV-Aligned Portfolio Guide
|
|
|
|
## Positioning
|
|
|
|
This repository should support a Linux/Unix Infrastructure Engineer CV. The main story is operational infrastructure work: Linux operations, Zabbix monitoring, migration validation, incident response, and log observability.
|
|
|
|
Do not reposition the repo as a generic cloud-native platform portfolio. DevOps side labs can be mentioned, but the main `professional-infra/` section should stay grounded in real operational work.
|
|
|
|
## Current Professional Projects
|
|
|
|
### Linux Operations Automation
|
|
|
|
Technology stack: Ansible, Bash, Docker Compose.
|
|
|
|
Focus:
|
|
|
|
- Linux provisioning, patching, hardening, and decommissioning,
|
|
- service and failure simulation,
|
|
- AAP-style LVM filesystem resize workflow,
|
|
- before/after operational evidence.
|
|
|
|
### Zabbix Monitoring + Incident Response
|
|
|
|
Technology stack: Ansible, Zabbix template assets, JSON/YAML-style operational docs.
|
|
|
|
Focus:
|
|
|
|
- Zabbix server, proxy, and agent automation structure,
|
|
- active/passive proxy design,
|
|
- Linux and AIX OS monitoring templates,
|
|
- maintenance and incident response runbooks,
|
|
- sample check and alert evidence.
|
|
|
|
### Migration Validation Framework
|
|
|
|
Technology stack: Python, JSON, HTML reports.
|
|
|
|
Focus:
|
|
|
|
- pre/post migration snapshots,
|
|
- drift detection,
|
|
- risk assessment,
|
|
- migration evidence reports.
|
|
|
|
### Log Observability ELK/Grafana
|
|
|
|
Technology stack: Docker Compose, Elasticsearch, Logstash, Kibana, Grafana, Filebeat.
|
|
|
|
Focus:
|
|
|
|
- log ingestion and parsing,
|
|
- incident log evidence,
|
|
- local demo observability stack.
|
|
|
|
## Standards
|
|
|
|
- Every project should have `make test`.
|
|
- Documentation should include CV relevance and interview talking points.
|
|
- Runtime logs, caches, snapshots, and generated reports should stay out of git.
|
|
- AIX should be represented by templates, samples, and runbooks; do not claim local AIX runtime.
|
|
- AAP should be represented as workflow/job-template documentation plus playbook variables; do not add AWX/AAP runtime unless explicitly requested.
|