Skip to content

v5.0.x: docs updates #10772

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

Merged
merged 6 commits into from
Sep 9, 2022
Merged

Conversation

jsquyres
Copy link
Member

@jsquyres jsquyres commented Sep 7, 2022

This is the v5.0.x version of #10762.

I'm going to wait until #10771 merges so that I can add it to this PR, and get all those commits in a single PR to v5.0.x.
EDIT: #10771 has been merged, and the commits have been added to this PR.

Trivial change: put the explanation text *before* the example.

Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
(cherry picked from commit 97f848d)
This file was a placeholder and did not contain any useful content,
anyway.

Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
(cherry picked from commit 9bdbe93)
Moved a bunch of MCA-related content out of faq/general-tuning to a
new file in running-apps/tuning.rst.

Removed AMCA documentation because that functionality has morphed into
the "--tuned" functionality.  Indeed, the --am CLI parameter is
silently converted to --tuned.

Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
(cherry picked from commit 6acc2c2)
@jsquyres jsquyres force-pushed the pr/v5.0.x/docs-updates branch from b2c056e to 40685d3 Compare September 7, 2022 01:56
@jsquyres
Copy link
Member Author

jsquyres commented Sep 7, 2022

bot:aws:recheck

@@ -638,7 +162,8 @@ the ``mpi_warn_on_fork`` MCA parameter. For example:
shell$ mpirun --mca mpi_warn_on_fork 0 ...

Of course, systems that ``dlopen("libmpi.so", ...)`` may not use Open
MPI's ``mpirun``, and therefore may need to use :ref:`a different
MPI's ``mpirun``, and therefore may need to use (JMS: this ref no
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Jeff, are you okay merging this into v5.0.x on the assumption that we WILL fixup all of these references before we ship? or would it be better to address now?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is in the FAQ section of the doc, and is destined to go away -- that's why I didn't bother fixing up the ref here.

See :ref:`the role of PMIx and PRRTE
<label-running-role-of-pmix-and-prte>` for more information.

Frameworks
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would this be the appropriate place to discuss how both Open MPI project, along with the PMIx project and the PRRTE project all have individual MCA frameworks?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not all of them may be present or available on your system. You can
use the :ref:`ompi_info(1) <man1-ompi_info>` command to see what
components are included in Open MPI |ompi_ver| on your system.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we include discussion about other MCA frameworks, we could also mention pmix_info(1) and prrte_info() briefly here.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, if we mention that PMIx and PRTE have MCA frameworks of their own (e.g., an in Attention box or something), we could also mention pmix_info and prte_info in another Attention box here, or something).

We'd need to make a new PR to main about this.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I've been thinking about that - users are going to confront a 3-headed world where they do need to know what the various layers do and how they can be directed. You might need a little overview somewhere so they can visualize it.

* Removed a bunch of redundant text and replaced it with links to
  elsewhere in the docs.
* Added developer-level rules of thumb for levels 1-9 of MCA params.
* Added code style documentation; consolidated this and "source code
  tree layout" into a single source-code.rst file.

Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
(cherry picked from commit 67473fc)
Note on the front page that the v5.0.0 docs are on the public web
site, in the tarball, and installed locally.

Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
(cherry picked from commit f33d3d4)
@jsquyres jsquyres marked this pull request as ready for review September 7, 2022 18:48
@jsquyres
Copy link
Member Author

jsquyres commented Sep 7, 2022

@gpaulsen @rhc54 I think those points are valid; I'll make another PR on main about them. I think this PR is fine to merge as-is; the docs are an evolving / living document... 😄 ✏️ 👓

@jsquyres
Copy link
Member Author

jsquyres commented Sep 7, 2022

bot:aws:retest

Signed-off-by: Thomas Naughton <naughtont@ornl.gov>
Co-authored-by: Jeff Squyres <jsquyres@users.noreply.github.com>
(cherry picked from commit 01ac437)
@jsquyres
Copy link
Member Author

jsquyres commented Sep 9, 2022

bot:aws:retest

@awlauria
Copy link
Contributor

awlauria commented Sep 9, 2022

@gpaulsen @rhc54 I think those points are valid; I'll make another PR on main about them. I think this PR is fine to merge as-is; the docs are an evolving / living document... smile pencil2 eyeglasses

Approving and merging based on this.

@awlauria awlauria merged commit 30ae351 into open-mpi:v5.0.x Sep 9, 2022
@jsquyres jsquyres deleted the pr/v5.0.x/docs-updates branch September 9, 2022 21:57
jsquyres added a commit to jsquyres/ompi that referenced this pull request Sep 12, 2022
* Typo fixes
* Add :ref: links to man pages (mostly `mpirun` and `ompi_info`)
* Add notes for contributors about PR'ing to `main` first and then
  cherry-picking to release branches later.  Thanks to @jolivain
  suggesting that we add this policy to the docs.
* Include contributor suggestion to submit fixes to the docs.
* Renamed Developers -> Git to "GitHub, Git, and related topics".
  Added info about:
  * Git commits and a reference to the contributors
    declaration (in contributors.rst)
  * Branching scheme
  * Details about PR to main first and cherry-picking to release
    branches
  * A few words about Github PR CI / MTT
* Added information about running Sphinx, and how to view the Sphinx
  docs locally
* Added notes about how to view man pages locally
* Added a placeholder oshrun.1 man page (it just refers to mpirun.1)
* Per
  open-mpi#10772 (comment),
  discuss PMIx and PRRTE MCA

Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
jsquyres added a commit to jsquyres/ompi that referenced this pull request Sep 19, 2022
* Typo fixes
* Add :ref: links to man pages (mostly `mpirun` and `ompi_info`)
* Add notes for contributors about PR'ing to `main` first and then
  cherry-picking to release branches later.  Thanks to @jolivain
  suggesting that we add this policy to the docs.
* Include contributor suggestion to submit fixes to the docs.
* Renamed Developers -> Git to "GitHub, Git, and related topics".
  Added info about:
  * Git commits and a reference to the contributors
    declaration (in contributors.rst)
  * Branching scheme
  * Details about PR to main first and cherry-picking to release
    branches
  * A few words about Github PR CI / MTT
* Added information about running Sphinx, and how to view the Sphinx
  docs locally
* Added notes about how to view man pages locally
* Added a placeholder oshrun.1 man page (it just refers to mpirun.1)
* Per
  open-mpi#10772 (comment),
  discuss PMIx and PRRTE MCA
* Mention Perl and Python as tools required by Open MPI developers
* Add some advice for downstream packagers:
  * Don't use Open MPI's bundled sub-packages (Libevent, Hwloc, PMIx,
    PRTE)
  * Discussion of components: included in project libraries vs. DSOs
* Add short "prerequisites" section for running MPI apps

Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
jsquyres added a commit to jsquyres/ompi that referenced this pull request Sep 19, 2022
* Typo fixes
* Add :ref: links to man pages (mostly `mpirun` and `ompi_info`)
* Add notes for contributors about PR'ing to `main` first and then
  cherry-picking to release branches later.  Thanks to @jolivain
  suggesting that we add this policy to the docs.
* Include contributor suggestion to submit fixes to the docs.
* Renamed Developers -> Git to "GitHub, Git, and related topics".
  Added info about:
  * Git commits and a reference to the contributors
    declaration (in contributors.rst)
  * Branching scheme
  * Details about PR to main first and cherry-picking to release
    branches
  * A few words about Github PR CI / MTT
* Added information about running Sphinx, and how to view the Sphinx
  docs locally
* Added notes about how to view man pages locally
* Added a placeholder oshrun.1 man page (it just refers to mpirun.1)
* Per
  open-mpi#10772 (comment),
  discuss PMIx and PRRTE MCA
* Mention Perl and Python as tools required by Open MPI developers
* Expanded on some "advice for packagers" from the "required support
  dependencies" section, and moved it to its own section:
  * Don't use Open MPI's bundled sub-packages (Libevent, Hwloc, PMIx,
    PRTE)
  * Discussion of components: included in project libraries vs. DSOs
* Add short "prerequisites" section for running MPI apps

Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
jsquyres added a commit to jsquyres/ompi that referenced this pull request Sep 20, 2022
* Typo fixes
* Add :ref: links to man pages (mostly `mpirun` and `ompi_info`)
* Add notes for contributors about PR'ing to `main` first and then
  cherry-picking to release branches later.  Thanks to @jolivain
  suggesting that we add this policy to the docs.
* Include contributor suggestion to submit fixes to the docs.
* Renamed Developers -> Git to "GitHub, Git, and related topics".
  Added info about:
  * Git commits and a reference to the contributors
    declaration (in contributors.rst)
  * Branching scheme
  * Details about PR to main first and cherry-picking to release
    branches
  * A few words about Github PR CI / MTT
* Added information about running Sphinx, and how to view the Sphinx
  docs locally
* Added notes about how to view man pages locally
* Added a placeholder oshrun.1 man page (it just refers to mpirun.1)
* Per
  open-mpi#10772 (comment),
  discuss PMIx and PRRTE MCA
* Mention Perl and Python as tools required by Open MPI developers
* Expanded on some "advice for packagers" from the "required support
  dependencies" section, and moved it to its own section:
  * Don't use Open MPI's bundled sub-packages (Libevent, Hwloc, PMIx,
    PRTE)
  * Discussion of components: included in project libraries vs. DSOs
* Add short "prerequisites" section for running MPI apps

Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
jsquyres added a commit to jsquyres/ompi that referenced this pull request Sep 20, 2022
* Typo fixes
* Add :ref: links to man pages (mostly `mpirun` and `ompi_info`)
* Add notes for contributors about PR'ing to `main` first and then
  cherry-picking to release branches later.  Thanks to @jolivain
  suggesting that we add this policy to the docs.
* Include contributor suggestion to submit fixes to the docs.
* Renamed Developers -> Git to "GitHub, Git, and related topics".
  Added info about:
  * Git commits and a reference to the contributors
    declaration (in contributors.rst)
  * Branching scheme
  * Details about PR to main first and cherry-picking to release
    branches
  * A few words about Github PR CI / MTT
* Added information about running Sphinx, and how to view the Sphinx
  docs locally
* Added notes about how to view man pages locally
* Added a placeholder oshrun.1 man page (it just refers to mpirun.1)
* Per
  open-mpi#10772 (comment),
  discuss PMIx and PRRTE MCA
* Mention Perl and Python as tools required by Open MPI developers
* Expanded on some "advice for packagers" from the "required support
  dependencies" section, and moved it to its own section:
  * Don't use Open MPI's bundled sub-packages (Libevent, Hwloc, PMIx,
    PRTE)
  * Discussion of components: included in project libraries vs. DSOs
* Add short "prerequisites" section for running MPI apps

Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
jsquyres added a commit to jsquyres/ompi that referenced this pull request Sep 21, 2022
* Typo fixes
* Add :ref: links to man pages (mostly `mpirun` and `ompi_info`)
* Add notes for contributors about PR'ing to `main` first and then
  cherry-picking to release branches later.  Thanks to @jolivain
  suggesting that we add this policy to the docs.
* Include contributor suggestion to submit fixes to the docs.
* Renamed Developers -> Git to "GitHub, Git, and related topics".
  Added info about:
  * Git commits and a reference to the contributors
    declaration (in contributors.rst)
  * Branching scheme
  * Details about PR to main first and cherry-picking to release
    branches
  * A few words about Github PR CI / MTT
* Added information about running Sphinx, and how to view the Sphinx
  docs locally
* Added notes about how to view man pages locally
* Added a placeholder oshrun.1 man page (it just refers to mpirun.1)
* Per
  open-mpi#10772 (comment),
  discuss PMIx and PRRTE MCA
* Mention Perl and Python as tools required by Open MPI developers
* Expanded on some "advice for packagers" from the "required support
  dependencies" section, and moved it to its own section:
  * Don't use Open MPI's bundled sub-packages (Libevent, Hwloc, PMIx,
    PRTE)
  * Discussion of components: included in project libraries vs. DSOs
* Add short "prerequisites" section for running MPI apps

Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
jsquyres added a commit to jsquyres/ompi that referenced this pull request Sep 23, 2022
* Typo fixes
* Add :ref: links to man pages (mostly `mpirun` and `ompi_info`)
* Add notes for contributors about PR'ing to `main` first and then
  cherry-picking to release branches later.  Thanks to @jolivain
  suggesting that we add this policy to the docs.
* Include contributor suggestion to submit fixes to the docs.
* Renamed Developers -> Git to "GitHub, Git, and related topics".
  Added info about:
  * Git commits and a reference to the contributors
    declaration (in contributors.rst)
  * Branching scheme
  * Details about PR to main first and cherry-picking to release
    branches
  * A few words about Github PR CI / MTT
* Added information about running Sphinx, and how to view the Sphinx
  docs locally
* Added notes about how to view man pages locally
* Added a placeholder oshrun.1 man page (it just refers to mpirun.1)
* Per
  open-mpi#10772 (comment),
  discuss PMIx and PRRTE MCA
* Mention Perl and Python as tools required by Open MPI developers
* Expanded on some "advice for packagers" from the "required support
  dependencies" section, and moved it to its own section:
  * Don't use Open MPI's bundled sub-packages (Libevent, Hwloc, PMIx,
    PRTE)
  * Discussion of components: included in project libraries vs. DSOs
* Add short "prerequisites" section for running MPI apps

Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
(cherry picked from commit 061f908)
yli137 pushed a commit to yli137/ompi that referenced this pull request Jan 10, 2024
* Typo fixes
* Add :ref: links to man pages (mostly `mpirun` and `ompi_info`)
* Add notes for contributors about PR'ing to `main` first and then
  cherry-picking to release branches later.  Thanks to @jolivain
  suggesting that we add this policy to the docs.
* Include contributor suggestion to submit fixes to the docs.
* Renamed Developers -> Git to "GitHub, Git, and related topics".
  Added info about:
  * Git commits and a reference to the contributors
    declaration (in contributors.rst)
  * Branching scheme
  * Details about PR to main first and cherry-picking to release
    branches
  * A few words about Github PR CI / MTT
* Added information about running Sphinx, and how to view the Sphinx
  docs locally
* Added notes about how to view man pages locally
* Added a placeholder oshrun.1 man page (it just refers to mpirun.1)
* Per
  open-mpi#10772 (comment),
  discuss PMIx and PRRTE MCA
* Mention Perl and Python as tools required by Open MPI developers
* Expanded on some "advice for packagers" from the "required support
  dependencies" section, and moved it to its own section:
  * Don't use Open MPI's bundled sub-packages (Libevent, Hwloc, PMIx,
    PRTE)
  * Discussion of components: included in project libraries vs. DSOs
* Add short "prerequisites" section for running MPI apps

Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants