On Thu, Mar 24, 2016 at 07:32:42PM +0100, Pierre-Yves Chibon wrote:
On Thu, Mar 24, 2016 at 12:22:04PM -0600, Luke Macken wrote:
> Hi all,
>
> I'd like to push out a production bodhi upgrade, along with some ansible
> changes that will change the permissions of how the masher is run.
>
> The latest bodhi code contains a number of fairly important bug fixes,
> and a couple of minor enhancements:
>
>
https://github.com/fedora-infra/bodhi/compare/2.1.7...develop
>
> The backend masher changes that are in ansible will hopefully provide a
> huge speedup in terms of how long it takes to mash the updates
> repositories. The changes for this involve running the fedmsg-hub as the
> apache user, and changing the ownership of /mnt/koji/mash/{atomic,updates}
accordingly.
>
>
https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=9460...
>
https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=9889...
>
https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=afbf...
>
https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=5b25...
>
> I tested the bodhi & db upgrades in staging, and performed limited
> testing of the masher due to various constraints.
How easy would it be to revert if needed? And will you be available tomorrow and
this week-end if something goes south? (I seem to remember tomorrow is a day
off).
Reverting will be fairly easy, and yes I will be available tomorrow and
this weekend.
I'll have a production db snapshot ready just in-case the alembic
migration fails. I've tested it in stg with the prod snapshots many
times already.
If the masher aspect fails, it'll be simple to re-chown things back to
the way they were and revert the ansible changes.
luke