[09:18:17] morning [10:09:42] I've just created a trove-only cloud vps project and I was reviewing the user docs. is this sentence accurate? "By default you can only access the DB from VMs within the same Cloud VPS project" [16:27:35] dhinus: That would be about the default security groups applied to the trove instance. If mariaddb/postgres ports aren't open to the rest of WMCS or the internet in the default group then it would be true. (And that seems correct to me.) [16:35:23] bd808: that makes sense but I haven't checked the sec groups yet... we should probably add a section about enabling access to a trove db from toolforge [16:43:57] seems reasonable. I wonder if it would be a bad practice to include some sort of "open to Toolforge" security group in the default objects we make for a new project so that folks really only have to connect the trove amphora to the security group to make things work? [16:53:08] dhinus: the default security group in the deorph-db project does not open any db ports and only opens ssh from other Cloud VPS projects. [16:57:07] bd808: thanks for looking, I think that would make sense... does the sec group have to be attached to each trove instance? or could we set it up project-wide so that all new trove instances will get it? [16:57:55] I will probably open a task so the other sres currently at the offsite can have a look next week [16:59:49] changing the default group would make things automatic project wide normally. I was thinking about a new and separate security group that would need to be manually applied, but there might be some way that could be made a default by modifying how the trove instances are provisioned. [17:00:51] making all trove instances available to Toolforge by default would have implications for projects not connected to a Toolforge tool. [17:02:34] A different direction entirely would be to make it possible to add a db container directly in a tool's namespace. That is probably mostly blocked on PVCs in Toolforge. [17:28:18] I agree we should not make trove available to toolforge by default, but a project-wide setting for projects like deorph-db would be nice [17:29:05] db-containers in toolforge namespaces is my long-term dream, but yes it's blocked on PVCs... and engineering time :)