Yes, you would do this by setting up separate data pools for segregated
clients, giving those pools a CRUSH rule placing them on their own servers,
and if using S3 assigning the clients to them using either wholly separate
instances or perhaps separate zones and the S3 placement options.
-Greg

On Fri, Apr 12, 2019 at 3:04 AM Varun Singh <[email protected]> wrote:

> Hi,
> We have a requirement to build an object storage solution with thin
> layer of customization on top. This is to be deployed in our own data
> centre. We will be using the objects stored in this system at various
> places in our business workflow. The solution should support
> multi-tenancy. Multiple tenants can come and store their objects in
> it. However, there is also a requirement that a tenant may want to use
> their own machines. In that case, their objects should be stored and
> replicated within their machines. But those machines should still be
> part of our system. This is because we will still need access to the
> objects for our business workflows. It's just that their data should
> not be stored and replicated outside of their systems. Is it something
> that can be achieved using Ceph? Thanks a lot in advance.
>
> --
> Regards,
> Varun Singh
>



>
_______________________________________________
ceph-users mailing list
[email protected]
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Reply via email to