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
Similar to the recent change
Ie00c42857e7a541aa1ccb8fe480756c1e7a38dc4, the patched version of
vhd-util in the openstack-ci PPA produces Xen (rackspace) acceptable
.vhd images from diskimage-builder. This is another tool that isn't
really captured by our gitops model (the need for this is all covered
in [1] as to why this is a big PITA; tl;dr when porting this into qemu
things that seem like they should work don't in Rackspace, and without
being able to see the operator side of the cloud to understand what
it's actually doing it's just an exercise in frustration).
Similar to the openafs situation, the code is available from the PPA
but the history has been kept in personal repos and uploaded manually.
Having it go through gerrit is good for transparency and longer term
maintenance.
We'll have to fiddle the upload jobs, etc. so it works for both
openafs and this; so this is just the first step to get things
started.
[1] https://docs.openstack.org/diskimage-builder/latest/developer/vhd_creation.html
Change-Id: I92b9c65ade7fba2851fd798bad4f658da400dec4
This is a project to hold things related to building the OpenAFS
packages used by OpenDev infra. These packages are pushed to a PPA
which is consumed by our production machines.
We keep a separate PPA for these packages as we have had occasions in
the past where we either needed more recent versions of OpenAFS for
various platform support, or had to apply patches with some urgency to
keep things going. Being able to quickly produce new packages has
been very helpful.
Previously these have been created by hand, where somebody uploads the
debian package bits to the PPA manually and a .deb is produced. Of
course the source of those packages is available, but it's not very
git-ops-y or collaborative.
This started in I07780595331da29af9f72185cbb3499210e89c19 where
fungi's concerns that I argued against were completely correct.
Trying to build across xenial -> jammy with one debian/* directory is
not going to work, and checking in multiple trees is very unwieldy in
that repo.
This proposes a separate repo where we can keep branches for each
distro's build. We can then use the existing infrastructure we've
built to build the source packages and push to the PPA for building.
I've chosen the name with "infra-" in front to make it clear these
aren't supposed to be general purpose packages in any way, but are for
opendev infra use. I've put this in the openstack tenant because the
build bits are still in openstack/openstack-zuul-jobs for historical
reasons -- this is where we do similar builds for RPM (which uses AFS
publishing jobs, and has openstack embedded in paths, etc.) and it
makes sense to keep them together. We can consider moving everything
under the opendev tenant in the future.
Change-Id: Ie00c42857e7a541aa1ccb8fe480756c1e7a38dc4
The opendev/elastic-recheck project has ongoing development
occurring on an "rdo" feature branch. Grant the release team for it
permission to merge that branch into master, as well as the ability
to delete the feature branch.
Change-Id: I406cb6dd721b48f893cd8a7ab9f36dcadec9a238
This charm implements a 3PAR backend for cinder, acting as
a subordinate charm.
Change-Id: I14c6bd857a09cab07546def009c654738b085c46
Required-By: I16075836abd321d53089d123a711c586b7597a5c