#12088 New Communishift Project
Closed: Invalid by zlopez. Opened by rwright.

NOTE

If your issue is for security or deals with sensitive info please
mark it as private using the checkbox below.

Describe what you would like us to do:


Can you please create a new Communishift Project for CommOps to use to host an analytics application we're building? We're creating a wrapper Django app that will use ODIC to login to Fedora IDP and allow users to use https://github.com/explorerhq/django-sql-explorer

We would ask that our container and project space be able to connect to db-datanommer02.iad2.fedoraproject.org on port 5432 and be able to be exposed to the internet via port 443.

When do you need this to be done by? (YYYY/MM/DD)


8/15/2024


@rwright Could you create a new request with correct issue template? See https://docs.fedoraproject.org/en-US/infra/communishift/#_request_new_namespace for more info.

Metadata Update from @zlopez:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

So, I am not sure how we could setup 'be able to connect to db-datanommer02.iad2.fedoraproject.org on port 5432'

communishift is in aws.
db-datanommer02 is internal to our IAD2 datacenter, behind NAT and a RHIT firewall.

Now, it's possible to setup a vpn, but... that really really really makes my security brain unhappy.

I'm not sure what the solution here is.

is it possible to replicate the content to EC2? Either by creating a server or using the AMQP service?

Possible? yes... but db-datanommer02 is a 1.5TB (and growing) database... so it's pretty beefly and doing inserts all the time.

Perhaps we could discuss at flock how to get something working here for the needs. Or at least brainstorm some on it?

@kevin is it OK to discuss during flock? I will be there all week - happy to have a chat or during Infra Hackfest.

Absolutely! We can and should!

Metadata