This commit adds back the job filter on the old side subunit stream
from grenade runs. The subunit stream will only end up under logs/old
if it's a grenade run. So to be more efficient lets filter looking
for a subunit stream there only to grenade jobs.
Change-Id: I5a6c9b17f923526745507a131658f581a9d94e0a
This commit removes the retry-get parameters from the subunit file
collection in the logstash gearman client. These were cargo-culted
from elsewhere in the yaml file and doesn't add anything useful in
this case. The param is only there to workaround jenkins limitations
with the console log uploading.
Change-Id: Ic751d5e295e605b20386ad9cde6500bae44f34d8
This commit will enable collection of subunit results from all subunit
emitting jobs in the gate and periodic pipelines. Now that we prune
the database to only 6 months of history we should have plenty of
headroom for the extra data generated by non-tempest-dsvm jobs.
(hopefully)
Depends-On: I58a640f804313e1e4b80680f0e39b86d76cb29da
Change-Id: If5691af792409f02352f25b1498dd78294a7cd74
We started collecting these things... and never stopped.
exmaple:
find /var/lib/puppet/reports/zm08.openstack.org/ -mtime +5 | wc -l
690
Change-Id: I72dc2bb32c76ae8f2ebd22801e8d3e9924c25d4d
Some infracloud machines do not respond to ssh. Comment them out here
so they don't fill up our logs with errors that aren't actionable.
Change-Id: If56e773e3fe8beb0aad42e079eb8cb8492cde652
We cannot use default guest/guest as it has been disabled
on our rabbit. So we need to generate a pass in hiera for that,
and pass it properly to the manifest.
Change-Id: I407119383b232f07888dc9821771f1ece383a431
Depends-On: I9582d68ca93f2f7b5742523e273ebf6b5a9c0c13
Add separate playbook for infacloud nodes to ensure they run in the
correct order - baremetal -> controller -> compute.
Baremetal is intentionally left out, it is not ready yet.
All 'disabled' flags on infracloud hosts are turned off. This patch
landing turns on management of the infracloud.
Co-Authored-By: Yolanda Robla <info@ysoft.biz>
Co-Authored-By: Spencer Krum <nibz@spencerkrum.com>
Change-Id: Ieeda072d45f7454d6412295c2c6a0cf7ce61d952
We only need one infracloud right now. Technically the controller
doesn't need to be in 'infracloud' because its secrets are duplicated.
This aligns the groups at any rate.
Change-Id: Ibc056505a4ef397c2adeae6a3b4afb21db9b4a02
k5start prints:
"Kerberos initialization for service/reprepro@OPENSTACK.ORG"
This then gets redirected into the list of files to remove on the next
run - which is an error, since that's not a filename. Put the
redirection inside of a bash command so that only the data gets
redirected.
Change-Id: Icae10763b4bce78c7b674715826547c228980dd6
We can't colocation debian and ubuntu - so allow for each having their
own pool independent pool structure.
Change-Id: I9fe0fa9769a5c0f6a852844b2db0dfb620e91375
The packages in restricted and multiverse are either non-free or
unsupported. While they're usually useful for desktop, they aren't
something that OpenStack should grow a dependency on.
Also remove non-free and contrib from debian. We don't do anything with
debian yet - but if we did, I'm pretty sure we would not want these.
Note: The existing restricted and multiverse dirs should be purged,
although it's not urgent to do so. 'reprepro --delete clearvanished'
Change-Id: I1d98ab1dea52598d01e3ce3d9a24306280a190fe
Now that the db files are in AFS, we need k5start because we need to be
able to write lockfiles for them.
Change-Id: I5c9554ca505ed56e84b601e40476527ef4af98fb
We need the gpg signing keys for the upstream repos in root's keyring.
Fuel uses golja-gnupg for importing keys - so seems like a good thing
for us to use too.
Change-Id: I343be9397ba53f494485d1ff0f1e1e4c96c0273f
In the current setup, the reprepro db and lists dirs are being written
into /root. Move them into AFS so that we store all the data in the same
place.
Also, update the script to point to the confdir for reprepro commands.
Note: This will require a manual move of the current db and lists dirs
from /root to /afs/.openstack.org/mirror/apt before this is run.
Change-Id: I2638621e6af98296704e680227fae174d8a0e541
Options are space delimited, not = delimeted. Also, AFS reports space
differently, so skip the space available check.
Change-Id: I097bc43481ecfb64d0c95f08c82bd3ceb5bd6be9
Our mirror vhost config uses symlinks in /var/www to control what is
published. Add an entry for the apt repo.
Change-Id: I301c61282e53d4cf596efe45b27dadce797f947e
Since these are baremetal hosts, they need to come from a static
inventory not the openstack inventory. Fortunately, thats pretty easy.
Also setting infracloud groups to be children of disabled to keep them
disabled until we are ready.
Change-Id: I87ed4008ed9c4867f79bbb5fbb6be53707b42625
The reprepro class in this is in-tree rather than in its own module
purely for ease of getting started. It's also highly hard-coded rather
than flexible.
This change will need a mirror.apt volume and service/reprepro principal
and keytab to be created before it lands.
Allow for pool trimming after a 2 hour delay. Each devstack run of
apt-get update should be able to be assumed to be valid for the length
of the devstack. For that reason, only delete files that are
unreferenced during the subsequent mirror run, ensuring at least a 2
hour delay between becoming unreferenced and going away.
Local testing indicates that a trusty mirror is 86G.
Change-Id: I84f6a0391f80e6bf567c4bfc18a41bd270fe8c01
This reverts commit 01f30d523b8b54336b59f097c00b521dc67eee95.
It also changes it to make the vos release verbose, and to use
set -e rather than explicit error checking.
Change-Id: Iffcf03899792b17b4873742b513ebada7f2efd8d
