[Pacemaker] Re: [Cluster-devel] [RFC] Splitting cluster.git into separate projects/trees

David Teigland teigland at redhat.com
Fri Nov 14 12:25:30 EST 2008

On Fri, Nov 14, 2008 at 10:18:13AM +0100, Fabio M. Di Nitto wrote:
> At this point we haven't really settled how many (sub) project will be
> created out of this split. This will come once we agree how to split.

I like the third option as long as the number of new git trees doesn't
explode (obviously no one wants 10 new git trees.)  Not to get ahead of
you, but for my own curiosity I looked at what minimum number of git trees
I'd have to start juggling... it's not too bad, but more than this might
get out of hand.

  libdlm, dlm_controld, libdlmcontrol, dlm_tool

  libfence, fenced, libfenced, fence_tool, fence_node


  libcman, cman_tool, cmannotifyd, qdiskd, mkqdisk
  move plugins into corosync tree?
  group_tool (groupd/libgroup won't exist, group_tool will just be a
  wrapper/shortcut for fence_tool/dlm_tool/gfs_control queries;
  maybe include queries of other related daemons, like ocfs2_controld?)

  gfs_controld, libgfscontrol, gfs_control
  mount.gfs2, mount.gfs, libgfs, libgfs2
  gfs_debug, gfs_fsck, gfs_grow, gfs_jadd, gfs_mkfs, gfs_quota, gfs_tool
  gfs2_convert, gfs2_edit, gfs2_fsck, gfs2_mkfs, gfs2_quota, gfs2_tool



gnbd goes away
cmirror moves away

More information about the Pacemaker mailing list