Cloud Foundry RabbitMQ Service
This repository contains the release for RabbitMQ for Cloud Foundry. It is deployable by BOSH in the usual way.
Clone the repository and install dependencies.
$ bundle install
Once you have a BOSH Lite up and running locally, run
To deploy the release into BOSH you will need a deployment manifest. You can generate a deployment manifest using the following command:
bosh interpolate \ --vars-file=manifests/lite-vars-file.yml \ manifests/cf-rabbitmq-template.yml
Alternatively, you can use the
scripts/generate-manifest in order to generate a vanilla manifest for BOSH lite.
Currently, the release has only been tested to run on manual networks (https://bosh.io/docs/networks/).
bundle exec rake --tasks to list all the test subsets.
To run only unit tests locally, run:
Integration tests require this release to be deployed into a BOSH director (see Deploying section above).
To run integration tests do
Embedded Release Tests
Sometimes testing BOSH releases can lead to writing many tests at the top of the test pyramid, which can increase the feedback loop. Also when tests fail debugging can be hard given there are many components working together.
Embedded release tests are jobs that we deploy in a co-located way so that we can execute tests within a given deployment, inside a VM. The goal is to pull tests down the test pyramid trying to shorten the feedback loop and bring the tests closer to the code.
To execute embedded release tests you need to co-locate the tests within the release being tested and deploy. The deployment should fail if the tests fail. The tests we use can be found in the test release repo.
Back in time Multitenant Broker Release used to live in the same Github repository as cf-rabbitmq-release, but not anymore. We have split both releases into two different repositories. They do different things and have different lifecyle, which explains our decision to do that.
A collection of ops-files and vars-files, features from Bosh 2 CLI, can be used to generate manifests. You’ll find a folder called
manifests in both repositories with a manifest template, some ops-files and example of vars-files. It's not required to have two different deployments for
cf-rabbitmq-multitenant-broker-release. In case you want to colocate both jobs you can leverage this ops-file to colocate them in the same deployment.