Skip to content

Commit f3bea9f

Browse files
committed
Retire the previous containerized Agent example from contrib
and update the README.md.
1 parent a2ad6c2 commit f3bea9f

File tree

7 files changed

+21
-115
lines changed

7 files changed

+21
-115
lines changed
Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1 @@
11
fiotest
2-
*.tmp
3-
var_lib_pbench-agent
Lines changed: 18 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,19 @@
11
# Running a Pbench Agent-driven Workload in a Container
2-
1. Create a workload script (`example-workload.sh` can be used to start)
3-
This script performs the invocation of a Pbench Agent workload driver, e.g.
4-
`pbench-user-benchmark`, or `pbench-fio`, or `pbench-uperf`.
5-
2. Setup the local execution environment to be aware of the target Pbench Server
6-
`./setup.sh <pbench server host name>:<port number>`
7-
3. Execute the workload
8-
Typically this script performs the necessary setup required for the
9-
containerized environment (`example-driver.sh` can be used to start, note
10-
that it also moves the results to the Pbench Server).
2+
3+
The Pbench Agent is available for use in a zero-installation scenario
4+
via containerized execution. Agent containers are available from
5+
[quay.io/pbench](https://quay.io/organization/pbench): there's a
6+
repository for each distribution (e.g.,
7+
[pbench-agent-all-centos-9](https://quay.io/repository/pbench/pbench-agent-all-centos-9?tab=tags))
8+
with tags for each Agent release as well as for "hot builds" for
9+
each development branch.
10+
11+
The `pbench` script provided here is a wrapper which facilitates
12+
the invocation of a Pbench Agent command using a containerized
13+
deployment of the Pbench Agent. Simply prefix a Pbench Agent
14+
command line with the path to this script to run it inside a
15+
container, without needing to install the Agent on the host
16+
system. (This is easily done by defining a shell alias for it.)
17+
18+
The provided `pbench_demo` script shows the sequence of commands
19+
which might be used to perform a `fio` benchmark run.

contrib/containerized-pbench/example-driver.sh

Lines changed: 0 additions & 45 deletions
This file was deleted.

contrib/containerized-pbench/example-workload.sh

Lines changed: 0 additions & 19 deletions
This file was deleted.

contrib/containerized-pbench/mover.sh

Lines changed: 0 additions & 11 deletions
This file was deleted.

contrib/containerized-pbench/pbench_demo

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,13 +12,13 @@
1212
# here because we're not using the default image).
1313
#-
1414
shopt -s expand_aliases
15-
alias pbench=$(git rev-parse --show-toplevel)/contrib/containerized-pbench/pbench
15+
alias pbench="$(git rev-parse --show-toplevel)"/contrib/containerized-pbench/pbench
1616

1717
FIOTEST=${PWD}/fiotest
1818
export PB_AGENT_PODMAN_OPTIONS="--pull newer -v ${FIOTEST}:/fiotest:z"
1919
export PB_AGENT_IMAGE_NAME=quay.io/pbench/pbench-agent-all-fedora-36:main
2020

21-
mkdir -p ${FIOTEST}
21+
mkdir -p "${FIOTEST}"
2222

2323
# Before we run the demo, we need a Pbench API key. The key can be an
2424
# environment variable of PBENCH_API_KEY or need to be supplied to this
@@ -28,6 +28,7 @@ if [[ -z "${api_key}" ]]; then
2828
echo "Pbench API key must be provided, either on the command line or via the PBENCH_API_KEY environment variable"
2929
exit 2
3030
fi
31+
3132
#+
3233
# Run the demo!
3334
#-

contrib/containerized-pbench/setup.sh

Lines changed: 0 additions & 27 deletions
This file was deleted.

0 commit comments

Comments
 (0)