Prior to 38d138e this condition existed with 'iad2' instead of
'rdu3'. @abompard took it out entirely, but that was wrong, it
makes the external proxies include this block. We need to put the
condition back with the correct data center name.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Added host vars for all the control plane vm's and bootstrap node.
Set latest version for downloading and setting things up.
Setup haproxy in rdu3 prod to load balance the ocp api and internal api.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
Time to retire ODCS. ELN is moved off and that was the last thing using
it. Thanks for all the service ODCS!
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This commit retires pdc from ansible.
The website should get redirected to a wiki page about the retirement.
If for some reason we need to bring things back, the vm's will still
have their disks and xml saved off so we can bring it back.
Would need to revert this, run proxy playbooks and do a little cleanup
on the redirect, then bring the vm's back up.
Hopefully we don't have to.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
With the EOL of Fedora 38 yesterday, we are no longer building any
modules and can retire our module build service.
Note that toddlers needs to be adjusted still, that will happen after
this.
Thanks for all the modules!
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This removes osbs and allmost all it's associated playbooks and files.
It served long and well, but we no longer need it.
flatpaks are building with a koji-flatpak plugin.
base/minimal/toolbox containers are building with kiwi.
We aren't building any other containers right now, and we did they could
be added to kiwi.
This is the end of an era... I look with nostolga on
ansible-ansible-openshift-ansible (a role to setup ansible on a control
host and run it from our ansible).
Good bye osbs!
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
We are hitting a sporadic and anoying 502 error with ostree pulls.
see https://pagure.io/releng/issue/11439
The problem seems to be between haproxy and varnish on kojipkgs01.
We set the httpclose option in haproxy globally, which closes
connections as soon as it thinks they are done.
Setting this option 'httpkeepalive' will keep connections alive
and handle the case of lots of fast connections downloading small
objects much better.
Sadly, we don't have a way to test this in staging, so we would need to
test in prod and roll back if there's problems.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
We added more to the api and machine-config, but those only go to
control nodes, not compute nodes. Just revert this section entirely, it
was a bad idea and we shall never speak of it again. :)
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This fixes ticket 10521.
Basically we want to just open the api. It requires auth to do anything
and other openshift instances have it available, so it shouldn't
hopefully expose us to too much risk. With ocp3 the api was part of the
normal port/web flow, but with ocp4 it's a seperate port.
This also adds new workers to haproxy. I can drop that part if it's
controversal, but it should be fine I would think.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
If we push this to all proxies (as we have), they will fail to start
haproxy because they cannot resolve the internal ocp iad2 hosts. ;(
The ocp clusters should only apply on the iad2 haproxy nodes, not all
proxies. Also fix logic on the staging one to apply in staging instead
of just production.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
Put the api ports that ocp4 needs behind haproxy (with bootstrap node)
and open them to just the ocp4 machines on the proxies.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
Note: there are still some calls here in old fas in openshift, but we
will remove those when we remove old fas (likely as soon as zodbot is
ported over to noggin).
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
