On Tue, Jul 11, 2017 at 8:36 PM, Wido den Hollander <wido@xxxxxxxx> wrote: > >> Op 11 juli 2017 om 17:03 schreef Sage Weil <sweil@xxxxxxxxxx>: >> >> >> Hi all, >> >> Luminous features a new 'service map' that lets rgw's (and rgw nfs >> gateways and iscsi gateways and rbd mirror daemons and ...) advertise >> themselves to the cluster along with some metadata (like the addresses >> they are binding to and the services the provide). >> >> It should be pretty straightforward to build a service that >> auto-configures haproxy based on this information so that you can deploy >> an rgw front-end that dynamically reconfigures itself when additional >> rgw's are deployed or removed. haproxy has a facility to adjust its >> backend configuration at runtime[1]. >> >> Anybody interested in tackling this? Setting up the load balancer in >> front of rgw is one of the more annoying pieces of getting ceph up and >> running in production and until now has been mostly treated as out of >> scope. It would be awesome if there was an autoconfigured service that >> did it out of the box (and had all the right haproxy options set). >> > > Are there easy Python bindings for this? I mean querying the service map. This could be a good use-case for extending the new `restful` module, to expose a read-only endpoint for reading the servicemap entries for a particular type of service. John > > I'm personally a fan of running Varnish (with Hitch for SSL) in front of RGW. Some people might also prefer Traefik [0] since that also supports dynamic configs. > > Wido > > [0]: https://traefik.io/ > >> sage >> _______________________________________________ >> ceph-users mailing list >> ceph-users@xxxxxxxxxxxxxx >> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com -- 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
