concourse-deploy-rabbitmq

Deploy RabbitMQ with omg in a Concourse pipeline.

Prerequisites

1. Git
2. Vault
3. Concourse

Steps to use this pipeline

1. Clone this repository.

   git clone https://github.com/enaml-ops/concourse-deploy-rabbitmq.git
   

2. Copy the sample config file deployment-props-sample.json.

   cd concourse-deploy-rabbitmq
   cp deployment-props-sample.json deployment-props.json
   

3. Edit deployment-props.json, adding the appropriate values.

   This file is used to populate a vault hash. It holds the BOSH credentials for both omg (username/password) and the Concourse bosh-deployment (UAA client) resource.

   $EDITOR deployment-props.json
   

   omg will also read other key/value pairs added here, matching them to command-line arguments. For example, to add the omg plugin parameter --syslog-address, you could add "syslog-address": "10.150.12.10" here rather than modifying the manifest generation script in ci/tasks.

   All available parameters/keys can be listed by querying the plugin. If not specified in deployment-props.json, default values will be used where possible.

   omg-linux deploy-product p-rabbitmq-plugin-linux --help
   

4. Load your deployment properties into vault. VAULT_HASH you define here and vault_hash_misc in pipeline-vars.yml below must match. You may consider using the vault hash here to hold common settings, referenced by multiple omg-based deployments. In such a case, you might name the hash something like secret/nonprod-common-props.

   export VAULT_ADDR=http://YOUR_VAULT_ADDR:8200
   export VAULT_HASH=secret/rabbitmq-nonprod-props
   vault write $VAULT_HASH @deployment-props.json
   

5. Delete or move deployment-props.json to a secure location.

6. Copy the pipeline variables template.

   cp pipeline-vars-template.yml pipeline-vars.yml
   

7. Edit pipeline-vars.yml, adding appropriate values.

   $EDITOR pipeline-vars.yml
   

   Note: When you are deploying Pivotal RabbitMQ, you must add your API Token found at the bottom of your Pivotal Profile page.

8. Create or update the pipeline.

   fly -t TARGET set-pipeline -p deploy-rabbitmq -c ci/pivotal-rabbitmq-service-pipeline.yml -l pipeline-vars.yml
   

   or

   fly -t TARGET set-pipeline -p deploy-rabbitmq -c ci/pivotal-rabbitmq-service-pipeline.yml -l pipeline-vars.yml
   

9. Delete or move pipeline-vars.yml to a secure location.

10. Unpause the pipeline

    fly -t TARGET unpause-pipeline -p deploy-rabbitmq
    

11. Trigger the deployment job and observe the output.

    fly -t TARGET trigger-job -j deploy-rabbitmq/get-product-version -w
    fly -t TARGET trigger-job -j deploy-rabbitmq/deploy -w