Source And Intent

infra-run exists to present infrastructure operations work in a form that can be reviewed without exposing employer systems, hostnames, storage identifiers, tickets, or internal procedures.

The project is inspired by professional Linux and infrastructure operations work: prechecks before changes, postchecks after changes, disk-pressure incidents, SSH and sudo hardening, storage expansion planning, cluster awareness, and the need to leave clear notes for other engineers.

What Is Realistic

The workflow shape: precheck, dry-run, execute only with explicit approval, postcheck, and report.
The operational topics: Linux health checks, disk-full triage, Veritas VxVM/VCS concepts, GPFS / IBM Spectrum Scale concepts, and selected OS hardening controls.
The caution around storage, clustering, SSH, sudo, audit, and filesystem changes.

What Is Simplified

Commands are written as examples and do not cover every vendor, OS release, package layout, or site standard.
The Veritas and GPFS scripts model common workflow steps but cannot validate a real cluster from this repository.
The Ansible roles apply selected baseline controls; they are not full compliance implementations.
Reporting examples use sanitized sample data.

What Was Sanitized

Hostnames, IP addresses, disk names, WWNs, ticket numbers, application names, company names, and environment-specific values.
Exact production procedures and internal approval paths.
Any data that could identify a real system or organization.

Production Caution

Do not run these scripts blindly on production systems. Review every command, adapt variables and paths, test in a lab, confirm backups and rollback plans, and follow the local change process.

This project does not claim that the exact scripts were used in production.

Roles This Supports

Linux System Administrator
Infrastructure Engineer
SRE / DevOps Operations Engineer
Linux Platform Engineer

1.9 KiB Raw Blame History