From a80d396257e931c942c847293127c3bf6c1974b7 Mon Sep 17 00:00:00 2001 From: Nick Dokos Date: Tue, 6 Jun 2023 16:01:36 -0400 Subject: [PATCH] Release docs - v0.72.0 release notes - v0.72.1.release notes - release checklist (greatly expanded but still WIP) - sample announcement (TBD) PBENCH-1129 --- docs/release/checklist.org | 141 +++++++++++++++++ docs/release/sample-announcement.txt | 168 +++++++++++++++++++++ docs/release/v0.72.0-relnotes.md | 216 +++++++++++++++++++++++++++ docs/release/v0.72.1-relnotes.md | 5 + 4 files changed, 530 insertions(+) create mode 100644 docs/release/checklist.org create mode 100644 docs/release/sample-announcement.txt create mode 100644 docs/release/v0.72.0-relnotes.md create mode 100644 docs/release/v0.72.1-relnotes.md diff --git a/docs/release/checklist.org b/docs/release/checklist.org new file mode 100644 index 0000000000..d85c272674 --- /dev/null +++ b/docs/release/checklist.org @@ -0,0 +1,141 @@ +#+TITLE: Release checklist + +* Clone the release branch + +#+begin_src shell + git checkout upstream/b0.72 + git branch -u upsream/b0.72 +#+end_src +so an update and rebase will get you to the latest commit on the upsream branch. + +* Test +** (Step 1) Build an RPM in the COPR -test repo + +Make sure that =agent/VERSION= in the branch reflects the release version (e.g. 0.72.0). +That will allow the =make= invocation below to create properly named RPMs (e.g. =pbench-agent-pbench-agent-0.72.0-1gXXXXXXX) +in the appropriate repo (=pbench-0.72-test= in this case) +#+begin_src shell + cd agent/rpm + make copr-test +#+end_src + +** (Step 2) Create VMs of various stripes for testing and prep them appropriately +(e.g. ssh keys need to be installed for ansible to work and repos need to be installed (e.g CRB repos on RHEL-8 and RHEL-9 and EPEL repos). + + +** (Step 3) Run the playbooks to do the prep, repo install, pbench-agent/pbench-systat install, the config of the agent and the firewall rules +TBD + +** (Step 4) Run the smoke tests +TBD + +** (Step 5) Run end-to-end tests +TBD linpack, uperf, fio: register tools, run the benchmark, clean up the +tools, push the results. + +* Lather, rinse, repeat +Repeat steps 3-5 in the [[* Test][Test]] section above until there are no +errors. In general, you /might/ have to rebuild the RPMs in Step 1 if +any changes to pbench code were made, but you probably do not need to +remake the VMs in Step 2, although you might need to either uninstall the +previous RPM or make sure that the build number of the new RPM is +bumped, so that `dnf` will know to update the installed RPM. + +* Commit any changes to the release branch + +If there are changes to pbench code, issue PRs for them and make +sure that they are merged. You might want to do another run through +the [[* Test][Test]] process before proceeding further. + +It may also be necessary to update the ansible roles on Galaxy: +#+begin_src shell + cd agent/ansible + make test + make publish +#+end_src + +Galaxy will refuse to update unless the version in +=agent/ansible/collection/galaxy.yml= is bumped (the current version +as of this writing is 1.0.10). + +* Write up release notes - submit for review +Revise until everybody is OK with the release notest. + +The release notes should contain: +- a short description of the release + +- installation notes identifying any user-visible changes to the installation process and the ansible roles + +- new commands and major changes to existing commands + +- a list of user-visible bug fixes and enhancements to individual programs + +- new deprecation notices and retirement notices of previously deprecated items + +- an optional section on future directions + +- a changelog of all the relevant commits since the last release + +The changelog can be obtained using something like =git v0.71.0..HEAD +--oneline --no-decorate=, but it will need to be manually pruned to +include only commits for the relevant component(s). + +Nobody will be happy with the release notes but do not sweat it too +much at this point: the release notes will be committed to the branch +after the release is cut and they can be revised again and again, even +after the release. + +* Make sure there are no pending updates to the release branch. +The only other change that should go in before the release is cut should be +the version bump in e.g. =agent/VERSION=. Do this in a separate commit. + +* Add a tag and cut the release on GitHub, adding the release notes. +From the top level of the repo on Github, click on "Releases" on the RHS. + +Click on "Draft a new release" and add a new tag.The tag should have +the form =v0.72.0=. Make sure that it points to the top of the release +branch, presumably to the commit that bumps the version in the VERSION +file. + +Modify the release notes to include the correct SHA1 from the top +of the release branch. Do *not* commit the release notes yet. +Instead cut-and-paste the contents to the text box of the new release +and add a title (try to be consistent with earlier releases). + +Make sure that the "Set as the latest release" box is checked and then +click on "Publish Release". + +* Retest +Redo the [[* Test][Test]] section above in the updated branch, creating the RPMs +in the final COPR repo. + +** Rebuild RPMs in the COPR repo for the release +#+begin_src shell + cd agent/rpm + make copr +#+end_src + +** Redo steps 3-4 +Install the RPMs on the set of VMs and run the smoke tests. If there +are problems, you will have to repeat the whole process up to this +point. + +** Build tagged containers + +#+begin_src shell + cd agent/containers/images + make everything + make push + make push-latest +#+end_src + +** Send announcement out + +See the boilerplate =docs/release/sample-announcement.txt= in this +directory for an example. + +** Submit post-release PR to the release branch +The commit should contain the updated release notes. If problems are +found later on, the release notes can be updated with more commits and +copied the same way as before into the text box of the release area on +Github. diff --git a/docs/release/sample-announcement.txt b/docs/release/sample-announcement.txt new file mode 100644 index 0000000000..56993c9739 --- /dev/null +++ b/docs/release/sample-announcement.txt @@ -0,0 +1,168 @@ +* Sample announcement for reference + + +Subject: Release of version 0.71 of the pbench-agent is now available +To: + + +We are pleased to announce the release of version 0.71 of +pbench-agent. There are some gotchas and known problems that are +described first: please read them carefully because you are almost +certainly going to run into one or more of them. + + +- The notion of a "default" tool set is being deprecated and will be +removed in the upcoming Pbench Agent v1.0 release. To replace it, the +Pbench Agent is introducing a few named tool sets. See "Default Tool +Set is Deprecated; Named tool sets introduced" in the Release Notes. + +- All tools registered prior to installing v0.71.0 must be +re-registered; tools registered locally, or remotely, on a host with +v0.69 or earlier version of the pbench-agent will be ignored. See +"Tool registration kept local to the host where registration happens" +in the Release Notes. + +- Note that pbench no longer installs tools: any missing tools will +only be found and reported when you start a run. + + + + +In addition, there are some known problems with specific distros: + +- The (currently unreleased) RHEL 9.1 version has very spotty coverage + in its Subscription Manager repos. Installation of pbench-agent on + it fails with missing basic packages (e.g. bzip2). There are + probably unofficial repos that could be used instead: this is under + investigation. + +- Installation on Fedora 36 succeeds but you will not be able to do + anything with it: Python 3.10 changed the way that pip install modules + (it inserts a "local" element in the path), so the PYTHONPATH settings + are wrong and modules cannot be found. This is a larger problem and we + are working on that, but the upshot is that you won't be able to use + Fedora 36 with this release. + +- You should upgrade the pbench Ansible roles with + + ansible-galaxy collection install --force pbench.agent + + If your version of ansible-galaxy does not support --force, delete + the existing roles and install: + + rm -rf $HOME/.ansible/collections/ansible_collections/pbench/agent + ansible-galaxy collection install pbench.agent + + The current version is 1.0.7. It contains a fix for the CentOS-Stream-8 + distro: without that fix, you are not going to be able to use the playbooks + to install on that distro. + +- If you are upgrading from v0.69, there is one additional problem: + the v0.69 installation probably installed the `pbench-perl-JSON-XS' + RPM, our own build of perl-JSON-XS which was missing from all RHEL + plaforms. It (and many other perl packages) is now available from + standard repos (EPEL on RHEL7, CRB (Codeready Builder) repo on + RHEL8/9, PowerTools repo on Centos-stream-8/9). However, the + installed `pbench-perl-JSON-XS' on v0.69 conflicts with the official + `perl-JSON-XS', so the RPM installation fails. The workaround is to + erase the `pbench-perl-JSON-XS' RPM before updating to v0.71.0: + + $ yum shell + > erase pbench-perl-JSON-XS + > update pbench-agent + + That's the best way to do it on a single system, but if you have a + lot of systems that you are installing to, it's probably easier to + use your inventory file to do the erasing with an ad-hoc Ansible + command and then install normally: + + ansible -i /path/to/Inventory/file servers -m command -a 'yum erase -y pbench-perl-JSON-XS' + ansible-playbook -i /path/to/Inventory/file pbench-agent-install.yml + +- Installing on RHEL 8.4 and 8.5 fails because of the ansible-core + dependency. There are more problems with the ansible package on + RHEL78.4 and 8.5 however: see + + https://access.redhat.com/discussions/6962395 + + If you cannot upgrade to RHEL 8.6, let us know: we might be able to + help. + + + + + +The RPMs are available in the main COPR pbench repo: + + https://copr.fedorainfracloud.org/coprs/ndokos/pbench/ + +We strongly recommend that you use Ansible playbooks to install pbench-agent. +See below for the link to the Installation Guide. + +You are going to need an inventory file. Here's a template: just list +the hosts where you want to install pbench-agent in the [servers] +section; nothing else needs to be touched: + +[servers] +hostA +hostB +... + +[servers:vars] +pbench_repo_name = pbench +fedoraproject_username = ndokos + +pbench_key_url = http://git.app.eng.bos.redhat.com/git/perf-dept.git/plain/bench/pbench/agent/{{ pbench_configuration_environment }}/ssh +pbench_config_url = http://git.app.eng.bos.redhat.com/git/perf-dept.git/plain/bench/pbench/agent/{{ pbench_configuration_environment }}/config + +After installation, the RPM version reported by `dnf list installed +pbench-agent' should be: + + pbench-agent.noarch 0.71.0-3g85910732a @copr-pbench-ndokos + +If you had previously installed a test version with a "greater" +version number, you might need to erase it first with `dnf erase +pbench-agent' before this version can be installed: we were a bit +cavalier with the numbering and `dnf' will not install this version if +the version number doesn't allow it. + +Containers +---------- + +Containers have been built based on the RPMs above and are available from + + https://quay.io + + +Release Notes +------------- + +The release notes for this release are available at + + https://github.com/distributed-system-analysis/pbench/releases/ + +There are a lot of changes in this release, so we recommend that you +read the release notes carefully. + + +Installation Guide +------------------ + +The pbench-agent installation guide is available internally at + + http://pbench.perf.lab.eng.bos.redhat.com + + +Problems +-------- + +Let us know of any problems you encounter. The best place is the +issue tracker: + + https://github.com/distributed-system-analysis/pbench/issues + +although for urgent problems the GChat pbench room can be used. + + +-- +The pbench team diff --git a/docs/release/v0.72.0-relnotes.md b/docs/release/v0.72.0-relnotes.md new file mode 100644 index 0000000000..a63807c4cc --- /dev/null +++ b/docs/release/v0.72.0-relnotes.md @@ -0,0 +1,216 @@ +This is a minor release of the Pbench agent. It consists mostly of bug fixes and deletions of deprecated components that were announced previously. + +The most visible parts of the changes are summarized below. The full change log can be found at [Changelog](https://github.com/distributed-system-analysis/pbench/compare/v0.71.0...v0.72.0), but note that most of the 408 commits are not for the agent: the list includes server and dashboard changes which are already incorporated into the current production Pbench server and dashboard. + +Installation +==== +The COPR repo names have changed: the `pbench-agent` RPM is now found in the [pbench-0.72 repo](https://copr.fedorainfracloud.org/coprs/ndokos/pbench-0.72/). The reason for this change was that COPR does not allow us to keep different versions of the RPM in the same repo: it deleted the older one as soon as a newer one was built. We needed that capability however, so we chose to go with separate repos for each release. + +There are some RPMs that are shared between versions (e.g. `pbench-sysstat`). We maintain those in the original COPR  [pbench repo](https://copr.fedorainfracloud.org/coprs/ndokos/pbench/) . The upshot is that the user now has to install *two* COPR repos (if doing it manually). The Ansible roles have been modified to do that, so if you are installing through Ansible, you don’t need to worry about that, except for adding the following line to the `[servers:vars]` section of the inventory file: + +``` +pbench_repo_name = pbench-0.72 +``` + +The inventory file should look like this: + +``` +[servers] + + +... + +[servers:vars] +pbench_repo_name = pbench-0.72 + +pbench_key_url = http://git.app.eng.bos.redhat.com/git/perf-dept.git/plain/bench/pbench/agent/{{ pbench_configuration_environment }}/ssh +pbench_config_url = http://git.app.eng.bos.redhat.com/git/perf-dept.git/plain/bench/pbench/agent/{{ pbench_configuration_environment }}/config +``` + +The version of the `pbench-agent` RPM for this release is 0.72.0-1g4391fbc01. + +Ansible roles +---- +New Ansible roles have been uploaded to Ansible Galaxy, so you will need to update your installation of those roles: + +``` +ansible-galaxy collection install pbench.agent -f +``` +In addition, there is no default for `pbench_repo_name` any longer (see above for an explanation). You will need to set it in your inventory file like this: + +``` +... +[servers:vars] +pbench_repo_name = pbench-0.72 + +pbench_key_url = +pbench_config_url = +``` + +New user-visible utilities +==== +The `pbench-tools-kill` script has been added. This is a new utility intended to provide complete cleanup if some Tool Meister component refuses to start. This is usually because there are old processes running and keeping network ports busy. The tool cleans up such errant processes so you can start afresh. + +Bug fixes and enhancements +==== +The Tool Meister subsystem has undergone a few fixes and some enhancements, primarily in logging and reporting of status; also, the [state-signals](https://github.com/distributed-system-analysis/state-signals) work was integrated into the Tool Meister (thanks Mustafa Eyceoz!). `pbench-linpack` has had some fixes (primarily thanks to Lukas Doktor). In addition, `pbench-specjbb`, `pbench-uperf` and `pbench-fio` have had bug fixes. + +The `user-tool` script was broken and that necessitated a few changes to the Tool Meister and also to `pbench-postprocess-tools`. Thanks to Keith Valin for finding the problem and to Michey Mehta for debugging it. + +As usual, if you find problems, please [open an issue on Github](https://github.com/distributed-system-analysis/pbench/issues). + +Support for latest RHEL and Fedora versions +==== +V0.72.0 supports RHEL 8.8, RHEL9.2 and Fedora 37 and 38, in addition to the previously supported RHEL versions. Fedora 36 is not supported any longer (primarily because COPR has dropped it). + +Deprecation notices and deletions of previously deprecated items +==== +A `default` tool set was implicitly used by `pbench-register-tool-set` . It was deprecated in v0.71.0 and is still deprecated in v0.72.0 - it will finally go away in the next release and you will need to choose a tool set explicitly when registering tools. The name for what used to be the default tool set is `legacy`. In addition, there are `light`, `medium` and `heavy` tool sets. Not supplying an argument for the tool set is still a warning but it is going to become an error in the next release. + +The `pbench-generate-token` command (see the "Futures" section below) is deprecated and will be deleted in the next release of the agent. + +The following have been previously deprecated and have now been deleted: `pbench-run-benchmark`, `pbench-cyclictest`, `pbench-dbench`, `pbench-iozone`, `pbench-migrate`, `pbench-netperf` . In addition, two contributed bench-scripts, `pbench-bzt` and `pbench-mpt`, have been deleted. + +The `stockpile` subproject has been removed, as well as the script `pbench-avg-stddev` which was unused. + + +Futures +==== +The following describes some details about future directions. One component of that is containerization. The Pbench server on production is already running in a container. Here we describe the current, experimental version of the containerized agent. The second component is user authentication and ownership of datasets. That is work in progress and what we describe here is what is available in the v0.72.0 release of the Pbench agent and the current production Pbench server. + +This section is meant as a foretaste of things to come. We expect most users to continue using RPMs for installing the agent and the `pbench-move-results` (or `pbench-copy-results`) utility to upload datasets, just as with previous versions of the Pbench agent. + +If you'd like to kick the tires a bit, read on and feel free to experiment, although we recommend that you don't use the following for "real" data. Things *should* work but that's not guaranteed: if you do venture forth and encounter problems, we would really like to know about them. Thanks in advance! + +Containerized Pbench agent +---- +There is an *experimental* Pbench agent container, intended as a demonstration project, available in the [contrib/containerized-pbench](https://github.com/distributed-system-analysis/pbench/tree/b0.72/contrib/containerized-pbench) directory of the b0.72 branch (the branch that was used to cut this release). The directory contains a README file, a `pbench` command and a demo script, `pbench-demo`. + +The demo script (which is to be thought of more as "executable documentation" than anything else at this point) uses the `pbench` command to execute a series of commands inside a container. The first time that the `pbench` command runs, it realizes that there is no container yet, so it downloads the `pbench-agent-all-fedora-36:b0.72` image from `quay.io` and starts the container. It then executes the first command that it was given *inside* that container. Subsequent invocations of the `pbench` command execute their arguments inside that container, first registering tools, then listing the tools, then running a simple `fio` benchmark under `pbench-user-benchmark` and finally pushing the results to the configured Pbench server. Although this is a very simple set of commands, it indicates how things would go in a more complicated invocation. + +There are a couple of **significant caveats**: this version of the demo script does *NOT* use `pbench-move-results` to send the results to the server (although it be could modified to do so). Instead it passes an authentication token to the `pbench-results-move` command (see below) to push the results. That token is generated by the `pbench-generate-token` script, which is invoked at the very beginning of the demo script: that script asks for a user ID and a password and then generates and stores that token in a file (the file is stored in a directory which is mapped into the container from the outside, so the token persists beyond the run of the demo script). That means you have to have a user ID and a password on the Pbench server before generating the token. + +To create a user ID with a password, you have to visit the [Pbench dashboard](http://pbench.perf.lab.eng.bos.redhat.com/dashboard/) and click on `Login` in the upper right. That will pop up a `login/sign up` dialog through which you can create an account that will then allow you to generate a token (or login to the dashboard and look around). N.B. All data sent to the AWS Pbench Satellite or `pbench.app.intlab.redhat.com` “pass-through” server is owned by a `legacy` user: it’s all visible, but can’t be modified. + +The trouble is that this is a *very* temporary arrangement: we expect that very soon, you will be able to use Red Hat SSO for logging in and generating the document. The accounts created as above will go away, as will the `pbench-generate-token` script which is already deprecated. Any datasets submitted through this mechanism will therefore be orphaned, hence the imprecation to use this to kick the tires, not for storing "real" results that you don't want to lose. We are *NOT* planning to migrate any such results. + + +New utilities to upload datasets as an authenticated user +---- +The existing `pbench-move-results` command works in exactly the same way as before: it uses `ssh/scp` to copy the results to a pass-through server, but there is no notion of a user owning those +results. Although we expect that to continue to be the main mode of operation for users of v0.72.0, we are moving towards a future where users will authenticate using SSO and that authenticated identity will become the owner of the datasets that are submitted by that user. The new commands `pbench-results-move` and `pbench-results-push` use an HTTP `PUT` to send results to a v1.0 Pbench Server which now provides a RESTful API to its services (`pbench-results-push` is used by the pass-through server to send the results to a Pbench server using a `legacy` user ID). The new commands will eventually supplant the existing `pbench-move-results`. Note that an early Pbench Server 1.0 integration with Pbench Agent introduced the `pbench-generate-token` command described above (available only Pbench Agent 0.71.0, 0.72.0) which is not compatible with the Pbench Server OIDC model that will allow us to use Red Hat SSO for authentication; the command is now deprecated and will be removed in the next Pbench Agent release. + +But we are not quite there yet: we may need to move to HTTPS in the Integration Lab and we need to finish setting up the authentication underpinnings in order to hook into the SSO infrastructure. Until that point, we encourage you to continue with pbench-move-results and the legacy interface to the server. If you have questions about any of this, ping us on GChat. + + + +Changelog (abbreviated - only the agent-side commits are included here) +==== +For the full Changelog, see the link near the top of these notes. + +Agent changes between v0.71.0 and v0.72.0: + +- 4391fbc01 Add a constraints.txt file to limit python-daemon to versions < 3.0.0 (#3448) +- c560bdf62 Clarify what tool-specific options are (#3444) +- 5fe6a7b24 Fixes for user-tool (#3440) +- d021d23e9 Fix the image tag (#3446) +- 2915816f6 Disable redis protected mode (#3434) +- bdc741a6f Correct the contents of the b0.72 jenkings/branch.name file +- 3cf0f8c1e Open firewall ports immediately as well as permanently (backport of #3419 to b0.72) (#3421) +- 89e45fb77 Ansible fixes b0.72 (#3407) +- f6d8e1030 Build pbench-tools-kill (#3408) +- 3f84f33ad Retire the previous containerized Agent example from contrib and update the README.md. +- 9053af10c pbench-results-push: Backport of #3348 and #3378 to b0.72 (#3377) +- 761445cb5 Separate `pbench-config` and `pbench-server-config` +- 6713d5ff7 Add an explicit ENTRYPOINT to the Agent "all" containers (#3320) +- d9c95e651 Update default Linux distros: drop Fedora 35 and add Fedora 37 (#3327) +- a96855108 Simple example of running pbench agent in a container +- e496ad7af Add `--output` option to `pbench-generate-token` +- 26f11d7d4 Drop controller from PUT agent side (#3220) +- 0e92342df Add support for building Agent containers to the CI (#3109) +- e07b6ba2d Stop using pbench logger in agent tests +- 95c0c400d Tweak the infrastructure for Click-based commands (#3157) +- 4292ae8df Add verify host names method used by Tool Meister +- c2047b348 Send tarball with access param +- b4a053b84 Prepare Agent container builds for use in the CI (#3086) +- 9e5c67a07 Remove unused helper functions from agent/base +- 26450d034 Add the new `pbench-tools-kill` command +- 76d1aeba1 State Signals in Pbench +- 8c3d1e06d Get the current Agent container build working again +- b472d03f4 Remove the now unused pbench-avg-stddev (perl) script (#3004) +- bacdd93ed Tweak the help texts for `pbench-tool-meister-start` and `pbench-fio` (#3002) +- 0f4f25b68 Add RPM builds to the CI pipeline (#2982) +- b58845eed Use `major`.`minor` version in COPR repo name +- fc97eb7a9 Minor correction to `yum` invocation +- 256c81279 Correct `utils.mk` path reference +- e2a11d895 Correct `VERSION` variable references +- 712506074 Correct use of `sha1` hash in rpm builds +- 16de4c976 Remove `pbench-run-benchmark` +- 9b9d8b521 Restore legacy tests for the agent +- 70927a085 Remove default repo name +- 84cce3786 Consolidate ansible directory hierarchy +- 5de49f2d2 Restore agent RPM builds +- e5dc47e68 Disable legacy tests +- b6e68ceac Remove trafficgen vestiges +- f8f00c7fb PBENCH-697 Delete stockpile submodule (#2971) +- 42f950890 Accessing results tarballs over http (#2967) +- a61494e97 Fix port requirements in pbench-uperf doc (#2969) +- cbf3b6ad4 Framework for building RPMs in the CI (#2961) +- e583efd9d Refactor support for distro/version pattern rules in makefiles +- 81072773a Initial support for building replacements for COPR chroots (#2957) +- 676ce68df Enhancements to the CI pipeline (Part 1, Take 2) (#2946) +- 7105b2520 Use the "epel" chroot for "Rocky Linux" +- 0c8e1826c Delete the epel role from pbench_agent_install.yml +- 2bf939b69 Add example playbook to open ports for redis/TDS (#2943) +- 8b602b60c Correct CentOS 7 container builds, update defaults +- 1ff802eb3 Avoid verify_common_bench_script_options in linpack pre-check (#2929) +- 0f12276ec Fix pbench-linpack options handling bug (#2926) +- 52e831372 Remove wayward "shbangs" in Python 3 library files (#2917) +- 32c85261e Correct dependencies in agent spec file +- 9997558b4 Default to Python 3.9 for unit tests (#2913) +- 657adef42 Ensure `fio` arguments are used with `bash -c` +- f3eca5064 Add more tests for `pbench-register-tool-set` +- 6ba02ca28 Fix pbench-register-tool-set argument handling (#2904) +- 2d97e96f5 Fix CentOS-Stream-8 repo +- d8a7fdb72 CentOS-Stream-8/9 dependency fixes (#2893) +- 015103855 Add unit tests for the `ToolGroup` class +- 6de91b5c4 Restore default tool set and deprecate +- beb61d12f Remove the unused `check_install_rpm` function +- 4e6b9d4be Remove contibuted `pbench-bzt` and `pbench-mpt` +- a957705ee Initial changes to support Python 3.10 +- 2f93c6f98 Add `numactl` RPM requirement (#2879) +- e160efa78 Tweak container builds for CentOS 9 +- c84c6ed32 Ensure use of `localhost` when stopping Redis +- b51b11672 Add local and remote pre-check for linpack +- ba6a2b784 Stop resolving benchmark binary location +- 2eff79bab Revert "Provide sneaky way to list bench-scripts tests" +- 32734f3b1 Revert "Add comments about the magic" +- c474689ce Revert "Remove use of `benchmark_bin` environment variable" +- 56ff71d41 Revert "Add failing tests for `uperf` and `fio` behaviors" +- 785946541 Revert "Correct `fio` and `uperf` existence checks" +- add741679 Revert "Correct local assigment then return code check" +- 04715fbcc Revert "Apply a round of code-review comments, still w which" +- e79ad4d1d Revert "Replace `which` with `command -v`" +- cd70a646a Revert "Stop resolving benchmark binary location" +- 226e73377 Stop resolving benchmark binary location +- 42a8d12e9 Replace `which` with `command -v` +- 877698f3b Apply a round of code-review comments, still w which +- d4399212f Correct local assigment then return code check +- 19cf4ec6d Correct `fio` and `uperf` existence checks +- 014662476 Add failing tests for `uperf` and `fio` behaviors +- 50f01577d Remove use of `benchmark_bin` environment variable +- ad1b2636b Add comments about the magic +- c38030bdd Provide sneaky way to list bench-scripts tests +- fbcd7f6a9 Correct `pbench-specjbb2005` use of `-send-tools` +- 42274065f `pbench-specjbb2005` now handles commented props +- 1f64660f3 Add UUIDs to command line of running Tool Meisters +- ea18664d0 Fix pbench-fio local fio-server execution +- 32e07f5fe Quick v0.71 fixes (#2821) +- 70cce64bb Isolate parameter transforms to ToolDataSink class +- 28f95ca45 Fix Tool Meister instance exit code handling +- 48dc95cad Correct spelling in `pidstat` tool help text +- 82b3ca6a7 Delete the spurious pbench3-devel RPM dependency (#2799) +- e5e885524 Delete deprecated bench-scripts from agent Makefile (#2802) +- 55ac48646 Initial commit for merging sos and perf data +- 509ffb352 Agent v0.72, Server v1.0 +- e4c184f6c Remove deprecated bench-scripts diff --git a/docs/release/v0.72.1-relnotes.md b/docs/release/v0.72.1-relnotes.md new file mode 100644 index 0000000000..449cd5ae39 --- /dev/null +++ b/docs/release/v0.72.1-relnotes.md @@ -0,0 +1,5 @@ +This release is a point release for v0.72.0. It fixes one problem that was found just as we were releasing v0.72.0. The problem was that `pbench-postprocess-tools` was not handling labeled hosts correctly (labels may be attached to hosts during tool registration). See issue #3454 and PR #3456 for a fuller description. + +Installation is as described in the [v0.72.0 release notes](https://github.com/distributed-system-analysis/pbench/releases/tag/v0.72.0). The version of the pbench-agent RPM for this release is 0.72.1-1g7d727fec5. + +For the rest of the changes, see the [v0.72.0 release notes](https://github.com/distributed-system-analysis/pbench/releases/tag/v0.72.0).