On 09/12/2018 01:56 AM, Clement Verna wrote: > On Wed, 12 Sep 2018 at 10:45, Michal Konečný <mkonecny@xxxxxxxxxx> wrote: > >> Hi, >> >> here is a patch for ansible for deployment of Anitya 0.13.0. Looks good to me. :) Note that this will still only update staging... When we want to roll this to prod openshift we will need: >>diff --git a/playbooks/openshift-apps/release-monitoring.yml b/playbooks/openshift-apps/release-monitoring.yml index 6b979f6..a0110e4 100644 --- a/playbooks/openshift-apps/release-monitoring.yml +++ b/playbooks/openshift-apps/release-monitoring.yml @@ -1,5 +1,5 @@ - name: make the app be real - hosts: os-masters-stg[0] + hosts: os-masters[0]:os-masters-stg[0] user: root gather_facts: False and then also the db from the existing prod host dumped and loaded (which I guess will mean a bit of downtime for the prod service). > > That's an interesting case Anitya is not in the frozen application list but > Openshift is. Since Anitya will now run on Openshift does that mean that to > deploy a new version it needs a FBR ? Nope. In this case IMHO, anitya is 'content'. We are not changing openshift config, but just adding/changing content, so I don't think it should require any freeze break. As long as the app isn't frozen and we don't need to make any changes to openshift config it should be fine. kevin
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
