On Sat, 12 Oct 2013 16:52:40 -0500
Ian Weller <ian@xxxxxxxxxxxxx> wrote:
> Here is my plan for upgrading fedmsg/datanommer/datagrepper. I'm not
> sure it'll be able to get done before freeze on Tuesday at this
> point... but I'd like to try to. I need somebody else to tell me if
> this is crazy.
You're crazy! :)
just kidding.
> Everything is working as expected in staging. Production has two
> servers, which adds a little bit more difficulty.
>
> stage 0: preliminary things
> - need a sysadmin-db to create a datagrepper database
I think toshio has this set for you now.
> - need to know domain/port for a memcached server
Either memcached03 or memcached04.
> - need shared storage on datagrepper{01,02} in
> /var/www/datagrepper_output (only datagrepper01 will be writing to
> it, but both will need to serve it via httpd)
I've setup a shared gluster volume for this.
> stage 1: upgrade fedmsg and datanommer on busgateway01
> - yum update fedmsg python-datanommer-{models,consumer}
> - run the two alembic upgrades (which need to be run in reverse order)
> - restart all the fedmsg services
> - verify everything is working:
> - fedmsg irc is spitting out messages
> - datanommer database is receiving new messages (verify with
> datanommer-latest)
Sounds good.
> stage 2: upgrade datagrepper on datagrepper{01,02}
> - add datagrepper::runner to datagrepper01 manifest
> - merge datagrepper from modules-staging into modules
> - yum update fedmsg python-datanommer-models datagrepper
> - create tables in datagrepper database
> - run-puppet nowait
ok.
> stage 3: upgrade fedmsg on the rest of production
> - a sysadmin-main (presumably) will need to do this
I think we are already updated from the mass updates last week, but if
not we can do this.
kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
