Rgw - multitenancy » History » Version 1
Jessica Mack, 06/07/2015 01:25 AM
1 | 1 | Jessica Mack | h1. Rgw - multitenancy |
---|---|---|---|
2 | |||
3 | h3. Summary |
||
4 | |||
5 | Introducing the rados gateway tenant. It provides a level of hierarchy on top of users and their data. This provides the ability to separate the users into different organizational entities. |
||
6 | |||
7 | h3. Owners |
||
8 | |||
9 | * Name (Affiliation) |
||
10 | * Name (Affiliation) |
||
11 | * Name |
||
12 | |||
13 | h3. Interested Parties |
||
14 | |||
15 | * Yehuda Sadeh (Inktank) |
||
16 | * Name (Affiliation) |
||
17 | * Name |
||
18 | |||
19 | h3. Current Status |
||
20 | |||
21 | A preliminary work that implemented this has been done as part of the Dumpling development. However, this has not been been merged upstream and needs to be brought up-to-date with the current code base. |
||
22 | |||
23 | h3. Detailed Description |
||
24 | |||
25 | We define a new 'tenant' level on top of the current user data structure. A tenant has its own set of users. Any user may be referred as tenant:user (or probably tenant/user, as the colon has been used in the past for subbusers), and this can be used to globally reference any user. Bucket names are now per-tenant. |
||
26 | We define a default tenant, which we access if tenant is not specified. |
||
27 | Open questions: |
||
28 | - how to handle virtual bucket names? Two different tenants can have the same bucket names |
||
29 | - what should we do with subusers? |
||
30 | |||
31 | h3. Work items |
||
32 | |||
33 | h3. Coding tasks |
||
34 | |||
35 | # Task 1 |
||
36 | # Task 2 |
||
37 | # Task 3 |
||
38 | |||
39 | h3. Build / release tasks |
||
40 | |||
41 | # Task 1 |
||
42 | # Task 2 |
||
43 | # Task 3 |
||
44 | |||
45 | h3. Documentation tasks |
||
46 | |||
47 | # Task 1 |
||
48 | # Task 2 |
||
49 | # Task 3 |
||
50 | |||
51 | h3. Deprecation tasksEdit section |
||
52 | |||
53 | # Task 1 |
||
54 | # Task 2 |
||
55 | # Task 3 |