📦
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
  • Ansible Hosts File
  • Host_Vars
  • Group_Vars
Edit on GitHub
  1. Before You Begin
  2. The site configuration

inventory

Ansible Hosts File

inventory/hosts is an ini formatted file. It defines the hosts and groups that cc-ansible will operate on. The majority of this file can be left as-is, and should only be customized by advanced users.

# These initial groups are the only groups required to be modified. The
# additional groups are for more control of the environment.
[control]
<host>

[network]
<host>

[compute]
# No compute node; this is a baremetal-only cluster.

[monitoring]
<host>

[storage]
<host>

[deployment]
localhost ansible_connection=local

[baremetal:children]
control
network
compute
storage
monitoring

The hostname of your control node will be added to the groups control, network, monitoring, and storage.

Host_Vars

Files in the inventory/host_vars directory set variables scoped to a given host. You will likely only have one host here, so there should be a file named after the hostname of your control node.

By default, it will look like the following:

# Initial assumption is that this is also the deployment node,
# therefore any provisioning can be done locally.
ansible_connection: local

#network_interface: eth1
#kolla_external_vip_interface: eth2
  • network_interface: the network interface name that will be used for all internal traffic, and where the haproxy internal vip will be bound.

  • kolla_external_vip_interface: the network interface name to be used for the external API endpoint.

Group_Vars

This is not used by default, but allows you to set variables per group, rather than per host.

PreviousThe site configurationNextdefaults.yml

Last updated 2 years ago