I have iterated and already got a LOT of comments from a LOT of people (Thanks everyone who spent time on it ). I'd say the document is out of draft already, it very much describes the idea of multi-tenancy that I hope we will be voting on some time in the future.
Taking into account that ~ 30% of people in our survey said they want "mutl-tenancy" - what I am REALLY interested in is to get honest feedback about the proposal. Manly: **"Is this the multi-tenancy you were looking for?" * Or were you looking for different droids (err, tenants) maybe?. I do not want to exercise my Jedi skills to influence your opinion, that's why the document is there (and some people say it's nice, readable and pretty complete) so that you can judge yourself and give feedback. The document is here: https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-67+Multi-tenant+deployment+of+Airflow+components Feel free to comment here, or in the document. I would love to hear more voices, and have some ideas what to do next to validate the idea, so please - engage for now - but also expect some follow-ups. J. On Wed, Mar 6, 2024 at 9:16 AM Jarek Potiuk <ja...@potiuk.com> wrote: > Sooo.. Seems that it's an AIP time :D I've just published a Draft of > AIP-67: > > Multi-tenant deployment of Airflow components > > > https://cwiki.apache.org/confluence/display/AIRFLOW/%5BDRAFT%5D+AIP-67+Multi-tenant+deployment+of+Airflow+components > > This AIP is a bit lighter in detail than the others you could see > from Jed , Nikolas and Maciej. This is really a DRAFT / High Level > idea of Multi-Tenancy that could be implemented as the follow-up after > previous steps of Multi-Tenancy implemented (or being implemented) > right now. > > I decided to - rather than describe all the details now - focus on > the concept of Multitenancy that I wanted to propose. Most of all > explaining the concept, comparing it to current ways of achieving some > forms of multi-tenancy and showing benefits and drawbacks of the > solution and connected costs (i.e. what complexity we need to add to > achieve it). > > When thinking about Multi-tenancy, I realized few things: > > * everyone might understand multi-tenancy differently > * some forms of multi-tenancy are achievable even today > * but - most of all - I started to question myself "Is this what we > can do, enough for some, sufficiently numerous groups of users to call > it a useful feature for them". > > So before we get into more details - my aim is to make sure we are all > at the same page on what we CAN do as a multi-tenancy, and eventually > to decide whether we SHOULD do it. > > Have fun. Bring in comments and feedback. > > More about all the currently active AIPs at today's Town Hall > > BTW. Do you think it's a surprise that 5 AIPS were announced just > before the Town Hall? I think not :D > > J. >
