Rohit Choudhary created ZEPPELIN-773:
----------------------------------------
Summary: Multi-tenancy in Zeppelin
Key: ZEPPELIN-773
URL: https://issues.apache.org/jira/browse/ZEPPELIN-773
Project: Zeppelin
Issue Type: New Feature
Components: zeppelin-server
Affects Versions: 0.5.6, 0.5.5
Reporter: Rohit Choudhary
Assignee: Rohit Choudhary
Priority: Critical
Fix For: 0.6.0
Attachments: ZeppelinMulti-tenancyDesign.docx
As Zeppelin evolves its notebook, for large scale data analysis, multiple
zeppelin users are expected to use and connect to the same set of data
repositories within an enterprise. Since Zeppelin notebooks could affect data,
state and its lineage, it is important to have separation of users, provide
them with appropriate sandboxes, in addition to capturing the right audit
details. Further, the IT within the organization would prefer to support fewer
Zeppelin instances (preferably one) to support its customers. Therefore, the
objectives of creating a multi-tenant zeppelin are:
● Supporting workloads of multiple customers
● Supporting multiple LOBs (lines of business), on a single data systems
● Support fine grained audits
As a natural evolution of Zeppelin Authentication and Authorization design,
partly user awareness in downstream data systems such as Spark/Hive and others,
is essential to achieve the above stated objectives.
Attached is a document that factors in the above considerations and provides
for an approach.
cc [~felixcheung] [~moon] [~vinayshu...@gmail.com] [~prabhjyotsingh]
[~rvenkatesh25]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
