Inspur is working on a log collection/management module for OpenStack.
It needs to be released under an open source license and fleshed out
before it can be officially proposed as an offical OpenStack project.
Create a inspur/venus-specs repository and use the same ACL with Venus
project(c187f81028) to record the
specifications of the venus preliminary changes.
Change-Id: I9129f2d71cfa211d4d65b5776d3afd02742825e1
Inspur is working on a log collection/management module for OpenStack.
It needs to be released under an open source license and fleshed out
before it can be officially proposed as an offical OpenStack project.
Create a inspur/python-venusclient repository and use the same ACL
with Venus project(c187f81028) to do
all that preliminary work.
Change-Id: I76b4fe9212c11891b974ddf1b8b6972971408d38
pytest-dev/pytest-testinfra is the new name/location for testinfra
project. We will do the swap in follow-up change.
Change-Id: I8f34ec79160edf3338ee5ca3e814cfb6019f74d3
The publish-openstack-artifacts job is a parent to a number of
release jobs, including release-openstack-python. In order to build
wheels with new enough metadata to support alternative long
description content types, run these jobs on the ubuntu-focal
nodeset rather than the OpenDev's current default of ubuntu-bionic.
Change-Id: I3399422251d25680688f4982e9a731b9d6485894
Inspur is working on a log collection/management module for OpenStack.
It needs to be released under an open source license and fleshed out
before it can be officially proposed as an offical OpenStack project.
Create a insput/venus repository to do all that preliminary work.
Change-Id: I1cd543371002125fa2b968b0f96325bfcaf5e382
This is the repository for Zuul configuration for 3rd party CI
testing, which will live in a tenant added with the follow-on
Iaf8a4dac561440cc3337b00a738979db60b014ce.
Change-Id: I59650915fa6b6ae3bbe56a38ecf467baf97016b0
ansible-lint is incompatible with Ansible 2.7 which is now causing
failures. Update to current Zuul versions.
Change-Id: I65878a896281ad67d512f0bd9219aa2058e4953a
The previously observed problem (looks like rogue server instances
again) still appears to persist there.
This reverts commit 492e9eeba1.
Change-Id: I8c70268af93f4fe32a730834b405942602417a82
This is a zuul-encrypted export of the signing subkey for the
Wallaby release cycle: 0x5d2d1e4fb8d38e6af76c50d53d4fec30cf5ce3da
Change-Id: I91b897956a3aa413c1a9b2ddd06d6a582665584e
After the project was moved to x/ namespace this was not done, so
finish the move.
Change-Id: Iabdd3a02e171d33285378260cf7a9c85e6724d56
Related-Bug: #1899975
This converts RAX to use the internal address for mirror access
Depends-On: https://review.opendev.org/759971
Change-Id: Ieb856cadcdeb9f6e099b1ce2711cc0d5e1e61f5a
We're seeing a high incidence of job nodes return RESULT_UNREACHABLE
mid-build, enough to cause frequent RETRY_LIMIT results for changes.
Temporarily cease running jobs there until we/they can work out
whatever connectivity or rogue instance issues are causing this.
Change-Id: I4afd92ee64911f0611733ed9c92ec0a4bada54f5
The manila contributor team has grown through mentoring
new core reviewers. We typically spend one or more
development cycles with a prospective core by asking them
to pick up a cross-project liaison role, sharing domain
knowledge in 1-1 sessions, assigning code reviews and
assessing them and reviewing code together.
By splitting core teams we can allow contributors to gain the
ropes to maintain all of manila eventually by beginning
in these distinct delivery items: SDK/CLI, UI and
Tempest tests.
Change-Id: I4e46b6d982a202f5d8f3f9cf7183e931fe5678bd
The cluster has been upgraded to Bionic. Wore out SSDs have been
replaced. And all nodes are now configured with RAID0 instead of RAID1
to provide additional I/O to nodes.
This reverts commit dd62a5e81e.
Change-Id: I97237aecf2d00ebf8c23f931d7079333d90927fb
We only have the -with-uwsgi variants now for fullstack and functional
There is also neutron-grenade-ovn now in grenade jobs
Change-Id: I8f7c55de5a71a93ea3de2393e39e584bcc5f9927
In order to include the new SNMP Armada App we are adding
these 3 files:
- snmp-armada-app.config: repo definition config
- projects.yaml: include the project to StarlingX environment
- main.yaml: add reference to new application
Story: 2008132
Task: 40857
Change-Id: I0cedc5519d7c56c7b050664cd960650e6756b40d
Signed-off-by: Nicolas Alvarez <nicolas.alvarez@windriver.com>
With victoria branched, use it for stable release and move ussuri to
previous stable release.
This is already prepared to upcoming changes in victoria:
* switch to victoria neutron-tempest-plugin template
https://review.opendev.org/#/c/756585/
* not listing *master* jobs being dropped in
https://review.opendev.org/#/c/756695/
Change-Id: I861169977053d5c73b8edc41dae78e5acc9c339d
After the rpm-packaging project was migrated to a SIG [1][2], we need
to create a release group in Gerrit to take care of new releases.
[1] - https://review.opendev.org/752661
[2] - https://review.opendev.org/752659
Change-Id: Ifb8860a96e71ccdf5baeefdddea7a21fe341ddf8
This job fails occasionally when we process several release patches at
the same time due to the shared AFS space. This adds a semaphore to
serialize these operations to avoid conflicts since this is a fairly
quick job.
Change-Id: I049ed49b1fe6a4359e4931b69cb0d29be751cdd5
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
zhangbailin