[SERVER-37434] Turn on GCP Atlas clusters on GCP for sys-perf Created: 03/Oct/18 Updated: 13/Jun/23 Resolved: 13/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Performance |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | April Schoffer | Assignee: | Backlog - Performance Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | perf-stop-regressions, sys-perf-atlas-followup | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Product Performance
|
| Participants: |
| Comments |
| Comment by David Daly [ 13/Jun/23 ] |
|
We discuss GCP elsewhere. This ticket is old and not useful for us anymore. |
| Comment by Henrik Ingo (Inactive) [ 04/Oct/18 ] |
|
This capture work for a terraform tf file to deploy a single workload client host on Azure, but not the sys-perf MongoDB clusters. Note that the current plan is that Atlas tests will only be scheduled manually from the Evergreen UI, so none of them will run "regularly" such as daily. (In practice it is up to the cloud team as to what and when to test, such as before they want to deploy something to prod.) |