+1 binding. Many thougths and discussions went into this AIP. Also User survery showed a strong demand for this - same we have also in our house. A multi team setup is eagerly needed. Nevertheless the complexity and missing turn-key delivery will be a challenge. I assume it needs to evolve. Besides a bit sceptic words the possibilities rule-out the additional complexity. I think we should commit making it - especially not with options to have some more breaking changes in AF3 is the right point to plan all meede structural changes in! Thanks Jarek for driving this!
Sent from Outlook for iOS<https://aka.ms/o0ukef> ________________________________ From: Jarek Potiuk <ja...@potiuk.com> Sent: Thursday, August 1, 2024 10:40:16 PM To: dev@airflow.apache.org <dev@airflow.apache.org> Subject: Re: [VOTE] AIP-67 - Multi-team deplyment of Airflow Components Voting ends a week from now - i.e Thursday 8th of August 2023 (midnight). On Thu, Aug 1, 2024 at 10:13 PM Jarek Potiuk <ja...@potiuk.com> wrote: > Hello here, > > I reviewed and - I hope - addressed all the comments so far. One most > recent change in the doc was to allow a connection/variable to belong to > multiple teams. Also I mentioned a potential future change that will allow > us to run "per-team" schedulers - leaving the UI/DB schema as the main > components that are shared between teams. > > I am also fine if this one's delivery will slip to 3.1 - because it has > many dependencies on other AIPs - and also makes some assumptions on > the other AIP-s scope when they are not yet fully fleshed out. So some > implementation details **might** change. the general approach is going to > stay: > > * not targeting manageable "mutliple tenants" - but more of a small-ish > set of teams within the same organisation that want to maintain separate > environments and isolated execution environment > > * common UI and scheduler (potentially per-team schedule) as the main > "common" piece > > * each team being able to manage their team separately - to the extent of > parsing DAGs and executing tasks > > The AIP proposal with updates: > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FAIRFLOW%2FAIP-67%2BMulti-team%2Bdeployment%2Bof%2BAirflow%2Bcomponents&data=05%7C02%7CJens.Scheffler%40de.bosch.com%7C3f883fcfd40c41a9724608dcb26a3538%7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C638581416424218968%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=LXRWcx%2B0xBpi6jeIb%2BJd4v72y8GojvYhbonctkx1sZ8%3D&reserved=0<https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-67+Multi-team+deployment+of+Airflow+components> > > > J. > >
