📦
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. Reference

Glance Image Storage

PreviousIronic Multi-Tenant NetworkingNextResource Reservation

Last updated 2 years ago

All images used to launch instances are stored by Glance. However, glance holds the metadata, and delegates the actual data storage to one or more backends. Configuration and best practices are summarized below.

The kolla-ansible docs with details are listed here:

Images saved using cc-snapshot are also stored in Glance. This means that it contains user-data, and should be treated with care.

File Backend

If not configured, Glance defaults to storing image data on the controller node, in the path /var/lib/glance/images.

Make sure you back up this directory!

Customize this path by setting:

glance_backend_file: "yes"
glance_file_datadir_volume: "/path/to/shared/storage/"

Notes for network filesystems

Even if using a network filesystem as the glance_file_datadir_volume, ensure that it has backups, or at least snapshots to allow recovery from file deletion.

If the mount "flaps", that is goes down and back up due to a network disruption, the following procedure must be taken to mount it inside the container.

  1. Stop the glance container docker stop glance_api

  2. unmount the network share umount /path/to/shared/storage

  3. remount the network share mount /path/to/shared/storage

  4. start the glance container docker start glance_api

https://docs.openstack.org/kolla-ansible/xena/reference/shared-services/glance-guide.html