Migrate to ElasticSearch and Heroku

Metro-Records / la-metro-councilmatic

:metro: An instance of councilmatic for LA Metro

MIT License

6 stars 2 forks source link

Migrate to ElasticSearch and Heroku #911

Closed hancush closed 8 months ago

hancush commented 1 year ago

We have successfully transitioned https://chicago.councilmatic.org/ away from Solr and AWS, to our contemporary Heroku stack. We've outlined the benefits of Heroku here (https://datamade.us/blog/why-were-switching-to-heroku/) and have found ElasticSearch to be much more ergonomic than Solr. DataMade will undertake this initiative on our own time, with an ETA for a working draft by the end of January 2023.

hancush commented 1 year ago

HCG to check whether all board reports are being indexed

neilarellano commented 1 year ago

Hi team! I wanted to check if the heroku staging site is supposed to be fully functional. Please advise.

hancush commented 1 year ago

@neilarellano So sorry for the delay! It does not look like the deployed search index contains all documents. I'll look into this in March.

hancush commented 1 year ago

Metro is going to monitor during agenda postings in September and will reach out to DataMade if they would like further guidance on testing.

hancush commented 11 months ago

@antidipyramid to draft list of next steps for cutover!!

hancush commented 10 months ago

We'll get everything locked and loaded for launch. Metro with coordinate DNS change with ITS for Dec. 4.

neilarellano commented 10 months ago

Hi @hancush! Do we have details on what we need to provide our ITS team for the cutover?

Also, we have a Measure M Independent Taxpayer Oversight Committee Meeting on December 6th. Maybe we can move the cutover for after that meeting.

@camachoo What do you think?

hancush commented 10 months ago

@antidipyramid Can you share documentation on managing custom domains on Heroku, please?

antidipyramid commented 10 months ago

@hancush Sure, I can link to it here and also send it over in an email.

neilarellano commented 10 months ago

Hi @antidipyramid ,

Are you able to send it over via email please? Please let us know exactly the DNS records we need to change and add for the migration so that we can forward it to our ITS team.

Thanks!

antidipyramid commented 10 months ago

A checklist to track progress during the transition:

[x] Provision a Councilmatic production instance on Heroku
[x] Provision a new production Dashboard instance on AWS
[x] Bring the heroku branches of both the Councilmatic and Dashboard Github repos up to date
[x] Find a suitable time and date (preferably on off-peak hours) to update the DNS (Dec. 6)
[x] Deploy production versions of the Councilmatic and Dashboard apps
[x] Update the app deployment pipelines from Github
[x] Create a full backup of the current servers and databases
[x] Update the DNS entry
[x] Bring old servers down (after trial period of one week)

antidipyramid commented 9 months ago

For everyone's reference, here are live links to the new instances:

@shrayshray @camachoo @neilarellano

antidipyramid commented 9 months ago

@hancush Looks like everything is in place for the Dec. 7 cutover. We've completed all of our pre-DNS update to-do's.

antidipyramid commented 9 months ago

Dec 8 update: Site is working as expected. After one week (Dec. 14), we'll bring the old servers down.

antidipyramid commented 9 months ago

Dec 15 update: old AWS servers have been stopped. The switch to Heroku is complete!