The domain model contains the following layers:
The schema below shows a stack that contains the Image domain layers and their locations:
The first layer of the domain model provides a verification of whether an
image itself or its property can be changed. An admin or image owner can
apply the changes. The information about a user is taken from the request
context
and is compared with the image owner
. If the user cannot
apply a change, a corresponding error message appears.
The second layer of the domain model is optional. It becomes available if you
set the property_protection_file
parameter in the Glance configuration
file.
There are two types of image properties in Glance:
The property protection layer manages access to the meta properties through Glance’s public API calls. You can restrict the access in the property protection configuration file.
On the third layer of the domain model, the following items are added to the message queue:
The fourth layer of the domain model is responsible for:
etc/policy.json
file.On the fifth layer of the domain model, if a user has an admin-defined size quota for all of his uploaded images, there is a check that verifies whether this quota exceeds the limit during an image upload and save:
The sixth layer of the domain model is used for interaction with the store via
the glance_store
library, like upload and download, and for managing an
image location. On this layer, an image is validated before the upload. If
the validation succeeds, an image is written to the glance_store
library.
This sixth layer of the domain model is responsible for:
On the seventh layer of the domain model:
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.