[Vrs-development] Cluster Management

[Ian Fung]

so i was looking at the plans for the CM. got some questions. we are
looking for a way to allow for LDS's to join/leave/etc the vrs. now i
dont know if this actually falls under the role of the cm, but i think
there should be a more intelligent way to handle communications between
LDS's. i had read in the archives that the idea was to have each LDS
keep a list of all other LDS's that is in the vrs. that seems like it
doesn't scale well. why does a certain LDS need to be aware of all other
LDS's? if say it received a request for a service it doesnt have, why
doesnt it just forward the request to another LDS. any given LDS can
just maintain a list of LDS's that are close to it. this can be in the
spirit of a dynamic routing protocol such as AODV. you can set up
forward and backward paths when you try to look for a service. has
anyone thought about doing this that way? if an LDS doesnt care about
maintaining a list of all other LDS nodes and discovery is done
dynamically, it will actually make things a lot easier. there are going
to be a lot of issues regarding how you would actually maintain the list
and what counts as an up-to-date list. for example if an LDS leaves the
vrs, its going to take a discrete amount of time before that information
is propagted to other LDS's. so what is considered as the current
version of the LDS list?