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: Ib1857448c2cb7e455d5002c27c6f0d83c999539e
hacking 3.0.x is too old. This also removes the note about old behavior
of pip which has been changed in recent versions.
Change-Id: I5a8dc51a94c8284c9c869728981dcb19de63d941
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: I28e9cc11f79f8ae506b98f2cfc7bc6e68eef5a32
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: I61bf3f0fa2cff8c80affabff9d78a6fab91ba815
osc-placement functional tests are using the master version
of placement which is failing due to the constraints mismatch
on stable branches testing.
- https://zuul.opendev.org/t/openstack/build/a2cc830f28f44ed5ae0e1c5f0a99ac75
During the discussion in Nova meeting, we did not find any reason why
we are using the latest placement on stable branch testing of osc-placement
- https://meetings.opendev.org/meetings/nova/2023/nova.2023-01-10-16.00.log.html#l-47
Below is the original patch which started using the placement from master
source.
- https://review.opendev.org/c/openstack/osc-placement/+/651939
To avoid the constraints mismatch on stable branch testing which can
happen in future also, let's use it from pypi version which will be the
same way as nova functional tests doing
- 26f24b7086/tox.ini (L64)
Also, remove basepython/ignore_basepython_conflict from tox.ini. Tox 4.2.6
still failing with the missing interpreter for [testenv:functional{,-py38,
-py39,-py310}]. It is due to a conflict between basepython = python3
and the version fragment in the generative target suppressed by
ignore_basepython_conflict = true.
This patch removes basepython = python3 assuming that developers already
switched for python3 in their environment as python2.7 is EOL.
Ref: https://review.opendev.org/c/openstack/nova/+/869545
Change-Id: I4e3e5732411639054baaa9211a29e2e2c8210ac0
As per 2023.1 testing runtime[1], we need to test on Ubuntu
Jammy (which will be taken care by tempest and devstack patches
to move base jobs to Jammy) and at least single job to run on
Ubutnu Focal (for smooth upgrade). Also, python 3.10 testing is
voting now.
This commit makes python 3.10 functional job as voting and python 3.10
unit test job are voting via generic template. Python 3.8/3.9 jobs are
running on Focal and python 3.10 on Jammy.
[1] https://governance.openstack.org/tc/reference/runtimes/2023.1.html
Change-Id: I97b82399af9a640353ba979965c202afcb224163
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: Ieb6339cd677c76f0158cc19c9a0bf32b2237594d
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: I381fb75fc354af99751917d95f30bbfca7adfc8b
The CLI now support the following syntax both for openstack resource
providers list and allocation candidate list commands:
--required T1,T2 --required T3
and it means (T1 or T2) and T3.
In the allocation candidate list command the above can be used both
outside and in a --group context.
Story: 2005345
Story: 2005346
Depends-On: https://review.opendev.org/c/openstack/placement/+/826719
Change-Id: I38ff55bdd072f3a9c1ed03e28192d045cb4096cf
This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for zed.
See also the PTI in governance [1].
I needed to squash in another change that is dropping the py36 and py37
support. We cannot do that separately as those jobs are already failing.
[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html
Change-Id: I378d5c3c1f3e96696670a4865caf5901269a5ee4
Add file to the reno documentation build to show release notes for
stable/xena.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/xena.
Sem-Ver: feature
Change-Id: Ida17fdbe9fce1971106bba7f84318b9a191a5589
Add file to the reno documentation build to show release notes for
stable/yoga.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/yoga.
Sem-Ver: feature
Change-Id: Ib9f97090a45e7e633c4f4667603c02c406447067
Add a guards for empty allocations in the allocation parsing code of
allocation show and allocation unset.
Closes-Bug: #1942740
Change-Id: Ic0e6e981d6602a76935f6bc6d9ffb0a707a5b1a9
This patch adds a functional test case to reproduce the bug when an
allocation show command on an empty (non existent) allocation causes
KeyError as the code expects project_id in the response but the
response is {"allocations":{}}. Also similarly for allocation unset
where microversion 1.38 fails on parsing out consumer_type from the
empty allocation too.
Related-Bug: #1942740
Change-Id: Iea27c9376480e3e94d12eec56b466331e5c6f171
This change fixes a regresssion intoduced
by the supprot for microverion auto-negotiation
which resulted in the inablity to generate
bash autocompltion.
When the client_manager does not have a api session established
such as when being invoked for auto completion this
change modifies get_version to return version.MAX_VERSION_NO_GAP
Story: #2008958
Task: #42592
Change-Id: I90e1e3caeaa22ff51df515226b3ac5c7b64c88b6
There were tests to verify that 'resource provider inventory set'
command with --dry-run and --aggregate option changes nothing on
the server side but there was no test to verify the result of that
command. This patch adds the test.
Change-Id: I8d2c25a654928d8d46d5e1d0ee203600c9a72600
The ``openstack resource provider allocation unset`` command now
supports ``--resource-class`` option, which accepts string of a
resource class. This will remove allocations for the given resource
class from all the providers. If ``--provider`` option is also
specified, allocations to remove will be limited to the given resource
class of the given resource provider.
example1::
# remove VGPU allocation from provider P for this consumer.
allocation unset <consumer_uuid> --provider P --resource-class VGPU
example2::
# remove VGPU allocations from all providers for this consumer.
allocation unset <consumer_uuid> --resource-class VGPU
Change-Id: I91baf9de5205ec15023706a1646556850302d3d9
Story: #2006779
Task: #37304
The placement client (osc-placement) supports the
``OS_PLACEMENT_API_VERSION`` environment variable,
but it is not described in the ``openstack -h`` command.
So this patch adds the description as well as other
environment variables.
Change-Id: I41a3718bfa27ecf370c7375b4f761cda47866b1a