gistfile1.txt

[
    {
	"name" : "watermark",
	"exec" : {
	        "path": "swift://AUTH_f6d34e39-ae2b-4d29-96f6-c35d70d8a4ca/watermark/watermark"
    },
	"file_list" : [
	    {"device": "stdin",
	     "path": "swift://AUTH_f6d34e39-ae2b-4d29-96f6-c35d70d8a4ca/watermark/space.jpg"},
	    {"device": "stdout",
	    "content_type": "message/cgi"},
	    {"device": "stderr"},
	    {"device": "input",
	    "path": "swift://AUTH_f6d34e39-ae2b-4d29-96f6-c35d70d8a4ca/watermark/logo.jpg"
	    }
	]
    }
]

Ron, I am new to using GitHub. I am looking at the zerovm network Broker. I have a distributed JOIN use case that needs many pt-2-pt connections between VMs (1000). I barely understand how Channels are defined in the manifest. One thing for sure, I won't know the network topology until after the VM are instantiated. I also need something like UDP broadcast. I posted my use case on the zerovm Google Group. Can you point me to some usage docs on Broker.

I need to construct a execution Tree, that starts on leaf nodes and merges with the parent until finally reaching the root. Its really similar to the classic Sort-Merge JOIN. I construct the leaf nodes from all the TABLE paritions, but can't know which VM nodes need to be paired until runtime. So I can't specify the Channels until runtime.

Thanks
David Holland