Workspace

Introduction

In Netilab every user is a part of an organization (i.e. tenant), and every organization consists of at least one Workspace. Regardless of the NetiLab hosting type (on premise / Azure) workspaces are defined by the following workspace objects:

• Instance of NetiLab application database

• Access to data sources and destinations

• Instance of Python compute server

How are workspaces defined

Since each organization is defined either by Azure AD (Azure hosting) or Local AD (on premise hosting), every workspace needs a unique Security Group. Users having access to a given workspace must therefore be a part of Security Group that identifies a Workspace.

Workspace access management is therefore completely determined by Active Directory (AD).

Workspace Types

Based on organization and hosting type workspaces can consists of various different objects. In general workspaces can be:

• Cloud workspace: All workspace objects are located directly in cloud. Organization does not need any infrastructure set up.

• Local workspace: All workspace objects are located on premise, meaning that the workspace does not need any (internet) connection all data is stored directly in organization infrastructure.

• Hybrid workspace: Workspace objects are scattered across cloud and on premise resources. Using Azure Hybrid connections and file synchronization NetiLab uses abstraction to work with those resources .

When a new organization wants to join NetiLab, the most appropriate workspace type for their needs and use cases must be determined.