Chef-Solo handling for replicaset databags #332
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Just starting off, want to say I'm definitely open to discussion on this pull request as I want to make sure I'm not suggesting any changes that reduce quality. I'm also not able to test this with chef-server, only chef-solo.
Right now, I'm unable to create a replicated, sharded cluster using chef-solo. When trying to start up the first mongod server, it errors out with the following Chef output:
You can see the complete example of how I'm trying to create the cluster in my MongoDB Cluster repo. It's quite possible I'm just using chef-solo-search improperly to create the information for the nodes, so please let me know if I am.
When using the change in this pull request, all the nodes come up successfully and look configured properly. The mongos server:
The mongod server:
The config server: