[SERVER-53814] Separate MongoDB config from resmoke Created: 14/Jan/21  Updated: 18/Feb/21  Resolved: 18/Feb/21

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Robert Guo (Inactive) Assignee: Raiden Worley (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-54419 Support last-lts and last-continuous ... Closed
Issue split
split to SERVER-54617 Create a resmoke configuration manage... Closed
split to SERVER-54618 Remove mongod configuration from prog... Closed
split to SERVER-54619 Extract resmokelib dependencies from ... Closed
split to SERVER-54621 Establish a resmoke fixture API Closed
split to SERVER-54622 Retrieve back-branch fixture files to... Closed
Related
related to SERVER-52231 add timeseries to all-features builders Closed
related to SERVER-53710 Add burn in tests to "disabled featur... Closed
Sprint: STM 2021-02-22, STM 2021-03-08
Participants:
Story Points: 3

 Description   

Resmoke has been running multi-version clusters ad-hoc by manipulating MongoDB parameters at various levels, this approach has limitations and maintenance burdens. As part of continuous delivery, we need a more seamless experience for spinning up multi-version clusters.

Impl TBD.



 Comments   
Comment by Raiden Worley (Inactive) [ 18/Feb/21 ]

I split this apart into component issues, linked.

Comment by Brooke Miller [ 18/Feb/21 ]

Based on the additional complexity, carl.worley will split this ticket up further to estimate.

Comment by Raiden Worley (Inactive) [ 03/Feb/21 ]

robert.guo and I discussed a design where most of the setup/configuration information for mongods will remain in the fixture files. The information needed to run a mongod for each branch will remain local to that branch, and when resmoke begins executing in a mixed mode it will retrieve the corresponding .py files from each git commit to assemble the mixed cluster.

This will require a consistent fixture API across branches, but will allow version-specific information to remain local. Any operation that does need to be aware of the multiversion nature of the system will be external to the fixtures and operate upon them, or else will be in the abstract fixture interface that is shared.

Comment by Brooke Miller [ 26/Jan/21 ]

robert.guo and carl.worley to discuss the implementation a bit further to make a decision on the direction to take, before next sprint, in order for us to estimate the effort.

Comment by Githook User [ 14/Jan/21 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-53710 SERVER-53814 remove burn_in_multiversion from all features builder
Branch: master
https://github.com/mongodb/mongo/commit/f3f6b1c0a0c540f7037e5c44248b14c7a9e2e4f1

Generated at Thu Feb 08 05:31:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.