| |
|
|
| Cluster Membership Service |
| The membership service is part of cluster software as
described in the OSDL
Cluster Architecture document. The OSDL cluster membership service implementation uses the Service Availability Forum Cluster Membership Service API as specified in the Application Interface Specification. The code location is bk://bitkeeper.osdl.org/osdlcluster. The most recently completed milestone: Verify TIPC multicast works from
the TIPC development tree. Done, but still needs stability work.
The next milestone being worked on: Use multicast to send
connectivity information between nodes as part of the membership
protocol.
The To
Do list may have more details on the status of the project. Target date is May 7, 2004. Dynamic_Voting_for_Cluster_Membership.pdf describes how the dynamic voting will be used for membership. 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 membership service will start out as a user level daemon. The intent is to use full connectivity and quorum to determine membership and guarantee consistency with dyanmic voting to define quorums adaptively and dynamically account for the set of nodes. This is descibed in the paper "Dynamic Voting for Consistent Primary Components" by Lotem, Keidar, and Dolev." The first step will be to simulate a cluster by sending connectivity information to the membership service and simulating membership protocol messages and verifying the membership algorthms work. After this, the membership service will probably use TIPC to get node connection information and to broadcast/multicast membership protocol messages between nodes. The SAF Cluster Membership Service API will be supported: saClmInitialize saClmSelectionObjectGet saClmDispatch saClmFinalize saClmTrackStart saClmTrackStop saClmClusterNodeGet saClmClusterNodeGetAsync Once the user mode implemention is working, a kernel mode membership component will be written. If possible, the SAF Membership Service API will be provided for in-kernel components. The API will be supported in user-mode. |
| |
|