Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Re-deploy Redis cache VM in us-west-2 #119

Closed
Mr0grog opened this issue Oct 17, 2018 · 4 comments
Closed

Re-deploy Redis cache VM in us-west-2 #119

Mr0grog opened this issue Oct 17, 2018 · 4 comments
Assignees
@Mr0grog
Labels
deployment

Comments

@Mr0grog
Copy link
Member

Mr0grog commented Oct 17, 2018

Our Redis cache instance is currently in us-east-1 (so it was near our API services when they were in Heroku). Since we’ve moved everything directly onto AWS and also moved it to us-west-2, I should move the cache there, too, so it adds minimal overhead.
@Mr0grog Mr0grog self-assigned this Oct 17, 2018
@Mr0grog Mr0grog mentioned this issue Oct 17, 2018
Open
Mr0grog added a commit to edgi-govdata-archiving/web-monitoring-ops that referenced this issue Nov 19, 2018
@Mr0grog
Update Redis cache server edgi-govdata-archiving/web-monitoring#119
77a5dc3 
Our previous cache was in us-east-1, which is very far away from where our services are now (they used to be on Heroku, which was in us-east-1). I've set up a new Redis instance in us-west-2 and incremented the `api` and `import-worker` configs here so they pick up the new value (it's in the secrets file, which you can find in Keybase).
Mr0grog added a commit to edgi-govdata-archiving/web-monitoring-ops that referenced this issue Nov 19, 2018
@Mr0grog
Add redis-cache and other non-kube services docs
0c2c999 
We've talked before about how our non-kube services need ops documentation here, too, so this is my first cut at putting that info in. It's surely far from perfect, but I wanted to make sure we have a good redis config documented since I just re-built it for edgi-govdata-archiving/web-monitoring#119 (see also 77a5dc3). This also means other people can critique and improve it :)
@Mr0grog Mr0grog mentioned this issue Nov 19, 2018
Merged
@Mr0grog
Copy link
Member Author

Mr0grog commented Nov 19, 2018

This is now up. I’m going to take down the old one after I get home, so I can watch it and troubleshoot if anything explodes. If it stays happy for an hour, I’ll mark this as done 💃

@Mr0grog
Copy link
Member Author

Mr0grog commented Nov 20, 2018

Old cache is now stopped and things seem good! Will terminate on the morrow.

@lightandluck
Copy link
Member

Nice! 🚀

@Mr0grog
Copy link
Member Author

Mr0grog commented Nov 20, 2018

…and the old one is now fully dead dead dead. Closing this :)

@Mr0grog Mr0grog closed this as completed Nov 20, 2018
@Mr0grog Mr0grog removed the ready label Nov 20, 2018
Mr0grog added a commit to edgi-govdata-archiving/web-monitoring-ops that referenced this issue Dec 3, 2018
@Mr0grog
Add redis-cache and other non-kube services docs (#9)
5c107d1 
We've talked before about how our non-kube services need ops documentation here, too, so this is my first cut at putting that info in. It's surely far from perfect, but I wanted to make sure we have a good redis config documented since I just re-built it for edgi-govdata-archiving/web-monitoring#119 (see also 77a5dc3). This also means other people can critique and improve it :)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Mr0grog Mr0grog

Labels
deployment
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Mr0grog @lightandluck