It's my fault - as release manager, I should have spotted that component 
sneaking into the release branch back in the 1.7 series, but I missed it. I 
have deleted it now as it was never intended to be released.

Sorry for the confusion.
Ralph

On May 15, 2014, at 8:33 PM, Hadi Montakhabi <hadi.montakh...@gmail.com> wrote:

> Ralph is right.
> I used 1.8, and after digging into it, I noticed it doesn't even compile the 
> pmi component. When I tried to configure without orte, I could see the errors 
> while compiling.
> It looks like it is well broken!
> 
> Peace, 
> Hadi
> 
> On May 15, 2014 7:28 PM, "Ralph Castain" <r...@open-mpi.org> wrote:
> Josh - he's talking about the PMI component in ompi/mca/rte. It generally 
> doesn't work.
> 
> 
> On May 15, 2014, at 5:15 PM, Joshua Ladd <jladd.m...@gmail.com> wrote:
> 
>> Hadi, 
>> 
>> Is your job launching and executing normally? During the launch, frameworks 
>> are initialized by opening all components, selecting the desired one, and 
>> closing the others. I think you're just seeing components being opened, 
>> queried, and ultimately closed. The important thing is knowing if PMI was 
>> selected.  Set: -mca ess_base_verbose 5 -mca plm_base_verbose 5 -mca 
>> grpcomm_base_verbose 5.  
>> 
>> Josh   
>> 
>> 
>> On Thu, May 15, 2014 at 4:13 PM, Ralph Castain <r...@open-mpi.org> wrote:
>> I wouldn't trust that PMI component in the RTE framework - it was only 
>> created as a test example for that framework. It is routinely broken and not 
>> maintained, and can only be used if forced.
>> 
>> Is this on the trunk? Or are you using the 1.8 series? If the latter, that 
>> component shouldn't even be there.
>> 
>> 
>> On May 15, 2014, at 1:09 PM, Hadi Montakhabi <hadi.montakh...@gmail.com> 
>> wrote:
>> 
>>> By "goes through orte component", I meant it does go into rte_orte_open 
>>> function in rte_orte_component.c.
>>> Let me try to formulate my question in a different way:
>>> There are two components in the rte framework, namely orte and pmi.
>>> The question is whether pmi could be used independent from orte? Or it 
>>> needs orte to function?
>>> 
>>> Peace,
>>> Hadi
>>> 
>>> 
>>> On Thu, May 15, 2014 at 2:59 PM, Ralph Castain <r...@open-mpi.org> wrote:
>>> What do you mean "goes through orte component"? It will still call into the 
>>> orte code base, but will use PMI to do the modex.
>>> 
>>> On May 15, 2014, at 12:54 PM, Hadi Montakhabi <hadi.montakh...@gmail.com> 
>>> wrote:
>>> 
>>>> Hello,
>>>> 
>>>> I am trying to utilize pmi instead of orte, but I come across the 
>>>> following problem.
>>>> I do configure using --with-slurm=[slurm installation path] and 
>>>> --with-pmi=[slurm installation path].
>>>> 
>>>> After compiling, I run the executable using:
>>>> $srun -n 2 --mpi=pmi2 ./executable
>>>> 
>>>> However, this still goes through orte component, not the pmi.
>>>> Am I missing something when I configure?
>>>> 
>>>> Peace,
>>>> Hadi
>>>> _______________________________________________
>>>> users mailing list
>>>> us...@open-mpi.org
>>>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>>> 
>>> 
>>> _______________________________________________
>>> users mailing list
>>> us...@open-mpi.org
>>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>>> 
>>> _______________________________________________
>>> users mailing list
>>> us...@open-mpi.org
>>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>> 
>> 
>> _______________________________________________
>> users mailing list
>> us...@open-mpi.org
>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>> 
>> _______________________________________________
>> users mailing list
>> us...@open-mpi.org
>> http://www.open-mpi.org/mailman/listinfo.cgi/users
> 
> 
> _______________________________________________
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
> _______________________________________________
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users

Reply via email to