-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 1/27/12 9:38 AM, Ivo Ladage-van Doorn wrote: > As far as I can see, the use case I mentioned in november last > year is not fully covered. In the case of using Cassandra for > storage (but same applies to other storage implementations) we have > a Cassandra keyspace associated with one particular tenant. When a > new tenant (service) comes available, we add a keyspace if it does > not yet exist. But in the current approach I don't see anything > that tells me the tenant has been deleted; there is no difference > between the tenant service being stopped and permanently removed. > The same question applies to creating backups for tenants. How can > I implement 'delete tenant' and 'backup tenant' features for my > storage engine? A full working code example with the new approach > would be nice.
Currently, the MT-proposal does not provide any means for external services to get notified when a tenant is 'created' or 'destroyed'. This would be a good addition to the current implementation. I'll add it to the list of use cases. As for the "backup tenant" scenario; I do not really see how the core platform should aid in this. Isn't this already provided with the two additional events mentioned above? - -- Met vriendelijke groeten | Kind regards Jan Willem Janssen | Software Architect +31 631 765 814 /My world is:/ Luminis Technologies B.V. IJsselburcht 3 6825 BS Arnhem +31 88 586 46 30 http://www.luminis-technologies.com http://www.luminis.eu KvK (CoC) 09 16 28 93 BTW (VAT) NL8169.78.566.B.01 -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPInJkAAoJEKF/mP2eHDc4vUwP/1D1BAN47Q2N5vRM/O9aJbxh NlRmL9gFRno3ILvrSwCxMkty1YJtPzSLmWZvlA7aEIPoidiQZISw7hS+u4Dp0k64 13ObdKxoVKuH6rHkPyqn9Lv8uF7yr76hyQ8w6L5hX/6h43vu/hdAAPcsq5FANru7 kS3VTX4rMb88Tngz781r8MsC2XllShddiXIEyvffCUfMdasEaesIKFK+eN4fDr+W iFujmn45+PmMf5yIU/78VMu9IY5V+jCdIrgzTKtQUD99m29ycOQMgNSnOXg5XBDa CLcICz6frj0C8rHAAranhy3Cc+D4MnxCToZ7/d3AdjkHHhfcWm2PbabkupiHH7jx FHjW89Ik+2pAuaVGhnG5Xh4K9pKgYker84+XGEFYI76lFJdmF/KEBQ1l9m6Wkwv2 nZUPyzns2Edwlu3bU4J60nMR1GoMlVwg3WWUYmguvKhvGaB9lD6g93DlP82Yw3ln iSFTWM5x4XS/QrCXPQe4Q7EIp+e78a8lkojriafRhwkt/tgErG7L04GD38WmHubj 9U9v24243AQ5HjTFROSn4LiZeY8InmuOmK2eeYrdV+EUVitjO3xo1C4tdbu9zCL3 4VeSSTDO7aNHCbSmGzuZqcR2KJ+gFqPD/OxVMQrlJsTJXVuELmZBty66zZm7XVt/ iyH9v5Yen+p/aX6md7ky =fgCt -----END PGP SIGNATURE----- _______________________________________________ Amdatu-developers mailing list [email protected] http://lists.amdatu.org/mailman/listinfo/amdatu-developers
