[wip] DEBUG add atop monitor unit

[hexfusion]

use atop to understand pivot writes during an upgrade.

[openshift-ci-robot]

@hexfusion: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

[wip] DEBUG add atop monitor unit

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: hexfusion
To complete the pull request process, please assign cgwalters
You can assign the PR to them by writing /assign @cgwalters in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[hexfusion]

/test e2e-aws

[cgwalters]

Oh, that's where the question about upgrade iops came from.

So ostree is definitely going to do a lot of IO quickly (it does multithreaded writes) and could probably saturate the queue. Hmm, we could probably use IOSchedulingClass=idle by default.

If you want to gather stats on this it's probably easier to use a container like this and just directly run e.g. pivot quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:8bc8fa4fc8494035e43e359702bdcd2b220e924c585f3c5d5b0e51d1c3bf2846 or so from inside an oc debug node/ or ssh.

[hexfusion]

thanks for the ideas @cgwalters !

[openshift-ci-robot]

@hexfusion: The following tests failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
ci/prow/e2e-aws-scaleup-rhel7	3d99839	link	/test e2e-aws-scaleup-rhel7
ci/prow/e2e-aws	3d99839	link	/test e2e-aws
ci/prow/e2e-gcp-op	3d99839	link	/test e2e-gcp-op

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.