Hi Ivo On Wed, Apr 25, 2012 at 12:57 PM, Ivo Ladage-van Doorn <[email protected]> wrote: > Hi ‘Platform guys’, > > While upgrading Amdatu Auth to platform 0.4.0-RC1, I noticed that there was > no real (up to date and intended for app developers) documentation about the > change in multi-tenancy design between platform 0.2.1 and 0.3.0/0.4.0.
True! We have no upgrade recipes (yet). Up till now we have documented the new mechanism design [0] and changes [1] with quite some overlap with your page. personally, I'd like to see some more HOWTO / Cookbook style docs as well. I think that could really lower the barrier for people. We are planning to review both structure and content of the wiki in the upcoming week. At least to get what is on there up-to-date and consistent with the upcoming 1.0 release. I imagine we will have some more discussions on what types of documentation should and should not be there. > Therefore I created two WIKI pages for the Auth project, describing this > change: > > http://www.amdatu.org/confluence/display/AmdatuAuth/Multi-tenancy+in+0.2.2 > http://www.amdatu.org/confluence/display/AmdatuAuth/Multi-tenancy+in+0.3.0 > > (NB: version numbers refer Auth 0.2.2 which is based on platform 0.2.1 and > Auth 0.3.0 wich is based on platform 0.4.0) > > Please read and review. I did not intent to fully describe the new > multi-tenancy design but to provide a quick how to for implementing a > multi-tenant bundle. When you finished the full multi-tenancy documentation, > I can refer to these pages for more info. Looks good and correct. We may need to borrow some of this for the platform wiki ;) Two minor comments to clarify on what I think you mean that you think we mean: <quote> Services registered in the PLATFORM space cannot resolve services that were registered in the TENANTS space and vice versa. The PLATFORM space represents services that are not tenant-aware, the TENANTS space represents services that are. </quote> It is TENANTS spaceS. Just like platform, which basically is a magic tenant, each configured tenant gets its own services/configuration space. By default no services are shared between any of the spaces. The binding is the strategy used for services registered from that bundle. PLATFORM means "only bind services to the platform space", while TENANT means bind services to every tenant space. Therefore we say the *bundle* is "multi-tenant" regardless of the binding strategy for its services and *services* have no concept of being multi-tenant or not. Grz Bram [0] http://www.amdatu.org/confluence/display/Amdatu/Amdatu+Tenant+Design [1] http://www.amdatu.org/confluence/display/Amdatu/Releases _______________________________________________ Amdatu-developers mailing list [email protected] http://lists.amdatu.org/mailman/listinfo/amdatu-developers
