notque SAP CC Images (Glance)
Inspect and list VM images: find available boot images, check image status, understand visibility and format.
MCP Tools
Read Tools
| Tool | Purpose | Key Parameters |
|---|---|---|
glance_list_images |
List available images | name, status (queued/saving/active/killed/deleted/deactivated), visibility (public/private/shared/community), owner |
glance_get_image |
Full image detail by UUID | image_id (required) |
glance_list_image_members |
List projects an image is shared with | image_id (required) |
Admin Tools (requires MCP_ADMIN_TOOLS=true)
| Tool | Purpose | Key Parameters |
|---|---|---|
glance_list_tasks† |
List image import tasks | status (pending/processing/success/failure), type |
Guardrails
- UUID validation:
image_idvalidated before API call - No write tools: Image upload/delete not available via MCP (use OpenStack CLI)
- Visibility meanings:
public= all projects see it;shared= explicitly shared via members;community= discoverable by all but not in default list
Gotchas
Public images are shared across all projects. When listing images without an
ownerfilter, you will see both project-owned (private) and platform-provided (public) images. Usevisibility=privateto see only your project's images.Size is in bytes, not GiB. The
sizefield is raw bytes. Divide by 1073741824 to get GiB. A null/zero size means the image data has not been uploaded yet (status will bequeued).min_disk and min_ram are constraints. These values (GiB and MiB respectively) define the minimum flavor requirements to boot a server from this image. Nova will reject a boot request if the flavor does not meet these minimums.
Status "active" is the only bootable state. Only images with
status=activecan be used to create servers. Images inqueued,saving, ordeactivatedcannot be booted from.Container image vs VM image confusion. Glance manages VM/bare-metal boot images (qcow2, raw, vmdk). For OCI container images, use Keppel (
sapcc-registry). Users frequently confuse these.Deactivated images exist but cannot be used. An admin can deactivate an image (e.g., due to CVE). It remains visible but cannot boot new servers. Existing servers using it are unaffected.
disk_format determines hypervisor compatibility. Common formats:
qcow2(KVM),vmdk(VMware),raw. In SAP CC, most images arevmdkfor vSphere-based regions.
Common Workflows
Find Available Boot Images
glance_list_imageswithstatus=activeandvisibility=public— see platform-provided images.- Note
min_diskandmin_ramto determine flavor requirements. - Check
disk_formatmatches the target hypervisor in your availability zone.
Check Why a Server Boot Failed Due to Image
glance_get_imagewith the image UUID from the failed server request.- Verify
status=active— if not, the image is unusable. - Check
min_diskandmin_ramagainst the chosen flavor — insufficient resources cause boot failure. - Confirm
disk_formatis compatible with the target region's hypervisor.
List Project-Owned Snapshots
glance_list_imageswithvisibility=privateandowner=<project_id>.- These are typically server snapshots or custom-uploaded images.
- Check
sizeto understand storage consumption (counts toward image quota).
Cross-Service References
| Need | Service | Tool |
|---|---|---|
| Server using this image | Nova | nova_list_servers (image field in response) |
| Image quota for the project | Limes | limes_get_project_quota(service=image) |
| Who uploaded/deleted an image | Hermes | hermes_list_events(target_type=image) |
| Container images (OCI) | Keppel | keppel_list_repositories |