|
136.
|
|
|
Status of the image (READ-ONLY)
|
|
|
|
(no translation yet)
|
|
|
|
Located in
glance/api/v2/images.py:655
|
|
139.
|
|
|
md5 hash of image contents. (READ-ONLY)
|
|
|
|
(no translation yet)
|
|
|
|
Located in
glance/api/v2/images.py:670
|
|
140.
|
|
|
Size of image file in bytes (READ-ONLY)
|
|
|
|
(no translation yet)
|
|
|
|
Located in
glance/api/v2/images.py:680
|
|
143.
|
|
|
Date and time of image registration (READ-ONLY)
|
|
|
|
(no translation yet)
|
|
|
|
Located in
glance/api/v2/images.py:698
|
|
144.
|
|
|
Date and time of the last image modification (READ-ONLY)
|
|
|
|
(no translation yet)
|
|
|
|
Located in
glance/api/v2/images.py:706
|
|
596.
|
|
|
A boolean that determines if the scrubber should clean up the files it uses for taking data. Only one server in your deployment should be designated the cleanup host.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
glance/scrubber.py:45
|
|
597.
|
|
|
Items must have a modified time that is older than this value in order to be candidates for cleanup.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
glance/scrubber.py:50
|
|
611.
|
|
|
%s file contains conflicting cleanup timestamp.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
glance/scrubber.py:481
|