-
Notifications
You must be signed in to change notification settings - Fork 108
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
update readthedocs config and add installation docs #3436
Changes from all commits
9827b40
5cc4789
8e53d17
757a5b5
7965a33
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
# Ansible based installation | ||
|
||
In the following: we describe how to install Pbench Agent using an ANSIBLE playbook. | ||
|
||
:::{note} | ||
The same Pbench Agent version must be installed on all the test systems that participate in a benchmark run, there is no support for mixed installations. | ||
::: | ||
|
||
## Setup | ||
|
||
1. Make sure that you have the ANSIBLE package installed. | ||
|
||
2. Install the `pbench.agent` ANSIBLE collection from Ansible Galaxy. | ||
|
||
```console | ||
ansible-galaxy collection install pbench.agent | ||
``` | ||
|
||
3. Tell ansible where to find these roles. | ||
Comment on lines
+13
to
+19
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Line 19 still references "ansible" with a spelling different from that used in lines 13, 11, and 3. |
||
|
||
```console | ||
export ANSIBLE_ROLES_PATH=$HOME/.ansible/collections/ansible_collections/pbench/agent/roles:$ANSIBLE_ROLES_PATH | ||
``` | ||
|
||
4. Create an inventory file (`~/.config/Inventory/myhosts.inv`) naming the hosts on which you wish to install Pbench Agent and the location of the config file. Example [inventory file](assets/myhosts.inv). | ||
|
||
:::{note} | ||
if you're planning to push performance data to a 0.69 Pbench Server, you need to specify the server's private RSA key. Example [inventory file](assets/0.69_myhosts.inv). | ||
::: | ||
|
||
5. Use the [example playbook](https://github.com/distributed-system-analysis/pbench/blob/main/agent/ansible/playbooks/pbench_agent_install.yml) or reference it to customize your own. | ||
|
||
6. Run the playbook. | ||
|
||
```console | ||
ansible-playbook -i ~/.config/Inventory/myhosts.inv pbench_agent_install.yml | ||
``` |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,11 @@ | ||
[servers] | ||
<host1> | ||
<host2> | ||
<host3> | ||
|
||
[servers:vars] | ||
# where to get the key | ||
pbench_key_url = <url> | ||
|
||
# where to get the config file | ||
pbench_config_url = <url> |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
[servers] | ||
<host1> | ||
<host2> | ||
<host3> | ||
|
||
[servers:vars] | ||
# where to get the config file | ||
pbench_config_url = <url> |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,23 @@ | ||
# Pbench containers | ||
|
||
# Pbench Agent Container | ||
|
||
Pbench Agent is available as container images on [Quay.io](https://quay.io/organization/pbench). This makes Pbench Agent a distro-independent solution and it could also be used in any containerized ecosystem. | ||
|
||
**Want to build container images from sources?** | ||
Follow [README](https://github.com/distributed-system-analysis/pbench/blob/main/agent/containers/images/README.md) | ||
|
||
Running Pbench Agent container is as simple as | ||
```console | ||
podman run quay.io/pbench/pbench-agent-all-centos-8 | ||
``` | ||
Depending on the use cases one has to run these containers with privileged mode, host network, pid, ipc, mount required volumes, etc. | ||
|
||
Example: | ||
```console | ||
podman run --name pbench --rm -ti --privileged --ipc=host --net=host --pid=host -e HOST=/host -e NAME=pbench -e IMAGE=quay.io/pbench/pbench-agent-all-centos-8 -v /run:/run -v /var/log:/var/log -v /etc/machine-id:/etc/machine-id -v /etc/localtime:/etc/localtime -v /:/host quay.io/pbench/pbench-agent-all-centos-8 | ||
``` | ||
|
||
:::{note} | ||
The volumes and config shown in the command snippet above may vary depending on users needs. | ||
::: | ||
|
||
Possibilities are endless, please give it a try <https://quay.io/organization/pbench>. |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,43 @@ | ||
# RPM based installation | ||
|
||
The Pbench Agent requires the installation of some generic bits, but it also | ||
requires some localization. It needs to know where to send the results for | ||
storage and analysis, and it needs to be able to authenticate to the results | ||
server. | ||
|
||
The generic bits are packaged as an RPM, available from | ||
[COPR](https://copr.fedorainfracloud.org/coprs/ndokos). | ||
Pbench Agent is built for all major releases of | ||
Fedora, RHEL, CentOS and openSUSE. | ||
|
||
In the following, we describe how to install Pbench Agent using an RPM. | ||
|
||
## Setup | ||
|
||
1. Enable required repos. | ||
|
||
```console | ||
dnf copr enable ndokos/pbench-0.72 | ||
dnf copr enable ndokos/pbench | ||
``` | ||
|
||
:::{note} | ||
- We release Pbench Agent RPMs under the `ndokos` COPR account with repos following the pattern `pbench-<release>`. | ||
- There are some RPMs that are shared between versions (e.g. pbench-sysstat). We maintain those in [ndokos/pbench](https://copr.fedorainfracloud.org/coprs/ndokos/pbench) repo. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. As per the earlier discussion, we should probably omit the hyperlink here. (If you want the user to be able to browse, we should direct them to the This text would read better if you inserted the word "the" before "nodokos". I would put |
||
- On a RHEL-based system enable the subscription manager and enable the `EPEL` repo. | ||
::: | ||
|
||
2. Install Pbench Agent package | ||
|
||
```console | ||
dnf install pbench-agent | ||
``` | ||
|
||
3. Restart terminal/shell session so that all environment varibales and PATH variables are updated | ||
|
||
or | ||
|
||
```console | ||
source /etc/profile.d/pbench-agent.sh | ||
``` | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -6,4 +6,5 @@ User Guide | |
|
||
getting_started | ||
UserGuide | ||
man_page | ||
man_page | ||
guides/end-to-end-workflow |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -43,6 +43,7 @@ | |
"sphinx.ext.autosectionlabel", | ||
"sphinx_design", | ||
"myst_parser", | ||
"sphinx_copybutton", | ||
Comment on lines
43
to
+46
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It would be good to keep these entries in order. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. These still need to be ordered, e.g.
|
||
] | ||
|
||
# Add any paths that contain templates here, relative to this directory. | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,5 @@ | ||
sphinx-design | ||
myst-parser | ||
sphinx-copybutton | ||
sphinx-rtd-theme | ||
myst-parser | ||
sphinx-design | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That comma should be a colon or m-dash (or period).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wasn't sufficiently specific...my apologies, @vishalvvr!
The comma at line 3 was fine; it's line 6 which needs the change. (Please change line 3 back.... 😊)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Line 3: remove the colon, and possibly remove the "In the following" phrase, since it's kind of obvious. If the result doesn't read well, try something like "This document describes" (which allows us to escape using the first-person pronoun).
Line 6: the comma should be replaced by a colon or m-dash (or period).