The kolla project has decided that it no longer needs to have a
dedicated kolla-ansible-core group that is different from the kolla-core
group. Membership between the two groups has already been synced, so
this change is essentially a no-op, but allows us to only maintain a
single group going forward.
[0] https://meetings.opendev.org/meetings/kolla/2022/kolla.2022-11-23-14.00.log.html
Change-Id: I1dc5e5ed9f93ad40f2089891c63b530994b290f2
The OpenStack TC has not been using StoryBoard for goal task
tracking for many years now, and wants to clean up the presence of
their governance-specific repositories there in order to avoid
future confusion[*]. Remove the use-storyboard option from both
openstack/governance and openstack/election, freeing up the
governance group as well. This can be safely merged at any time,
since it alone won't make any changes to storyboard.openstack.org
(follow up action will be required on the part of an SB admin to
mark the projects inactive and remove their associated group).
[*] https://meetings.opendev.org/meetings/tc/2022/tc.2022-11-16-16.00.html
Change-Id: I34d41f495daa06d438b5f4f8329270fe03731bbb
During PTG it was decided that we need to provide coordination service
as part as OpenStack-Ansible deployment and decided to stop on Zookeeper
as most feature-complete solution. With that we looked for alternative
role that's present under opendev umbrella, but according to
our experience [1] of contribution to that repo it feels tought
to try to re-use it as it's missing some aspects that we feel essential
to have. Based on that we decided to re-write the role from scratch
and maintain it additionally to already existing one.
[1] https://review.opendev.org/q/project:+windmill/ansible-role-zookeeper+AND+owner:noonedeadpunk
Needed-By: https://review.opendev.org/c/openstack/governance/+/863161
Change-Id: I83d53d801f7f0e27769fda7e1a606d90726f98b2
The Charms team would like to enabled passive voting on patches
for backport candidates. This means that backport candidate votes
will not block a patch from merging, but will allow the team to
better track patches that should be backported.
Change-Id: I00e701c7763e91e54f4a7b40442b213e09c5c644
Add a project for defining the zuul jobs for testing charms.
Change-Id: I69a9c9f388371a7a8ad1c7fe5cfc8f6c444d4f45
Required-By: I07ace283a8255f106c141d7bea06618f802e3b51
In order to implement post-check pipeline for dealing with secrets in
the check pipeline it is required to add additional flag to gerrit that
will be set as a prerequisite to start jobs.
Change-Id: I3f0d7fe7e0014c28465aaab060e74e39a527b745
Add new charm that enables Keystone to support OpenID Connect via
Federation.
Change-Id: Ic758858db00a72a136e21c18f452df07f4ea74c2
Required-By: I1b7495f0a5010f9768845882a6e072b5be3f18b9
The STS-Silicom app is intended to be used to configure
PTP/SyncE configurations on certain NICs from the Silicom
vendor.
Story: 2010213
Task: 46215
Signed-off-by: Steven Webster <steven.webster@windriver.com>
Change-Id: Ie6bf611af6f6e61aefd54dbfeed61896c98b437b
Currently the value persists only if it's the max or min, and only
when there are no code changes or if it's a trivial rebase.
The behavior we'd like is that the assigned priority should persist
across the series of patch sets, even if there are code changes,
because this label indicates the relative importance of getting eyes
on the review, and is not directly involved in the code being approved.
A -1 Review-Priority ("Branch Freeze"), in addition to being sticky,
will continue to block submission of the patch.
Change-Id: Iee323ab80f9a58bf49827c23934560edfad57bf3
This project will contain whitebox neutron related tempest tests useful
for the Tripleo based deployments, which don't fit well into official
neutron-tempest-plugin repository.
Change-Id: Ie0c7bc4558e4e73910664b6796d5ada7848bf5d2
In order to filter some potentially problematic content from the
x/stackalytics repository's master branch history, grant its
maintainers permission to push --force that rewrite including
changes from other committers and merge commits.
Change-Id: I0b7fc39fb422f89a04ec926607619c3418016787
Setup and import OpenStack K8S Charms for deployment of
OpenStack with the control plane hosted in Kubernetes.
Change-Id: I6876645221488892b826929810a16a53b846902c
Required-By: I5bfe97d30661dbf0908c16f633decab40cb5edc2
The OpenInfra Foundation community managers are collaborating on a
document about how projects can apply The Four Opens in practical
terms, avoid common pitfalls, and learn hard-won lessons from
free/libre open source projects which have come before.
This project will start empty, and then once created an initial
change will add the relevant boilerplate files.
Change-Id: I98f8a91442f4b1250189af2ec1234bf2814a7a53
This change updates the defintion of Review-priority
to match the new defintion in our contrib docs.
Change-Id: I2b172439e959753b6a62483703bfa8bd93175187