On Wed, Nov 5, 2014 at 4:38 PM, Loic Dachary <loic@xxxxxxxxxxx> wrote: > I guess using radosgw with the S3/Swift API is close enough in terms of what Consul needs to store key/values. But maybe I don't understand what you mean by "easily accessible distributed KV store" and wrongly assume radosgw is easy enough ;-) Yes, we did consider RGW. We were originally looking for something simpler for internal use. More than librados but less than a full object storage gateway. We didn't need Apache or multi-tenant authentication, just somewhere to store keys and pull them out elsewhere. Closer to clustered Memcache or Redis. Consul provides most of that now and adds a few things like locks and long polling >> On a side note, I haven't spoken to Dan in a while but curious on his >> thoughts on the overlap on Consul in config management land. Service >> discovery, remote execution, etc have some overlap in Puppet, Chef, >> etc. Related to Ceph we're pondering it as alternative for deploying >> mons/osds (larger scale ceph-deploy perhaps) > > Is there a framework for integration tests of some kind in Consul ? Although https://github.com/puppetlabs/beaker/ provides that for puppet, it is still rarely used and it is painful because even when used to develop a module, it is likely to break in unpredictable ways because module dependencies have no integration tests and suffer from frequent regressions. It would be great to see modern tools such as Consul encourage a more robust approach to integration tests with proper tooling from the start. I'm not entirely sure about integration tests. Certainly there are unit tests for the code but there doesn't seem to be much (that I can see) about testing things like external health checks or remote exec. -- 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
