📦
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
  • What are Default Resource Properties?
  • Configuration and Usage
Edit on GitHub
  1. Reference
  2. Resource Reservation

Default Resource Properties

What are Default Resource Properties?

When a user creates a resource reservation, they include properties they want the reserved resource to match. For example, specifying the type of baremetal node to reserve, or a minimum amount of RAM. Default resource properties can be configured so that requests without resource properties, which would normally be unbounded, and will result in random resources being reserved, are given some set of constraints. This is may be desired when not all resources are equal. For example, when there is a mixture of x86 and ARM nodes, or when some nodes have GPUs.

Configuration and Usage

The following configuration options can be set in defaults.yml

  • blazar_host_default_resource_properties is the resource property array to use when none is given when creating a host reservation. Note that the $ character must be escaped to \$. Setting this to '[]' and changing blazar_host_retry_without_default_resources to false will use no default resource properties.

  • blazar_host_retry_without_default_resources is a boolean value, whether any defaults should be used if the allocation using default resource properties fails.

  • blazar_network_default_resource_properties is the resource property array to use when none is given when creating a network reservation. Note that the $ character must be escaped to \$. Setting this to '[]' and changing blazar_network_retry_without_default_resources to false will use no default resource properties.

  • blazar_network_retry_without_default_resources is a boolean value, whether any defaults should be used if the allocation using default resource properties fails.

PreviousResource ReservationNextMonitoring

Last updated 2 years ago