Recently the hosted database that translate.openstack.org uses was
upgraded to MySQL 5.7. It turns out there was a breaking
security-related change to MySQL that means you require PROCESS
privileges to dump the DB. I guess the migration didn't do this, and
via the RAX hosting UI there's no easy way to add this (there's no
root user available by default; perhaps this is a corner case of the
upgrade process).
Rather than trying to figure out the backend, to work around this use
--no-tablespaces to the dump command. We just need a dump of the
zanata tables as backup, so this is fine.
Change-Id: Idaa35249fe15867103fa7b70dbdc7d135c5e1396
As noted inline, a recent mysql client update has broken the
"--all-databases" flag, at least for the client version and very old
server version we use.
Emperically, dumping individual databases still works with this
client. Switch this to stream the db directly into borg.
Ignore the old backups and remove the bup backup while we are here,
since this is all borg now.
Change-Id: I5fe762a003ce2c2ba4830367be87598f67f7e763
This patch describes the major upgrade of the live translation
platform to version 4. We use the same procedure and version
like in translate-dev, manual steps are described here:
https://etherpad.openstack.org/p/zanata_upgrade_4xx
Change-Id: Ic53e0bbf8f82d6d811f1e4d4bea2b85a868de9d2
Migrate backups to new backup01.ord.rax.ci.openstack.org
We decided to start fresh backups on the new server, so this is ready
to go. I have performed an initial backup on each server so it has
accepted the host key of the new server and been tested (I also fixed
up review-dev.o.o, which was rebuilt but keys not updated ... todo:
add this to puppet, but since it changes so infrequently not high
priority).
Change-Id: I0872f9fcf4a334d32f632b3cb04801deefab4fd1
This is part of the Zanata upgrade process. We will be deploying new
Zanata to translate01.openstack.org so add node def in site.pp to
support that. This keeps the old translate.o.o def too so that it is
left alone untouched.
Note that this also adds code to pass through wildlfy's install URL and
fixes the specification of the wildfly version number. I think the
version number var being wrong was not a problem for us because the
wildfly installation only runs if there is no installation dir in place.
Change-Id: I4b6ababcc34e2464cf6a824e92a1c146d553dcaf
This was not done when we spun the server up the first time around. We
noticed as part of the work for doing an upgrade. Go ahead and get this
in place before any upgrading so that we have backups handy if
necessary.
Change-Id: I307f555fb607b2d592177f11923929e007858ab8
Now that the checksum has been updated to SHA-1, we can re-add it
back to this repository, which also locks translate.openstack.org
to version 3.7.3 until we are ready to upgrade.
This partially reverts commit 14ba55836a.
Change-Id: I310b3413ee2214b8da50e8dd5339e331cebd749d
Depends-On: Ib4b59866bdfe449918be35a443b898e58dd7e432
Remove the Zanata URL and checksum from translate.openstack.org. Due to
the latest change in puppet-zanata, this will upgrade it to version
3.7.3. Remove it entirely so that the checksum type can be updated in
puppet-zanata, and then it will be added back here to make sure
translate doesn't upgrade without us watching.
Change-Id: Ic98b9a76f2d2b7a9c3ca42f704a62336e8e0050c
Depends-On: If794ec02cbecfde370304c41bad8cd011800fb2e
Manifest for translate.openstack.org and related site.pp change.
This is very similar to the translate_dev.pp we have already.
I've added some application level (wildfly and zanata) versioning
options so we can upgrade the versions on this production server
independent of changes we make in the puppet-zanata module, which
will deploy to the dev server.
Add support for using a non-snakeoil SSL certificate.
Finally, add infra root admins who have Zanata accounts as Zanata
admins.
Change-Id: I224ab532b31d70aabcec5c7092ce7d4ecbfec9f3
Ian Wienand