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
This spec outlines a database modification strategy for Glance that
will facilitate rolling upgrades.
Change-Id: Ic2fa8e5c8a2d28e3d88b73b5bfd6d99bc11d0183
Co-authored-by: Hemanth Makkapati <hemanth.makkapati@rackspace.com>
Co-authored-by: Brian Rosmaita <brian.rosmaita@rackspace.com>
Mox does not support python 3. We have a shim module 'mox3' that was
built a couple of years ago, is unmaintained, and as it gets tested more
heavily is showing race conditions under python3.
So, it is proper to reduce our reliance on mox.
Change-Id: Iac2f8ad018aed19219e3250cb516e660fb348dcd
This spec provides a gap analysis of what is required for the Glance
project to assert the various rolling upgrade tags and specifies the
actions necessary to close the gaps.
Change-Id: I40c2b85e9d9a806d528d5be5d97ca8a730631463
Co-authored-by: Hemanth Makkapati <hemanth.makkapati@rackspace.com>
Co-authored-by: Brian Rosmaita <brian.rosmaita@rackspace.com>
Currently, when a partial download request is sent, the
``Content-Range`` is parsed in glance/common/wsgi.py to
obtain the byte range. What this means is that the user
is expected to specify the byte range he/she intends to
download in a format of a HTTP range response.
For example: A user has to give "bytes 12-30/32" instead
of "bytes=12-32".
W3 standards (RFC 7233) specify ``Content-Range`` to be sent
as a response for a ``Range`` header in a HTTP request.
(https://tools.ietf.org/html/rfc7233#section-4.2)
This lite-spec suggests the acceptance of ``Range`` headers
for partial download requests.
Change-Id: I5bdadde682a0c50836bd95e2a6651d6e7e18f172
This spec outlines the motivation and implementation details for porting
Glance database migrations from SQLAlchemy-based scripts to Alembic.
Change-Id: Ia8e72ce863ab8f2d1ba021f950dae1b8596cadfa
Currently image location updates (removing, replacing) are permitted for
images even if their state is not ``active``.
This lite-spec describes the need to prevent removal of image
locations of images that are not in ``active`` state and the replacement of
image locations of images that are not in ``active`` or ``queued`` state by
returning a Conflict Error (409 response code).
Change-Id: I6d984fcafa49ad806dce2bd56abcee66fdc77525
Some of the Newton specs did not get enough attention from cores
during the cycle. Let's start the Ocata folder for starting planning on
the specs for next cycle.
This needs to be started/merged in Newton for people to start planning
on writing specs and then help the glance team and community
determine/plan work for Ocata.
Co-Authored-By: Nikhil Komawar <nik.komawar@gmail.com>
Co-Authored-By: Brian Rosmaita <brian.rosmaita@rackspace.com>
Change-Id: I16d1dd18c3efceb2245239f9c95483e717c70c4d
melissaml