airflow-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Song Liu <song...@outlook.com>
Subject 答复: 答复: About multi user support in airflow
Date Tue, 27 Feb 2018 08:51:11 GMT
Hi Chris & Joy,

About the access control feature in new web-server, is it kind of a filter mechanism based
on the rights ? will the dag storage be separated per user also ?

Also for the multi-user support, how to isolate the execution space for different user ? for
example, if one user execute one bash to delete other user's data.

Or from the design perspective, is the airflow aiming to serve multi-user ?

Thanks,
Song
________________________________
发件人: Chris Riccomini <criccomini@apache.org>
发送时间: 2018年2月2日 15:28
收件人: dev@airflow.incubator.apache.org
抄送: Trent Robbins
主题: Re: 答复: About multi user support in airflow

@song, you might also be interested in the work that Joy Gao is doing to
add more access controls to the UI:

https://github.com/wepay/airflow-webserver

On Thu, Feb 1, 2018 at 8:12 PM, Song Liu <songliu@outlook.com> wrote:

> Hi Trent,
>
> One way is to deploy one standalone airflow components (scheduler, worker,
> broker, mysql etc.) in docker for every single user, but there needs to
> only one web service for user accessing, that would mean the web service
> should be interact with multiple other worker / scheduler for individual
> user, do I understand correctly ?
>
> For Flask, how could the multi-user feature be supported ? could you help
> clarify ?
>
> Also, could you help share what's the reason/design behind why it doesn't
> support multi-user feature in airflow ?
>
> Thanks,
> Song
> ________________________________
> 发件人: Trent Robbins <robbintt@gmail.com>
> 发送时间: 2018年2月2日 3:50
> 收件人: dev@airflow.incubator.apache.org
> 主题: Re: About multi user support in airflow
>
> Hi Song,
>
> I would recommend using airflow in docker with individual databases for
> individual contributors. Does this make sense for your needs? There are
> other similar concepts that could also be used.
>
> I don't think there is another way to split DAGs by user permission.
> However, this feature doesn't seem particularly challenging to implement
> since it uses Flask. But who knows!
>
> Trent
>
> On Thu, Feb 1, 2018 at 19:24 Song Liu <songliu@outlook.com> wrote:
>
> > Hi,
> >
> > In production, multi-user support is needed, which means that every user
> > could login the airflow platform, and could manage their own dags
> > separately.
> >
> > But currently it seem that all the dags are managed into a single dags
> > folder, so for multi-user support what I need to do ?
> >
> > Many thanks for helping out.
> >
> > Thanks,
> > Song
> >
> --
> (Sent from cellphone)
>
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message