* Update blazar-specs from branch 'master'
to 1b34a81d919d138ca24ee3664bfd5e84634e0c40
- Fix PDF docs build
Update tox config to include upper-constraints as dependencies. This
resolves issues with building PDF docs.
Change-Id: I7d6789cecfeb432e0a0c38f996f559c24c85ca03
* Update blazar-specs from branch 'master'
to c1b323eacea0dc2c0de8f7c415da9d89b4215085
- Change dashes to underscore in setup.cfg
Recent versions of setuptools are warning that usage of dash-separated
keys will not be supported in future versions.
Change-Id: Id19425239ae3ab8769c3d847a4e4bf886ee0493f
* Update blazar-specs from branch 'master'
to e8615903e8a5cd0fa7fb48d8cc04bd9888552b89
- remove unicode from code
Change-Id: I9ffdd1f00af22f0ce5de11371041aecf4737ade2
* Update blazar-specs from branch 'master'
- Switch to newer openstackdocstheme version
Switch to openstackdocstheme 2.2.1 version. Using
this version will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Set openstackdocs_pdf_link to link to PDF file. Note that
the link to the published document only works on docs.openstack.org
where the PDF file is placed in the top-level html directory. The
site-preview places the PDF in a pdf directory.
Disable openstackdocs_auto_name to use 'project' variable as name.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: Ic436b800e4474a0e45703231f8138ad97505335b
* Update blazar-specs from branch 'master'
- Cleanup py27 support, fix docs
This repo is now testing only with Python 3, so let's make
a few cleanups:
- Remove obsolete sections from setup.cfg
- Update requirements, no need for python_version anymore
- Cleanup doc/source/conf.py to remove now obsolete content.
- Use newer openstackdocstheme version
- Remove install_command from tox.ini, the default is fine
- Enable sphinx warnings, fix all
Change-Id: I921faba15db8657115f78b7f008145c177a6ec59
* Update blazar-specs from branch 'master'
- Add spec for resource property discovery API
This spec proposes a new REST API that allows users to query for the
list of possible resource properties (and their possible values) in
order to make it easier to craft reservation requests referencing
resource_properties.
Change-Id: I96f70210e4f2fbd49d4e8354133c797604b2568c
* Update blazar-specs from branch 'master'
- Merge "Add flexible reservation usage enforcement spec"
- Add flexible reservation usage enforcement spec
This spec proposes a new mechanism to allow operators to define custom
policies that determine whether a given user request to create or update
a lease is valid. A chain of enforcement filters will be called on every
lease request. Two filters will initially be defined: one that checks
that leases do not exceed a length threshold, and one that delegates to
an external HTTP service. Future filter implementations may be included
with Blazar, but there is also a mechanism for operators to provide
their own filter implementations as Python modules.
Change-Id: I376d348a334a09614545b1cadafb3cc76cfa1b1c
* Update blazar-specs from branch 'master'
- Small Cleanups
Remove install_command, the default is just fine.
Update openstackdocstheme version, remove obsolete setting of
html_last_updated_fmt.
Update pbr version.
Change-Id: I759fcb2d65b6cc7132486088e1e3f1388a9a2e6d
* Update blazar-specs from branch 'master'
- Merge "Support preemptible instances with Blazar"
- Support preemptible instances with Blazar
This spec proposes to add support for preemptible instances with Blazar.
It would allow to increase utilization by filling gaps between
reservations, as well as provide an implementation of preemptible
instances that does not require modifications to the Nova compute
service.
Change-Id: Iba016a52666d44c82ea7c820814b18952dcaf9ed
* Update blazar-specs from branch 'master'
- Merge "[ussuri][goal] Drop python 2.7 support"
- [ussuri][goal] Drop python 2.7 support
OpenStack is dropping the py2.7 support in ussuri cycle.
specs repo has py2 specific requirement which is removed
or tox optimization.
Ussuri Communtiy-wide goal:
https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html
Change-Id: I262c6035ce1307409d2fdea730d69c5e162bc668
* Update blazar-specs from branch 'master'
- Add spec of json Schema Validation for Blazar API
Change-Id: I5b4b52211b6aa8d8388c4b9c4ff4b59830736187
Implements: bp json-schema-validation
* Update blazar-specs from branch 'master'
- Migrate specs from blazar repository
This commit includes small changes to fix Sphinx warnings and a specs
template file for the Train release.
Change-Id: Ifb44a1d948f8fcd6db95b154a84ed18e3ee4b042
- OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.htmlhttp://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html
Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.