Runbook 06 — Tenant Resource Recreation

STATUS: PLACEHOLDER — drafted post-deploy.

Purpose

Recreate the standard testcloud tenant resources (domain, project, user, networks, images, keypairs, flavors) using a proper IPAM-aligned design per D-010 + D-016 (not the ad-hoc user1 pattern from the original test cloud).

Prerequisites

• Cloud fully deployed and validated
• DNS zones populated (Runbook 07 may precede this if Designate-via-tenant DNS is in scope at tenant create time)
• NetBox IPv4 tenant pool prefix present (per D-016; default 10.20.0.0/16)

TODO

• Create domain domain1
• Create project project1 in domain domain1
• Create user user1 in project1 (member role + load-balancer_member

  role for Octavia)

• Tenant network with CIDR carved from NetBox IPv4 tenant pool

  - Suggested convention: `10.20.<project-index>.0/24` per D-016
  - project1 → `10.20.1.0/24`
  - Per D-016 hybrid model, the per-project /24 is Neutron-managed and
    NOT added back to NetBox

• Tenant router connected to ext_net (Provider 10.12.4.0/22)
• Glance image: noble-amd64 (cloud-init enabled)
• Flavor m1.small (1 vCPU, 2 GiB RAM, 20 GiB root)
• Keypair for user1
• openrc files: ~/admin-openrc, ~/user1-openrc
• Application credentials for user1 (audit trail)
• Take second KVM snapshot (per D-012 Snapshot 2)

v1 vs. v2 note

In v1, tenant networks are IPv4-only. v2 adds IPv6 tenant subnets carved from the v2 IPv6 tenant pool (currently reservation status in NetBox).