... to avoid the failure in CI.
py38: 205 E failed with env name py38 conflicting with base python
python3 [tox/session/cmd/run/single.py:56]
Change-Id: I0b4a1f3087dc0dd27f4c05bd98088eaefab66b35
* Replace .testr.conf by .stestr.conf for migration and update
.gitignore and test-requirements.txt files accordingly
* Use 3.18.0 as the minversion for tox
Signed-off-by: HeroicHitesh <email.hiteshkumar@gmail.com>
Change-Id: I2bb0f23771e6ff1e3f775520a719514c2a3f3aa3
Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
Change-Id: I4f21b16ae3518b11b49e3c190b609c44c1e753d4
a few cleanups:
- Remove obsolete sections from setup.cfg
- Switch to using sphinx-build
- Remove install_command from tox.ini, the default is fine
- Update pbr requirements
- Fix problems, mainly "Could not lex literal block"
- Use py38 job for Victoria cycle
Change-Id: Id706786bed4b20682704d524986850b7c71e225d
Switch to openstackdocstheme 2.2.1 version. Using
these versions will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
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: I853c21c0789296164632c47a0b3534321cec01ee
OpenStack is dropping the py2.7 support in ussuri cycle.
specs repo either has py27 job or requirement or tox env.
Doc building still use deprcated oslosphinx and incompatible
version of yasfb which lead to error-
sphinx.errors.ExtensionError: Could not import extension yasfb (exception: cannot import name 'logging')
This commit replace oslosphinx with openstackdocstheme ti fix the error.
Ussuri Communtiy-wide goal:
https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html
Change-Id: I76a9e0e3259ec52564f31a239079cd91da897ee9
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: I15775f36d0fbba05c5493037b389f7dc363a049e
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: I389b8c3ba61b70ead1b0ef91ed5e6e3ce49d0765
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I4f2e8be3789877a16710352a33bae36550a8b65c
Story: #2002586
Task: #24298
specs/rocky/rocky-template.rst should be a symlink, not a text file
containing the path to the actual template. This fixes the tests, and
also improves them to properly report errors when whole sections are
missing.
Change-Id: Ie95d45d134e8f332ecdecc687a68deb7af6c30c3
Define and register default API policies in Python code similar
to config options.
Support for such declaration of API access polcies has been put as
cross-project community goal for OpenStack Queens release.
Specifies blueprint policy-in-code
Change-Id: I9bf9a52d3af716d0731bbcaa371872a2f83bf40c
Allow user to decide whether do nested loop or not
for argument 'for_each' of 'repeat' function.
Blueprint: improve-repeat-function
Change-Id: Ib40eb9e5bf7f0dd53fd44ca2ccc2cd6d4e8da732
Currently properties group spec is already merged, but
still is not implemented, so need to move it to backlog due
to small community's interest.
implements bp heat-property-group
Co-Authored-by: Kanagaraj Manickam <mkr1481@gmail.com>
Change-Id: Id4847f79e6a9ad4b9dc3be2459604dd9583cb36e
Spec for discussing and suggesting better way to
fix and improve current translation mechanism.
Related-bug: #1620859
Change-Id: Id66ddc38a3fd8fb135bf49a7c083972fcd74b272
We have deprecated combination alarm, and this blueprint
to support composite alarm which is similar with the
combination alarm in functionality.
Change-Id: I6a8b7c6752229353208b7d8e9ef1b1d90670f570
Blueprint: add-aodh-composite-alarm
This creates new resource type whose intended use case is for admin-only
useto manage the Netowrking services quota. This would be an enhancement
toavoid manual, post-deployment modifications of the project's neturon
quota.
Change-Id: I62a715d8f7cb9adb0139b841d09694666929d9e7