On Wed, Apr 4, 2018 at 12:54 AM, Gregory Farnum <gfarnum@xxxxxxxxxx> wrote: > Orit also discussed RGW in this context. She noted that RGW has good > coverage of the basic S3 functionality but that more advanced features > tend to miss some tests because they aren’t a good fit for the way we > currently use teuthology. Her specific example was bucket sharding: > trivial tests exist to make sure the commands operate and don’t > immediately break, but actually stressing the sharding code requires > millions of entries with ongoing IO, and dumping that much data into a > cluster simply takes too long to reasonably be part of every suite run > right now. So most testing is infrequent, manual, and ad-hoc. > After discussion we suggested developers should build those tests even > if they can’t be run regularly right now, because they can at least be > run by teams prior to releases and it’s still cheaper and more > reliable to find machine time than make a person do them all. I > committed to discussing with the Ceph Leadership team whether it would > be appropriate to start setting aside a small portion of time in the > sepia lab to regularly do larger-scale tests like this, once they > exist. (We suggested one or two days a month.) > PROBLEM TOPIC: build scale tests in separate suites and reserve lab > time to run them. We discussed this scale testing (for both correctness and performance) a bit in the CDM today, with a pad at http://pad.ceph.com/p/teuthology-large-suite . -Greg -- 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
