Create a new Organization model

What does this MR do and why?

Create an organization model and corresponding database table to satisfy the cells requirements.

There is a large collection of work waiting for the Organization model to exist.

The purpose of adding this bare table now is to Create a default organization (#409628 - closed) and also reference organization entries through foreign keys such as #394796 (closed), #407837 (closed), and #409024 (closed).

What is the anticipated growth for the new table over the next 3 months, 6 months, 1 year? What assumptions are these based on?

Single digit rows for the next year. Based on the roadmap.

How many reads and writes per hour would you expect this table to have in 3 months, 6 months, 1 year?

Very limited writes. Potentially a lot of reads. In 1 year (or when Cell is in full production) Organization read will be at least 1 per request.

Under what circumstances are rows updated? What assumptions are these based on?

Row updates will be infrequent for the foreseeable future.

Based on the anticipated data volume and access patterns, does the new table pose an availability risk to GitLab.com or self-managed instances? Does the proposed design scale to support the needs of GitLab.com and self-managed customers?

There is no risk due to anticipated data volume or access patterns. The design will scale.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Closes #409585 (closed)