TODO 4.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122
  1. --------------------------------------------------------
  2. The Corosync Cluster Engine Topic Branches and Backlog
  3. --------------------------------------------------------
  4. ----------------------------
  5. Last Updated: January 2012
  6. ----------------------------
  7. --------------------------------------
  8. Current priority list for Needle 2.0
  9. --------------------------------------
  10. 1. quorum improvements
  11. --------------------------------------
  12. Current priority list for Needle 2.1
  13. --------------------------------------
  14. 1. implement topic-onecrypt
  15. 2. implement add/remove nodes from udpu
  16. 3. logsys glue layer removal
  17. 4. implement topic-zerocopy
  18. 5. implement topic-rdmaud
  19. 6. harden and finish ykd algorithm
  20. 7. implement topic-xmlschema
  21. We use topic branches in our git repository to develop new disruptive features
  22. that define our future roadmap. This file describes the topic branches
  23. the developers have interest in investigating further.
  24. targets can be: whitetank, needle2.0, needle3.0, or future (3.0+).
  25. Finished can be: percentage or date merged to master. Once in a shipped
  26. version, please remove from the topic list.
  27. ------------------------------------------------------------------------------
  28. topic-quorum
  29. ------------------------------------------------------------------------------
  30. Main Developer: Fabio "the coding monkey" Di Nitto
  31. Started: yes
  32. Finished: 90%
  33. target: needle2.0
  34. This topic is about bringing votequorum/quorum up to speed and feature complete.
  35. Current status:
  36. - features are implemented, most of debugging done
  37. - need to do:
  38. * document new votequorum options once we are sure their behavior won't change
  39. * configuration bits in corosync.conf for quorum related business
  40. ------------------------------------------------------------------------------
  41. topic-xmlschema
  42. ------------------------------------------------------------------------------
  43. Main Developer: Honza Friesse
  44. Started: not started
  45. Finished: 0%
  46. target: needle2.1
  47. XML configuration for corosync exists, but imput file is not checked against
  48. XML schema. This topic is about implementing preferably RelaxNG schema of
  49. corosync configuration.
  50. ------------------------------------------------------------------------------
  51. topic-onecrypt
  52. ------------------------------------------------------------------------------
  53. Main Developer: Honza Friesse
  54. Started: not started
  55. Finished: 0%
  56. target: needle2.1
  57. Description:
  58. Currently encryption code is located in totemudp.c, totemudpu.c, and iba has
  59. no encryption support. This topic merges the encryption code into a new
  60. file such as totemcrp.c and provides a mechanism for totemnet.c to register
  61. encrypt and decrypt functions with totem[udp|iba|udpu] and use them as
  62. requested by the configuration.
  63. ------------------------------------------------------------------------------
  64. topic-netmalloc
  65. ------------------------------------------------------------------------------
  66. Main Developer: Honza Friesse
  67. Started: not started
  68. Finished: 0%
  69. target: needle2.1
  70. Description:
  71. The totemiba.c driver must allocate memory and assign it to a protection domain
  72. in order for an infiniband driver to transmit memory. In the current
  73. implementation, totemsrp.c also allocates these same frames. This results in
  74. an extra memcpy when transmitting with libibverbs technology. Memory copies
  75. are to be avoided. The simple solution is to have each network driver provide
  76. a memory allocation function. When totemsrp wants a free frame, it requests
  77. it from the network driver.
  78. ------------------------------------------------------------------------------
  79. topic-rdmaud
  80. ------------------------------------------------------------------------------
  81. Main Developer: Honza Friesse Steven Dake
  82. Started: not started
  83. Finished: 0%
  84. target: needle2.1
  85. Description:
  86. Currently our RDMA code uses librdmacm to setup connections. We are not
  87. certain this extra library is needed, and may be able to use only ibverbs. If
  88. this is possible, the totem code may be more reliable, especially around
  89. failure conditions.
  90. ------------------------------------------------------------------------------
  91. topic-zerocopy
  92. ------------------------------------------------------------------------------
  93. Main Developer: Honza Friesse
  94. Started: not started
  95. Finished: 0%
  96. target: needle2.1
  97. Description:
  98. Totem has many copies involved in messaging which we would like to investigate
  99. removing. Our goal is to deliver wire speed performance for rdma networks,
  100. and if this can be achieved by our other topic investigations, we may not
  101. further investigate this topic. The basic idea of the topic is to handle
  102. message assembly/fragmentation in libcpg, and have totem be responsible for
  103. sending these pages that are shared via posix shared memory.
  104. ------------------------------------------------------------------------------
  105. other topics not yet defined:
  106. * disallow binding to localhost interfae in redundant ring configuation.
  107. * doxygenize include and lib directories.
  108. * sort out binding to localhost in general
  109. * totem multiring
  110. * load balancing over different speed links in RRP