Please grant db access to 'pivots_rw' to access the 'pivots' db from two servers: stagingvm (r.d.o and b.d.o) and scratchvm. The 'pivots' db should be hosted on db3-vip.
Thanks.
Below is from IRC:
[4:39pm] Amazon: probably best to just grant r.d.o and b.d.o access to the pivots database server
[4:40pm] DamZ: I confirmed that stagingvm doesn't have access to the production pivot db
[4:40pm] Amazon: danithaca: go ahead and file an infrastructure database issue requesting that db access be granted for that particular pivots user
Comments
Comment #1
basic commentedI've added a user for stagingvm, but not for scratchvm. Why does scratchvm need access for this?
beta.d.o is on the production infrastructure so the existing db_url configs work fine there for pivots. redesign.d.o is on stagingvm and should now have access to pivots as well.
Let me know if you still need it on scratchvm.
-Rudy
Comment #2
danithaca commentedThanks Rudy. On scratchvm, a Java/Python script is running to update the pivots recommendation in the database. Since this is quite time-consuming, we have the script running on scratchvm rather than on the production server. Thanks.
Comment #3
basic commentedGot it. I've added an acl on scratchvm as well
Comment #4
danithaca commentedit worked. thanks!