> Op 9 januari 2017 om 17:00 schreef Samuel Just <sjust@xxxxxxxxxx>: > > > 30M namespaces is not a problem since they are pretty much just object > name prefixes. 30M different cephx users probably would be a problem. Yes, figured so. Not going that route now. Will use namespaces to separate data from our application's users in RADOS to make it all future proof. Don't want to play with object name prefixes if RADOS already provides this. Hint: https://github.com/42on/librmb Wido > -Sam > > On Mon, Jan 9, 2017 at 12:59 AM, Wido den Hollander <wido@xxxxxxxx> wrote: > > > >> Op 7 januari 2017 om 2:03 schreef Blair Bethwaite <blair.bethwaite@xxxxxxxxx>: > >> > >> > >> On 7 January 2017 at 04:04, Samuel Just <sjust@xxxxxxxxxx> wrote: > >> > Namespaces are pretty much just a prefix, nothing tracks them. Are > >> > you using them simply to avoid name conflicts? > > > > Yes, but also to be able to list objects (I know, slow!) per 'user'. > > > >> > >> I assumed for some sort of data and/or security segregation using > >> cephx? 30M pools is not exactly feasible... > >> > > > > Eventually yes. We have 30M users in this system now and using namespaces seems like a clean way to separate their data inside RADOS. > > > > Might use different cephx users in the future if we want to. > > > > Wido > > > >> -- > >> Cheers, > >> ~Blairo > >> -- > >> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > >> the body of a message to majordomo@xxxxxxxxxxxxxxx > >> More majordomo info at http://vger.kernel.org/majordomo-info.html > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
