Update queens specs from 'approved' to 'implemented' or to
rocky/approved or to untargeted, define the redirects, and
make appropriate changes on the supporting pages.
Change-Id: I48aa6a2f11831ffc544e8b02b0bfdb80aa51d3e2
Maintenance on oslosphinx ended with the Pike release. This
patch includes the following changes:
* switch to openstackdocstheme
* set context options for openstackdocstheme
- glance-specs doesn't have its own bug tracker, so config
to create bugs in the glance bug tracker with tag 'glance-specs'
* update requirements file
* update setup.cfg to use warning-is-error
* update four specs whose warnings were previously ignored
* add an '_extra' directory with stub .htaccess file
* configure docs build to include '_extra'
* update build command in tox.ini
Change-Id: I4da477fd39685a22fb4ef9d702af9b9a79bda0c2
At the summit, we discussed keeping the file endpoint around for
service-to-service communication. This patch reflects that in the
approved spec.
Change-Id: I886f4e02a5a79fcbe6f78976c89fc4afb5c18576
Adds a FAQ section to the image import spec to answer some common questions
so that people not intimately familiar with the design can make better
informed comments on the implementation patches.
Change-Id: I31516f8c6e3a89031c20366e151c75b4c46b8372
This is an attempt to collate the various alternatives which were proposed
in the comments on the spec, and list their advantages and disadvantages.
Change-Id: Ie4e9961e38ff61a1fcf1910aa5bdac1f380b33ec
Recent discussions in #openstack-glance and at the virtual midcycle
meeting indicate that some key agreements are not sufficiently clear
in the current text. This patch adds a section titled "Summary
of the Constraints Around This Project" to clarify these key points.
MitakaPriority
Change-Id: I2c3f659c400ecf0c8e354ff5f80100724e7879a8
This spec is being implemented under Mitaka and it's a long standing
one. It seems ok to move it under Mitaka and let the implementation
happen.
Change-Id: Ia3e1fef30788123fc037b4dbb39439ae9d0b5363
A cloud must choose what the best target format for its own deployment
is without requiring the user to pass this information over. A user
shouldn't worry about what the target formats in a cloud are. To some
extent, the user should not care about the image being converted at all.
This patch removes the requirement of passing `target_` fields in the
import call but it keeps them, as a way to inform the user how the cloud
operates, in the `info` call.
Glance already provides a way for cloud operators to specify what format
images should be converted to: `conversion_format`
MitakaPriority
Change-Id: I60e2987e430a2f4a2e0dc3f34e96577a1c854364
This change proposal introduces a new mechanism for uploading/downloading
chunked files to Swift store, that prevents possible 401 errors if user
token expires during the operation. It helps to improve the reliability
of image uploads and downloads by providing the ability to reauthenticate
during the process, thereby enhancing the stability of the entire system.
Implements bp prevention-of-401-in-swift-driver
Change-Id: Ib18b626b7545c26d2c96c94db78030a80214e18e
Extracts the single root disk image and its metadata and saves
in Glance database. Metadata can be used by Nova image properties
filter. Image can be used to launch VM. Pre-processing saves
time during launch.
Change-Id: If77f79e47c56c4c1e60573479e253cb2ec3c3af3
Co-Authored-By: Deepti Ramakrishna <deepti.ramakrishna@intel.com>
Adds into the Glance metadata definitions items from the
Common Information Model (CIM) schema for processor, storage,
virtualization, and resource related elements. The goal being to
introduce standards related terms to associate with OpenStack
resources such as images, flavors, compute nodes among others to
make OpenStack clouds out-of-the box interoperable from a end-user
perspective, enabling them to expect similar behavior.
Change-Id: I3a6aa12f3435d1c5a14f746d20c2f63945886f55
This spec proposes a refactoring of the Glance image import functionality
along the lines worked out at the Mitaka summit and lengthy subsequent
discussion on this patch set.
ApiImpact
DocImpact
SecurityImpact
Change-Id: If143638a5ae21068c062048dc6e5e91b31cd524f
Implements: blueprint image-import-refactor
I propose to add the ability to filter the images on the properties
'id', 'name', 'container_format', 'disk_format' using the 'in' operator.
APIImpact
Implements spec-bp: in-filtering-operator
Change-Id: Ia2a00f11ba961457243fa748d51ba7c38429845a
Per discussion on the mailing list [1] and the related
nova specification [2] it has been decided that the
signature should be of the image data directly, rather
than of the glance MD5 "checksum" hash of the image
data.
This spec updates the prior approved and implemented
Liberty spec with these modifications.
[1] http://bit.ly/1Q0M0C7
[2] https://review.openstack.org/#/c/188874/19
DocImpact
SecurityImpact
Related-Bug: #1516031
Change-Id: Ibc66afbab2ce3192134422740fd6a4379a03305c
This spec details the abiltiy to cleanly purge "deleted" rows.
This provides confirmed data destruction beyond the current
archive_deleted_rows functionality.
Implements: blueprint database-purge
Change-Id: I271948b0d29a98f84d4757494c35be9218094f2d
Prevent failure of setting an image to the 'active' status after
image upload due to an expired user token.
Co-Authored-By: Mike Fedosin <mfedosin@mirantis.com>
Implements bp trust-authentication
Change-Id: I407bac84750b2e26bacd59d21dd72289209bf955
Currently Glance's Cinder backend driver doesn't support
uploading, downloading, and deletion.
As missing parts in Cinder listed in
https://blueprints.launchpad.net/glance/+spec/glance-cinder-driver
(os-brick library, readonly-volumes, multi-attach) are now supported,
now we can implement uploading and downloading for it.
Change-Id: Ic548289c3bf195abde28a5cf52944632b926b487
This change proposal introduces a buffering wrapper around image
data for use during image uploads. This buffering wrapper helps
improve the reliability of image uploads by providing the
ability to recover from errors occurring during the upload process.
The ability to recover from errors comes from buffering the image
segments before uploading to swift. When an error occurs, Swift
client resumes the upload process from the last successful position
determined using 'seek' and 'tell' operations on the buffered image
segment.
Change-Id: I41ab910cfef219b48230d9345246f1e5143774b4
Put approved specs in a specific dir and move them under `implemented`
once they've been completely implemented. This way, we can differentiate
between implemented specs and unfinished specs more easily.
Change-Id: Id90b2b0a7cd0542078d6f4830e84da7b06cd76d9
Now that the name of the new milestone has been decided, it is time to create
a folder to house specs for it.
Change-Id: Ic13e5f89f600d3d48f4f8c16576d4a5722e1110a
Brian Rosmaita