Changes between Version 1 and Version 2 of distributed

05/20/09 05:18:03 (10 years ago)
varun (IP:



  • distributed

    v1 v2  
    6262There are three major parts to the config file. Changes need to be made to each of them in order to set up a distributed instance. Let's look at each section independently. 
    64 === <global> === 
     64 === <global> === 
    6565Every container has a unique guid, specified by the <guid> element. 
    6666The <location> elements tell the container to create soap proxies and stubs for all the actors in the container according to the protocol and url specified. When running a distributed instance, you will have to use the containers real dns name or its IP address instead of localhost. 
    67 === <actors> === 
     67 === <actors> === 
    6868The <actors> section contains one <actor> clause for every actor that will be a part of this container. Each <actor> clause contains every piece of information needed by the container to instantiate and describe the actor. Actors are described by a guid that should be unique system-wide. When running a distributed instance, any actor that will communicate over soap must have a known static guid. More details are in the next section. 
    69 === <topology> === 
     69 === <topology> === 
    7070The <topology> section defines one edge from every actor that is going to request a resource to every actor that will delegate control over that resource. For example, there is an edge from the slice controller to the clearinghouse and from the clearinghouse to the aggregate manager. Every link specifies information about the <from> and <to> actors and for soap, where to find them. 
    8282There are changes to be made in all three major sections of the config file 
    84 === <global> === 
     84 === <global> === 
    8585Make sure the two containers have different guids. Change this in the <guid> element. 
    8686Change the location line to reflect the name of the machine instead of localhost. Keep in mind that this hostname must be resolvable by the other container. For our example, this would look like: 
    95 === <actors> === 
     95 === <actors> === 
    9696Make sure only the actors that are going to be local to this container are being described. Remove the others.  
    128 == <topology> == 
     128 === <topology> === 
    129129In the topology section, you will have to create edges between any actor in the local container and any remote actor, as well as edges between actors entirely within the local container. In our example this means that container1.xml will contain an edge between the local slice controller and the clearinghouse and container2.xml will contain an edge between the remote slice controller and the local clearinghouse as well as an edge between the local clearinghouse and local aggregate manager.