migrated notes from infra/hosts
motd changes; excluding CSI infos
removed csi_* vars from group_vars; converted csi_purpose & csi_relationship into notes
fixed merge conflicts
minor changes; var
updating YAMLs & playbooks
udpated YAMLs & playbooks again
updated correctly; buildhw.yml
fixing merge conflicts
dest added in motd.yml
Some of the openqa workers are encrypted and some aren't (this is a bit of a
mess that's partly a result of all the redeployments we did around
https://bugzilla.redhat.com/show_bug.cgi?id=2009585 ). We should only run
the nbde_client role on workers which are encrypted. Hopefully this gets that
right.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This is syntactically wrong, and it's not necessary any more
anyhow because we got someone to disconnect the problematic
network interfaces from the hardware.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
They aren't encrypted, and it causes networking config problems.
We'd like to solve the underlying problem but we don't know how,
this is good enough for now. Also drop the workaround things
again because they don't seem to help.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
nirik did some stuff in the virthost and buildhw groups to try
and deal with a problem where network configuration created
during the initrd phase for the nbde_client role is activated
by NM during the regular system boot phase, which results in
the network configuration not being the one we actually want
and carefully set up. However, he didn't add this stuff to the
openqa-workers group playbook even though that uses the
nbde_client role too, and we sure are having the same problem
on the openQA workers. Adding it now to see if it helps.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
The linux-system-roles.nbde_client does the right things and so one less
thing for us to maintain. It also avoids the problem we have on some
machines now where network interface names are not as the old clevis
role expected, so unlocking didn't work on boot. Hopefully this fixes
all those issues.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
The main goal of these changes is to allow all workers in each
deployment NFS write access to the factory share. This is because
I want to try using os-autoinst's at-job-run-time decompression
of disk images instead of openQA's at-asset-download-time
decompression; it avoids some awkwardness with the asset file
name, and should also actually allow us to drop the decompression
code from openQA I think.
I also rejigged various other things at the same time as they
kinda logically go together. It's mostly cleanups and tweaks to
group variables. I tried to handle more things explicitly with
variables, as it's better for use of these plays outside of
Fedora infra.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We decided that since this wasn't really a staging host, we should stop
calling it 'stg' and putting it in stg group. Since it's used for
testing new openqa and edge features, lab seemed appropriate.
This brings up a openqa-lab01 on qvmhost-x86-01 and a power9 and aarch64
workers. More workers to be added as they are installed. Ther will be at
least one more power9 and 2 more aarch64 boxes.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
In ansible 2.8 the - character isn't supposed to be valid in group names.
While we could override this, might has well just bite the bullet and change it.
So, just switch all group names to use _ instead of -
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
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.
