Generated by GPT-5-mini| OpenStack Glance | |
|---|---|
| Name | Glance |
| Title | OpenStack Glance |
| Developer | OpenStack Foundation |
| Initial release | 2010 |
| Programming language | Python |
| License | Apache License 2.0 |
| Website | OpenStack |
OpenStack Glance OpenStack Glance is a service for discovering, registering, and retrieving virtual machine images commonly used with OpenStack Nova, KVM, QEMU, Xen Project, and VMware ESXi. Developed under the auspices of the OpenStack Foundation and implemented in Python (programming language), Glance interoperates with ecosystem projects such as Keystone (OpenStack), Cinder (OpenStack), Swift (OpenStack), Neutron (OpenStack), and Horizon (OpenStack) to provide image lifecycle management across private, public, and hybrid clouds. It supports multiple storage backends and image formats and exposes RESTful interfaces used by orchestration tools like Heat (software) and configuration management systems such as Ansible, Puppet, and Chef (software).
Glance functions as the canonical image repository for cloud platforms built with OpenStack technologies, enabling cataloging and delivery of disk and metadata artifacts to compute services like Nova (OpenStack Compute), container runtimes such as Docker, and virtualization platforms including Microsoft Hyper-V. The project originated from contributors at Rackspace, NASA, and the broader OpenStack community, and it aligns with standards promulgated by organizations like the Open Cloud Computing Interface and interoperability efforts including the Cloud Native Computing Foundation ecosystem. Glance supports extensibility through plugins and driver interfaces to connect with object stores and block stores provided by vendors such as Amazon Web Services, Google Cloud Platform, IBM Cloud, and enterprise vendors like Red Hat, Canonical (company), and SUSE.
Glance implements a modular architecture comprising an API server, a registry, and configurable storage backends. The API server provides HTTP endpoints that authenticate via Keystone (OpenStack) tokens and delegate image metadata persistence to the registry component while storing image payloads in backends including OpenStack Swift, Ceph, Amazon S3, and traditional block devices managed by Cinder (OpenStack). Components communicate over message buses such as RabbitMQ or Apache Kafka in deployments integrated with OpenStack Barbican for key management and OpenStack Manila for shared filesystem requirements. Pluggable drivers permit integration with enterprise systems from Dell EMC, Hewlett Packard Enterprise, and NetApp as well as cloud-native storage like MinIO.
Glance handles image metadata (name, checksum, architecture) and binary image data supporting formats such as QCow2, VMDK, VHD, Raw image format, and ISO 9660 images used for installers. It supports image import, export, snapshotting, and image conversion workflows often orchestrated by tooling from ImageMagick (for ancillary artifacts) or qemu-img for format conversion. Cataloging features enable public and private image visibility models used in multi-tenant clouds and enterprise catalogs maintained by vendors like Canonical (company) for Ubuntu cloud images, Red Hat for RHEL images, and SUSE for SUSE Linux Enterprise images.
Glance exposes RESTful APIs documented in OpenStack API references and consumed by client libraries and SDKs provided by language ecosystems such as the OpenStack SDK (python-openstacksdk) for Python (programming language), Fog (software) for Ruby (programming language), and community SDKs for Go (programming language), Java (programming language), and JavaScript. Authentication and authorization integrate with Keystone (OpenStack) and token exchange patterns compatible with identity providers like OpenID Connect and SAML 2.0 integrations offered by Okta or Microsoft Azure Active Directory. API versioning and schema evolution permit clients including orchestration engines like Heat (software) and CI/CD pipelines using Jenkins to manage image lifecycles programmatically.
Glance is commonly deployed on Linux distributions maintained by Red Hat, Canonical (company), and SUSE using packaging for Debian and RPM (file format). Production deployments rely on configuration management and orchestration tools such as Ansible, Puppet, Chef (software), and container platforms like Kubernetes for operator patterns and Helm charts. Integration points include image stores on Ceph, object storage gateways to Amazon S3, and platform services like Neutron (OpenStack) for network booting via PXE and iPXE or tying into Ironic (OpenStack) for bare-metal provisioning. Enterprises often combine Glance with backup and snapshot solutions from vendors like Veeam or Commvault for image lifecycle retention.
Glance enforces access control through Keystone (OpenStack) RBAC roles and tenant scoping, with optional encryption of image data at rest using LUKS or integration with Barbican (OpenStack) for secret management. Transport-layer security uses TLS with certificates issued by authorities such as Let's Encrypt or enterprise CAs from DigiCert. Image signing and provenance can be achieved through tools like Notary (project) and supply-chain frameworks advocated by the Open Web Application Security Project and Cloud Security Alliance. Secure deployment practices mirror guidance from NIST and compliance frameworks such as SOC 2 and ISO/IEC 27001 implemented by cloud providers including Amazon Web Services and Google Cloud Platform.
Glance scales horizontally by deploying multiple API and registry nodes behind load balancers like HAProxy or NGINX and leverages backend scaling in systems like Ceph or Swift (OpenStack) for throughput and capacity. Caching layers using Varnish or CDN integrations with providers such as Akamai or Cloudflare reduce latency for image distribution to edge sites and public cloud regions operated by Amazon, Google, and Microsoft Azure. Large-scale operators such as Rackspace and telecommunications providers adopt sharding, replication, and object lifecycle policies from S3 semantics to optimize storage costs and access patterns, while telemetry and monitoring via Prometheus, Grafana, and ELK Stack inform capacity planning and autoscaling strategies.