Cant install rabbitmq-p service on pcf dev local
ZeroGraviti opened this issue · comments
I created a post here https://stackoverflow.com/questions/60274043/how-can-i-install-the-p-rabbitmq-service-on-my-local-pcfdev with the details.
Please guide me.
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/171377366
The labels on this github issue will be updated when the story is started.
There's an entry in the FAQ addressing this specific issue. Note that this solution will only work for the newer non-deprecated offering of CF Dev.
I did use the asset (pcfdev-v1.2.0-darwin.tgz) to run locally and this is not the deprecated version of cf dev.
The splash message should tell you how to cf dev deploy-service. Were you able to see it?
I need to have a rabbitmq broker registered as an errand at the time of deployment. I couldn't figure that out yet. Let me know if I am looking for the wrong thing.
The splash message should tell you how to
cf dev deploy-service. Were you able to see it?
the only service which I could deploy is mysql - here is the splash message
$ cf dev start -m 8192 -c 4
Downloading Network Helper...
Progress: |====================>| 100.0%
Installing cfdevd network helper (requires administrator privileges)...
Password:
Setting up IP aliases for the BOSH Director & CF Router (requires administrator privileges)
Downloading Resources...
Progress: |====================>| 100.0%
Setting State...
Creating the VM...
Starting VPNKit...
Waiting for the VM...
Deploying the BOSH Director...
Deploying CF...
Progress: 8 of 15 (8m22s)
Done (10m42s)
██████╗███████╗██████╗ ███████╗██╗ ██╗
██╔════╝██╔════╝██╔══██╗██╔════╝██║ ██║
██║ █████╗ ██║ ██║█████╗ ██║ ██║
██║ ██╔══╝ ██║ ██║██╔══╝ ╚██╗ ██╔╝
╚██████╗██║ ██████╔╝███████╗ ╚████╔╝
╚═════╝╚═╝ ╚═════╝ ╚══════╝ ╚═══╝
is now running!
To begin using CF Dev, please run:
cf login -a https://api.dev.cfdev.sh --skip-ssl-validation
Admin user => Email: admin / Password: admin
Regular user => Email: user / Password: pass
To deploy a particular service, please run:
cf dev deploy-service <service-name> [Available services: mysql]
I need to have a rabbitmq broker registered as an errand at the time of deployment. I couldn't figure that out yet. Let me know if I am looking for the wrong thing.
Here are the contents of the deployment manifest which I have used -
$ cat cf-rabbitmq-deployment.yml
instance_groups:
- azs:
- z1
- z2
instances: 3
jobs:
- name: rabbitmq-server
properties:
rabbitmq-server:
administrators:
broker:
password: broker
username: broker
management:
password: admin
username: admin
cluster_partition_handling: autoheal
cookie: this is something secret
plugins:
- rabbitmq_management
- rabbitmq_mqtt
- rabbitmq_stomp
ports:
- 5672
- 5671
- 1883
- 8883
- 61613
- 61614
- 15672
- 15674
version: 3.6
release: cf-rabbitmq
name: rmq
networks:
- name: default
persistent_disk_type: 10GB
stemcell: xenial
vm_type: default
- azs:
- z1
- z2
instances: 1
jobs:
- name: rabbitmq-haproxy
release: cf-rabbitmq
- consumes:
nats:
deployment: cf
from: nats
name: route_registrar
properties:
route_registrar:
routes:
- name: rabbitmq
port: 15672
registration_interval: 20s
uris:
- rabbitmq.dev.cfdev.sh
release: routing
- name: bpm
release: bpm
name: haproxy
networks:
- name: default
stemcell: xenial
vm_type: default
name: cf-rabbitmq
releases:
- name: cf-rabbitmq
version: latest
- name: routing
version: latest
- name: bpm
version: latest
stemcells:
- alias: xenial
os: ubuntu-xenial
version: 456.14
update:
canaries: 1
canary_watch_time: 30000-180000
max_in_flight: 1
serial: false
update_watch_time: 30000-180000
And my modified release :-
$ cat releases/cf-rabbitmq/cf-rabbitmq-233.0.0.yml
name: cf-rabbitmq
version: 233.0.0
commit_hash: 0e49ab7
uncommitted_changes: false
jobs:
- name: rabbitmq-haproxy
version: c145cbc01f36cd112486704da6e0bc7fbd5267e9fcbc19c2e8add6682b1b8238
fingerprint: c145cbc01f36cd112486704da6e0bc7fbd5267e9fcbc19c2e8add6682b1b8238
sha1: sha256:842d61d6a69dcfdfc078d80c4c46a05a253990c588b4472df1ab74c12f7d3370
- name: rabbitmq-server
version: 460aa39266bc268b35e100b048b0a1f4d0dc7c29df5b5e30322a8980c7fc2b6a
fingerprint: 460aa39266bc268b35e100b048b0a1f4d0dc7c29df5b5e30322a8980c7fc2b6a
sha1: sha256:fca344fee2f392b22e94ef56446ce0ea8f4d27c600a13055eefb30a2489f3111
- name: broker-deregistrar
version: 6b1247fd8d5ca1cc0584914f9bdfaae8788b96a2
fingerprint: 6b1247fd8d5ca1cc0584914f9bdfaae8788b96a2
sha1: 97a63c37cdcdf6533a44c0dca05e1e81b205d3a5
- name: broker-registrar
version: 39bb7711ea89f7303693f4dee52262e7cc358b36
fingerprint: 39bb7711ea89f7303693f4dee52262e7cc358b36
sha1: 2b91882eb27d86994555d9925983b83e25b1e034
- name: rabbitmq-broker
version: 9136d1b957440484cd20b25766ebd13647e2ae7f
fingerprint: 9136d1b957440484cd20b25766ebd13647e2ae7f
sha1: 5957ef3c507ae11e5ac04cf79e4f2b7a6bae2d2b
packages:
- name: basht
version: 7079f05c64eaa4f8fb9985a514bf3290d270f921fa3b9cf6e1bf9f70a664e793
fingerprint: 7079f05c64eaa4f8fb9985a514bf3290d270f921fa3b9cf6e1bf9f70a664e793
sha1: sha256:9f6a1e10e91d6897982cc26fdca9cb302984fbb4e7bcb01f0c16cda7610fdaf2
dependencies: []
- name: erlang
version: 5ee06df6df4117350dc550427e6ee87ea7f24593bb8379e2e50124f173624c57
fingerprint: 5ee06df6df4117350dc550427e6ee87ea7f24593bb8379e2e50124f173624c57
sha1: sha256:e04a9ce6eaf964a7b14750985b18af0e8d263e591f126ececa9da92e1428d8f1
dependencies: []
- name: golang
version: a506863a7b055eddee2183cd96f9e2687b48e45e318d3f5b217e5ad2407e456f
fingerprint: a506863a7b055eddee2183cd96f9e2687b48e45e318d3f5b217e5ad2407e456f
sha1: sha256:0cd7943d3031e2e09a04207cc5d74cb0e0e81996c12400f7680bce1b48009ac8
dependencies: []
- name: haproxy
version: d62b2386083f039a3116c8471657cde553dd2ab85b052118214fa61ad5a92a30
fingerprint: d62b2386083f039a3116c8471657cde553dd2ab85b052118214fa61ad5a92a30
sha1: sha256:1645e250d0dee17352dac0ca1686ba5643b5e6a56a60752d79acf20bf37780bb
dependencies: []
- name: rabbitmq-common
version: c7b701f8368c5f7d76569d43187eeed4bb32513e071a4cd3964bf62f04cc2dbb
fingerprint: c7b701f8368c5f7d76569d43187eeed4bb32513e071a4cd3964bf62f04cc2dbb
sha1: sha256:391c2bec3eedfe4bb7cfaeef61c034bc5f02269545d003ae4605f394258ed5ee
dependencies: []
- name: rabbitmq-server
version: e313e6229a4a484e135e20283649d23b9594fce5f4f73c17912802c6f5022169
fingerprint: e313e6229a4a484e135e20283649d23b9594fce5f4f73c17912802c6f5022169
sha1: sha256:6d7db26c16d9768299e40e366586499e0fca6c4c994b66bd3db485543622a9df
dependencies: []
- name: rabbitmq-upgrade-preparation
version: 36036ff59cc06da07fe256a8147fc3fc0883c5088643e878ab92390a2063190a
fingerprint: 36036ff59cc06da07fe256a8147fc3fc0883c5088643e878ab92390a2063190a
sha1: sha256:4d82a4c3447495c34bf66b6f0f38dc00924318220dcaa01616575eabcc5ff990
dependencies:
- golang
license:
version: a15ad8054f690c010fa3465e0926350d26338d6e40645b94c592d26c65afc810
fingerprint: a15ad8054f690c010fa3465e0926350d26338d6e40645b94c592d26c65afc810
sha1: sha256:53311649b0cc714e4631a04eb4b678724db8afd3c4c8f774163adf62ebdf836a
and the bosh cli outputs -
$ bosh releases | grep rabb
cf-rabbitmq 233.0.0* 0e49ab7
$ bosh vms (output snippet)
Deployment 'cf-rabbitmq'
Instance Process State AZ IPs VM CID VM Type Active Stemcell
haproxy/483d9abe-72b1-48bf-b84b-f82a6d7f79df running z1 10.144.0.19 9be4ac59-3c58-4a07-864e-7c897b4ed296 default true -
rmq/35342ff3-f5b1-4997-8207-b96891a100bd running z1 10.144.0.16 101cb340-dad2-432f-b983-6d1ff792e4ec default true -
rmq/3c32c92e-28af-4e85-8cd4-c930d7dc8e21 running z2 10.144.0.18 0f89d215-73ac-4dc3-bc54-653f161c754a default true -
rmq/661d3a57-5c5c-4baa-9bb4-1a8ee2102e79 running z1 10.144.0.17 fcc8c4a9-ab86-4f04-bddb-985d23c87f99 default true -
4 vms
Succeeded
$ bosh deployments
Using environment '10.144.0.2' as client 'admin'
Name Release(s) Stemcell(s) Team(s)
cf binary-buildpack/1.0.33 bosh-warden-boshlite-ubuntu-xenial-go_agent/456.14 -
bosh-dns/1.10.0
bosh-dns-aliases/0.0.3
bpm/1.1.3
capi/1.86.0
cf-cli/1.19.0
cf-networking/2.24.0
cf-syslog-drain/10.2
cflinuxfs3/0.121.0
credhub/2.5.2
diego/2.36.0
dotnet-core-buildpack/2.2.12
garden-runc/1.19.5
go-buildpack/1.8.42
java-buildpack/4.20
log-cache/2.3.1
loggregator/105.6
loggregator-agent/3.21
nats/27
nginx-buildpack/1.0.15
nodejs-buildpack/1.6.52
php-buildpack/4.3.78
pxc/0.19.0
python-buildpack/1.6.36
r-buildpack/1.0.11
routing/0.191.0
ruby-buildpack/1.7.42
silk/2.24.0
staticfile-buildpack/1.4.43
statsd-injector/1.10.0
uaa/74.0.0
cf-rabbitmq bosh-dns/1.10.0 bosh-warden-boshlite-ubuntu-xenial-go_agent/456.14 -
bpm/1.1.3
cf-rabbitmq/233.0.0
routing/0.191.0
2 deployments
Succeeded
By the looks of it, you already have cf-rabbitmq installed if it shows up in the output of bosh vms. What else were you hoping to achieve?
Moreover, the splash message and invocation asserts that you did not invoke the start command with the -f flag, as mentioned in the FAQ. Your start invocation should have looked like:
$ cf dev start -m 8192 -c 4 -f ./path/to/pcfdev-v*.tgz
Downloading Network Helper...
...
To deploy a particular service, please run:
cf dev deploy-service <service-name> [Available services: mysql, rabbitmq, redis, scs]
Do I need to add the path
-f ./path/to/pcfdev-v*.tgz
every single time I start cf ? I assumed (most probably wrongly) that this was required only for the first time.
What you see in the bosh vms output was my own install of rabbitmq after the fact.
Yes you need to add the path, every single time.
Works !