| |
||
|
||
|
|
Cluster Event Service |
|
||
|
||
|
||
|
||
| The event service is part of cluster software as described in
the OSDL
Cluster Architecture document. The OSDL cluster event service implementation uses the Service Availability Forum event service API as specified in the Application Interface Specification. The code location is bk://bitkeeper.osdl.org/osdlcluster in the event directory. You can also find a tarball of the most recent osdlcluster view Here. Bug reports go to the OSDL developer bugzilla. Select "dev projects" as the catagory. Mailing list for OSDL cluster discussion at: osdlcluster@osdl.org. To sign up for the mailing list go to http://lists.osdl.org/mailman/listinfo/osdlcluster. The implementation of the event service will start out to be a user level daemon using sockets to communicate the event information. In the beginning the event service will use tipc to determine membership but then use the membership service once its implementation is farther along. In any case the event service will probably use tipc name sequences for the socket connections used to transmit event control and data. The SAF event service API will be supported in stages starting with: saEvtEventCallbackT saEvtInitialize saEvtSelectionObjectGet saEvtDispatch saEvtFinalize saEvtChannelOpen saEvtChannelClose saEvtEventAllocate saEvtEventFree saEvtEventDataGet saEvtEventPublish saEvtEventSubscribe saEvtEventUnsubscribe saEvtEventAttributesSet saEvtEventAttributesGet Then later adding: Retention time. saEvtEventRetentionTimeClear Once the user mode implemention is working, a kernel mode component will be written to support in kernel cluster components that need the event service. The To Do list may have more details on the status of the project. Currently working on item 5a) and 10) in the TODO list. Target for completion of task 10 is the week of Aug 6th, 5a is the week of Aug 13th |
| |
|