[DRIVERS-318] List of deployment configurations we must test against Created: 29/Jul/16 Updated: 17/Mar/20 Resolved: 01/Aug/16 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | A. Jesse Jiryu Davis | Assignee: | A. Jesse Jiryu Davis |
| Resolution: | Done | Votes: | 0 |
| Labels: | testing | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
bjori, sam.kleinman, and I are proposing to experiment with a replacement for Mongo Orchestration on Evergreen next quarter. (The experimental replacement uses Automation, which might be a firmer foundation for driver tests.) Please verify that this is a comprehensive list of required deployments for your driver's tests, once we're all migrated to Evergreen: Version
SSL
Auth
Topology Types
Storage Engine
Will this sharded topology suffice, or does some test really need a sharded cluster with multiple shards, or with replicated shards? Will anyone require mixed-version deployments in Evergreen? Not currently in scope: Kerberos, LDAP. |