On Jun 25, 2009, at 9:30 AM, Iain Bason wrote:
On Jun 25, 2009, at 11:10 AM, Ralph Castain wrote:
They do flow along the route at all times. However, without static
ports the orted has to start by directly connecting to the HNP and
sending the orted's contact info to the HNP.
This is th
On Jun 25, 2009, at 11:10 AM, Ralph Castain wrote:
They do flow along the route at all times. However, without static
ports the orted has to start by directly connecting to the HNP and
sending the orted's contact info to the HNP.
This is the part I don't understand. Why can't they send th
They do flow along the route at all times. However, without static
ports the orted has to start by directly connecting to the HNP and
sending the orted's contact info to the HNP. Then the HNP includes
that info in the launch msg, allowing the orteds to wireup their routes.
So the difference
On Jun 23, 2009, at 7:17 PM, Ralph Castain wrote:
Not any more, when using regex - the only message that comes back is
one/node telling the HNP that the procs have been launched. These
messages flow along the route, not direct to the HNP - assuming you
use the static port option.
Is ther
On Jun 23, 2009, at 5:10 PM, Ralph Castain wrote:
I agree - hence my comments the other day.
However, you might look at the regex work that is on-going. My plan
was to utilize the regex to tell the child daemons of the tree what
to launch, and then use the static ports to complete the wire
Should have pointed something out here...
On Jun 23, 2009, at 4:10 PM, bosi...@osl.iu.edu wrote:
The solution is to add a new option to the children orte_parent_uri,
which
is only set when the orted is _not_ directly spawned by the HNP.
When this
option is present on the argument list, the
I agree - hence my comments the other day.
However, you might look at the regex work that is on-going. My plan
was to utilize the regex to tell the child daemons of the tree what to
launch, and then use the static ports to complete the wireup along the
route. Thus, the HNP would only see me
