You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by "Shiroshica Kulatilake (JIRA)" <ji...@apache.org> on 2014/10/03 09:30:33 UTC
[jira] [Commented] (STRATOS-761) Tenant isolation for policies and
definitions - in Autoscalar
[ https://issues.apache.org/jira/browse/STRATOS-761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14157764#comment-14157764 ]
Shiroshica Kulatilake commented on STRATOS-761:
-----------------------------------------------
Commited changes to tenant-isolation-feature on apache/stratos (https://github.com/apache/stratos/commits/tenant-isolation-feature)
8e5cba6fd346fed1bab10fcdb4ab1e1f6ba9fe89, 0c837be9482d4b8581b3f9391a389e0354ffefbf, 56697256448fd9d056958e95de048c5960df952e & 71a5ec1c37955bb3c2f13a2c93a604094aabb5cd
> Tenant isolation for policies and definitions - in Autoscalar
> -------------------------------------------------------------
>
> Key: STRATOS-761
> URL: https://issues.apache.org/jira/browse/STRATOS-761
> Project: Stratos
> Issue Type: New Feature
> Affects Versions: 4.1.0 M1, 4.1.0 M2
> Reporter: Shiroshica Kulatilake
> Assignee: Shiroshica Kulatilake
> Fix For: 4.1.0 M2
>
>
> Currently in Stratos there is no isolation tenant wise when creating policies and definitions and also when using these. With this feature the following should be possible.
> 1. Ability for tenants to create their own policies and definitions
> 2. When using policy and definitions - tenant users should be able to by default only see those policies/definitions created within that space
> 3. Ability to create publicly available policies and definitions by the super tenant - which could be used by all tenants
> 4. Ability to set quota's to policies, definitions and subscriptions for each tenant when creating the tenant
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)