On Wed, 29 Jul 2015 07:58:57 -0600 Stephen John Smoogen <smooge@xxxxxxxxx> wrote: > On 29 July 2015 at 07:54, Pierre-Yves Chibon <pingou@xxxxxxxxxxxx> > wrote: > > On Wed, Jul 29, 2015 at 07:31:15AM -0600, Stephen John Smoogen > > wrote: > >> In doing something like this we would need to know what the impact > >> is. What parts of production of an Alpha would be down during the > >> upgrade? I think there things releng has in pagure but I don't > >> know if those would make any release parts impossible if it was > >> down for 2-3 hours. > > > > That is also something I don't know, git access will remain > > available (via ssh always, via http most of the time (except when I > > restart apache)). The update only influences the web-UI part, not > > gitolite in anyway. The dependency here is two things: 1) buildrawhide and buildbranched scripts are pulled from there now each day when their cron job runs. If things are down, they would fail. However, this is just a few minutes around the time the cron jobs run, so as long as those are avoided that should be fine. 2) releng uses pagure.io now for a bunch of things. If we needed a change to build fedora 23 and pagure was down it would affect things, but that would need to be a lengthy downtime (like days/weeks). I can't imagine an upgrade causing that, especially since we have backups and could just restore from them in a matter of hours. Anyhow, I am +1 to this. We should be able to backout if it causes a big problem (change db back and downgrade rpm). kevin
Attachment:
pgpq4fwo3gG54.pgp
Description: OpenPGP digital signature
_______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
