The QA team pointed out to us that usually devstack plugins are
branchless [1] (and tagless but that's already the case here).
They haven't been branched since ussuri, we think that we simply
missed to retire them few series ago.
I think that's the right moment to do a little spring cleaning.
Let's drop these deliverables.
[1] http://lists.openstack.org/pipermail/openstack-discuss/2021-April/021526.html
Change-Id: I7df2166cdd4b9266287d47d90c3cd49d6d122c71
This patch aims to move Mistral under the DPL governance model.
Since nobody was promoted a PTL candidacy for Mistral for the
next cycle, the Mistral core team made a decision to move the
project under the DPL model.
Change-Id: I9960501520bc3fbccfe49c1b528b5fa48a93b696
Let's reset the TC liaisons with empty list as we have
new TC members. TC members can volunteer to select the
interested projects for liaisons and for remaining one
we can automatically assign it using script.
Change-Id: I4c61c49e197e8c65d875d5b6fd7ec5c031312a91
Add new charm that provides Manila insights to
the OpenStack Dashboard (Horizon) service.
Depends-On: I892ad71c30c01b83256e301b3e77cdb814d9c3a5
Change-Id: I843ff4c67a2077cb204f49d354db8e14a49fd9e4
Add new charms that provides the OpenStack Magnum service
and its dashboard.
Depends-On: I9faa96360bdc3eebb12f88f5f53d0ae13e0e398b
Change-Id: I0649a57fb69510f0f6223854f2066411409c3e56
Add new charm that provides the NetApp backend support
to the OpenStack Manila service.
Depends-On: Ib843838e452f934ff86e9367d9a7d94ce1731076
Change-Id: Idffb0ed019b4759a1680cb407c6c9ebcfbdae33d
As disscussed in Wallaby PTG [1], QA and Horizon team decided to
move the horizon dashboard test from tempest-horizon to Tempest.
Scenario tests in tempest-horizon have been merged into the tempest
repository. tempest-horizon is branchless so we can retire it
without a deprecation phase.
Depends-On: https://review.opendev.org/c/openstack/project-config/+/774378
Change-Id: Ie18ae4891d41e39d9cb23aee50f11b329e724172
The Cinder project meets all the requirements for the api
interoperability tag:
1 - The project follows the OpenStack API interoperability
guidelines [0] when making changes to the REST API
2 - The Block Storage API v3 uses the microversions versioning
scheme
3 - Branchless API tests from tempest and the cinder-tempest-plugin
run on every commit
[0] http://specs.openstack.org/openstack/api-wg/guidelines/api_interoperability.html
Change-Id: Ie8b2231126db01707507320a3597a398fa208ae8
This role aims to manage SSL certificate issue process -
ie generation of self-signed certificates or distribution of user
provided ones
Depends-On: https://review.opendev.org/c/openstack/project-config/+/773385
Change-Id: I5b2d06a428738b29a1e2d583950a5e33a2ce4cdb
The Neutron project meets all the requirements for the api interop tag.
It follow the api interop guidelines, supports API discoverablity by
using extensions mechanism, and has branchless API testing through
tempest and neutron-tempest-plugin.
Change-Id: Ica7ed7e3cdc146b3d9de268f0414d8d33c1090fa
Add the rbd-iscsi-client repo to the cinder project. It will
follow the independent release model.
rbd-iscsi-client was added to global-requirements by commit
2ce1a5eaab. The cinder project is assuming maintenance of the
library.
Depends-on: Icac3f5f74b2fca06c8b25fa78d895bbb710ea308
Change-Id: I8f968adcc827cc7171c8310a585d3c79aba12940
This project was never released yet, was not ready yet for ussuri and victoria
and the OpenstackSDK team think that it require a serious redesign/rewrite [1]
so these changes propose to ignore it from a release point of view.
Set the release-management key so that it gets properly ignored by the release
management team.
[1] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019853.html
Change-Id: I1a548605a8593cbe2d311a6c2ed307d65cacc93f
For personal reason, Canwei Li has no time to continue the work for Watcher PTL.
Ke Chen(His colleage) from ZTE will take over the role.
Change-Id: I7a31c41ce83fbb7dd2a5da02a6a27dec8651e277
OpenStack Manila offers a long living API with tests that
ensure backwards compatibility is maintained as the API is
modified.
When evolving the API, the project conforms to the Interoperability
Guideline [1]. The Shared File Systems service API [2] is
micro-versioned [3] and when incrementing the API version, tests
are added to assert compatibility and stability at the prior
micro-version. These tests are never removed until the base version
of the API moves beyond the version that is being tested. So far,
the project has not made any changes to the base API version.
The service provides a version discovery API, conforming to the
version discovery guideline from the API SIG [4]. This version
discovery path can be accessed by unauthenticated users/automation
clients. If a client wants to operate at a prior supported version,
all new API changes remain hidden from the client.
The tests for the API reside in a branchless tempest plugin [5].
The same tempest plugin is used to test all supported stable
branches of the project, including those in extended
maintenance.
[1] https://specs.openstack.org/openstack/api-wg/guidelines/api_interoperability.html
[2] https://docs.openstack.org/api-ref/shared-file-system/
[3] https://specs.openstack.org/openstack/api-wg/guidelines/microversion_specification.html
[4] https://specs.openstack.org/openstack/api-wg/guidelines/microversion_specification.html#version-discovery
[5] https://opendev.org/openstack/manila-tempest-plugin
Change-Id: I557c033629076deb6c3f370123943d904683f85a
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
Yumeng changed her company and work priority, so she is going to step down
from the PTL position and Xinran Wang from Intel will take over the
role.
Change-Id: I58c71216901641a5ce22eb2ede73c68e91b3f260
This project was never supposed to have any releases,
it's a tool that was used by 3rd Party CI in Ironic.
Set the release-management key so that it gets properly
ignored by the release management team.
Change-Id: I707de0df26a69fdbcbf76078e9c8a6a86f1247f2
Karbor did not have any PTL candidates for the Wallaby
cycle. As per its activities in Victoria cycle and no
maintainers, the TC decided to retire Karbor deliverables in
the Wallaby cycle. The retirement was announced on the ML[1].
As per retirement process this commit proposes to remove
the Karbor project from the official OpenStack projects.
If there are any maintainers who would like to continue the
development of this projects then they can continue under
opendev in x namespace or repropose it to OpenStack governance.
Thank you to all the contributors of Karbor for your hard work!
[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-November/018643.html
Depends-on: https://review.opendev.org/c/openstack/project-config/+/767057
Change-Id: If4bdd357fea98df9ae7bb94889a5e75c68c9913f
Since we got a maintainer that is interested in revivng os_monasca role
it was decided to revive os_monasca and get it maintained again.
Depends-On: https://review.opendev.org/c/openstack/project-config/+/765799
Change-Id: Iff5b8a47a5418024e0d03070d62df43753cb09e0
Searchlight did not have any PTL candidate for the Wallaby
cycle. As per its activities in Victoria cycle and no
maintainer, TC decided to retire Searchlight deliverables in
the Wallaby cycle. It is announced on ML too[1].
As per retirement process this commit proposes to remove
the Searchlight project from the official OpenStack projects.
If there are any maintainer who would like to continue the
development of this projects then they can continue under
opendev in x namespace or repropose it to OpenStack governance.
Depends-On: https://review.opendev.org/c/openstack/project-config/+/764535
[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-November/018637.html
Change-Id: Ia8f0c05c8d6504f889b9abbc3802e55939c947be
Qinling did not have any PTL candidate for the Wallaby
cycle. As per its activities in Victoria cycle and no
maintainer, TC decided to retire Qinling deliverables in
the Wallaby cycle. It is announced on ML too[1].
As per retirement process this commit proposes to remove
the Qinling project from the official OpenStack projects.
If there are any maintainer who would like to continue the
development of this projects then they can continue under
opendev in x namespace or repropose it to OpenStack governance.
Depends-On: https://review.opendev.org/c/openstack/project-config/+/764536
[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-November/018638.html
Change-Id: I202c3a880f65ef356ce375062a3b81d087a65c21
Generating the TC liaisons assignments using
./tools/assign_liaisons.py on top of already
assigned one.
Change-Id: If449b175a8e7dababf8242ccdd4a692b0d60dd42