Rsyslog roles are not used actively by OSA code and were hardly
maintained recently, thus we fully remove their usage and deprecate
Depends-On: https://review.opendev.org/c/openstack/openstack-ansible/+/861886
Change-Id: If8b6bc069dc105d3c630567769bc4df8fce642eb
This is a follow-up to our 2019 analysis of the user
survey results. This includes comparisons between the
2019 and 2021 date.
Change-Id: I1161093d2d728e5d4c875f6db65b0bbdcb79201b
Add a project for defining the zuul jobs for testing charms.
Depends-On: I69a9c9f388371a7a8ad1c7fe5cfc8f6c444d4f45
Change-Id: I07ace283a8255f106c141d7bea06618f802e3b51
I would like to nominate myself as vice-chair of the
Technical Committee for the 2023.1 cycle.
I was vice-chair in the Zed cycle already and I want to continue
helping our chair in all day-to-day duties.
Thanks for considering my nomination.
Change-Id: I2161a578e8e6825fe2d400d5ac814e0295dd203e
Goal implementation should be finished during 2023.1 development cycle.
In order to start progressing on it we should select goal for
implementation first.
Change-Id: Ib3893bc1fafd8626465de4f9d9ff467404bea97c
Ubuntu 22.04 has been released on April 21 and by now already have first
point release as well as upgrade path from 20.04 (Focal). By the end of
Antelope development cycle Ubuntu 22.04 will be around for a year,
which makes a good timing for us to set a goal of migrating CI/CD jobs
to start using this distro.
Change-Id: Ic89ae25dcaebc4f27e9214a857d4d681d0992667
I would like to nominate myself as chair of the
Technical Committee for next cycle.
I served as TC Chair since Xena cycle and trying my
best to be more active in TC and perform all duties
on time. Few of the things got initiated in the past couple
of cycles and went well (and we will continue these) are:
* TC + Community Leaders interaction: We as TC always
want to get feedback from the community on TC activity and
what direction do they want us to work on? But we hardly
receive any feedback when we initiated it in the past on ML.
Starting a separate session in PTG with TC and Leaders helped
us to receive feedback and also improved the interaction with
community.
* TC doing more Technical work: As feedback from the community
in TC+Leaders sessions, we started doing more technical work than just
project updates (add, remove projects) things. But still, a lot to improve on
this. We will continue working on this and helping the community in both
ways technical as well as from process/governance perspectives.
* Re-starting the interaction with Board members is one of the
good things. It helps to have more visibility of the OpenStack community,
TC as well as discussing our challenges at a broader level.
I would like to continue the chair role and do the same as I am
currently doing. Thanks for considering my nomination.
Change-Id: I8de7cd9ee045e62cfb72b5d7a046bab322f4176b
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
