A Chef cookbook for installing and configuring MongoDB, supporting single instances, replication, sharding, and monitoring.
chef-mongodb is a Chef cookbook that automates the installation, configuration, and management of MongoDB databases. It solves the problem of manual, error-prone MongoDB setup by providing reusable, version-controlled infrastructure code. The cookbook supports complex deployments including replication, sharding, and integration with MongoDB's monitoring system.
DevOps engineers, system administrators, and infrastructure teams who manage MongoDB deployments using Chef for configuration management. It's particularly useful for organizations running MongoDB in production environments requiring automation and consistency.
Developers choose this cookbook because it provides a battle-tested, community-supported way to automate MongoDB deployments entirely through code. It reduces configuration drift, ensures repeatability across environments, and supports advanced MongoDB features like sharding and replication out of the box.
MongoDB Chef cookbook
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports everything from single instances to complex sharded clusters with replication, as detailed in the USAGE section for various topologies like 'mongodb::shard' and 'mongodb::replicaset'.
Embeds MongoDB management into Chef's infrastructure-as-code workflow, allowing version-controlled, repeatable configurations per the stated philosophy in the README.
Enables fine-tuning through Chef attributes for all MongoDB settings, including replSet and sharded_collections, as shown in the ATTRIBUTES section with examples like node['mongodb']['config']['dbpath'].
Simplifies production monitoring by automating deployment of MongoDB Monitoring System agents with configurable settings, such as api_key and version, per the MMS Agent attributes.
Requires Chef >11 and Ruby >1.9, which are legacy versions that may conflict with modern infrastructure stacks and limit compatibility with newer Chef features.
Configuring sharding and replication involves multiple recipes and careful attribute coordination (e.g., cluster_name and shard_name), making it error-prone without deep Chef expertise, as noted in the USAGE section.
Only actively tested on Ubuntu, Debian, CentOS, and Redhat per the REQUIREMENTS, leaving other platforms unsupported and reliant on community contributions for fixes.
Heavily ties to 10gen repositories and MMS services, which may not align with teams using alternative MongoDB distributions or monitoring tools, limiting flexibility.