You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 20, 2020. It is now read-only.
First, thanks for creating this cookbook! It is evident that you put a lot of effort into making this and it is a tremendous help to the community to have a working cookbook that supports mongo 3 with lots of configuration options being manageable through chef. The only other cookbook I've had similar success with is the original edelight mongodb-cookbook which has now been taken over by chef-brigade: https://github.com/chef-brigade/mongodb-cookbook . They are also working on adding mongo 3 support, but not quite there yet as their cookbook is a bit more complex.
One thing that would be really nice to have is automatic configuration of the replica set using chef search to identify other nodes using the same replica set name and having chef run the appropriate commands to configure the cluster. The cookbook I linked above does this using the mongo ruby gem to connect to mongo during convergence and automatically reconfigures the cluster based on what it finds in chef server's own database.
Currently, with your cookbook, replica set configuration seems to be accomplished by manually running the appropriate rs.initiate() and rs.add() commands. Alternatively since you support MMS automation agent, one can plug in to that system to leverage the features provided by MMS to manage the replica set. However, if one did not wish to use MMS but desired to use mongo 3, the only option seems to be manual configuration.
Are you planning to add automatic replica set configuration in the near future? I would switch to using your cookbook exclusively if this was possible.
What other features are planned?
Great work so far, thanks again.
The text was updated successfully, but these errors were encountered:
Hello,
First, thanks for creating this cookbook! It is evident that you put a lot of effort into making this and it is a tremendous help to the community to have a working cookbook that supports mongo 3 with lots of configuration options being manageable through chef. The only other cookbook I've had similar success with is the original edelight mongodb-cookbook which has now been taken over by chef-brigade: https://github.com/chef-brigade/mongodb-cookbook . They are also working on adding mongo 3 support, but not quite there yet as their cookbook is a bit more complex.
One thing that would be really nice to have is automatic configuration of the replica set using chef search to identify other nodes using the same replica set name and having chef run the appropriate commands to configure the cluster. The cookbook I linked above does this using the mongo ruby gem to connect to mongo during convergence and automatically reconfigures the cluster based on what it finds in chef server's own database.
Currently, with your cookbook, replica set configuration seems to be accomplished by manually running the appropriate rs.initiate() and rs.add() commands. Alternatively since you support MMS automation agent, one can plug in to that system to leverage the features provided by MMS to manage the replica set. However, if one did not wish to use MMS but desired to use mongo 3, the only option seems to be manual configuration.
Are you planning to add automatic replica set configuration in the near future? I would switch to using your cookbook exclusively if this was possible.
What other features are planned?
Great work so far, thanks again.
The text was updated successfully, but these errors were encountered: