📦
CHI-in-a-box
  • What is CHI-in-a-Box?
  • Before You Begin
    • Assumed Knowledge
    • Hosts and Services
    • Network Overview
    • CC-Ansible
    • The site configuration
      • inventory
      • defaults.yml
      • passwords.yml
      • certificates/
      • node_custom_config/ (optional)
      • post-deploy.yml (optional)
    • How Deployment Works
    • Security considerations
  • Setup Guides
    • Evaluation Site
      • Bring up the Control Plane
    • Production Baremetal
      • Baremetal QuickStart
      • Host Networking Configuration
    • Troubleshooting
      • Networking
    • Verification Checklist
    • Dev-in-a-Box
    • Edge-in-a-Box
  • Reference
    • Chameleon Identity Federation
    • Ironic Flat Networking
    • Ironic Multi-Tenant Networking
    • Glance Image Storage
    • Resource Reservation
      • Default Resource Properties
    • Monitoring
      • IPMI Metrics
      • SNMP Metrics
  • Example Deployments
    • ARM/x86 mixed architecture
    • Edge computing/container testbed
  • Operations
    • Hardware management
    • Certificate management
    • Chameleon tools
      • Hammers 🔨
        • maintenance_reservation
      • Disk image subscription
      • Usage reporting
    • Troubleshooting
      • Known issues
        • Neutron (networking)
        • Nova (KVM)
        • Ironic (bare metal)
      • Instance networking diagnostics
      • Security incident triage
      • Troublesome Hardware
    • Alert runbooks
      • Cron Job No Recent Success
      • Instance Failure
      • Image Cache Space
      • Ironic Node Error State
      • Jupyter Server Launch Failure
      • MySQL Host Down
      • MySQL Replication Error
      • Node Exporter Down
      • Node Network Bridge Down
      • Node Network Bridge Low Traffic
      • Nova Ironic Instance Launch Failure
      • OpenStack API Down
      • PeriodicTask No Recent Success
      • Portal Down
      • Precis Parsed Events Low
      • Provider Conflict
      • Runbook Template
    • User support guide
    • Upgrading to a new Release
  • Development
    • Developing OpenStack Services
    • Dev-in-a-box
Powered by GitBook
On this page
Edit on GitHub
  1. Before You Begin

How Deployment Works

Deploying a CHI-in-a-Box site proceeds as a sequence of steps. Most will only need to be completed once, but they can be repeated as needed in case of configuration changes.

Commands are executed using the cc-ansible executable in the CHI-in-a-box repository, and configuration done by editing text files. These commands and edits are done on the Deploy Host, in order to configure and manage the Control Nodes. Most minimal installations will simply run the Deploy Host on the same node as the CO

  1. Download and install dependencies, and the CHI-in-a-Box tools on your Deploy Host

  2. Initialize your Site-Configuration

  3. Configure the network interfaces on your Control Nodes.

  4. Add your Control Nodes to the ansible inventory in your site configuration, and set any host variables needed to connect

  5. Fill out your defaults.yml with all site-wide config values

  6. Bootstrap the control nodes

  7. Deploy services onto the control nodes

  8. Run Post-Deploy which will use values from defaults.yml to pre-create various openstack objects with the (now running) API, as well as several periodic utility tasks.

  9. Run manual steps using the OpenStack CLI, API, or scripts

Previouspost-deploy.yml (optional)NextSecurity considerations

Last updated 2 years ago