On Fri, Mar 9, 2018 at 4:02 PM, Casey Bodley <cbodley@xxxxxxxxxx> wrote: > > On 03/09/2018 09:45 AM, John Spray wrote: >> >> The idea is not to put all the admin functionality in a library. >> Rather, to have a minimal library that does the bits that don't make >> sense in the admin REST API -- the parts that bootstrap authentication >> and set up zones. > > > Has much thought been put into the requirements for multisite configuration? > There are some aspects that can be managed within a single cluster, and > those can and should be exposed by the radosgw admin api. But in general, > zone creation and configuration has to happen on its own resident cluster. The thing that sets up a connection between two clusters probably wants to be outside of either cluster -- for that reason it's not been much of a topic for the in-Ceph management bits. When I talk about "setting up a zone", I'm using that interchangeably to mean either setting up a single RGW cluster or setting up a zone that's intended to be hooked up elsewhere in a multisite configuration later. I would love for the RGW experts to give this some though: the tools that hook up multiple ceph clusters are more likely to be vendor-specific and less likely to be core Ceph, but it would be good to have a straight answer for people who ask what interface they should use to do it from their vendor tool. John > -- > 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
