Deploying Cloud Foundry with Chef
This means of deploying Cloud Foundry is an ongoing effort maintained by the Cloud Foundry community to set up a production ready PaaS. Alternatively, operations professionals are encouraged to use BOSH as Pivotal's supported way of providing and consuming publicly available releases.
All the cookbooks work best with Chef client connected to a Chef server; they also work with chef-solo but may require more configuration.
The cookbooks have been tested with Chef 10.14.4; they should also work with more recent versions in the 10.x series.
|cloud_controller||cloudfoundry-cloud_controller||Released||GitHub||Supports only cloud_controller v1 at this time; cloud_controller v2 coming soon.|
|health_manager||cloudfoundry-health_manager||Released||GitHub||Supports only health_manager “next”.|
|DEA||cloudfoundry-dea||Released||GitHub||Supports only the legacy DEA. Support for DEA ng coming soon.|
|router||cloudfoundry-nginx||Released||GitHub||Installs nginx 1.2.x for use by the router.|
|Ruby||cloudfoundry-ruby-runtime||Released||GitHub||Supports MRI Ruby 1.8.7, 1.9.2 and 1.9.3.|
|Filesystem||cloudfoundry-filesystem-service||Released||GitHub||Supports only the “legacy” service.|
|MongoDB||cloudfoundry-mongodb-service||Released||GitHub||Supports only the “legacy” service.|
|RabbitMQ||cloudfoundry-rabbitmq-service||Released||GitHub||Supports only the “legacy” service.|
|Service broker||cloudfoundry-service_broker||Released||GitHub||Supports only the “legacy” service.|
These cookbooks are required because the other cookbooks depend on them, but they usually have no serviceable parts:
|cloudfoundry||Released||GitHub||Mandatory dependency for all other cookbooks.|
|cloudfoundry_service||Released||GitHub||Mandatory dependency for all service cookbooks.|