Commit Graph

10 Commits

Author SHA1 Message Date
Pavel Raiskup
3b5f56e66b copr: aws x86_64 spawner playbook 2020-04-24 21:34:16 +02:00
Kevin Fenzi
db9e25330b inventory: try removing all the calls to ansible_python_interpreter and rely on the auto detection.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2020-04-24 21:34:15 +02:00
Pavel Raiskup
0050e0bdd4 copr: be: flip to fedora-messaging 2020-04-24 21:34:10 +02:00
Pavel Raiskup
fbbbc627d2 copr: be-dev: update images once more
.. all architectures.
2020-04-24 21:34:08 +02:00
Pavel Raiskup
d77ef6c712 copr: backend: configurable aarch64 builder image 2020-04-24 21:34:08 +02:00
Pavel Raiskup
27d39cbecc copr: be-dev: update OS builder images 2020-04-24 21:34:08 +02:00
Pavel Raiskup
249069afa5 copr: builders: cut the image name definition to group_vars
This will allow us to temporarily affect staging instance only,
and test that the images are actually OK.  We should though put
the timestamp to the image name.
2020-04-24 21:34:08 +02:00
Pavel Raiskup
3cc27430b6 copr: rework letsencrypt
We need two-phase configuration for Let's Encrypt:

1. initialize; the letsencrypt automation, this is happening only
   once per VM (when it is spawned)
2. periodic; using certbot-renew.timer.

Both those phases are now wrapped into copr/certbot role.

Phase 1. needs to be done before the web-server is started (so
include the role on appropriate place in the playbook), so we can
do 'certbot --standalone' (bounds to port 80).
Phase 2. is accomplished using the running web-server, using
'certbot renew --webroot'.

If (and only if) the certificate is renewed, web server needs to
be restarted (and lighttpd needs to have post-processed
certificate format).  So we also need the deploy hook script in
hand (two actually, lighttpd/httpd) so 'certbot renew'
automatically does what we expect it to do.
2019-07-19 11:20:00 +02:00
Pavel Raiskup
a13b244681 copr: backend: flip to /usr/bin/python3 ansible interpreter 2019-06-06 08:58:33 +02:00
Kevin Fenzi
4b31ac5152 ansible: Change all our group names from foo-bar to foo_bar or foo-bar-baz to foo_bar_baz
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>
2019-05-20 17:38:09 +00:00