Hi William, > > The user has a public network of hundreds of machines and 10 of them > > will be used to run a cluster. They are concerned about a broadcast > > going to all of those hundreds of machines to discover the 10 nodes that > belong to the cluster. > > So they would prefer that opensaf talk to just the 10 nodes in that > > cluster without broadcasting to all machines in the network.
Alternatively, using the existing multicast feature of DTM, you can restrict discovery messages by adding those 10 nodes to a reserved multicast group(even though they are in same subnet), so that they will get discovered using multicast messaging. Thanks -Nagu > -----Original Message----- > From: Nagendra Kumar > Sent: 17 August 2014 23:45 > To: William R Elliott; Mathivanan Naickan Palanivelu; Opensaf- > [email protected] > Cc: David S Thompson; Rick Sturm; Steven Graham; Lisa Ann Lentz-Liddell > Subject: Re: [users] Question concerning opensaf broadcasts > > Hi William, > As of now, the broadcast will be received by each > machine in the > subnet. There could be ways(as of now, it is not there) to configure lists of > IP > addresses (in case of TIPC) and allow opensaf talk to configured IPs. Cluster > expansion/shrinking would further require the ways to add/del the nodes IPs at > run time. > > Thanks > -Nagu > > > -----Original Message----- > > From: William R Elliott [mailto:[email protected]] > > Sent: 14 August 2014 23:09 > > To: Mathivanan Naickan Palanivelu; [email protected] > > Cc: Lisa Ann Lentz-Liddell; Rick Sturm; Steven Graham; David S > > Thompson > > Subject: Re: [users] Question concerning opensaf broadcasts > > > > The user has a public network of hundreds of machines and 10 of them > > will be used to run a cluster. They are concerned about a broadcast > > going to all of those hundreds of machines to discover the 10 nodes that > belong to the cluster. > > So they would prefer that opensaf talk to just the 10 nodes in that > > cluster with out broadcasting to all machines in the network. > > > > > > William Elliott | Sr. Analyst, Forward R&D | Office: +1 (800) 519-8360 > > Ext. 3859 > > | Mobile: +1 (407) 619-0337 |--www.NetCracker.com-- Proven Partner to > > Communications Service Providers > > > > -----Original Message----- > > From: Mathivanan Naickan Palanivelu [mailto:[email protected]] > > Sent: Thursday, August 14, 2014 1:21 PM > > To: William R Elliott; [email protected] > > Cc: David S Thompson; Rick Sturm; Steven Graham; Lisa Ann > > Lentz-Liddell > > Subject: RE: [users] Question concerning opensaf broadcasts > > > > Hi, > > A couple of questions inline: > > > > >-----Original Message----- > > >From: William R Elliott [mailto:[email protected]] > > >Sent: Thursday, August 14, 2014 9:34 PM > > >To: [email protected] > > >Cc: David S Thompson; Rick Sturm; Steven Graham; Lisa Ann > > >Lentz-Liddell > > >Subject: [users] Question concerning opensaf broadcasts > > > > > >Hello, > > >We are using opensaf 4.4 and we have a user who's concerned about the > > >broadcasting being done by opensaf. Since the OpenSAF configuration > > > > > > Could you elaborate more on the nature of concern and why: > > 1) Is the concern about number of broadcasts? > > 2)Is the apprehensive anxiety about any sort of broadcast during > > cluster formation, OR Broadcast in an idle cluster OR broadcast during > > a configuration change, OR? > > > > Thanks, > > Mathi. > > > > >contains the list of machines in the cluster is there any way to have > > >opensaf talk directly to these machines and avoid using broadcasts > > >for discovery upon start up regardless of which transport mechanismed used > i.e. > > TCP or TIPC? > > > > > > > > >thanks > > > > > > > > >William Elliott | Sr. Analyst, Forward R&D | Office: +1 (800) > > >519-8360 Ext. 3859 | > > >Mobile: +1 (407) 619-0337 |--www.NetCracker.com-- Proven Partner to > > >Communications Service Providers > > > > > > > > > > > > > > >________________________________ > > >The information transmitted herein is intended only for the person or > > >entity to which it is addressed and may contain confidential, > > >proprietary and/or privileged material. Any review, retransmission, > > >dissemination or other use of, or taking of any action in reliance > > >upon, this information by persons or entities other than the intended > > >recipient is prohibited. If you received this in error, please > > >contact the sender > > and delete the material from any computer. > > >--------------------------------------------------------------------- > > >-- > > >------- _______________________________________________ > > >Opensaf-users mailing list > > >[email protected] > > >https://lists.sourceforge.net/lists/listinfo/opensaf-users > > > > > > ________________________________ > > The information transmitted herein is intended only for the person or > > entity to which it is addressed and may contain confidential, > > proprietary and/or privileged material. Any review, retransmission, > > dissemination or other use of, or taking of any action in reliance > > upon, this information by persons or entities other than the intended > > recipient is prohibited. If you received this in error, please contact the > > sender > and delete the material from any computer. > > > > ---------------------------------------------------------------------- > > -------- _______________________________________________ > > Opensaf-users mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/opensaf-users > > ------------------------------------------------------------------------------ > _______________________________________________ > Opensaf-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/opensaf-users ------------------------------------------------------------------------------ _______________________________________________ Opensaf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-users
