This adds the ubuntu-bionic-32GB label to vexxhost, which makes it
available in two regions (airship citycloud is the other).
The cpu/ram specs are matched in both clouds.
Change-Id: Iac79fab2478cc383083531886ee6b8a9e7c87187
The pip installed in the venv with "python3 -m venv" on Xenial is 8.X
-- this does not understand python_requires metadata on packages and
can thus pull in requirements that won't actually run inside the
virtualenv.
Avoid this by upgrading pip in the venv before installing.
While this is the immediate need; do the same on the other venv's we
create for general sanity.
Change-Id: I316e9587b6e290cd421b47f506c91dbebe0975c0
This change adds the gerritreview bot messages to the starlingx channel
on any changes submitted to any of the 32 starlingx projects.
Signed-off-by: Thiago Brito <thiago.brito@windriver.com>
Change-Id: I45429d10f17520235beb719c3e3750174f8b8d2b
In order to help drive the ptgbot during the PTG event, give
ttx OP rights on #openinfra-events channel.
Change-Id: I6afb3c1ea67fce8c9f9d58295e3a393d1b35c6ea
This is a combination of 2 commits:
Fix the renaming of ansible-role-refstack-client
In [0] that project was moved from x/ to openinfra/, but the patch
missed that at the same time refstack was also moved, changing the
path for the ACL.[1]
[0] https://review.opendev.org/c/openstack/project-config/+/765787
[1] https://review.opendev.org/c/openstack/project-config/+/808479
Fix use of yaml.load()
The use of this function has been deprecated for a long time[2]. With
PyYAML==6.0 the call is now failing, so replace it with the safe
version.
[2] https://msg.pyyaml.org/load
Signed-off-by: Dr. Jens Harbott <harbott@osism.tech>
Change-Id: I439d1f167b5893a134a5b628ebc00fd6617e0cbd
Going to be adding more hardware resources,
as well as applying some placement and nova-scheduler configuration options.
Change-Id: Ie8b956dd02129e25bc1c9c46c8b9e53040579681
LE recently expired it's root certificate. Unfortunately, the base
Ubuntu distros (up to focal) use a 2019 ca-certificates package that
hasn't accounted for this. Even more unfortunately, deboostrap can't
use the updates repo to get a more recent certificate package when
building the initial chroot.
The end result is that the chroot can't contact the mirrors via https
to actually pull the updated certificates package from them, breaking
the build.
To work around this use http:// for the mirror location.
Change-Id: Ifdb177d2ed75eab9e2acb984a9be785fba517d3e
We are planning to upgrade our Gerrit install to 3.3. Jeepyb shouldn't
trigger 3.2 builds once that is done as those images won't be used. Bump
to 3.3 as a result.
Depends-On: https://review.opendev.org/c/opendev/system-config/+/813072
Change-Id: If69016e7a14b98829ccc52ead3f532c9470ae912
The gerrit image uses the bullseye python 3.9 image now instead of
buster 3.7. Update the depenency in project-config where we trigger
things.
Change-Id: I2b658871ca624024f9aef027fe1039dcf3549a1b
We want the RDO 3rd Party CI to report on Packstack using
CentOS Stream 9 jobs. This commit gives the tripleo-ci group, which
already has permissions on TripleO repos, Verified +1/-1 permissions on
the Packstack repo.
Change-Id: Ic2b3ad13f7bf9b262e3abf59ac63c02f22e5f848
Still adjusting to Zuul as is just very explosive.
Goes from a load of 2 to 30 because codeset ends up being
tested in instances on the same node. This may help.
Change-Id: I0f07fb08e87a16e011952d0b755b9527f5a43a30
It seems that zuul gets a 403 when trying to set up this app
installation which implies the repo on the github side disabled us. This
403 stops zuul's startup process so we remove it.
Change-Id: I97e4f174cd083a6b0bbe1fafaf6664720923ac9e
I think I generally messed these up on the original import as every
stat seems to refer to the same thing. Over time, the layout of
openstacksdk stats has changed meaning this doesn't work at all now.
Use stats that are actually in graphite which should show the overall
health of API requests.
Change-Id: I6bd82b38d80db2b56a399f80132a723564f9bc40
Scaling down once more, memory is doing good, but CPU
seems to get a bit explosive and impacts CI performance.
32 -> 24 at this point reduces risk and load potential by 25%.
Change-Id: Ic712c0ca5242d988204a38407c1dd5751c0ced41
Unfortunately with 40 we still saw OOM kills, Launch Errors as
well as reported long run times due to CPU overcommit.
Change-Id: I40a928fc910d557c9c846918037760ac39b0d74a
Unfortunately 50 instances on the current crashes out nova-compute.
Let's find a happy number, so the cloud is responsive. Setting to 40, but
anticipating that we may have to go even lower for consistency and responsiveness.
Change-Id: Ia726ed400bc881d1a97f0c39a05c481f38c6a0eb
Zuul
James E. Blair
Ian Wienand
Thiago Brito
Thierry Carrez
Dr. Jens Harbott
fungi.admin
Martin Kopec
Sagi Shnaidman
OpenStack Proposal Bot
Yuriy Shyyan
Clark Boylan
Kendall Nelson
Javier Pena
Jens Harbott