Mailing-List: contact dev-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of indika.kuma@gmail.com
 designates 209.85.161.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=OLlJ2hOH2lOwJ8c/HhbfAZ9BpTYptJFh6gdojF8LzmpZVGMNfQGNRLAT7umfLoywBL
         Gxtv6auoHugN2dvoMzhgC8A2yRkm0DKgayr1TSv2MdCgQKuKGx0L4+ZyJ70ODee9ueFX
         eiRmDMuxHs+caCf2MnkqMo7AIh+/NSly0aXzY=
MIME-Version: 1.0
In-Reply-To: <AANLkTikb21VCPK-JdTORgKnJM50ZJF0b3mt7NjrR7h0H@mail.gmail.com>
References: <AANLkTi=CkD5bGhZUXQe5=senwOqJohgyMHQqaMFVajsK@mail.gmail.com>
	<AANLkTik=s9SVabZH=gBRCvw79aY=mfcFWGuAc8C_pHsU@mail.gmail.com>
	<AANLkTikiPxms9ymJ7w2n5h-hy65EzZMBdxRcqqC_A2=O@mail.gmail.com>
	<AANLkTi=pBZt53YOPPRQ4GYYSZ+bizBKJiAncdOLPbn6W@mail.gmail.com>
	<AANLkTimD=qiGTc45A5OUvH_E=MCty+ceLFsaFyfs6+9O@mail.gmail.com>
	<AANLkTikb21VCPK-JdTORgKnJM50ZJF0b3mt7NjrR7h0H@mail.gmail.com>
Date: Fri, 7 Jan 2011 17:25:55 +0600
Message-ID: <AANLkTi=_H7LR1S7KzWDrrkBGeK4UuWBLBzWhXt=kpvMj@mail.gmail.com>
Subject: Re: Multi-tenancy, and authentication and authorization
From: indika kumara <indika.kuma@gmail.com>
To: dev@cassandra.apache.org
Content-Type: multipart/alternative; boundary=00248c0ef2f2b1d15704993fe159

--00248c0ef2f2b1d15704993fe159
Content-Type: text/plain; charset=ISO-8859-1

Hi Stu,

I highly appreciate your help.

First, I would like to get familiar with the Cassandra, especially the
current work on mult-tenancy and security.  Is there any resource other than
the wiki that can be used to learn about the internals of the Cassandra. I
would appreciate your suggestions on proper ways to implement mult-tenancy.
I would like to contact you and others through email in due course. I am
looking forward to contribute to the Cassandra

Thanks,

Indika


On Fri, Jan 7, 2011 at 11:22 AM, Stu Hood <stuhood@gmail.com> wrote:

> > (1) has the problem of multiple memtables (a large amount just isn't
> viable
> There are some very straightforward solutions to this particular problem: I
> wouldn't rule out running with a very large number of
> keyspace/columnfamilies given some minor changes.
>
> As Brandon said, some of the folks that were working on multi-tenancy for
> Cassandra are no longer focused on it. But the code that was generated
> during our efforts is very much available, and is unlikely to have gone
> stale. Would love to talk about this with you.
>
> Thanks,
> Stu
>
> On Thu, Jan 6, 2011 at 8:08 PM, indika kumara <indika.kuma@gmail.com>
> wrote:
>
> > Thank you very much Brandon!
> >
> > On Fri, Jan 7, 2011 at 12:40 AM, Brandon Williams <driftx@gmail.com>
> > wrote:
> >
> > > On Thu, Jan 6, 2011 at 12:33 PM, indika kumara <indika.kuma@gmail.com
> > > >wrote:
> > >
> > > > Hi Brandon,
> > > >
> > > > I would like you feedback on my two ideas for implementing mufti
> > tenancy
> > > > with the existing implementation.  Would those be possible to
> > implement?
> > > >
> > > > Thanks,
> > > >
> > > > Indika
> > > >
> > > > >>>>> Two vague ideas: (1) qualified keyspaces (by the tenet domain)
> > (2)
> > > > multiple Cassandra storage configurations in a single node (one per
> > > > tenant).
> > > > For both options, the resource hierarchy would be /cassandra/
> > > > <cluster_name>/<tenant name (domain)>/keyspaces/<ks_name>/
> > > >
> > >
> > > (1) has the problem of multiple memtables (a large amount just isn't
> > viable
> > > right now.)  (2) more or less has the same problem, but in JVM
> instances.
> > >
> > > I would suggest a) not trying to offer cassandra itself, and instead
> > build
> > > a
> > > service that uses cassandra under the hood, and b) splitting up tenants
> > in
> > > this layer.
> > >
> > > -Brandon
> > >
> >
>

--00248c0ef2f2b1d15704993fe159--