Project

General

Profile

Actions
Copy link

Feature #801

closed

librados: allow access to multiple clusters

Added by Sage Weil about 13 years ago. Updated almost 13 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
librados
Target version:
v0.31
% Done:

100%

Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

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?

Subtasks 13 (0 open — 13 closed)

Subtask #815: Remove globals & partition g_confResolvedColin McCabe02/28/2011

Actions
Subtask #839: Globals cleanup. Replace g_conf.name with g_conf.entity_name.to_str(). Remove g_conf.type.ResolvedColin McCabe02/28/2011

Actions
Subtask #840: Clean separation between different components of initializationResolvedColin McCabe02/28/2011

Actions
Subtask #841: don't call daemon_init in library codeResolvedColin McCabe02/28/2011

Actions
Subtask #842: initialization: have appropriate library-specific defaultsResolvedColin McCabe02/28/2011

Actions
Subtask #843: Decouple dout from g_confResolvedColin McCabe02/28/2011

Actions
Subtask #844: g_conf should become a pointerResolvedColin McCabe02/28/2011

Actions
Subtask #845: g_conf should not be defined in library code.ResolvedColin McCabe02/28/2011

Actions
Subtask #846: De-globalize SimpleMessenger, etc.Resolved02/28/2011

Actions
Subtask #1160: introduce CephContext to some structures in common/ResolvedColin McCabe06/09/2011

Actions
Subtask #1164: initialize g_ceph_context in common_preinitResolvedColin McCabe06/09/2011

Actions
Subtask #1227: write tests of libceph, librgw, librados library thread-safetyRejectedColin McCabe06/24/2011

Actions
Subtask #1231: NUM_THREADS=3 testrados segfaultsRejectedColin McCabe06/24/2011

Actions
Actions
Copy link
 #1

Updated by Sage Weil about 13 years ago

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.

Actions
Copy link
 #2

Updated by Yehuda Sadeh about 13 years ago

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.

Actions
Copy link
 #3

Updated by Greg Farnum about 13 years ago

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?

Actions
Copy link
 #4

Updated by Colin McCabe about 13 years ago

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

Actions
Copy link
 #5

Updated by Colin McCabe about 13 years ago

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?

Actions
Copy link
 #6

Updated by Sage Weil about 13 years ago

  • Target version changed from v0.26 to 12
Actions
Copy link
 #7

Updated by Sage Weil about 13 years ago

  • 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
Actions
Copy link
 #8

Updated by Sage Weil almost 13 years ago

  • Translation missing: en.field_position deleted (598)
  • Translation missing: en.field_position set to 376
Actions
Copy link
 #9

Updated by Sage Weil almost 13 years ago

  • Target version changed from 12 to v0.29
  • Translation missing: en.field_position deleted (376)
  • Translation missing: en.field_position set to 622
Actions
Copy link
 #10

Updated by Sage Weil almost 13 years ago

  • Target version changed from v0.29 to v0.30
  • Translation missing: en.field_position deleted (624)
  • Translation missing: en.field_position set to 2
Actions
Copy link
 #11

Updated by Sage Weil almost 13 years ago

  • 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
Actions
Copy link
 #12

Updated by Sage Weil almost 13 years ago

  • Translation missing: en.field_position deleted (26)
  • Translation missing: en.field_position set to 13
Actions
Copy link
 #13

Updated by Sage Weil almost 13 years ago

  • Target version changed from v0.30 to v0.31
Actions
Copy link
 #14

Updated by Sage Weil almost 13 years ago

  • 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
Actions
Copy link
 #15

Updated by Sage Weil almost 13 years ago

  • Status changed from New to Resolved
Actions
Copy link

Also available in: Atom PDF