Add file to the reno documentation build to show release notes for
stable/2024.1.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2024.1.
Sem-Ver: feature
Change-Id: Ideffed96cfc56ad74898308f039cdf5e005bcda8
The 2024.1 release will support direct upgrade from 2023.1, so this
scenario should be tested in CI.
Change-Id: Idbe56fd0eaa2e4b04ce64051bd706ad7757cddf2
As per the current release tested runtime, we test
till python 3.11 so updating the same in python
classifier in setup.cfg
Change-Id: Id0f37bebfb5298c5a84aa8f46f9b2d161b1f81ca
Add file to the reno documentation build to show release notes for
stable/2023.2.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2023.2.
Sem-Ver: feature
Change-Id: Ibe63023c8e1c74118ebae76ea1d4a93eec2aaa31
Python 3.11 job run on Debian Bookworm which does
not the mysql pkg for example, libmysqlclient-dev
instead they have mariadb. Updating bindep.txt file
to adjust the pkgs as per Debian bookworm.
Change-Id: Ib47d5e77b14353402fad06e7adc04f8ee8a7e94c
We were explicitly warning on one type of warning. We should warn on all
of them, since they are issues that need prompt addressing.
Change-Id: Ice70d5f0eb93537c4580964d0c70d439182977c0
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
We were not using our own base class for some of the functional tests,
which resulted in us missing SQLAlchemy 2.0 issues. Correct this.
Change-Id: I921646053c9c68b06df54d206c3d51838c4cafa6
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
We were missing a number of users of SQLALchemy APIs that were either
changed or removed in 2.0. These were yielding the following errors in
2.0.
TypeError: MetaData.__init__() got an unexpected keyword argument
'bind'
TypeError: TableClause.insert() got an unexpected keyword argument
'values'
TypeError: TableClause.update() got an unexpected keyword argument
'values'
AttributeError: 'Engine' object has no attribute 'execute'
Resolve these issues. We will fix the test class issue in a follow-up.
Change-Id: I8724b0738f097739f55cd8566bb30b7ddbe154d9
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
As discussed in the upstream meeting, update the placement bug tracker,
link from storyboard to launchpad, so new bugs should be reported in
launchpad instead storyboad.
Whats not updated:
- all links of storyboard which do not point to bugs
- links of existing stories, features, docs etc
Change-Id: I64b9d6feb4fb35f36c5a290b8b79d9b78736efd2
Add file to the reno documentation build to show release notes for
stable/2023.1.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2023.1.
Sem-Ver: feature
Change-Id: If400681138cdb2b63790567bed6354ade2a49f8b
We're now close to RC1, we need to ensure that 2023.1 Placement will support
the new traits.
NOTE(sbauza) : We recently removed the gabbit check on the number of traits,
we don't need to amend it (I31431a6eb4f144135da0dc9c6d5e4c6b75d1af5d)
Change-Id: Id0f93c6a42d4e42cce668fe8927ab4249bfa9bd6
Placement API policies have been modified to drop the system
scope (every policy is now project scoped) and also modified
the defaults. Most of the policies are default to admin_or_service
role except reshape which is service role only and project resource
usage which is allowed for project reader and admin-or-service role.
Implement: policy-defaults-improvement
Change-Id: I806753e5b36a18be191a839256aaa84b511778f4
RBAC defaults for enforce_scope and enforce_new_defaults for
placement service is False. Nova is setting them for Nova service
to True in https://review.opendev.org/c/openstack/nova/+/866218
Placement tests fixture are used in Nova functional tests and
setting the rbac defaults causing placement to run with defaults
of what Nova is setting. To avoid this conflict, in placement
tests fixture, we need to set enforce_scope and enforce_new_defaults
to the same value it is for placement service.
Needed-By: https://review.opendev.org/c/openstack/nova/+/866218
Change-Id: I7e94d107962efdd7779733375327f5c8248c7087
* removed skipsdist=True to make sure placement available in the virtual
env
* passenv fixed as space separated list is not allowed any more
* improved the doc generation command line to print all the errors
instead of stopping at the first one
* added functional-py310 for convenience
* removed basepython = python3 as we assume all developer switched to
python3 in their env already
* removed ignore_basepython_conflict = True as without the basepython
definition generative targets now work without conflict
* updated the install_command to mimic better what tox uses by default
Depends-On: https://review.opendev.org/c/zuul/zuul-jobs/+/866943
Change-Id: I1de24b7a98f149fce33d4e5eca82460eea72140b
This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for antelope. Also,
updating the template name to generic one.
See also the PTI in governance [1].
[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html
Change-Id: I7bef657a342fa8b7b08ffcca4459e2831204ee60
The python 3.10 tox job runs on ubuntu 22.04 in the A cycle ubuntu 22.04
will also become the default for other jobs. python-dev is nolonger packaged
on ubuntu 22.04 so the tox job fails.
This change sync the python deps to match those use in nova which
already works across all tested distros.
Change-Id: I7fa25fea03f0c9c645a1eb10b22f058ca548d2fb
Add file to the reno documentation build to show release notes for
stable/zed.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/zed.
Sem-Ver: feature
Change-Id: I14ea1cdff8272e3c5f7796558ab9aff70557180f
With oslo.db 12.1.0 the following sqlalchemy warning become an error:
sqlalchemy.exc.RemovedIn20Warning: Retrieving row members using strings
or other non-integers is deprecated; use row._mapping for a dictionary
interface to the row (Background on SQLAlchemy 2.0 at:
https://sqlalche.me/e/b8d9)
We tried to fix this before but missed a test_case that still used dict
access to get the fields of a Row instead of attribute access. We fixed
that test here. Also while fixed it I noticed that the generic
_AttributeCache object states that it stores dicts but actually it
sometimes stores dict but sometimes it stores Row objects. So the doc is
updated and the dict path converted to store namedtuple objects in the
cache instead. Note that Row is also acts like a namedtuple except that
._mapping does not exists in namedtuple but exists in Row. The trait
object assumed it gets a Row object with ._mapping from the cache so
that is adjusted to only assume a namedtuple and use _asdict() to covert
it to dict which is available both in Row and namedtuple.
Change-Id: I23ac1d85290a2dec307f8e76aafb02096259b605