On Tue, 13 Dec 2016 13:45:17 +0100 Mikolaj Izdebski <mizdebsk@xxxxxxxxxx> wrote: > Hello, > > So far we've been using staging Koschei for two different things: > pre-production deployment testing and to aid development by testing > new upstream features and bugfixes (by deploying snapshots). > > After recent introduction of replication to PostgreSQL databases, we > can no longer run some of database migrations without sysadmin-main > assistance. Moreover, staning-sync playbook is broken as it worked by > dropping and re-creating koschei database. (Note that Koschei *must* > be synced after Koji sync, or it will be broken.) I don't think this is true. I think we can get it working with replication. ;) Or at least it's worth trying some more... > I can see two alternative solutions to this problem: > > Option 1: Switch to "dev-stg-prod" model that some other apps are > using. By that I mean creating a separate development environment in > cloud, with separate database (and possibly, even separate Koji). > Staging would be used only for pre-production deployment testing. Dev > instance could be created on-demand, only when actually needed, and > terminated afterwards. > > Option 2: Use separate db for Koschei staging (possibly on one of > existing Koschei hosts) without replication enabled. > > What should be the preferred course of action? Option 3: Try and get things working with replication. ;) I just replied to your ticket about this: https://pagure.io/fedora-infrastructure/issue/5584#comment-46177 can you try that and let us know if it works? Ideally I would like to get some standard manual playbooks to do these things on the replicated db's. kevin
Attachment:
pgpweOBux_zZZ.pgp
Description: OpenPGP digital signature
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
