Просмотр исходного кода

TODO: Remove TODO file

TODO file has many problems like it's not updated regularly, it's not
updated at all in already distributed tarballs, ...

All relevant RFEs were filled at github as issues with flag "TODO file
convert" so file can finally be removed from git.

Signed-off-by: Jan Friesse <jfriesse@redhat.com>
Reviewed-by: Christine Caulfield <ccaulfie@redhat.com>
Jan Friesse 11 лет назад
Родитель
Сommit
c9232d5d6c
1 измененных файлов с 0 добавлено и 96 удалено
  1. 0 96
      TODO

+ 0 - 96
TODO

@@ -1,96 +0,0 @@
---------------------------------------------------------
- The Corosync Cluster Engine Topic Branches and Backlog
---------------------------------------------------------
-
-----------------------------
- Last Updated: May 2012
-----------------------------
-
---------------------------------------
- Current priority list for Needle 2.1
---------------------------------------
-* disallow binding to localhost (Honza)
-* don't rely on mcast loop (Honza)
-* Add support for LOG_TRACE and log received messages in this level (Honza)
-* Proper support for DNS (always return one address even if function
-   is called multiple times) (Honza)
-* porting of qdisk to votequorum and eventually finalize qdevice API
-   in votequorum. (Fabio)
-* Cleaner shutdown process -> free memory (Fabio)
-
---------------------------------------
- Current priority list for Needle 2.X
---------------------------------------
-* logsys glue layer removal
-* harden and finish ykd algorithm
-* implement topic-xmlschema
-* Modify totemsrp to allow dynamic definitions of the ring counts
-   to allow a larger number of redundant rings then 2.
-* Investigate always-on flight recorder
-* implement topic-rdmaud
-
---------------------------------
-Ideas for future releases (3.0+)
---------------------------------
-* topic-netmalloc
-* doxygenize include and lib directories.
-* re-evaluate using libtool to link libraries.
-* Support for clang as compiler (depends on libtool)
-* reorganize library/headers/code in the tree
-* change and simplify build defaults
-* libtotem cleanup/rewrite
-    * Rewrite totem fragmentation layer
-    * rewrite top level totempg interface
-    * Split fragmentation layer in totem (ie: totempg talks to totemfrg
-      talks to totemsrp)
-    * Add a getopt and setopt feature to top level interface to allow
-      runtime configuration of the interface
-* Improve cpg - opaque data in callbacks (client stores data about
-   itself, every node can access them), permissions (read only/read
-   write/ some application may disable listeners) - Probably implemented
-   as extra user space library on top of normal cpg
-* Better statistic - histogram
-* totem multiring
-* load balancing over different speed links in RRP
-
-We use topic branches in our git repository to develop new disruptive features
-that define our future roadmap.  This file describes the topic branches
-the developers have interest in investigating further.
-
-targets can be: needle2.1, needle2.X, or future (3.0).
-Once in a shipped version, please remove from the topic list.
-
-------------------------------------------------------------------------------
-topic-xmlschema
-------------------------------------------------------------------------------
-XML configuration for corosync exists, but imput file is not checked against
-XML schema. This topic is about implementing preferably RelaxNG schema of
-corosync configuration.
-
-------------------------------------------------------------------------------
-topic-onecrypt
-------------------------------------------------------------------------------
-Currently encryption code is located in totemudp.c, totemudpu.c, and iba has
-no encryption support.  This topic merges the encryption code into a new
-file such as totemcrp.c and provides a mechanism for totemnet.c to register
-encrypt and decrypt functions with totem[udp|iba|udpu] and use them as
-requested by the configuration.
-
-------------------------------------------------------------------------------
-topic-netmalloc
-------------------------------------------------------------------------------
-The totemiba.c driver must allocate memory and assign it to a protection domain
-in order for an infiniband driver to transmit memory.  In the current
-implementation, totemsrp.c also allocates these same frames.  This results in
-an extra memcpy when transmitting with libibverbs technology.  Memory copies
-are to be avoided.  The simple solution is to have each network driver provide
-a memory allocation function.  When totemsrp wants a free frame, it requests
-it from the network driver.
-
-------------------------------------------------------------------------------
-topic-rdmaud
-------------------------------------------------------------------------------
-Currently our RDMA code uses librdmacm to setup connections.  We are not 
-certain this extra library is needed, and may be able to use only ibverbs.  If
-this is possible, the totem code may be more reliable, especially around
-failure conditions.