-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Use consistent CLI flags for exporter (#144)
* refactor: Use consistent CLI flags for exporter * Add deprecate notices for old flags when used * Update docs with new flags * refactor: Make starting debug server configurable * Run debug server on separate port only on localhost by default --------- Signed-off-by: Mahendra Paipuri <[email protected]>
- Loading branch information
1 parent
2a6b79f
commit 3a71e26
Showing
11 changed files
with
270 additions
and
174 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,22 +1,22 @@ | ||
# SLURM epilog and prolog scripts | ||
|
||
CEEMS exporter needs to perform few privileged actions to collect certain information of | ||
CEEMS exporter needs to perform few privileged actions to collect certain information of | ||
compute units. An example [systemd service file](https://github.com/mahendrapaipuri/ceems/blob/main/build/package/ceems_exporter/ceems_exporter.service) | ||
provided in the repo shows the linux capabilities necessary for these privileged actions. | ||
provided in the repo shows the linux capabilities necessary for these privileged actions. | ||
|
||
If the operators would like to avoid privileges on CEEMS exporter and run it fully in | ||
userland an alternative approach, in SLURM context, is to use Epilog and Prolog scripts | ||
to write the necessary job information to a file that is readable by CEEMS exporter. | ||
If the operators would like to avoid privileges on CEEMS exporter and run it fully in | ||
userland an alternative approach, in SLURM context, is to use Epilog and Prolog scripts | ||
to write the necessary job information to a file that is readable by CEEMS exporter. | ||
This directory provides those scripts that should be used with SLURM. | ||
|
||
An example [systemd service file](https://github.com/mahendrapaipuri/ceems/blob/main/init/systemd/ceems_exporter_no_privs.service) | ||
is also provided in the repo that can be used along with these prolog and epilog scripts. | ||
An example [systemd service file](https://github.com/mahendrapaipuri/ceems/blob/main/init/systemd/ceems_exporter_no_privs.service) | ||
is also provided in the repo that can be used along with these prolog and epilog scripts. | ||
|
||
> [!IMPORTANT] | ||
> The CLI arguments `--collector.slurm.job.props.path` and `--collector.slurm.gpu.job.map.path` | ||
are hidden and cannot be seen in `ceems_exporter --help` output. However, these arguments | ||
> The CLI arguments `--collector.slurm.job-props-path` and `--collector.slurm.gpu-job-map-path` | ||
are hidden and cannot be seen in `ceems_exporter --help` output. However, these arguments | ||
exists in the exporter and can be used. | ||
|
||
Even with such prolog and epilog scripts, operators should grant the user running CEEMS | ||
exporter permissions to run `ipmi-dcmi` command as this command can be executable by only | ||
`root` by default. | ||
Even with such prolog and epilog scripts, operators should grant the user running CEEMS | ||
exporter permissions to run `ipmi-dcmi` command as this command can be executable by only | ||
`root` by default. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.