Medulla Organizations

[AndrewBabbitt97]

Is there an existing issue for this?

• [X] I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

We need the ability to have multiple organizations hosted out of a single Medulla instance.

Describe the solution you'd like

We need the concept of an organization inside of Medulla.

The general considerations for this are as follows:

• A user can own any number of apps (including zero)
• A organization can own any number of apps (including zero)
• A organization can have one or more users as a part of it

I propose adding this as a CRD called Organization.

Kubernetes supports the concept of ownership and references. That should allow us to relate resources such as an app to an organization.

Additional context

Multi tenancy is a huge requirement for Medulla in the long run and a lot of other features implementations will be dictated by how it works. We need to evaluate this early and come up with a solution so we start organizing things such as apps and databases into organizations.

[babanfaraj]

@AndrewBabbitt97 can we somehow break this issue down further? Off of a quick thought, it seems like this includes work with the database, KubeOps, and more. For new members it may be more clear if we can break this out.

[AndrewBabbitt97]

@babanfaraj

Organizations are just containers for other things, you won't be developing database features or anything else as a part of this ticket.

The additional context is there for a better understanding of the reasoning for implementing this.

[babanfaraj]

@AndrewBabbitt97 The concept of an organization makes sense along with the reasoning. I guess I am asking for more of a feature like tickets to accomplish it.

[AndrewBabbitt97]

@babanfaraj I have added additional details to the ticket. The proposed solution is a CRD that uses Kubernetes relations to tie apps and organizations together.

Users are technically stored in the Identity service database, I'm open to ideas on how we want to integrate that with orgs.

The goal of this ticket is mostly the implementation of the organization resource, integration bits will likely be down the line as we start merging the database service and others.

[keithlogan94]

Status for Baban

What did you work on yesterday? Nothing was pulled into today What did will you work on today? Worked on entity for organization, but now working on controller, KubeOps Controller. This tangles with other controller for application. Created a controller class for organization, need to create one ofr applications and test it out.
Are there any blockers in your way? The other issue for KubeOps is a blocker to this issue. Waiting for final review of KubeOps. Are we on track to complete the work by end of the sprint with the sprint goal? Don't think it will get done by tomorrow. It also needs to get reviewed and that takes time.

[babanfaraj]

@AndrewBabbitt97 can an app be owned by multiple organization or should we ignore this case for now?

[keithlogan94]

Status for Baban

What did you work on yesterday? Created a controller for applications and updated applicatione entity, updated org controller, now all doing is trying get ownership ref to work by testing it out, don't antiicpate finishing by end of sprint, if done by end of today will create pr, maybe. What did will you work on today? Same
Are there any blockers in your way? No blockers Are we on track to complete the work by end of the sprint with the sprint goal? Maybe it can be finished by end of today, there may be a pull request

[babanfaraj]

Status for Baban

What did you work on yesterday? Debugged on going issues with the KubeOps error being thrown. What did will you work on today? Continue to debug why the KubeOps is throwing errors in regards to the Database controller
Are there any blockers in your way? No blockers Are we on track to complete the work by end of the sprint with the sprint goal? If this is still a current sprint priority, then yes.