logo1
GSD Skill Creator
OpenStack Reference

Documentation > Specialized Systems > OpenStack Cloud Platform > OpenStack Reference

OpenStack Reference

Quick-reference material for OpenStack operators — NASA SE phase mapping, cross-cloud compatibility tables, and a consolidated reference card with service names, default ports, log locations, and primary CLI commands. This page is designed for fast lookup during operational tasks. For the adaptive automation layer that extends these services, see CAP-136 OpenStack Cloud ASIC Chipset (19 skills, 31 agents, 9 communication loops). For the full NASA SE methodology framework, see CAP-137 NASA SE Documentation.

NASA SE Phase Mapping

How the 7-phase NASA SE lifecycle applies to OpenStack operations. Each phase has a defined scope, entry criteria, and exit criteria (phase gate) that must be satisfied before advancing.

  • Pre-Phase A → Requirements Baseline — Platform requirements gathering, stakeholder interviews, constraint documentation. Gate: Approved Mission Concept Review (MCR)
  • Phase A → Architecture Decision — Service topology selection, HA model choice, network plugin decision. Gate: System Requirements Review (SRR) baseline signed
  • Phase B → Design Freeze — Node layout diagrams, storage backend selection, network topology finalized. Gate: Preliminary Design Review (PDR) package approved
  • Phase C → Deployment Ready — Kolla-Ansible inventory and globals.yml prepared, certificates staged, images pulled. Gate: Critical Design Review (CDR) sign-off
  • Phase D → Integration Complete — Deployment executed, smoke tests passed, TAID verification suite completed. Gate: System Acceptance Review (SAR) evidence package accepted
  • Phase E → Operations Active — Monitoring configured, runbooks accessible, operators trained. Ongoing gate: Monthly operational review against compliance matrix
  • Phase F → Closeout Authorized — Workload evacuation plan approved, data disposition documented. Gate: Closeout Review (CR) report accepted

Cross-Cloud Compatibility

OpenStack service equivalents in major public cloud providers. Use this table when migrating workloads or translating documentation between environments.

  • Keystone (Identity) → AWS IAM / GCP Cloud IAM / Azure Active Directory
  • Nova (Compute) → AWS EC2 / GCP Compute Engine / Azure Virtual Machines
  • Neutron (Networking) → AWS VPC / GCP VPC / Azure Virtual Network
  • Cinder (Block Storage) → AWS EBS / GCP Persistent Disk / Azure Managed Disks
  • Glance (Image) → AWS AMI/EC2 Image Builder / GCP Compute Images / Azure Compute Gallery
  • Swift (Object Storage) → AWS S3 / GCP Cloud Storage / Azure Blob Storage
  • Heat (Orchestration) → AWS CloudFormation / GCP Deployment Manager / Azure ARM Templates
  • Horizon (Dashboard) → AWS Console / GCP Cloud Console / Azure Portal

Quick Reference Card

Service names, default ports, primary log paths, and key CLI commands for rapid operational lookup.

  • Keystone — Port 5000 (public) / 35357 (admin) — Log: /var/log/kolla/keystone/keystone.log — CLI: openstack token issue, openstack project list, openstack user create
  • Nova — Port 8774 (compute API) — Log: /var/log/kolla/nova/nova-api.log, nova-compute.log — CLI: openstack server create, openstack server migrate, nova evacuate
  • Neutron — Port 9696 — Log: /var/log/kolla/neutron/neutron-server.log — CLI: openstack network create, openstack floating ip create, openstack security group rule create
  • Cinder — Port 8776 — Log: /var/log/kolla/cinder/cinder-api.log — CLI: openstack volume create, openstack volume snapshot create, openstack volume backup create
  • Glance — Port 9292 — Log: /var/log/kolla/glance/glance-api.log — CLI: openstack image create, openstack image list, glance image-upload
  • Swift — Port 8080 — Log: /var/log/kolla/swift/proxy-server.log — CLI: openstack container create, openstack object create, swift stat
  • Heat — Port 8004 — Log: /var/log/kolla/heat/heat-api.log — CLI: openstack stack create, openstack stack update, openstack stack delete
  • Horizon — Port 80/443 — Log: /var/log/kolla/horizon/horizon.log — Access: https://[controller-vip]/dashboard

Best for: Operators needing fast lookup during procedures, architects mapping OpenStack concepts to other cloud platforms