Lei, I am not sure if this would work but SAF Msg Queue Service provides the concept of "Message Queue Groups" that are actually meant for load-sharing. So you could have a SIP Server front-end with a virtual IP receiving the SIP Invite requests and then using the Message Groups in the backend to do the load sharing among all your nodes. Sayan
________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Qiao, Lei (TSG-GDCC-CMEP/SH) Sent: Wednesday, October 31, 2007 3:07 AM To: Chad Tindel Cc: [email protected] Subject: [Users] ??: ??: ??: Does OpenSAF support virtual IP? Thank you Chad. LVM seems to be a solution but I need go deeper about it. Actually I don't think the Load-balancing Methods of LVM can meet the specific requirement. For example, in most cases the granularity of load-balancing is the "Call", or only requests that initiate a dialog(like sip INVITE) , not only the requests or simply messages. I think in these cases we should develop the distribution algorithm and I don't know if LVM has the mechanism can support user's customized message distribution algorithm. Or perhaps we have to find another way out. Best Regards, Qiao Lei while(1){ Problem *newProblem = new Problem(); solveProblem(newProblem); cout<<"This is the life!"<<endl; } 尽力而为还不够，得竭尽全力才行。 发件人: Chad Tindel [mailto:[EMAIL PROTECTED] ________________________________ 发送时间: 2007年10月31日 13:36 收件人: Qiao, Lei (TSG-GDCC-CMEP/SH) 抄送: Murthy E-G19462; [email protected] 主题: Re: 答复: [Users] 答复: Does OpenSAF support virtual IP? Sorry for the late response and thank you two. Yes, both of you are right. Firstly, I am concerning that several application nodes can use one virtual IP to provide services, this seems can be done by OpenSAF interface service, which says "IP Address Virtualization (VIP) provides a mechanism to associate a virtual IP address with a particular application. The virtual IP address moves along with the application across the nodes." What Chad talks about is my second consideration(sorry I don't put it clearly, but it is important), it is about something like a load-balancer between the remote applications and the cluster which runs several application nodes, the remote applications can access the service provided by the cluster via one IP, but the traffic is distributed among the application nodes in the cluster. We don't want only one application node in the cluster keeps busy and the other N-1 nodes are just standby. Right. So each SIP server instance needs its own distinct IP address and runs active/active/active on every payload. The LVS would be configured as a 2N redundancy with a single IP, representing the IP address that the clients talk to. Chad
_______________________________________________ Users mailing list [email protected] http://list.opensaf.org/maillist/listinfo/users
