Skip to content

Resource explorer

The Resource explorer is the inventory view. Where the dashboard is about money, this page is about what you actually have running, category by category, with the cost each category contributes.

What it lists

The explorer reads your live inventory from the OpenStack APIs and organises it into tabs, one per resource type:

Category Source Key fields shown
Servers Nova Name, flavor, vCPUs, RAM, disk, status, created date
Volumes Cinder Name, size (GB), status, type, attached server
Floating IPs Neutron Address, status, attached port
Images Glance Name, size, status, visibility, format
Routers Neutron Name, status, external gateway
Load balancers Octavia Name, VIP address, provisioning and operating status
Snapshots Cinder Name, size, status, source volume
Backups Cinder Name, size, status, source volume

Each tab carries a count badge so you can see at a glance how many of each resource exist in the current scope.

Scope: projects and regions

Like the dashboard, the explorer respects the project and region filters. Inventory is per region, so switching region changes the list. When you view all regions or all projects, the explorer aggregates the results into a single set of tabs, tagging each row with the project and region it came from.

Finding things

Within a category you can:

  • Search by name or attribute to jump straight to a resource.
  • Sort by a column (for example size or created date) to find the biggest or oldest resources.
  • Filter to narrow the list.

Loads on demand

The table data is fetched as you open a tab, which keeps the initial page fast. A summary (counts and per-category cost) shows immediately, then the detailed rows fill in.

Per-category cost

Each category shows the cost it contributes, so you can tell at a glance whether your spend is dominated by compute, by storage, or by network. This is the bridge between inventory (this page) and the money view (the dashboard).

Working with tags and orphans

The explorer is where inventory management connects to optimisation:

  • Apply and manage labels here so spend can be grouped later. See Tags and cost allocation.
  • Resources that appear unused (for example a volume with no attachment, or an unattached floating IP) are strong candidates for cleanup. The Orphan resources view surfaces these automatically, but you can also spot them here by their status.

Where to go next