Hello here.
I applied a number of comments mostly from TP, Ash, Daniel who were
concerned about the scope of the AIP (including the DB changes) but Also
Shubham, Nikolas and others.
The small (but most visible) change where "multi-tenant" might promise too
much. I also talked to at least a few
2:55:08 PM
To: dev@airflow.apache.org <mailto:dev@airflow.apache.org>
Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [DISCUSS] DRAFT AIP-67 Multi-tenant
deployment of Airflow components
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments u
bject: RE: [EXTERNAL] [COURRIEL EXTERNE] [DISCUSS] DRAFT AIP-67 Multi-tenant
deployment of Airflow components
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you can confirm the sender and know the
content is safe.
AVERTISSEMENT: Ce
From: Jarek Potiuk
Sent: Wednesday, March 27, 2024 6:04:14 AM
To: dev@airflow.apache.org
Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [DISCUSS] DRAFT AIP-67 Multi-tenant
deployment of Airflow components
CAUTION: This email originated from outside of the organization. Do not click
links or open
:04:14 AM
To: dev@airflow.apache.org
Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [DISCUSS] DRAFT AIP-67 Multi-tenant
deployment of Airflow components
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you can confirm the sender and know
of each team can only see and work with their own workflows.
> >>> However, Data engineers are granted access to all tenants, enabling
> them
> >> to
> >>> assist with DAG troubleshooting and optimization across all teams. Upon
> >>> logging in, users are prese
user-friendly.
>>>
>>> *Image:* https://imgur.com/gallery/uQNqiVc <
>> https://imgur.com/gallery/uQNqiVc> (highly recommend reviewing
>>> the image to understand the underlying setup)
>>>
>>>
>> *
etails, the AIP is available here -
> >
> https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-67+Multi-tenant+deployment+of+Airflow+components
> <
> https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-67+Multi-tenant+deployment+of+Airflow+components
> >
> >
> >
Amazon MWAA
>
>
>
> *From: *Jarek Potiuk mailto:ja...@potiuk.com>>
> *Reply-To: *"us...@airflow.apache.org <mailto:us...@airflow.apache.org>"
> mailto:us...@airflow.apache.org>>
> *Date: *Monday, March 11, 2024 at 4:05 PM
> *To: *"dev@airflow.a
Cc: "dev@airflow.apache.org" , "Mehta, Shubham"
Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [DISCUSS] DRAFT AIP-67 Multi-tenant
deployment of Airflow components
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless
etails, the AIP is available here -
> https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-67+Multi-tenant+deployment+of+Airflow+components
>
>
> Thanks
> Shubham
> Product Manager - Amazon MWAA
>
>
>
> *From: *Jarek Potiuk
> *Reply-To: *"us...@airflow.apac
d user interface design, only time will tell.
>>
>> Thank you for all you do for the Airflow community J. I hope the above
>> proves helpful in advancing this conversation.
>>
>> -Adam
>> ________
>> From: Mehta, Shubham
>> Se
Thursday, March 14, 2024 3:21:12 PM
> To: us...@airflow.apache.org ;
> dev@airflow.apache.org
> Subject: Re: [DISCUSS] DRAFT AIP-67 Multi-tenant deployment of Airflow
> components
>
> Hi folks,
>
> Firstly, thanks Jarek for putting together such a thorough and
> wel
rsation.
-Adam
From: Mehta, Shubham
Sent: Thursday, March 14, 2024 3:21:12 PM
To: us...@airflow.apache.org ; dev@airflow.apache.org
Subject: Re: [DISCUSS] DRAFT AIP-67 Multi-tenant deployment of Airflow
components
Hi folks,
Firstly, thanks Jarek for p
e.org"
Date: Monday, March 11, 2024 at 4:05 PM
To: "dev@airflow.apache.org" ,
"us...@airflow.apache.org"
Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [DISCUSS] DRAFT AIP-67 Multi-tenant
deployment of Airflow components
CAUTION: This email originated from outside of the org
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%
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
17 matches
Mail list logo
