Host Registries

This section is the canonical inventory of every GPUS-managed compute, network, and data asset. Each registry is the single source of truth for its operational domain — when adding, changing, or decommissioning infrastructure, the corresponding registry must be updated as part of the change (see the new-asset checklist in iar.md).

Registries

Registry	Domain	Asset Count	Format
wdc-hostregistry.csv	WDC on-premises Linux infrastructure	4 hosts (SKY, RAIN, SUN, WIND)	CSV download
gcp-hostregistry.csv	GCP cloud infrastructure	3 VMs + 1 Cloud SQL instance	CSV download
meraki-hostregistry.csv	Cisco Meraki network fabric	32 devices across 5 networks	CSV download

Which registry has what

WDC Linux registry covers the on-premises servers running in the WDC datacenter — SKY and RAIN (DNS/DHCP), SUN (monitoring/Prometheus), WIND (logging/ELK). Each row is a Linux host with SSH access, AIDE baseline, auditd, full CIS hardening. Schema is built around the operational concerns of a Linux host (SSH user, OS version, disk layout, services).

GCP cloud registry covers the three Rocky Linux VMs in gpus-infra (OAK for OpenVAS, MAPLE for Prometheus/Grafana/Wazuh Manager, CEDAR for ELK/Wazuh Indexer) plus the Cloud SQL gpus-forms-db instance backing the forms portal. The compute_class column distinguishes vm rows (full VM operational metadata) from cloud_sql rows (managed-service metadata: tier, engine version, connection name). This pattern generalizes for any future managed-service additions (Cloud Run services, Memorystore, etc.) without forcing a separate registry per service type.

Meraki network registry covers all 32 Meraki devices managed through Meraki Dashboard org 395909 — 4 security appliances (MX), 11 switches (MS), 17 wireless access points (MR). Each row carries serial, MAC, model, network assignment, EOL status, and a risk-graded criticality. The lifecycle_action column is the operationally important field: it tells you which devices need to be decommissioned, replaced, or procured for in the next 90 days.

Schemas

The three registries have intentionally different schemas because their operational concerns differ. Linux hosts care about SSH users and disk layouts; Meraki devices care about firmware versions and end-of-support dates; managed services care about connection names and tiers. Forcing a single unified schema across all three would produce a half-empty wide table that's harder to read and use than three purpose-built schemas.

When in doubt, the registry's column headers describe themselves — each schema is documented inline.

Naming conventions

File naming — {domain}-hostregistry.csv, hyphenated. Files live in mkdocs-portal/docs/hostregistry/ (this directory).

Hostname conventions:

• WDC Linux: short uppercase names tied to function (SKY, RAIN, SUN, WIND).
• GCP VMs: lowercase tree names (oak, maple, cedar) per CLAUDE.md convention.
• Meraki devices: site-prefixed where managed (wdc-fw-primary, oakec-fw-primary); legacy descriptive names retained for field-office and residential APs (First Floor AP, APT 707).

GCP disk naming convention — <vm> for boot disk, <vm>-data for the LVM data partition, <vm>-<role> for additional purpose-specific disks (e.g., oak-docker for OpenVAS container layer storage). Useful to know when running gcloud compute disks list — the convention is not enforced by GCP, only by us.

Updating registries

The registries are updated as part of the new-asset / change-management workflow defined in standard-changes.md. Mechanically, registries are bare CSVs in this directory; updates are made via direct git commit to main, no per-row review process. Cross-references in other docs (information asset registry, IRP, DRP, runbooks) cite the registry by filename in backticks.

Cross-references

Document	Why it cites the registries
iar.md	Each asset class enumerated, with criticality and classification
incident-after-action-review.md	Same content, response-plans context
irp.md	Incident response runbooks reference registry rows for asset identification
standard-changes.md	Change workflow that touches infrastructure
gpus-it-priorities.md	T2 Meraki, T3 WDC, etc. lifecycle planning
dns-dhcp.md	DNS A records aligned with registry hostnames
forms-portal.md	Cloud SQL backend for forms
meraki-infrastructure.md	Meraki domain reference doc

Document history

Version	Date	Author	Change
1.0	2026-04-28	Rajesh Chhetry	Initial registry directory; restructure from flat infrastructure/wdchostregistry.csv to dedicated hostregistry/ folder. Added gcp-hostregistry.csv and meraki-hostregistry.csv.