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. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org For additional commands, e-mail: dev-h...@airflow.apache.org
