panko was deprecated in Xena cycle already, this patch marks
* panko
* python-pankoclient
* puppet-panko
as retired and move their entries to legacy.yaml.
Change-Id: I0bec371f442c4e39557bf1f0d94697e1577bb838
Add new charm that enables Keystone to support OpenID Connect via
Federation.
Depends-On: Ic758858db00a72a136e21c18f452df07f4ea74c2
Change-Id: I1b7495f0a5010f9768845882a6e072b5be3f18b9
It updates the ubuntu version to 22.04 and python
version to py3.10 which is default in Ubuntu 22.04.
Python 3.9 and python3.10 will be the two versions
to test in 2023.1 cycle.
Moving Centos stream in the list of 'Best effort' to test
them.
Change-Id: I008d086279f0105561a74216a67a3aa9e624fec7
The purpose of this change is to make it explicit that "team leadership"
for the requirements team is equally shared between the 2 named
individuals. While this is more of a co-PTL model we're leveraging the
distibuted team leadership model adopted by the TC resolution[1]
[1] https://governance.openstack.org/tc/resolutions/20200803-distributed-project-leadership.html
Change-Id: Ib6c4c4f4a45f42e4daaa910cd728f946e72ff75c
As part of our discussion from the latest PTG, as well as several
prior, one of the goals for the project was to retire any of the
unused repositories under the openstack-helm umbrella.
This change seeks to retire the openstack-helm-addons repo
since it has not been maintained and the existing charts are not
actively supported.
Depends-on: https://review.opendev.org/c/openstack/openstack-helm-addons/+/850890
Change-Id: Iea729e8c591de4d7e1fd680fef575e2a53b1f67f
In Zed cycle, we started collecting the operators feedback
- https://etherpad.opendev.org/p/BER-2022-OPS-SRBAC
- https://etherpad.opendev.org/p/rbac-operator-feedback
and based on that we changed the direction for RBAC goal:
1. Finish delivering project personas. This is to introduce the member
and reader roles to operate things within their project. By default,
any other project role like foo will not be allowed to do anything
in the project.
2. Change in scope implementation. Services with project resources
(except Ironic as they have user using the system scope) that have
already implemented scope (or have yet to) should make all policy
rules set scope_types=['project'].
Discussion reference for policy popup team
- https://etherpad.opendev.org/p/rbac-zed-ptg#L171
Change-Id: If7b052149df3f37f2173e6719c8c6d0d81787cc7
Add the initial set of K8S charmed operators for various parts
of the OpenStack Control Plane to the OpenStack Charms project.
Change-Id: I5bfe97d30661dbf0908c16f633decab40cb5edc2
Depends-On: I6876645221488892b826929810a16a53b846902c
As part of our discussion from the latest PTG, as well as several
prior, one of the goals for the project was to retire any of the
unused repositories under the openstack-helm umbrella.
This change seeks to retire the openstack-helm-deployments repo
since it has not been maintained and the use-case that it was
originally created for is no longer being actively pursued.
Depends-on: https://review.opendev.org/c/openstack/openstack-helm-deployments/+/847410
Change-Id: Idb63ff8e74427d2b2adab5f003441fb0f6b218b1
At the October 2021 PTG and April 2022 PTG we discussed the need to for
something like "technical preview" state for the e.g. new OpenStack
projects which don't meet all requirements for being official OpenStack
project (see Skyline for example).
This patch adds framework for such projects. It's called "emerging
technology" state which can be set for new projects.
It also defines "inactive" state for the existing, not well maintained
projects.
Change-Id: I32a07f8bb46723f36c1bf846644b6aa768778a4f
Foundation bylaws mention the "ATC" term and during
the merging of UC to TC we changed it to "AC". Adding a line
stating that both are the same term and that way we will comply
with the bylaws also
- https://openinfra.dev/legal/openstack-technical-committee-member-policy
Change-Id: Icd7efda1d7a49c6ddb1b7f4ac9687e7e6b231a84
The security-analysis repo is slated for retirement by the Security
SIG. This change removes the security-analysis repository from the
list that is currently maintained by the Security SIG.
https://lists.openstack.org/pipermail/openstack-discuss/2022-June/028816.html
Change-Id: I1d59c3534d9982c97f451cfc8ee711a44e71a6ef
Adding infra contributors opportunities in upstream investment
(copy from previous year) which still need help.
Change-Id: I7fe371b5844f1524d02bb911763957658e9afedd
Recently we discussed with Release Management team some possible
improvements in the project governance. Summary of that discussion can
be found in [1].
This patch updates potential triggers to consider project to be dropped
in the dropping-projects document to reflect those improvements
mentioned in [1].
[1] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028418.html
Change-Id: I3c9bb37be8ab9ab5282377169de906db2bf5b7fc
Validate on Zuul builds and Gerrit.
This is needed for project stats check. Please check etherpad for more
detail discussion or output example [1].
Run project_stats_check.py with no arguments will run on all projects
defined in `reference/projects.yaml`.
If you wish to run for specific project or branch. Run like:
`project_stats_check.py -p heat,sahara -b master,stable/xena`
[1] https://etherpad.opendev.org/p/health_check
Change-Id: I84c3a4898a74c26746fd66d046a80b8936a608e9
