Skip to content

move down jobid,vpid from ORTE to OPAL layer #249

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

ggouaillardet
Copy link
Contributor

opal_process_name_t is now an union of :

  • opal_identifier_t (id)
  • opal_proc_name_t (name)
    and orte_process_name_t is typedef'ed to opal_proc_name_t

the OPAL_NAME DSS type was introduced in order to correctly pack/unpack
an opal_process_name_t on an heterogeneous cluster

@rhc54 @bosilca this is working proof of concept to move jobid/vpid from the ORTE into the OPAL layer

opal_process_name_t is now an union of :
 * opal_identifier_t (id)
 * opal_proc_name_t (name)
and orte_process_name_t is typedef'ed to opal_proc_name_t

the OPAL_NAME DSS type was introduced in order to correctly pack/unpack
an opal_process_name_t on an heterogeneous cluster
@mellanox-github
Copy link

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
http://bgate.mellanox.com/jenkins/job/gh-ompi-master-pr/5/

Build Log
last 50 lines


Test FAILed.

@ggouaillardet
Copy link
Contributor Author

#261 is a better implementation that obsoletes this PR

jsquyres pushed a commit to jsquyres/ompi that referenced this pull request Sep 21, 2016
Protect the tools from PMI environments by ensuring they use the "tool" ess component
dong0321 pushed a commit to ICLDisco/ompi that referenced this pull request Oct 8, 2019
Be a little less restrictive on interface requirements
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants