Hi list, over the last week we have been working on a revised Multi-Tenancy model for Amdatu Platform 1.0. This included (partially offline) discussions on what we will and wont cover as well as how we will implement it. In a nutshell, comparing to the "old"model the goal is to come up with a solution that is optional, transparent/non invasive, still very flexible and ready for provisioning. The results are covered in the pages listed below providing an architectural overview [0], requirements [1], use-cases [2] and a more detailed design[3].
This is not the end and it is not a done deal as over the next couple of weeks we will spend some more iterations to refine, implement and proof the model. Therefore at this point we would very much appreciate feedback from the community and specifically anyone interested in Multi-Tenancy. Do you feel requirements and use cases cover your needs? Do the design and proposed implementation make sense? Any feedback will be most valuable to our end goal, which is to come up with a stable future proof model for 1.0! Thanks and greetz, Bram [0] http://www.amdatu.org/confluence/display/Amdatu/Multi-tenancy [1] http://www.amdatu.org/confluence/display/Amdatu/Amdatu+Core+Tenant+Requirements [2] http://www.amdatu.org/confluence/display/Amdatu/Amdatu+Core+Tenant+Use+Cases [3] http://www.amdatu.org/confluence/display/Amdatu/Amdatu+Core+Tenant+Design _______________________________________________ Amdatu-users mailing list [email protected] http://lists.amdatu.org/mailman/listinfo/amdatu-users
