roachtest: surface cloud cluster spec info in artifacts #112707
Labels
A-testing
Testing tools and infrastructure
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
T-testeng
TestEng Team
Comments
jbowens
added
C-enhancement
|
cc @cockroachdb/test-eng |
vidit-bhat
added a commit
to vidit-bhat/cockroach
that referenced
this issue
May 16, 2024
Previously, getting the spec of the VMs on which a roachtest ran was tricky to derive. This was inadequate because it's often necessary to understand the particulars of a roachtest run's environment. To address this, this patch creates a json file per VM describing its spec in. These files are stored in the Artifacts directory. Epic: none Fixes: cockroachdb#112707 Release note: None
vidit-bhat
added a commit
to vidit-bhat/cockroach
that referenced
this issue
May 17, 2024
Previously, getting the spec of the VMs on which a roachtest ran was tricky to derive. This was inadequate because it's often necessary to understand the particulars of a roachtest run's environment. To address this, this patch creates a json file per VM describing its spec in. These files are stored in the Artifacts directory. Epic: none Fixes: cockroachdb#112707 Release note: None
craig bot
pushed a commit
that referenced
this issue
May 20, 2024
124243: roachtest: surface cloud cluster spec info in artifacts r=vidit-bhat a=vidit-bhat Previously, getting the spec of the VMs on which a roachtest ran was tricky to derive. This was inadequate because it's often necessary to understand the particulars of a roachtest run's environment. To address this, this patch creates a json file per VM describing its spec. These files are stored under `artifacts/vm_spec`. Epic: none Fixes: #112707 Release note: None Co-authored-by: Vidit Bhat <[email protected]>
blathers-crl bot
pushed a commit
that referenced
this issue
May 24, 2024
Previously, getting the spec of the VMs on which a roachtest ran was tricky to derive. This was inadequate because it's often necessary to understand the particulars of a roachtest run's environment. To address this, this patch creates a json file per VM describing its spec in. These files are stored in the Artifacts directory. Epic: none Fixes: #112707 Release note: None
vidit-bhat
added a commit
to vidit-bhat/cockroach
that referenced
this issue
May 24, 2024
Previously, getting the spec of the VMs on which a roachtest ran was tricky to derive. This was inadequate because it's often necessary to understand the particulars of a roachtest run's environment. To address this, this patch creates a json file per VM describing its spec in. These files are stored in the Artifacts directory. Epic: none Fixes: cockroachdb#112707 Release note: None
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's often necessary to understand the particulars of a roachtest run's environment. In particular, on the storage team we often need to know the bandwidth and IOPS limits of disks, and whether they're persistent disk or local SSDs. Today, this data is tricky to derive involving reading source code, mapping instance types per-Cloud provider and looking up Cloud-provider docs to establish bandwidth/IOPS limits. Surfacing information about the cloud provider cluster specification within the artifacts would ease this process.
Internal slack link: https://cockroachlabs.slack.com/archives/C023S0V4YEB/p1697737111168569
Jira issue: CRDB-32561
The text was updated successfully, but these errors were encountered: