Now I've built the whole thing and it works, I feel like this
is a cleaner design: we use a lot more role variables in the
messaging config files, set defaults for them that are
appropriate for non-infra use, and set the correct values for
the infra servers in the group vars. Let's just hope I got it
all right...
Signed-off-by: Adam Williamson <awilliam@redhat.com>
There are several variables we set to the same value for openQA
prod and staging servers. Instead of duplicating these between
the openqa and openqa_stg groups, let's invent an openqa_common
and put them in there, and add both servers to it.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
env_suffix isn't actually set to .stg on openQA staging because
it's not a normal staging host. Let's not set it in case it
breaks other plays, but use a custom var instead.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This is a big change to support fedora-messaging based consumers
instead of fedmsg ones in the openqa/dispatcher role. This needs
the fedora-messaging branch of fedora_openqa, until that is
merged to stable. For now this is all conditionalized so prod
will continue to use fedmsg. This also improves some variable
usage and documentation in the fedmsg path too.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This is a slightly inexact science, but I think we have solid
free space on both servers and it does seem like assets are
getting thrown away pretty aggressively, so let's see how this
does.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Since this message format spec is public now:
https://pagure.io/fedora-ci/messages
Let's have production send out messages in that format as well
as staging (well, more or less that format...actually a sort of
'pre-production' version of an addition to that format).
Signed-off-by: Adam Williamson <awilliam@redhat.com>
The special configuration for check-compose mails for two-week
Atomic nightly composes was broken due to fedfind changes. We
need to tweak this template a bit as part of fixing it up.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Staging is running out of space...let's kick it back down to
300, and also create a separate setting for update group asset
size. We test lots of updates, and for each update we only need
to upload one disk image, so we really don't need 300GB of
asset space for update job groups, that just means we'll keep
like 300 update disk images lying around. If PPC starts getting
incompletions again I'll have to, uh, do something? Yeahhh.
Something.
Unattended wiki interaction with the new openidc auth method
requires a special token file which @puiterwijk created and
put in the private store for us. Have the appropriate roles
install it.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
relvalconsumer is the fedmsg consumer bot that creates Wikitcms
release validation test events. Up till now it's just been
running on one of my personal boxes; we should really move it
to infra. Run it on the openQA servers for now, as there's
nowhere more obviously correct, and I have root access there to
fix problems.
We add new inventory groups because it's *really important*
that there be exactly one (no more, no less) production consumer
at any given time. I don't want to just use the 'openqa' group
for this because it's vaguely possible it could contain more
than one host in future, and we really wouldn't want that to
result in there being two production relvalconsumers running.
I'm still kinda trying to make the openqa roles usable outside
of infra, so now I have a minute, let's do this: it makes the
static UID/GID for geekotest optional and configurable, instead
of hard coding it. For infra we set the value to 601, as we
are already using, in the openqa and openqa-stg group config.
bastion.phx2 does not relay, only does fp.o local delivery, so
since we're sending the compose check emails via bastion, we
have to send to fp.o addresses.
Cloud folks want this email sent only if there's some kind of
problem (missing image or openQA failure), I've just added an
option to check-compose to allow for that, enable it here.
This is for https://phab.qadevel.cloud.fedoraproject.org/T690 ,
it goes along with some changes to check-compose itself to
allow reports for different milestones to have different config
settings, which (if I didn't mess anything up) should result in
those reports going to Mike McGrath and the cloud@ list, as
requested, while Rawhide and Branched reports continue to go to
test@ and devel@.
I just killed the old BOS openqa deployment, which sends out
those 'compose check' emails, so I'm gonna go ahead and have
this new openqa deployment start sending out those emails a
little earlier than planned. This should result in both prod
and staging openqa running a compose check each day, but only
prod should actually send out an email report.
This adds openQA server, worker and dispatcher roles, and
applies them to the appropriate hosts. A few secret vars are
required. See trac #4958 for discussion.
