On 2/25/15 2:31 PM, Sage Weil wrote: > Hey, > > We are considering switching to civetweb (the embedded/standalone rgw web > server) as the primary supported RGW frontend instead of the current > apache + mod-fastcgi or mod-proxy-fcgi approach. "Supported" here means > both the primary platform the upstream development focuses on and what the > downstream Red Hat product will officially support. > > How many people are using RGW standalone using the embedded civetweb > server instead of apache? In production? At what scale? What > version(s) (civetweb first appeared in firefly and we've backported most > fixes). > > Have you seen any problems? Any other feedback? The hope is to (vastly) > simplify deployment. Hi, We have been using civetweb proxied by Apache on RHEL7 on both our RGW clusters and have been very happy with performance and setup. This has been our default since we upgraded to Hammer. Only thing we had to make sure that on our ProxyPass we were specifying nocanon the proxy pass would mangle http encoding. Reason we use Apache on the front end is so we can collocate a Django web front end application for the object store to get around the necessary for CORS (we designed this before RGW was CORS aware anyway). Thanks, derek -- Derek T. Yarnell University of Maryland Institute for Advanced Computer Studies -- 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
