Feature #801
closed
librados: allow access to multiple clusters
Added by Sage Weil about 13 years ago.
Updated almost 13 years ago.
Description
the current api assumes you are only talking to a single cluster. we need to have a 'cluster handle' returned by the initialize method, and passed to open_pool etc, to allow multiple clusters. it'll change the api in an annoying way, but better now than later, right?
See librados_api branch.
BTW if we do end up changing this, we should be consistent with naming... some functions are rados_verb_noun and others are rados_noun_verb.
And while we're breaking backward compatibility, the read and write functions have some strange parameters ordering: offset, then buffer, then length. Should reorder that to something that'll make sense a bit more.
Do we want to implement support for multiple clusters in SimpleMessenger, or are we going to have basically full incarnations of the client for each cluster we talk to?
BTW if we do end up changing this, we should be consistent with naming...
some functions are rados_verb_noun and others are rados_noun_verb.
Done in commit:7af2e2d7b8a2f24fe022106fa8c979683bf3146f
the read and write functions have some strange parameters ordering:
offset, then buffer, then length
It may be strange, but it seems to be consistent. Is there another order that would be better?
- Target version changed from v0.26 to 12
- Translation missing: en.field_story_points set to 3
- Translation missing: en.field_position set to 1
- Translation missing: en.field_position changed from 1 to 555
- Translation missing: en.field_position deleted (
598)
- Translation missing: en.field_position set to 376
- Target version changed from 12 to v0.29
- Translation missing: en.field_position deleted (
376)
- Translation missing: en.field_position set to 622
- Target version changed from v0.29 to v0.30
- Translation missing: en.field_position deleted (
624)
- Translation missing: en.field_position set to 2
- Translation missing: en.field_story_points changed from 3 to 8
- Translation missing: en.field_position deleted (
24)
- Translation missing: en.field_position set to 24
- Translation missing: en.field_position deleted (
26)
- Translation missing: en.field_position set to 13
- Target version changed from v0.30 to v0.31
- Translation missing: en.field_position deleted (
23)
- Translation missing: en.field_position set to 1
- Translation missing: en.field_position changed from 1 to 690
- Status changed from New to Resolved
Also available in: Atom
PDF