Murano/Specifications/Per Tenant Isolation

=Per-Tenant Isolation (for Murano-v0.4)=

Introduction
Murano Metadata Repository Server was introduced in Murano-v0.4 release. But there are no access restrictions: any user is able to edit any service definition or file. To prevent this behavior new per-tenant isolation feature will be added to Murano-v0.4.1 release.

Details
In current implementation all files are grouped by data types and stored in corresponding directories. All those directories are located inside '"Services'" directory along with manifest files (service definitions). Since Metadata Server stores data on a file system, the best solution for data isolation would be dividing data into separate folders.

Directory structure
This initial data for all common servicies. It will contain all shared resources. The contents of this folder will be non-editable from UI. There will be only one way to modify it - by copying files directly to the Common folder (Note: files should be copied to the correct place and all client and server caches should be cleaned). Folder content will be copied to tenant folders.
 * Common folder

Separate folder named by tenant_id for an each tenant will be created. Users belonging to the same tenant will have equal rights on file modification. This folder should be created on the first uploading request and filled with data from Common folder. All modification will be held in tenant's folders.
 * Tenant folders

Client Cache Structure

 * Murano Conductor cache organizations will stay the same - it has per-task isolation, so diffirent task will execute in a different tenant.
 * Murano Dashbord cache should be organized by tenants: for each tenant there will be a separate tenant_id folder with cache for that tenant.

UI Changes
In Murano Dashboard only minor changes should be made. For each tenant separate folder for storing cache will be created.