NOTE
If your issue is for security or deals with sensitive info please mark it as private using the checkbox below.
Please create a RDS instance to support the size and scale of Datanommer, including the timescaleDb extension for Postgresql.
End of August 2024
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: aws, low-gain, medium-trouble, ops
I'd be happy to help work on this, if that's okay.
Yeah, perhaps @abompard (who knows the database) and/or @dkirwan could help with the initial setup in aws?
I don't know much about AWS, but I do know a bit about datanommer :-) Feel free to ping me if the docs or the current ansible playbook is not clear enough.
Want to arrange a time that suits you both, can look at getting you access to an instance in AWS to populate. @phsmoura @abompard
@phsmoura Were you able to get the access and info you need for this ticket?
Hey @smilner , sorry I didnt respond.. I probably missed the email with the update in this issue. Yes, just got the access and made the PRs adding the instance in DNS. Next step is to create a playbook to install datanommer there, we are working on it
So, this was never fully finished or used, so we think it will be made obsolete by new work in commops.
We would like to propose just taking the rds instance down and the datanommer vm.
If there's still a need/desire for these things, please let us know!
Go ahead and delete. We'll reopen after we reassess. I know mwinters is doing a lot in this space in a different direction.
ok, thanks. Will leave this ticket open to track dropping those things.
@phsmoura can you do that? at least the datanommer01 aws instance from aws and ansible?
I went through all regions in aws and couldn't find the instance to remove. Also did a PR removing it from ansible. PR: 2939
Log in to comment on this ticket.