Uploaded image for project: 'Drivers'
  1. Drivers
  2. DRIVERS-318

List of deployment configurations we must test against

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Done
    • Icon: Minor - P4 Minor - P4
    • None
    • None

    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

      • 2.4 latest release and nightly
      • 2.6 latest release and nightly
      • 3.0 latest release and nightly
      • 3.2 latest release and nightly
      • 3.4 (soon) latest release and nightly
      • nightly

      SSL

      • No SSL
      • SSL required, with strong client cert validation and valid server cert, FIPS mode

      Auth

      • No auth
      • Auth required (MONGODB-CR until 3.0, then SCRAM-SHA-1)

      Topology Types

      • Standalone
      • 3-node RS with a primary, secondary, and arbiter
      • Sharded cluster with 2 mongos servers, 3 config servers, and a single standalone shard

      Storage Engine

      • wiredTiger
      • mmapv1
      • inMemory

      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.

      Attachments

        Activity

          People

            jesse@mongodb.com A. Jesse Jiryu Davis
            jesse@mongodb.com A. Jesse Jiryu Davis
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: