TODO 3.3 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667
  1. Application Interface Specification TODO list
  2. Generic Items
  3. -------------
  4. * EVT, DLOCK, MSG APIs functionality need to be developed.
  5. * Error checking on parameters could use improvement.
  6. * Allow AIS Executive to configure cluster name.
  7. * Compliance testing of return values would be helpful.
  8. * Support B.01.01 version of spec (currently support A.01.01 version).
  9. * Consider implementing SOCK_SEQPACKET for the AF_UNIX family of sockets on
  10. Linux. This would save an extra system call every time an operation must
  11. be done from the API.
  12. * There are lots of TODO's in the code that need attention.
  13. Group Messaging Interface
  14. -------------------------
  15. * Very important: single node may not work too well. Debug this
  16. mode of operation.
  17. * Very important: implement full EVS semantics when holes occur in
  18. delivery messages after a configuration change but before the new
  19. configuration is delivered.
  20. * Very important: block new messages from being multicast until recovery
  21. of each service has completed after a configuration change. This could be
  22. done with a "plug" in the token which "stops" any GMI_PRIO_MED or GMI_PRIO_LOW
  23. messages from being multicast until all members of the configuration have
  24. unplugged the token. Then queued messages in MED or LOW priority can be
  25. sent, ensuring correct partition operation.
  26. * Implement error creation config file to test GMI since all my lossy
  27. hardware has been fixed.
  28. * Add secrecy/authentication to group messaging interface.
  29. * Add support for multiple rings with gateway ring to ring for added scalability
  30. in LANs.
  31. * Add support for multiple rings with gateway tuned to long haul networks for
  32. added scalability in WANs. Look at spread.org as a design.
  33. * Add support for low delivery-time delay FIFO messages.
  34. * Add support for SAFE ordering.
  35. * Add support for encryption/authentication using Helix. nonce will start
  36. at zero and increment for every message sent or rotation on the ring. Group
  37. key produced using group key generation protocol.
  38. Cluster Membership
  39. ------------------
  40. * Make timeout on SaClmClusterNodeGet work. Currently the timeout is 5
  41. seconds, but the spec requires the timeout to be specified in the API call.
  42. Availability Management Framework
  43. ---------------------------------
  44. * Very Important: Implement configuration change support. This includes partitions.
  45. * Currently the executive can record and manage only one component service
  46. instance per component. As a result, one component cannot act as standby/active
  47. for two other components in the system (AIS Spec page 74 Figure 16. Example of
  48. n+1 redundancy model).
  49. - Fix to follow spec.
  50. * If a user of the AMF library doesn't respond with saAmfResponse, the state
  51. of the application will never change. Fix by adding timeouts to readiness state
  52. and ha state changes to force saAmfResponse state changes triggered.
  53. * Create array namespace for each invocation id per connection to avoid
  54. cross file descriptor contamination.
  55. * Implement resource proxy functions. (currently dummy functions)
  56. * Implement pending operations. (currently dummy functions)
  57. * Implement NWAY and NWAYACTIVE redundancy models.
  58. Checkpointing
  59. -------------
  60. * Very Important: Implement configuration change support. This includes partitions.
  61. * Implement thread support for checkpointing library.
  62. * Implement expiration times on checkpoints.