Hey all,
We're attempting to get PostgreSQL as a service running in our PCF environment. To do that, I'm trying to use this community release which includes pgsql as well as a number of other services:
https://github.com/cloudfoundry-community/cf-services-contrib-release
I've created a yaml file that's supposed to add posgres to our Cloud Foundry setup, but when I go to deploy the manifest, I'm getting an error:
"Latest version for stemcell `bosh-stemcell' is unknown"
This is what the attempt looks like:
#bosh deployment cf-services.yml
Deployment set to `/Users/TimothyDunphy/test/cf-services.yml'
#bosh deploy
Acting as user 'director' on deployment 'cf-services-contrib' on 'microbosh-ba846726bed7032f1fd4'
Getting deployment properties from director...
Unable to get properties list from director, trying without it...
Latest version for stemcell `bosh-stemcell' is unknown
We're using Pivotal Cloud Foundry with Ops Manager Director v1.5.5 and Elastic Runtime 1.5.4. Bosh command line is: BOSH 1.3165.0
How can we correct this problem?
For reference, here's our yaml file:
name: cf-services-contrib
director_uuid: fd713790-b1bc-401a-8ea1-b8209f1cc90c
releases:
- name: cf-services-contrib
version: 1
compilation:
workers: 3
network: default
reuse_compilation_vms: true
update:
canaries: 1
canary_watch_time: 30000-60000
update_watch_time: 30000-60000
max_in_flight: 4
networks:
- name: floating
type: vip
cloud_properties: {}
- name: default
type: dynamic
resource_pools:
- name: common
network: default
size: 8
stemcell:
name: bosh-stemcell
version: latest
jobs:
- name: gateways
release: cf-services-contrib
template:
- elasticsearch_gateway
- mongodb_gateway
- memcached_gateway
- postgresql_gateway_ng
- redis_gateway
- rabbit_gateway
- vblob_gateway
instances: 1
resource_pool: common
networks:
- name: default
default: [dns, gateway]
properties:
# Service credentials
uaa_client_id: "cf"
uaa_endpoint: http://uaa.devcloudwest.inbcu.com
uaa_client_auth_credentials:
username: admin
password: b8b7b0917be5ce20d3e2
- name: mongodb_service_node
release: cf-services-contrib
template: mongodb_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]
- name: memcached_service_node
release: cf-services-contrib
template: memcached_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]
- name: vblob_service_node
release: cf-services-contrib
template: vblob_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]
- name: elasticsearch_service_node
release: cf-services-contrib
template: elasticsearch_node
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: "free"
networks:
- name: default
default: [dns, gateway]
- name: postgresql_service_node
release: cf-services-contrib
template: postgresql_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
postgresql_node:
plan: default
networks:
- name: default
default: [dns, gateway]
- name: redis_service_node
release: cf-services-contrib
template: redis_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]
- name: rabbit_service_node
release: cf-services-contrib
template: rabbit_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]
properties:
networks:
apps: default
management: default
cc:
srv_api_uri: http://api.devcloudwest.inbcu.com
nats:
address: 100.114.130.11
port: 25555
user: nats #CHANGE
password: ffbd63b59eb418d6a17b
authorization_timeout: 5
service_plans:
mongodb:
default:
description: "Developer, shared VM, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
backup:
enable: true
lifecycle:
enable: true
serialization: enable
snapshot:
quota: 1
memcached:
default:
description: "Developer"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
vblob:
default:
description: "Developer"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
elasticsearch:
"free":
description: "Developer"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
postgresql:
default:
description: "Developer, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
backup:
enable: false
lifecycle:
enable: false
serialization: enable
snapshot:
quota: 1
redis:
default:
description: "Developer, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
backup:
enable: false
lifecycle:
enable: false
serialization: enable
snapshot:
quota: 1
rabbit:
default:
description: "Developer, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
bandwidth_quotas:
per_second: 1
per_day: 10
time_window: 86400
backup:
enable: false
lifecycle:
enable: false
serialization: enable
snapshot:
quota: 1
mongodb_gateway:
token: f777da76-06b4-4817-a8d5-87bd77834aef
default_plan: default
supported_versions: ["2.2"]
version_aliases:
current: "2.2"
cc_api_version: v2
mongodb_node:
supported_versions: ["2.2"]
default_version: "2.2"
max_tmp: 900
memcached_gateway:
token: dc13a7d7-8276-411e-9f4a-065bfef5e4c4
supported_versions: ["1.4"]
version_aliases:
current: "1.4"
cc_api_version: v2
memcached_node:
supported_versions: ["1.4"]
default_version: "1.4"
vblob_gateway:
token: 98b4cbbe-6ef0-41ef-951c-532704645254
supported_versions: ["0.51"]
version_aliases:
current: "0.51"
cc_api_version: v2
vblob_node:
supported_versions: ["0.51"]
default_version: "0.51"
elasticsearch_gateway:
token: 7db2f57b-66d0-40ad-a45b-af43f68a9b26
supported_versions: ["0.20"]
version_aliases:
current: "0.20"
cc_api_version: v2
elasticsearch_node:
supported_versions: ["0.20"]
default_version: "0.20"
postgresql_gateway:
token: f75df200-4daf-45b5-b92a-cb7fa1a25660
default_plan: default
supported_versions: ["9.3"]
version_aliases:
current: "9.3"
cc_api_version: v2
postgresql_node:
supported_versions: ["9.3"]
default_version: "9.3"
max_tmp: 900
password: secret
redis_gateway:
token: b1d19bde-ea9c-43b5-a0c1-f000e801b8b7
default_plan: default
supported_versions: ["2.6"]
version_aliases:
current: "2.6"
cc_api_version: v2
redis_node:
supported_versions: ["2.6"]
default_version: "2.6"
max_tmp: 900
rabbit_gateway:
token: ce1e0d30-d803-4f02-895e-1fa7d09be797
default_plan: "default"
supported_versions: ["3.0"]
version_aliases:
current: "3.0"
cc_api_version: v2
rabbit_node:
supported_versions: ["3.0"]
default_version: "3.0"
max_tmp: 900
m_actions: ["restart"] #restarts crashed rabbitMQ nodes

swift_gateway:
token: 0247daa4-7689-4784-8950-89213215f0be
default_plan: "free"
supported_versions: ["1.0"]
cc_api_version: v2
swift_node:
supported_versions: ["1.0"]
default_version: "1.0"
name_suffix: 'a9s.eu'
swift_operator_role_id: '2021022271a74ecdb94ceeeeeae657ad'
admin_reseller_role_id: '3032033371a74ecdb94asedt4df896bj'

Couple of thoughts:

1. The cf-contrib-services release is old, the gateway is not supported
in upcoming CF versions. But it is open source and perhaps you can
upgraded it.

Perhaps try postgresql-docker-boshrelease instead.

Thanks for that info! I'll check out postgresql-docker-boshrelease!

2. The "bosh-stemcell" missing is because it now has a different name.
Run "bosh stemcells" to get the name of the stemcell you have available.
Then replace this name into your manifest.
If you switch to the boshrelease I suggested then you'll get the stemcell
name discovery for free via make_manifest script.

OK here's what I see:


#bosh stemcells
Acting as user 'director' on 'microbosh-ba846726bed7032f1fd4'


+------------------------------------------+---------------+---------+-----------------------------------------+
| Name | OS | Version | CID
|

+------------------------------------------+---------------+---------+-----------------------------------------+
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | | 2865.1* |
sc-90c410aa-7ea0-47e6-b6e2-b3e65f712331 |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3062* |
sc-abf52559-959b-49c7-98a5-2287094a50b6 |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3094* |
sc-4117bede-0db9-467d-adf2-6e01c2d35463 |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3100* |
sc-bb5af5e6-4c50-4187-8961-68fbfcd244e0 |

+------------------------------------------+---------------+---------+-----------------------------------------+

(*) Currently in-use

Stemcells total: 4

I'll give that a shot. I'll try changing the name of the stemcell in the
manifest. However I notice now that I get the same error when I run a bosh
cloud check command:

#bosh cck
Acting as user 'director' on deployment 'cf-services-contrib' on
'microbosh-ba846726bed7032f1fd4'
Latest version for stemcell `bosh-stemcell' is unknown

I'll also look into the make_manifest script!

If you're on vsphere you will need to create an extra template for your
networking needs etc. Ping me directly or via the github issues if you want
help on that.

Thanks! That will be a tremendous help! As I'm not an expert on VMWare and
that's what our cloud foundry is running on. As we're having a 1/2 for the
holiday today I may take that on next week. Thanks for the offer of help!

On Thu, Dec 31, 2015 at 11:13 AM, Dr Nic Williams <drnicwilliams(a)gmail.com

wrote:

Couple of thoughts:

1. The cf-contrib-services release is old, the gateway is not supported
in upcoming CF versions. But it is open source and perhaps you can
upgraded it.

Perhaps try postgresql-docker-boshrelease instead.

2. The "bosh-stemcell" missing is because it now has a different name.

Run "bosh stemcells" to get the name of the stemcell you have available.
Then replace this name into your manifest.

If you switch to the boshrelease I suggested then you'll get the stemcell
name discovery for free via make_manifest script.

If you're on vsphere you will need to create an extra template for your
networking needs etc. Ping me directly or via the github issues if you want
help on that.




On Thu, Dec 31, 2015 at 7:58 AM, Tim Dunphy <bluethundr(a)gmail.com> wrote:

Hey all,

We're attempting to get PostgreSQL as a service running in our PCF
environment. To do that, I'm trying to use this community release which
includes pgsql as well as a number of other services:

https://github.com/cloudfoundry-community/cf-services-contrib-release

I've created a yaml file that's supposed to add posgres to our Cloud
Foundry setup, but when I go to deploy the manifest, I'm getting an error:

"Latest version for stemcell `bosh-stemcell' is unknown"

This is what the attempt looks like:

#bosh deployment cf-services.yml
Deployment set to `/Users/TimothyDunphy/test/cf-services.yml'
#bosh deploy
Acting as user 'director' on deployment 'cf-services-contrib' on
'microbosh-ba846726bed7032f1fd4'
Getting deployment properties from director...
Unable to get properties list from director, trying without it...
Latest version for stemcell `bosh-stemcell' is unknown

We're using Pivotal Cloud Foundry with Ops Manager Director v1.5.5 and
Elastic Runtime 1.5.4. Bosh command line is: BOSH 1.3165.0

How can we correct this problem?

For reference, here's our yaml file:

name: cf-services-contrib
director_uuid: fd713790-b1bc-401a-8ea1-b8209f1cc90c

releases:
- name: cf-services-contrib
version: 1

compilation:
workers: 3
network: default
reuse_compilation_vms: true

update:
canaries: 1
canary_watch_time: 30000-60000
update_watch_time: 30000-60000
max_in_flight: 4

networks:
- name: floating
type: vip
cloud_properties: {}
- name: default
type: dynamic

resource_pools:
- name: common
network: default
size: 8
stemcell:
name: bosh-stemcell
version: latest

jobs:
- name: gateways
release: cf-services-contrib
template:
- elasticsearch_gateway
- mongodb_gateway
- memcached_gateway
- postgresql_gateway_ng
- redis_gateway
- rabbit_gateway
- vblob_gateway
instances: 1
resource_pool: common
networks:
- name: default
default: [dns, gateway]
properties:
# Service credentials
uaa_client_id: "cf"
uaa_endpoint: http://uaa.devcloudwest.inbcu.com
uaa_client_auth_credentials:
username: admin
password: b8b7b0917be5ce20d3e2

- name: mongodb_service_node
release: cf-services-contrib
template: mongodb_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: memcached_service_node
release: cf-services-contrib
template: memcached_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: vblob_service_node
release: cf-services-contrib
template: vblob_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: elasticsearch_service_node
release: cf-services-contrib
template: elasticsearch_node
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: "free"
networks:
- name: default
default: [dns, gateway]

- name: postgresql_service_node
release: cf-services-contrib
template: postgresql_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
postgresql_node:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: redis_service_node
release: cf-services-contrib
template: redis_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: rabbit_service_node
release: cf-services-contrib
template: rabbit_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

properties:
networks:
apps: default
management: default

cc:
srv_api_uri: http://api.devcloudwest.inbcu.com

nats:
address: 100.114.130.11
port: 25555
user: nats #CHANGE
password: ffbd63b59eb418d6a17b
authorization_timeout: 5

service_plans:
mongodb:
default:
description: "Developer, shared VM, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
backup:
enable: true
lifecycle:
enable: true
serialization: enable
snapshot:
quota: 1

memcached:
default:
description: "Developer"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125

vblob:
default:
description: "Developer"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125

elasticsearch:
"free":
description: "Developer"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125

postgresql:
default:
description: "Developer, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
backup:
enable: false
lifecycle:
enable: false
serialization: enable
snapshot:
quota: 1

redis:
default:
description: "Developer, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
backup:
enable: false
lifecycle:
enable: false
serialization: enable
snapshot:
quota: 1


rabbit:
default:
description: "Developer, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
bandwidth_quotas:
per_second: 1
per_day: 10
time_window: 86400
backup:
enable: false
lifecycle:
enable: false
serialization: enable
snapshot:
quota: 1

mongodb_gateway:
token: f777da76-06b4-4817-a8d5-87bd77834aef
default_plan: default
supported_versions: ["2.2"]
version_aliases:
current: "2.2"
cc_api_version: v2
mongodb_node:
supported_versions: ["2.2"]
default_version: "2.2"
max_tmp: 900

memcached_gateway:
token: dc13a7d7-8276-411e-9f4a-065bfef5e4c4
supported_versions: ["1.4"]
version_aliases:
current: "1.4"
cc_api_version: v2
memcached_node:
supported_versions: ["1.4"]
default_version: "1.4"

vblob_gateway:
token: 98b4cbbe-6ef0-41ef-951c-532704645254
supported_versions: ["0.51"]
version_aliases:
current: "0.51"
cc_api_version: v2
vblob_node:
supported_versions: ["0.51"]
default_version: "0.51"

elasticsearch_gateway:
token: 7db2f57b-66d0-40ad-a45b-af43f68a9b26
supported_versions: ["0.20"]
version_aliases:
current: "0.20"
cc_api_version: v2
elasticsearch_node:
supported_versions: ["0.20"]
default_version: "0.20"

postgresql_gateway:
token: f75df200-4daf-45b5-b92a-cb7fa1a25660
default_plan: default
supported_versions: ["9.3"]
version_aliases:
current: "9.3"
cc_api_version: v2
postgresql_node:
supported_versions: ["9.3"]
default_version: "9.3"
max_tmp: 900
password: secret

redis_gateway:
token: b1d19bde-ea9c-43b5-a0c1-f000e801b8b7
default_plan: default
supported_versions: ["2.6"]
version_aliases:
current: "2.6"
cc_api_version: v2
redis_node:
supported_versions: ["2.6"]
default_version: "2.6"
max_tmp: 900

rabbit_gateway:
token: ce1e0d30-d803-4f02-895e-1fa7d09be797
default_plan: "default"
supported_versions: ["3.0"]
version_aliases:
current: "3.0"
cc_api_version: v2
rabbit_node:
supported_versions: ["3.0"]
default_version: "3.0"
max_tmp: 900
m_actions: ["restart"] #restarts crashed rabbitMQ nodes

swift_gateway:
token: 0247daa4-7689-4784-8950-89213215f0be
default_plan: "free"
supported_versions: ["1.0"]
cc_api_version: v2
swift_node:
supported_versions: ["1.0"]
default_version: "1.0"
name_suffix: 'a9s.eu'
swift_operator_role_id: '2021022271a74ecdb94ceeeeeae657ad'
admin_reseller_role_id: '3032033371a74ecdb94asedt4df896bj'

--
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

I've made a little progress! And thanks for your suggestion to use the
postgresql-docker-boshrelease.
But we're only ER 1.5.5 and I don't believe there's docker support for that
version. We're on 1.6 in our POC environment, which does support docker,
but I need to implement this in the 1.5.5 environement for now.
What I did was list the change the name of the bosh stemcell in the
manifest. And changed the word 'template' to 'templates' in the manifest
due to warning I was receiving. Lastly I changed the name of the manifest
to the current deployment.
Now I'm getting this error:
Error 40000: Object ("mongodb_gateway") did not match the required type
`Hash'
When I run a debug I get this output:
D, [2015-12-31 17:34:41 #19911] [task:2219] DEBUG -- DirectorJobRunner:
SENT: hm.director.alert
{"id":"0667960d-04d6-45b0-8790-65626c1cac1f","severity":3,"title":"director
- error during update deployment","summary":"Error during update deployment
for 'cf-22b9f4d62bb6f0563b71' against Director
'fd713790-b1bc-401a-8ea1-b8209f1cc90c':
#<Bosh::Director::ValidationInvalidType: Object (\"mongodb_gateway\") did
not match the required type `Hash'>","created_at":1451583281}
E, [2015-12-31 17:34:41 #19911] [task:2219] ERROR -- DirectorJobRunner:
Object ("mongodb_gateway") did not match the required type `Hash'
This is how I have my mongodb_gateway defined:
mongodb_gateway:
token: f777da76-06b4-4817-a8d5-87bd77834aef
default_plan: default
supported_versions: ["2.2"]
version_aliases:
current: "2.2"
cc_api_version: v2
mongodb_node:
supported_versions: ["2.2"]
default_version: "2.2"
max_tmp: 900
Is there a specific process I need to follow to generate the token? I think
that's what it's barking at here.
I'm enclosing the manifest file and the debug output from the bosh command.
I'd appreciate any help I can find! :)
Thanks,
Tim
On Thu, Dec 31, 2015 at 11:30 AM, Tim Dunphy <bluethundr(a)gmail.com> wrote:

Couple of thoughts:

1. The cf-contrib-services release is old, the gateway is not supported
in upcoming CF versions. But it is open source and perhaps you can
upgraded it.

Perhaps try postgresql-docker-boshrelease instead.

Thanks for that info! I'll check out postgresql-docker-boshrelease!

2. The "bosh-stemcell" missing is because it now has a different name.
Run "bosh stemcells" to get the name of the stemcell you have available.
Then replace this name into your manifest.
If you switch to the boshrelease I suggested then you'll get the stemcell
name discovery for free via make_manifest script.

OK here's what I see:


#bosh stemcells
Acting as user 'director' on 'microbosh-ba846726bed7032f1fd4'


+------------------------------------------+---------------+---------+-----------------------------------------+
| Name | OS | Version | CID
|

+------------------------------------------+---------------+---------+-----------------------------------------+
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | | 2865.1* |
sc-90c410aa-7ea0-47e6-b6e2-b3e65f712331 |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3062* |
sc-abf52559-959b-49c7-98a5-2287094a50b6 |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3094* |
sc-4117bede-0db9-467d-adf2-6e01c2d35463 |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3100* |
sc-bb5af5e6-4c50-4187-8961-68fbfcd244e0 |

+------------------------------------------+---------------+---------+-----------------------------------------+

(*) Currently in-use

Stemcells total: 4

I'll give that a shot. I'll try changing the name of the stemcell in the
manifest. However I notice now that I get the same error when I run a bosh
cloud check command:

#bosh cck
Acting as user 'director' on deployment 'cf-services-contrib' on
'microbosh-ba846726bed7032f1fd4'
Latest version for stemcell `bosh-stemcell' is unknown

I'll also look into the make_manifest script!

If you're on vsphere you will need to create an extra template for your
networking needs etc. Ping me directly or via the github issues if you want
help on that.

Thanks! That will be a tremendous help! As I'm not an expert on VMWare and
that's what our cloud foundry is running on. As we're having a 1/2 for the
holiday today I may take that on next week. Thanks for the offer of help!

On Thu, Dec 31, 2015 at 11:13 AM, Dr Nic Williams <drnicwilliams(a)gmail.com

wrote:

Couple of thoughts:

1. The cf-contrib-services release is old, the gateway is not supported
in upcoming CF versions. But it is open source and perhaps you can
upgraded it.

Perhaps try postgresql-docker-boshrelease instead.

2. The "bosh-stemcell" missing is because it now has a different name.

Run "bosh stemcells" to get the name of the stemcell you have available.
Then replace this name into your manifest.

If you switch to the boshrelease I suggested then you'll get the stemcell
name discovery for free via make_manifest script.

If you're on vsphere you will need to create an extra template for your
networking needs etc. Ping me directly or via the github issues if you want
help on that.




On Thu, Dec 31, 2015 at 7:58 AM, Tim Dunphy <bluethundr(a)gmail.com> wrote:

Hey all,

We're attempting to get PostgreSQL as a service running in our PCF
environment. To do that, I'm trying to use this community release which
includes pgsql as well as a number of other services:

https://github.com/cloudfoundry-community/cf-services-contrib-release

I've created a yaml file that's supposed to add posgres to our Cloud
Foundry setup, but when I go to deploy the manifest, I'm getting an error:

"Latest version for stemcell `bosh-stemcell' is unknown"

This is what the attempt looks like:

#bosh deployment cf-services.yml
Deployment set to `/Users/TimothyDunphy/test/cf-services.yml'
#bosh deploy
Acting as user 'director' on deployment 'cf-services-contrib' on
'microbosh-ba846726bed7032f1fd4'
Getting deployment properties from director...
Unable to get properties list from director, trying without it...
Latest version for stemcell `bosh-stemcell' is unknown

We're using Pivotal Cloud Foundry with Ops Manager Director v1.5.5 and
Elastic Runtime 1.5.4. Bosh command line is: BOSH 1.3165.0

How can we correct this problem?

For reference, here's our yaml file:

name: cf-services-contrib
director_uuid: fd713790-b1bc-401a-8ea1-b8209f1cc90c

releases:
- name: cf-services-contrib
version: 1

compilation:
workers: 3
network: default
reuse_compilation_vms: true

update:
canaries: 1
canary_watch_time: 30000-60000
update_watch_time: 30000-60000
max_in_flight: 4

networks:
- name: floating
type: vip
cloud_properties: {}
- name: default
type: dynamic

resource_pools:
- name: common
network: default
size: 8
stemcell:
name: bosh-stemcell
version: latest

jobs:
- name: gateways
release: cf-services-contrib
template:
- elasticsearch_gateway
- mongodb_gateway
- memcached_gateway
- postgresql_gateway_ng
- redis_gateway
- rabbit_gateway
- vblob_gateway
instances: 1
resource_pool: common
networks:
- name: default
default: [dns, gateway]
properties:
# Service credentials
uaa_client_id: "cf"
uaa_endpoint: http://uaa.devcloudwest.inbcu.com
uaa_client_auth_credentials:
username: admin
password: b8b7b0917be5ce20d3e2

- name: mongodb_service_node
release: cf-services-contrib
template: mongodb_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: memcached_service_node
release: cf-services-contrib
template: memcached_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: vblob_service_node
release: cf-services-contrib
template: vblob_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: elasticsearch_service_node
release: cf-services-contrib
template: elasticsearch_node
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: "free"
networks:
- name: default
default: [dns, gateway]

- name: postgresql_service_node
release: cf-services-contrib
template: postgresql_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
postgresql_node:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: redis_service_node
release: cf-services-contrib
template: redis_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: rabbit_service_node
release: cf-services-contrib
template: rabbit_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

properties:
networks:
apps: default
management: default

cc:
srv_api_uri: http://api.devcloudwest.inbcu.com

nats:
address: 100.114.130.11
port: 25555
user: nats #CHANGE
password: ffbd63b59eb418d6a17b
authorization_timeout: 5

service_plans:
mongodb:
default:
description: "Developer, shared VM, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
backup:
enable: true
lifecycle:
enable: true
serialization: enable
snapshot:
quota: 1

memcached:
default:
description: "Developer"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125

vblob:
default:
description: "Developer"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125

elasticsearch:
"free":
description: "Developer"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125

postgresql:
default:
description: "Developer, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
backup:
enable: false
lifecycle:
enable: false
serialization: enable
snapshot:
quota: 1

redis:
default:
description: "Developer, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
backup:
enable: false
lifecycle:
enable: false
serialization: enable
snapshot:
quota: 1


rabbit:
default:
description: "Developer, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
bandwidth_quotas:
per_second: 1
per_day: 10
time_window: 86400
backup:
enable: false
lifecycle:
enable: false
serialization: enable
snapshot:
quota: 1

mongodb_gateway:
token: f777da76-06b4-4817-a8d5-87bd77834aef
default_plan: default
supported_versions: ["2.2"]
version_aliases:
current: "2.2"
cc_api_version: v2
mongodb_node:
supported_versions: ["2.2"]
default_version: "2.2"
max_tmp: 900

memcached_gateway:
token: dc13a7d7-8276-411e-9f4a-065bfef5e4c4
supported_versions: ["1.4"]
version_aliases:
current: "1.4"
cc_api_version: v2
memcached_node:
supported_versions: ["1.4"]
default_version: "1.4"

vblob_gateway:
token: 98b4cbbe-6ef0-41ef-951c-532704645254
supported_versions: ["0.51"]
version_aliases:
current: "0.51"
cc_api_version: v2
vblob_node:
supported_versions: ["0.51"]
default_version: "0.51"

elasticsearch_gateway:
token: 7db2f57b-66d0-40ad-a45b-af43f68a9b26
supported_versions: ["0.20"]
version_aliases:
current: "0.20"
cc_api_version: v2
elasticsearch_node:
supported_versions: ["0.20"]
default_version: "0.20"

postgresql_gateway:
token: f75df200-4daf-45b5-b92a-cb7fa1a25660
default_plan: default
supported_versions: ["9.3"]
version_aliases:
current: "9.3"
cc_api_version: v2
postgresql_node:
supported_versions: ["9.3"]
default_version: "9.3"
max_tmp: 900
password: secret

redis_gateway:
token: b1d19bde-ea9c-43b5-a0c1-f000e801b8b7
default_plan: default
supported_versions: ["2.6"]
version_aliases:
current: "2.6"
cc_api_version: v2
redis_node:
supported_versions: ["2.6"]
default_version: "2.6"
max_tmp: 900

rabbit_gateway:
token: ce1e0d30-d803-4f02-895e-1fa7d09be797
default_plan: "default"
supported_versions: ["3.0"]
version_aliases:
current: "3.0"
cc_api_version: v2
rabbit_node:
supported_versions: ["3.0"]
default_version: "3.0"
max_tmp: 900
m_actions: ["restart"] #restarts crashed rabbitMQ nodes

swift_gateway:
token: 0247daa4-7689-4784-8950-89213215f0be
default_plan: "free"
supported_versions: ["1.0"]
cc_api_version: v2
swift_node:
supported_versions: ["1.0"]
default_version: "1.0"
name_suffix: 'a9s.eu'
swift_operator_role_id: '2021022271a74ecdb94ceeeeeae657ad'
admin_reseller_role_id: '3032033371a74ecdb94asedt4df896bj'

--
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

--
GPG me!!
gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

I've made a little progress! And thanks for your suggestion to use the
postgresql-docker-boshrelease.
But we're only ER 1.5.5 and I don't believe there's docker support for that
version. We're on 1.6 in our POC environment, which does support docker,
but I need to implement this in the 1.5.5 environement for now.
What I did was list the change the name of the bosh stemcell in the
manifest. And changed the word 'template' to 'templates' in the manifest
due to warning I was receiving. Lastly I changed the name of the manifest
to the current deployment.
Now I'm getting this error:
Error 40000: Object ("mongodb_gateway") did not match the required type
`Hash'
When I run a debug I get this output:
D, [2015-12-31 17:34:41 #19911] [task:2219] DEBUG -- DirectorJobRunner:
SENT: hm.director.alert
{"id":"0667960d-04d6-45b0-8790-65626c1cac1f","severity":3,"title":"director
- error during update deployment","summary":"Error during update deployment
for 'cf-22b9f4d62bb6f0563b71' against Director
'fd713790-b1bc-401a-8ea1-b8209f1cc90c':
#<Bosh::Director::ValidationInvalidType: Object (\"mongodb_gateway\") did
not match the required type `Hash'>","created_at":1451583281}
E, [2015-12-31 17:34:41 #19911] [task:2219] ERROR -- DirectorJobRunner:
Object ("mongodb_gateway") did not match the required type `Hash'
This is how I have my mongodb_gateway defined:
mongodb_gateway:
token: f777da76-06b4-4817-a8d5-87bd77834aef
default_plan: default
supported_versions: ["2.2"]
version_aliases:
current: "2.2"
cc_api_version: v2
mongodb_node:
supported_versions: ["2.2"]
default_version: "2.2"
max_tmp: 900
Is there a specific process I need to follow to generate the token? I think
that's what it's barking at here.
I'm enclosing the manifest file and the debug output from the bosh command.
I'd appreciate any help I can find! :)
Thanks,
Tim
On Thu, Dec 31, 2015 at 11:30 AM, Tim Dunphy <bluethundr(a)gmail.com> wrote:

Couple of thoughts:

1. The cf-contrib-services release is old, the gateway is not supported
in upcoming CF versions. But it is open source and perhaps you can
upgraded it.

Perhaps try postgresql-docker-boshrelease instead.

Thanks for that info! I'll check out postgresql-docker-boshrelease!

2. The "bosh-stemcell" missing is because it now has a different name.
Run "bosh stemcells" to get the name of the stemcell you have available.
Then replace this name into your manifest.
If you switch to the boshrelease I suggested then you'll get the stemcell
name discovery for free via make_manifest script.

OK here's what I see:


#bosh stemcells
Acting as user 'director' on 'microbosh-ba846726bed7032f1fd4'


+------------------------------------------+---------------+---------+-----------------------------------------+
| Name | OS | Version | CID
|

+------------------------------------------+---------------+---------+-----------------------------------------+
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | | 2865.1* |
sc-90c410aa-7ea0-47e6-b6e2-b3e65f712331 |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3062* |
sc-abf52559-959b-49c7-98a5-2287094a50b6 |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3094* |
sc-4117bede-0db9-467d-adf2-6e01c2d35463 |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3100* |
sc-bb5af5e6-4c50-4187-8961-68fbfcd244e0 |

+------------------------------------------+---------------+---------+-----------------------------------------+

(*) Currently in-use

Stemcells total: 4

I'll give that a shot. I'll try changing the name of the stemcell in the
manifest. However I notice now that I get the same error when I run a bosh
cloud check command:

#bosh cck
Acting as user 'director' on deployment 'cf-services-contrib' on
'microbosh-ba846726bed7032f1fd4'
Latest version for stemcell `bosh-stemcell' is unknown

I'll also look into the make_manifest script!

If you're on vsphere you will need to create an extra template for your
networking needs etc. Ping me directly or via the github issues if you want
help on that.

Thanks! That will be a tremendous help! As I'm not an expert on VMWare and
that's what our cloud foundry is running on. As we're having a 1/2 for the
holiday today I may take that on next week. Thanks for the offer of help!

On Thu, Dec 31, 2015 at 11:13 AM, Dr Nic Williams <drnicwilliams(a)gmail.com

wrote:

Couple of thoughts:

1. The cf-contrib-services release is old, the gateway is not supported
in upcoming CF versions. But it is open source and perhaps you can
upgraded it.

Perhaps try postgresql-docker-boshrelease instead.

2. The "bosh-stemcell" missing is because it now has a different name.

Run "bosh stemcells" to get the name of the stemcell you have available.
Then replace this name into your manifest.

If you switch to the boshrelease I suggested then you'll get the stemcell
name discovery for free via make_manifest script.

If you're on vsphere you will need to create an extra template for your
networking needs etc. Ping me directly or via the github issues if you want
help on that.




On Thu, Dec 31, 2015 at 7:58 AM, Tim Dunphy <bluethundr(a)gmail.com> wrote:

Hey all,

We're attempting to get PostgreSQL as a service running in our PCF
environment. To do that, I'm trying to use this community release which
includes pgsql as well as a number of other services:

https://github.com/cloudfoundry-community/cf-services-contrib-release

I've created a yaml file that's supposed to add posgres to our Cloud
Foundry setup, but when I go to deploy the manifest, I'm getting an error:

"Latest version for stemcell `bosh-stemcell' is unknown"

This is what the attempt looks like:

#bosh deployment cf-services.yml
Deployment set to `/Users/TimothyDunphy/test/cf-services.yml'
#bosh deploy
Acting as user 'director' on deployment 'cf-services-contrib' on
'microbosh-ba846726bed7032f1fd4'
Getting deployment properties from director...
Unable to get properties list from director, trying without it...
Latest version for stemcell `bosh-stemcell' is unknown

We're using Pivotal Cloud Foundry with Ops Manager Director v1.5.5 and
Elastic Runtime 1.5.4. Bosh command line is: BOSH 1.3165.0

How can we correct this problem?

For reference, here's our yaml file:

name: cf-services-contrib
director_uuid: fd713790-b1bc-401a-8ea1-b8209f1cc90c

releases:
- name: cf-services-contrib
version: 1

compilation:
workers: 3
network: default
reuse_compilation_vms: true

update:
canaries: 1
canary_watch_time: 30000-60000
update_watch_time: 30000-60000
max_in_flight: 4

networks:
- name: floating
type: vip
cloud_properties: {}
- name: default
type: dynamic

resource_pools:
- name: common
network: default
size: 8
stemcell:
name: bosh-stemcell
version: latest

jobs:
- name: gateways
release: cf-services-contrib
template:
- elasticsearch_gateway
- mongodb_gateway
- memcached_gateway
- postgresql_gateway_ng
- redis_gateway
- rabbit_gateway
- vblob_gateway
instances: 1
resource_pool: common
networks:
- name: default
default: [dns, gateway]
properties:
# Service credentials
uaa_client_id: "cf"
uaa_endpoint: http://uaa.devcloudwest.inbcu.com
uaa_client_auth_credentials:
username: admin
password: b8b7b0917be5ce20d3e2

- name: mongodb_service_node
release: cf-services-contrib
template: mongodb_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: memcached_service_node
release: cf-services-contrib
template: memcached_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: vblob_service_node
release: cf-services-contrib
template: vblob_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: elasticsearch_service_node
release: cf-services-contrib
template: elasticsearch_node
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: "free"
networks:
- name: default
default: [dns, gateway]

- name: postgresql_service_node
release: cf-services-contrib
template: postgresql_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
postgresql_node:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: redis_service_node
release: cf-services-contrib
template: redis_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: rabbit_service_node
release: cf-services-contrib
template: rabbit_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

properties:
networks:
apps: default
management: default

cc:
srv_api_uri: http://api.devcloudwest.inbcu.com

nats:
address: 100.114.130.11
port: 25555
user: nats #CHANGE
password: ffbd63b59eb418d6a17b
authorization_timeout: 5

service_plans:
mongodb:
default:
description: "Developer, shared VM, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
backup:
enable: true
lifecycle:
enable: true
serialization: enable
snapshot:
quota: 1

memcached:
default:
description: "Developer"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125

vblob:
default:
description: "Developer"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125

elasticsearch:
"free":
description: "Developer"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125

postgresql:
default:
description: "Developer, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
backup:
enable: false
lifecycle:
enable: false
serialization: enable
snapshot:
quota: 1

redis:
default:
description: "Developer, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
backup:
enable: false
lifecycle:
enable: false
serialization: enable
snapshot:
quota: 1


rabbit:
default:
description: "Developer, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
bandwidth_quotas:
per_second: 1
per_day: 10
time_window: 86400
backup:
enable: false
lifecycle:
enable: false
serialization: enable
snapshot:
quota: 1

mongodb_gateway:
token: f777da76-06b4-4817-a8d5-87bd77834aef
default_plan: default
supported_versions: ["2.2"]
version_aliases:
current: "2.2"
cc_api_version: v2
mongodb_node:
supported_versions: ["2.2"]
default_version: "2.2"
max_tmp: 900

memcached_gateway:
token: dc13a7d7-8276-411e-9f4a-065bfef5e4c4
supported_versions: ["1.4"]
version_aliases:
current: "1.4"
cc_api_version: v2
memcached_node:
supported_versions: ["1.4"]
default_version: "1.4"

vblob_gateway:
token: 98b4cbbe-6ef0-41ef-951c-532704645254
supported_versions: ["0.51"]
version_aliases:
current: "0.51"
cc_api_version: v2
vblob_node:
supported_versions: ["0.51"]
default_version: "0.51"

elasticsearch_gateway:
token: 7db2f57b-66d0-40ad-a45b-af43f68a9b26
supported_versions: ["0.20"]
version_aliases:
current: "0.20"
cc_api_version: v2
elasticsearch_node:
supported_versions: ["0.20"]
default_version: "0.20"

postgresql_gateway:
token: f75df200-4daf-45b5-b92a-cb7fa1a25660
default_plan: default
supported_versions: ["9.3"]
version_aliases:
current: "9.3"
cc_api_version: v2
postgresql_node:
supported_versions: ["9.3"]
default_version: "9.3"
max_tmp: 900
password: secret

redis_gateway:
token: b1d19bde-ea9c-43b5-a0c1-f000e801b8b7
default_plan: default
supported_versions: ["2.6"]
version_aliases:
current: "2.6"
cc_api_version: v2
redis_node:
supported_versions: ["2.6"]
default_version: "2.6"
max_tmp: 900

rabbit_gateway:
token: ce1e0d30-d803-4f02-895e-1fa7d09be797
default_plan: "default"
supported_versions: ["3.0"]
version_aliases:
current: "3.0"
cc_api_version: v2
rabbit_node:
supported_versions: ["3.0"]
default_version: "3.0"
max_tmp: 900
m_actions: ["restart"] #restarts crashed rabbitMQ nodes

swift_gateway:
token: 0247daa4-7689-4784-8950-89213215f0be
default_plan: "free"
supported_versions: ["1.0"]
cc_api_version: v2
swift_node:
supported_versions: ["1.0"]
default_version: "1.0"
name_suffix: 'a9s.eu'
swift_operator_role_id: '2021022271a74ecdb94ceeeeeae657ad'
admin_reseller_role_id: '3032033371a74ecdb94asedt4df896bj'

--
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

--
GPG me!!
gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

I can't open your yml attachments from my phone (gists are good as they
are readable and syntax highlighted)
The error - somewhere you are passing "mongodb_gateway" as a value to a
key; but BOSH wants you to pass a Hash (key/value)
I think that your jobs: section should be upgraded to replace release: and
template: keys with a single templates: key; and it is a list of Hash
(name: & release:)

Ok! So this is what I have now, that seems to be causing the error:
- name: mongodb_service_node
release: cf-services-contrib
templates: mongodb_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]
So if I understand you correctly, I think what bosh wants is something like
this:
templates: {
name: mongodb_service_node,
release: cf-services-contrib,
instances: 1,
resource_pool: common,
persistent_disk: 10000,
properties:
- plan: default,
networks:
- name: default
default: [dns, gateway]
}
However the last two lines are tripping me up! How would I express the
properties and networks sections in yaml?
Thanks,
Tim
On Thu, Dec 31, 2015 at 1:59 PM, Dr Nic Williams <drnicwilliams(a)gmail.com>
wrote:

I can't open your yml attachments from my phone (gists are good as they
are readable and syntax highlighted)

The error - somewhere you are passing "mongodb_gateway" as a value to a
key; but BOSH wants you to pass a Hash (key/value)

I think that your jobs: section should be upgraded to replace release: and
template: keys with a single templates: key; and it is a list of Hash
(name: & release:)




On Thu, Dec 31, 2015 at 9:43 AM, Tim Dunphy <bluethundr(a)gmail.com> wrote:

I've made a little progress! And thanks for your suggestion to use the postgresql-docker-boshrelease.
But we're only ER 1.5.5 and I don't believe there's docker support for that
version. We're on 1.6 in our POC environment, which does support docker,
but I need to implement this in the 1.5.5 environement for now.


What I did was list the change the name of the bosh stemcell in the
manifest. And changed the word 'template' to 'templates' in the manifest
due to warning I was receiving. Lastly I changed the name of the manifest
to the current deployment.

Now I'm getting this error:

Error 40000: Object ("mongodb_gateway") did not match the required type
`Hash'


When I run a debug I get this output:

D, [2015-12-31 17:34:41 #19911] [task:2219] DEBUG -- DirectorJobRunner:
SENT: hm.director.alert
{"id":"0667960d-04d6-45b0-8790-65626c1cac1f","severity":3,"title":"director
- error during update deployment","summary":"Error during update deployment
for 'cf-22b9f4d62bb6f0563b71' against Director
'fd713790-b1bc-401a-8ea1-b8209f1cc90c':
#<Bosh::Director::ValidationInvalidType: Object (\"mongodb_gateway\") did
not match the required type `Hash'>","created_at":1451583281}
E, [2015-12-31 17:34:41 #19911] [task:2219] ERROR -- DirectorJobRunner:
Object ("mongodb_gateway") did not match the required type `Hash'

This is how I have my mongodb_gateway defined:

mongodb_gateway:
token: f777da76-06b4-4817-a8d5-87bd77834aef
default_plan: default
supported_versions: ["2.2"]
version_aliases:
current: "2.2"
cc_api_version: v2
mongodb_node:
supported_versions: ["2.2"]
default_version: "2.2"
max_tmp: 900

Is there a specific process I need to follow to generate the token? I
think that's what it's barking at here.

I'm enclosing the manifest file and the debug output from the bosh
command. I'd appreciate any help I can find! :)

Thanks,
Tim



On Thu, Dec 31, 2015 at 11:30 AM, Tim Dunphy <bluethundr(a)gmail.com>
wrote:

Couple of thoughts:

1. The cf-contrib-services release is old, the gateway is not supported
in upcoming CF versions. But it is open source and perhaps you can
upgraded it.

Perhaps try postgresql-docker-boshrelease instead.

Thanks for that info! I'll check out postgresql-docker-boshrelease!

2. The "bosh-stemcell" missing is because it now has a different name.
Run "bosh stemcells" to get the name of the stemcell you have
available. Then replace this name into your manifest.
If you switch to the boshrelease I suggested then you'll get the
stemcell name discovery for free via make_manifest script.

OK here's what I see:


#bosh stemcells
Acting as user 'director' on 'microbosh-ba846726bed7032f1fd4'


+------------------------------------------+---------------+---------+-----------------------------------------+
| Name | OS | Version |
CID |

+------------------------------------------+---------------+---------+-----------------------------------------+
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | | 2865.1* |
sc-90c410aa-7ea0-47e6-b6e2-b3e65f712331 |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3062* |
sc-abf52559-959b-49c7-98a5-2287094a50b6 |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3094* |
sc-4117bede-0db9-467d-adf2-6e01c2d35463 |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3100* |
sc-bb5af5e6-4c50-4187-8961-68fbfcd244e0 |

+------------------------------------------+---------------+---------+-----------------------------------------+

(*) Currently in-use

Stemcells total: 4

I'll give that a shot. I'll try changing the name of the stemcell in the
manifest. However I notice now that I get the same error when I run a bosh
cloud check command:

#bosh cck
Acting as user 'director' on deployment 'cf-services-contrib' on
'microbosh-ba846726bed7032f1fd4'
Latest version for stemcell `bosh-stemcell' is unknown

I'll also look into the make_manifest script!

If you're on vsphere you will need to create an extra template for your
networking needs etc. Ping me directly or via the github issues if you want
help on that.

Thanks! That will be a tremendous help! As I'm not an expert on VMWare
and that's what our cloud foundry is running on. As we're having a 1/2 for
the holiday today I may take that on next week. Thanks for the offer of
help!

On Thu, Dec 31, 2015 at 11:13 AM, Dr Nic Williams <
drnicwilliams(a)gmail.com> wrote:

Couple of thoughts:

1. The cf-contrib-services release is old, the gateway is not supported
in upcoming CF versions. But it is open source and perhaps you can
upgraded it.

Perhaps try postgresql-docker-boshrelease instead.

2. The "bosh-stemcell" missing is because it now has a different name.

Run "bosh stemcells" to get the name of the stemcell you have
available. Then replace this name into your manifest.

If you switch to the boshrelease I suggested then you'll get the
stemcell name discovery for free via make_manifest script.

If you're on vsphere you will need to create an extra template for your
networking needs etc. Ping me directly or via the github issues if you want
help on that.




On Thu, Dec 31, 2015 at 7:58 AM, Tim Dunphy <bluethundr(a)gmail.com>
wrote:

Hey all,

We're attempting to get PostgreSQL as a service running in our PCF
environment. To do that, I'm trying to use this community release which
includes pgsql as well as a number of other services:

https://github.com/cloudfoundry-community/cf-services-contrib-release

I've created a yaml file that's supposed to add posgres to our Cloud
Foundry setup, but when I go to deploy the manifest, I'm getting an error:

"Latest version for stemcell `bosh-stemcell' is unknown"

This is what the attempt looks like:

#bosh deployment cf-services.yml
Deployment set to `/Users/TimothyDunphy/test/cf-services.yml'
#bosh deploy
Acting as user 'director' on deployment 'cf-services-contrib' on
'microbosh-ba846726bed7032f1fd4'
Getting deployment properties from director...
Unable to get properties list from director, trying without it...
Latest version for stemcell `bosh-stemcell' is unknown

We're using Pivotal Cloud Foundry with Ops Manager Director v1.5.5 and
Elastic Runtime 1.5.4. Bosh command line is: BOSH 1.3165.0

How can we correct this problem?

For reference, here's our yaml file:

name: cf-services-contrib
director_uuid: fd713790-b1bc-401a-8ea1-b8209f1cc90c

releases:
- name: cf-services-contrib
version: 1

compilation:
workers: 3
network: default
reuse_compilation_vms: true

update:
canaries: 1
canary_watch_time: 30000-60000
update_watch_time: 30000-60000
max_in_flight: 4

networks:
- name: floating
type: vip
cloud_properties: {}
- name: default
type: dynamic

resource_pools:
- name: common
network: default
size: 8
stemcell:
name: bosh-stemcell
version: latest

jobs:
- name: gateways
release: cf-services-contrib
template:
- elasticsearch_gateway
- mongodb_gateway
- memcached_gateway
- postgresql_gateway_ng
- redis_gateway
- rabbit_gateway
- vblob_gateway
instances: 1
resource_pool: common
networks:
- name: default
default: [dns, gateway]
properties:
# Service credentials
uaa_client_id: "cf"
uaa_endpoint: http://uaa.devcloudwest.inbcu.com
uaa_client_auth_credentials:
username: admin
password: b8b7b0917be5ce20d3e2

- name: mongodb_service_node
release: cf-services-contrib
template: mongodb_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: memcached_service_node
release: cf-services-contrib
template: memcached_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: vblob_service_node
release: cf-services-contrib
template: vblob_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: elasticsearch_service_node
release: cf-services-contrib
template: elasticsearch_node
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: "free"
networks:
- name: default
default: [dns, gateway]

- name: postgresql_service_node
release: cf-services-contrib
template: postgresql_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
postgresql_node:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: redis_service_node
release: cf-services-contrib
template: redis_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: rabbit_service_node
release: cf-services-contrib
template: rabbit_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

properties:
networks:
apps: default
management: default

cc:
srv_api_uri: http://api.devcloudwest.inbcu.com

nats:
address: 100.114.130.11
port: 25555
user: nats #CHANGE
password: ffbd63b59eb418d6a17b
authorization_timeout: 5

service_plans:
mongodb:
default:
description: "Developer, shared VM, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
backup:
enable: true
lifecycle:
enable: true
serialization: enable
snapshot:
quota: 1

memcached:
default:
description: "Developer"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125

vblob:
default:
description: "Developer"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125

elasticsearch:
"free":
description: "Developer"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125

postgresql:
default:
description: "Developer, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
backup:
enable: false
lifecycle:
enable: false
serialization: enable
snapshot:
quota: 1

redis:
default:
description: "Developer, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
backup:
enable: false
lifecycle:
enable: false
serialization: enable
snapshot:
quota: 1


rabbit:
default:
description: "Developer, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
bandwidth_quotas:
per_second: 1
per_day: 10
time_window: 86400
backup:
enable: false
lifecycle:
enable: false
serialization: enable
snapshot:
quota: 1

mongodb_gateway:
token: f777da76-06b4-4817-a8d5-87bd77834aef
default_plan: default
supported_versions: ["2.2"]
version_aliases:
current: "2.2"
cc_api_version: v2
mongodb_node:
supported_versions: ["2.2"]
default_version: "2.2"
max_tmp: 900

memcached_gateway:
token: dc13a7d7-8276-411e-9f4a-065bfef5e4c4
supported_versions: ["1.4"]
version_aliases:
current: "1.4"
cc_api_version: v2
memcached_node:
supported_versions: ["1.4"]
default_version: "1.4"

vblob_gateway:
token: 98b4cbbe-6ef0-41ef-951c-532704645254
supported_versions: ["0.51"]
version_aliases:
current: "0.51"
cc_api_version: v2
vblob_node:
supported_versions: ["0.51"]
default_version: "0.51"

elasticsearch_gateway:
token: 7db2f57b-66d0-40ad-a45b-af43f68a9b26
supported_versions: ["0.20"]
version_aliases:
current: "0.20"
cc_api_version: v2
elasticsearch_node:
supported_versions: ["0.20"]
default_version: "0.20"

postgresql_gateway:
token: f75df200-4daf-45b5-b92a-cb7fa1a25660
default_plan: default
supported_versions: ["9.3"]
version_aliases:
current: "9.3"
cc_api_version: v2
postgresql_node:
supported_versions: ["9.3"]
default_version: "9.3"
max_tmp: 900
password: secret

redis_gateway:
token: b1d19bde-ea9c-43b5-a0c1-f000e801b8b7
default_plan: default
supported_versions: ["2.6"]
version_aliases:
current: "2.6"
cc_api_version: v2
redis_node:
supported_versions: ["2.6"]
default_version: "2.6"
max_tmp: 900

rabbit_gateway:
token: ce1e0d30-d803-4f02-895e-1fa7d09be797
default_plan: "default"
supported_versions: ["3.0"]
version_aliases:
current: "3.0"
cc_api_version: v2
rabbit_node:
supported_versions: ["3.0"]
default_version: "3.0"
max_tmp: 900
m_actions: ["restart"] #restarts crashed rabbitMQ nodes

swift_gateway:
token: 0247daa4-7689-4784-8950-89213215f0be
default_plan: "free"
supported_versions: ["1.0"]
cc_api_version: v2
swift_node:
supported_versions: ["1.0"]
default_version: "1.0"
name_suffix: 'a9s.eu'
swift_operator_role_id: '2021022271a74ecdb94ceeeeeae657ad'
admin_reseller_role_id: '3032033371a74ecdb94asedt4df896bj'

--
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

--
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

<bosh_error.txt><cf-services-list.yml>

--
GPG me!!
gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

Schema for each job is at

http://bosh.io/docs/deployment-manifest.html#jobs

Thanks!! I'll check it out!

On Thu, Dec 31, 2015 at 2:42 PM, Dr Nic Williams <drnicwilliams(a)gmail.com>
wrote:

Schema for each job is at
http://bosh.io/docs/deployment-manifest.html#jobs




On Thu, Dec 31, 2015 at 11:38 AM, Tim Dunphy <bluethundr(a)gmail.com>
wrote:

I can't open your yml attachments from my phone (gists are good as they

are readable and syntax highlighted)
The error - somewhere you are passing "mongodb_gateway" as a value to a
key; but BOSH wants you to pass a Hash (key/value)
I think that your jobs: section should be upgraded to replace release:
and template: keys with a single templates: key; and it is a list of Hash
(name: & release:)

Ok! So this is what I have now, that seems to be causing the error:

- name: mongodb_service_node
release: cf-services-contrib
templates: mongodb_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

So if I understand you correctly, I think what bosh wants is something
like this:

templates: {
name: mongodb_service_node,
release: cf-services-contrib,
instances: 1,
resource_pool: common,
persistent_disk: 10000,
properties:
- plan: default,
networks:
- name: default
default: [dns, gateway]
}


However the last two lines are tripping me up! How would I express the
properties and networks sections in yaml?

Thanks,
Tim


On Thu, Dec 31, 2015 at 1:59 PM, Dr Nic Williams <
drnicwilliams(a)gmail.com> wrote:

I can't open your yml attachments from my phone (gists are good as they
are readable and syntax highlighted)

The error - somewhere you are passing "mongodb_gateway" as a value to a
key; but BOSH wants you to pass a Hash (key/value)

I think that your jobs: section should be upgraded to replace release:
and template: keys with a single templates: key; and it is a list of Hash
(name: & release:)




On Thu, Dec 31, 2015 at 9:43 AM, Tim Dunphy <bluethundr(a)gmail.com>
wrote:

I've made a little progress! And thanks for your suggestion to use the postgresql-docker-boshrelease.
But we're only ER 1.5.5 and I don't believe there's docker support for that
version. We're on 1.6 in our POC environment, which does support docker,
but I need to implement this in the 1.5.5 environement for now.


What I did was list the change the name of the bosh stemcell in the
manifest. And changed the word 'template' to 'templates' in the manifest
due to warning I was receiving. Lastly I changed the name of the manifest
to the current deployment.

Now I'm getting this error:

Error 40000: Object ("mongodb_gateway") did not match the required
type `Hash'


When I run a debug I get this output:

D, [2015-12-31 17:34:41 #19911] [task:2219] DEBUG --
DirectorJobRunner: SENT: hm.director.alert
{"id":"0667960d-04d6-45b0-8790-65626c1cac1f","severity":3,"title":"director
- error during update deployment","summary":"Error during update deployment
for 'cf-22b9f4d62bb6f0563b71' against Director
'fd713790-b1bc-401a-8ea1-b8209f1cc90c':
#<Bosh::Director::ValidationInvalidType: Object (\"mongodb_gateway\") did
not match the required type `Hash'>","created_at":1451583281}
E, [2015-12-31 17:34:41 #19911] [task:2219] ERROR --
DirectorJobRunner: Object ("mongodb_gateway") did not match the required
type `Hash'

This is how I have my mongodb_gateway defined:

mongodb_gateway:
token: f777da76-06b4-4817-a8d5-87bd77834aef
default_plan: default
supported_versions: ["2.2"]
version_aliases:
current: "2.2"
cc_api_version: v2
mongodb_node:
supported_versions: ["2.2"]
default_version: "2.2"
max_tmp: 900

Is there a specific process I need to follow to generate the token? I
think that's what it's barking at here.

I'm enclosing the manifest file and the debug output from the bosh
command. I'd appreciate any help I can find! :)

Thanks,
Tim



On Thu, Dec 31, 2015 at 11:30 AM, Tim Dunphy <bluethundr(a)gmail.com>
wrote:

Couple of thoughts:

1. The cf-contrib-services release is old, the gateway is not
supported in upcoming CF versions. But it is open source and perhaps you
can upgraded it.

Perhaps try postgresql-docker-boshrelease instead.

Thanks for that info! I'll check out postgresql-docker-boshrelease!

2. The "bosh-stemcell" missing is because it now has a different
name.
Run "bosh stemcells" to get the name of the stemcell you have
available. Then replace this name into your manifest.
If you switch to the boshrelease I suggested then you'll get the
stemcell name discovery for free via make_manifest script.

OK here's what I see:


#bosh stemcells
Acting as user 'director' on 'microbosh-ba846726bed7032f1fd4'


+------------------------------------------+---------------+---------+-----------------------------------------+
| Name | OS | Version
| CID |

+------------------------------------------+---------------+---------+-----------------------------------------+
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | | 2865.1*
| sc-90c410aa-7ea0-47e6-b6e2-b3e65f712331 |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3062*
| sc-abf52559-959b-49c7-98a5-2287094a50b6 |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3094*
| sc-4117bede-0db9-467d-adf2-6e01c2d35463 |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3100*
| sc-bb5af5e6-4c50-4187-8961-68fbfcd244e0 |

+------------------------------------------+---------------+---------+-----------------------------------------+

(*) Currently in-use

Stemcells total: 4

I'll give that a shot. I'll try changing the name of the stemcell in
the manifest. However I notice now that I get the same error when I run a
bosh cloud check command:

#bosh cck
Acting as user 'director' on deployment 'cf-services-contrib' on
'microbosh-ba846726bed7032f1fd4'
Latest version for stemcell `bosh-stemcell' is unknown

I'll also look into the make_manifest script!

If you're on vsphere you will need to create an extra template for
your networking needs etc. Ping me directly or via the github issues if you
want help on that.

Thanks! That will be a tremendous help! As I'm not an expert on
VMWare and that's what our cloud foundry is running on. As we're having a
1/2 for the holiday today I may take that on next week. Thanks for the
offer of help!

On Thu, Dec 31, 2015 at 11:13 AM, Dr Nic Williams <
drnicwilliams(a)gmail.com> wrote:

Couple of thoughts:

1. The cf-contrib-services release is old, the gateway is not
supported in upcoming CF versions. But it is open source and perhaps you
can upgraded it.

Perhaps try postgresql-docker-boshrelease instead.

2. The "bosh-stemcell" missing is because it now has a different
name.

Run "bosh stemcells" to get the name of the stemcell you have
available. Then replace this name into your manifest.

If you switch to the boshrelease I suggested then you'll get the
stemcell name discovery for free via make_manifest script.

If you're on vsphere you will need to create an extra template for
your networking needs etc. Ping me directly or via the github issues if you
want help on that.




On Thu, Dec 31, 2015 at 7:58 AM, Tim Dunphy <bluethundr(a)gmail.com>
wrote:

Hey all,

We're attempting to get PostgreSQL as a service running in our PCF
environment. To do that, I'm trying to use this community release which
includes pgsql as well as a number of other services:


https://github.com/cloudfoundry-community/cf-services-contrib-release

I've created a yaml file that's supposed to add posgres to our
Cloud Foundry setup, but when I go to deploy the manifest, I'm getting an
error:

"Latest version for stemcell `bosh-stemcell' is unknown"

This is what the attempt looks like:

#bosh deployment cf-services.yml
Deployment set to `/Users/TimothyDunphy/test/cf-services.yml'
#bosh deploy
Acting as user 'director' on deployment 'cf-services-contrib' on
'microbosh-ba846726bed7032f1fd4'
Getting deployment properties from director...
Unable to get properties list from director, trying without it...
Latest version for stemcell `bosh-stemcell' is unknown

We're using Pivotal Cloud Foundry with Ops Manager Director v1.5.5
and Elastic Runtime 1.5.4. Bosh command line is: BOSH 1.3165.0

How can we correct this problem?

For reference, here's our yaml file:

name: cf-services-contrib
director_uuid: fd713790-b1bc-401a-8ea1-b8209f1cc90c

releases:
- name: cf-services-contrib
version: 1

compilation:
workers: 3
network: default
reuse_compilation_vms: true

update:
canaries: 1
canary_watch_time: 30000-60000
update_watch_time: 30000-60000
max_in_flight: 4

networks:
- name: floating
type: vip
cloud_properties: {}
- name: default
type: dynamic

resource_pools:
- name: common
network: default
size: 8
stemcell:
name: bosh-stemcell
version: latest

jobs:
- name: gateways
release: cf-services-contrib
template:
- elasticsearch_gateway
- mongodb_gateway
- memcached_gateway
- postgresql_gateway_ng
- redis_gateway
- rabbit_gateway
- vblob_gateway
instances: 1
resource_pool: common
networks:
- name: default
default: [dns, gateway]
properties:
# Service credentials
uaa_client_id: "cf"
uaa_endpoint: http://uaa.devcloudwest.inbcu.com
uaa_client_auth_credentials:
username: admin
password: b8b7b0917be5ce20d3e2

- name: mongodb_service_node
release: cf-services-contrib
template: mongodb_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: memcached_service_node
release: cf-services-contrib
template: memcached_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: vblob_service_node
release: cf-services-contrib
template: vblob_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: elasticsearch_service_node
release: cf-services-contrib
template: elasticsearch_node
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: "free"
networks:
- name: default
default: [dns, gateway]

- name: postgresql_service_node
release: cf-services-contrib
template: postgresql_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
postgresql_node:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: redis_service_node
release: cf-services-contrib
template: redis_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: rabbit_service_node
release: cf-services-contrib
template: rabbit_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

properties:
networks:
apps: default
management: default

cc:
srv_api_uri: http://api.devcloudwest.inbcu.com

nats:
address: 100.114.130.11
port: 25555
user: nats #CHANGE
password: ffbd63b59eb418d6a17b
authorization_timeout: 5

service_plans:
mongodb:
default:
description: "Developer, shared VM, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
backup:
enable: true
lifecycle:
enable: true
serialization: enable
snapshot:
quota: 1

memcached:
default:
description: "Developer"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125

vblob:
default:
description: "Developer"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125

elasticsearch:
"free":
description: "Developer"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125

postgresql:
default:
description: "Developer, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
backup:
enable: false
lifecycle:
enable: false
serialization: enable
snapshot:
quota: 1

redis:
default:
description: "Developer, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
backup:
enable: false
lifecycle:
enable: false
serialization: enable
snapshot:
quota: 1


rabbit:
default:
description: "Developer, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
bandwidth_quotas:
per_second: 1
per_day: 10
time_window: 86400
backup:
enable: false
lifecycle:
enable: false
serialization: enable
snapshot:
quota: 1

mongodb_gateway:
token: f777da76-06b4-4817-a8d5-87bd77834aef
default_plan: default
supported_versions: ["2.2"]
version_aliases:
current: "2.2"
cc_api_version: v2
mongodb_node:
supported_versions: ["2.2"]
default_version: "2.2"
max_tmp: 900

memcached_gateway:
token: dc13a7d7-8276-411e-9f4a-065bfef5e4c4
supported_versions: ["1.4"]
version_aliases:
current: "1.4"
cc_api_version: v2
memcached_node:
supported_versions: ["1.4"]
default_version: "1.4"

vblob_gateway:
token: 98b4cbbe-6ef0-41ef-951c-532704645254
supported_versions: ["0.51"]
version_aliases:
current: "0.51"
cc_api_version: v2
vblob_node:
supported_versions: ["0.51"]
default_version: "0.51"

elasticsearch_gateway:
token: 7db2f57b-66d0-40ad-a45b-af43f68a9b26
supported_versions: ["0.20"]
version_aliases:
current: "0.20"
cc_api_version: v2
elasticsearch_node:
supported_versions: ["0.20"]
default_version: "0.20"

postgresql_gateway:
token: f75df200-4daf-45b5-b92a-cb7fa1a25660
default_plan: default
supported_versions: ["9.3"]
version_aliases:
current: "9.3"
cc_api_version: v2
postgresql_node:
supported_versions: ["9.3"]
default_version: "9.3"
max_tmp: 900
password: secret

redis_gateway:
token: b1d19bde-ea9c-43b5-a0c1-f000e801b8b7
default_plan: default
supported_versions: ["2.6"]
version_aliases:
current: "2.6"
cc_api_version: v2
redis_node:
supported_versions: ["2.6"]
default_version: "2.6"
max_tmp: 900

rabbit_gateway:
token: ce1e0d30-d803-4f02-895e-1fa7d09be797
default_plan: "default"
supported_versions: ["3.0"]
version_aliases:
current: "3.0"
cc_api_version: v2
rabbit_node:
supported_versions: ["3.0"]
default_version: "3.0"
max_tmp: 900
m_actions: ["restart"] #restarts crashed rabbitMQ nodes

swift_gateway:
token: 0247daa4-7689-4784-8950-89213215f0be
default_plan: "free"
supported_versions: ["1.0"]
cc_api_version: v2
swift_node:
supported_versions: ["1.0"]
default_version: "1.0"
name_suffix: 'a9s.eu'
swift_operator_role_id: '2021022271a74ecdb94ceeeeeae657ad'
admin_reseller_role_id: '3032033371a74ecdb94asedt4df896bj'

--
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

--
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

<bosh_error.txt><cf-services-list.yml>

--
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

--
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

Ok, so I pared the yaml to just what I want. I got rid of mongodb,
elasticsearch and everything else. And reduced it to just postgres (which
is what I was after in the beginning).
Although I did figure out the yaml problem I was having before I ditched
that approach. ;)
And now I'm getting this error:
Started preparing deployment > Binding releases. Failed: Release
`cf-services-contrib' doesn't exist (00:00:00)
Error 30005: Release `cf-services-contrib' doesn't exist
If I do bosh releases this is what I see:
#bosh releases
Acting as user 'director' on 'microbosh-ba846726bed7032f1fd4'
+-----------------------+----------------------+-------------+
| Name | Versions | Commit Hash |
+-----------------------+----------------------+-------------+
| cf | 208.12* | a0de569a+ |
| cf-autoscaling | 13* | 927bc7ed+ |
| cf-metrics | 34* | 22f7e1e1 |
| cf-mysql | 20* | caa23b3d+ |
| | 22* | af278086+ |
| cf-rabbitmq | 161* | 4d298aec |
| cf-riak-cs | 10* | 5e7e46c9+ |
| newrelic_broker | 1.3* | 1ce3471d+ |
| notifications-with-ui | 18* | 490b6446+ |
| push-console-release | console-du-jour-203* | d2d31585+ |
| spring-cloud-broker | 1.0.0* | efd69612 |
+-----------------------+----------------------+-------------+
(*) Currently deployed
(+) Uncommitted changes
Releases total: 10
This is my yaml file as it stands right now:
name: cf-22b9f4d62bb6f0563b71
director_uuid: fd713790-b1bc-401a-8ea1-b8209f1cc90c
releases:
- name: cf-services-contrib
version: 1
compilation:
workers: 3
network: default
reuse_compilation_vms: true
update:
canaries: 1
canary_watch_time: 30000-60000
update_watch_time: 30000-60000
max_in_flight: 4
networks:
- name: floating
type: vip
cloud_properties: {}
- name: default
type: dynamic
resource_pools:
- name: common
network: default
size: 8
stemcell:
name: bosh-vsphere-esxi-ubuntu-trusty-go_agent
version: '2865.1'
jobs:
- name: gateways
release: cf-services-contrib
templates:
- name: postgresql_gateway_ng
instances: 1
resource_pool: common
networks:
- name: default
default: [dns, gateway]
properties:
# Service credentials
uaa_client_id: "cf"
uaa_endpoint: http://uaa.devcloudwest.inbcu.com
uaa_client_auth_credentials:
username: admin
password: secret
# templates: {
# name: mongodb_service_node,
# release: cf-services-contrib,
# instances: 1,
# resource_pool: common,
# persistent_disk: 10000,
# properties - plan: default,
# networks - name: default
# }
properties:
networks:
apps: default
management: default
cc:
srv_api_uri: http://api.devcloudwest.inbcu.com
nats:
address: 100.114.130.11
port: 25555
user: nats #CHANGE
password: secret
authorization_timeout: 5
service_plans:
postgresql:
default:
description: "Developer, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
backup:
enable: false
lifecycle:
enable: false
serialization: enable
snapshot:
quota: 1
postgresql_gateway:
token: f75df200-4daf-45b5-b92a-cb7fa1a25660
default_plan: default
supported_versions: ["9.3"]
version_aliases:
current: "9.3"
cc_api_version: v2
postgresql_node:
supported_versions: ["9.3"]
default_version: "9.3"
max_tmp: 900
password: secret
So do I have to create the new release first? What is the problem that I'm
having now?
Thanks,
Tim
On Thu, Dec 31, 2015 at 2:44 PM, Tim Dunphy <bluethundr(a)gmail.com> wrote:

Schema for each job is at

http://bosh.io/docs/deployment-manifest.html#jobs

Thanks!! I'll check it out!

On Thu, Dec 31, 2015 at 2:42 PM, Dr Nic Williams <drnicwilliams(a)gmail.com>
wrote:

Schema for each job is at
http://bosh.io/docs/deployment-manifest.html#jobs




On Thu, Dec 31, 2015 at 11:38 AM, Tim Dunphy <bluethundr(a)gmail.com>
wrote:

I can't open your yml attachments from my phone (gists are good as they

are readable and syntax highlighted)
The error - somewhere you are passing "mongodb_gateway" as a value to a
key; but BOSH wants you to pass a Hash (key/value)
I think that your jobs: section should be upgraded to replace release:
and template: keys with a single templates: key; and it is a list of Hash
(name: & release:)

Ok! So this is what I have now, that seems to be causing the error:

- name: mongodb_service_node
release: cf-services-contrib
templates: mongodb_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

So if I understand you correctly, I think what bosh wants is something
like this:

templates: {
name: mongodb_service_node,
release: cf-services-contrib,
instances: 1,
resource_pool: common,
persistent_disk: 10000,
properties:
- plan: default,
networks:
- name: default
default: [dns, gateway]
}


However the last two lines are tripping me up! How would I express the
properties and networks sections in yaml?

Thanks,
Tim


On Thu, Dec 31, 2015 at 1:59 PM, Dr Nic Williams <
drnicwilliams(a)gmail.com> wrote:

I can't open your yml attachments from my phone (gists are good as they
are readable and syntax highlighted)

The error - somewhere you are passing "mongodb_gateway" as a value to a
key; but BOSH wants you to pass a Hash (key/value)

I think that your jobs: section should be upgraded to replace release:
and template: keys with a single templates: key; and it is a list of Hash
(name: & release:)




On Thu, Dec 31, 2015 at 9:43 AM, Tim Dunphy <bluethundr(a)gmail.com>
wrote:

I've made a little progress! And thanks for your suggestion to use the postgresql-docker-boshrelease.
But we're only ER 1.5.5 and I don't believe there's docker support for that
version. We're on 1.6 in our POC environment, which does support docker,
but I need to implement this in the 1.5.5 environement for now.


What I did was list the change the name of the bosh stemcell in the
manifest. And changed the word 'template' to 'templates' in the manifest
due to warning I was receiving. Lastly I changed the name of the manifest
to the current deployment.

Now I'm getting this error:

Error 40000: Object ("mongodb_gateway") did not match the required
type `Hash'


When I run a debug I get this output:

D, [2015-12-31 17:34:41 #19911] [task:2219] DEBUG --
DirectorJobRunner: SENT: hm.director.alert
{"id":"0667960d-04d6-45b0-8790-65626c1cac1f","severity":3,"title":"director
- error during update deployment","summary":"Error during update deployment
for 'cf-22b9f4d62bb6f0563b71' against Director
'fd713790-b1bc-401a-8ea1-b8209f1cc90c':
#<Bosh::Director::ValidationInvalidType: Object (\"mongodb_gateway\") did
not match the required type `Hash'>","created_at":1451583281}
E, [2015-12-31 17:34:41 #19911] [task:2219] ERROR --
DirectorJobRunner: Object ("mongodb_gateway") did not match the required
type `Hash'

This is how I have my mongodb_gateway defined:

mongodb_gateway:
token: f777da76-06b4-4817-a8d5-87bd77834aef
default_plan: default
supported_versions: ["2.2"]
version_aliases:
current: "2.2"
cc_api_version: v2
mongodb_node:
supported_versions: ["2.2"]
default_version: "2.2"
max_tmp: 900

Is there a specific process I need to follow to generate the token? I
think that's what it's barking at here.

I'm enclosing the manifest file and the debug output from the bosh
command. I'd appreciate any help I can find! :)

Thanks,
Tim



On Thu, Dec 31, 2015 at 11:30 AM, Tim Dunphy <bluethundr(a)gmail.com>
wrote:

Couple of thoughts:

1. The cf-contrib-services release is old, the gateway is not
supported in upcoming CF versions. But it is open source and perhaps you
can upgraded it.

Perhaps try postgresql-docker-boshrelease instead.

Thanks for that info! I'll check out postgresql-docker-boshrelease!

2. The "bosh-stemcell" missing is because it now has a different
name.
Run "bosh stemcells" to get the name of the stemcell you have
available. Then replace this name into your manifest.
If you switch to the boshrelease I suggested then you'll get the
stemcell name discovery for free via make_manifest script.

OK here's what I see:


#bosh stemcells
Acting as user 'director' on 'microbosh-ba846726bed7032f1fd4'


+------------------------------------------+---------------+---------+-----------------------------------------+
| Name | OS | Version
| CID |

+------------------------------------------+---------------+---------+-----------------------------------------+
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | | 2865.1*
| sc-90c410aa-7ea0-47e6-b6e2-b3e65f712331 |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3062*
| sc-abf52559-959b-49c7-98a5-2287094a50b6 |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3094*
| sc-4117bede-0db9-467d-adf2-6e01c2d35463 |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3100*
| sc-bb5af5e6-4c50-4187-8961-68fbfcd244e0 |

+------------------------------------------+---------------+---------+-----------------------------------------+

(*) Currently in-use

Stemcells total: 4

I'll give that a shot. I'll try changing the name of the stemcell in
the manifest. However I notice now that I get the same error when I run a
bosh cloud check command:

#bosh cck
Acting as user 'director' on deployment 'cf-services-contrib' on
'microbosh-ba846726bed7032f1fd4'
Latest version for stemcell `bosh-stemcell' is unknown

I'll also look into the make_manifest script!

If you're on vsphere you will need to create an extra template for
your networking needs etc. Ping me directly or via the github issues if you
want help on that.

Thanks! That will be a tremendous help! As I'm not an expert on
VMWare and that's what our cloud foundry is running on. As we're having a
1/2 for the holiday today I may take that on next week. Thanks for the
offer of help!

On Thu, Dec 31, 2015 at 11:13 AM, Dr Nic Williams <
drnicwilliams(a)gmail.com> wrote:

Couple of thoughts:

1. The cf-contrib-services release is old, the gateway is not
supported in upcoming CF versions. But it is open source and perhaps you
can upgraded it.

Perhaps try postgresql-docker-boshrelease instead.

2. The "bosh-stemcell" missing is because it now has a different
name.

Run "bosh stemcells" to get the name of the stemcell you have
available. Then replace this name into your manifest.

If you switch to the boshrelease I suggested then you'll get the
stemcell name discovery for free via make_manifest script.

If you're on vsphere you will need to create an extra template for
your networking needs etc. Ping me directly or via the github issues if you
want help on that.




On Thu, Dec 31, 2015 at 7:58 AM, Tim Dunphy <bluethundr(a)gmail.com>
wrote:

Hey all,

We're attempting to get PostgreSQL as a service running in our PCF
environment. To do that, I'm trying to use this community release which
includes pgsql as well as a number of other services:


https://github.com/cloudfoundry-community/cf-services-contrib-release

I've created a yaml file that's supposed to add posgres to our
Cloud Foundry setup, but when I go to deploy the manifest, I'm getting an
error:

"Latest version for stemcell `bosh-stemcell' is unknown"

This is what the attempt looks like:

#bosh deployment cf-services.yml
Deployment set to `/Users/TimothyDunphy/test/cf-services.yml'
#bosh deploy
Acting as user 'director' on deployment 'cf-services-contrib' on
'microbosh-ba846726bed7032f1fd4'
Getting deployment properties from director...
Unable to get properties list from director, trying without it...
Latest version for stemcell `bosh-stemcell' is unknown

We're using Pivotal Cloud Foundry with Ops Manager Director v1.5.5
and Elastic Runtime 1.5.4. Bosh command line is: BOSH 1.3165.0

How can we correct this problem?

For reference, here's our yaml file:

name: cf-services-contrib
director_uuid: fd713790-b1bc-401a-8ea1-b8209f1cc90c

releases:
- name: cf-services-contrib
version: 1

compilation:
workers: 3
network: default
reuse_compilation_vms: true

update:
canaries: 1
canary_watch_time: 30000-60000
update_watch_time: 30000-60000
max_in_flight: 4

networks:
- name: floating
type: vip
cloud_properties: {}
- name: default
type: dynamic

resource_pools:
- name: common
network: default
size: 8
stemcell:
name: bosh-stemcell
version: latest

jobs:
- name: gateways
release: cf-services-contrib
template:
- elasticsearch_gateway
- mongodb_gateway
- memcached_gateway
- postgresql_gateway_ng
- redis_gateway
- rabbit_gateway
- vblob_gateway
instances: 1
resource_pool: common
networks:
- name: default
default: [dns, gateway]
properties:
# Service credentials
uaa_client_id: "cf"
uaa_endpoint: http://uaa.devcloudwest.inbcu.com
uaa_client_auth_credentials:
username: admin
password: b8b7b0917be5ce20d3e2

- name: mongodb_service_node
release: cf-services-contrib
template: mongodb_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: memcached_service_node
release: cf-services-contrib
template: memcached_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: vblob_service_node
release: cf-services-contrib
template: vblob_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: elasticsearch_service_node
release: cf-services-contrib
template: elasticsearch_node
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: "free"
networks:
- name: default
default: [dns, gateway]

- name: postgresql_service_node
release: cf-services-contrib
template: postgresql_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
postgresql_node:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: redis_service_node
release: cf-services-contrib
template: redis_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: rabbit_service_node
release: cf-services-contrib
template: rabbit_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

properties:
networks:
apps: default
management: default

cc:
srv_api_uri: http://api.devcloudwest.inbcu.com

nats:
address: 100.114.130.11
port: 25555
user: nats #CHANGE
password: ffbd63b59eb418d6a17b
authorization_timeout: 5

service_plans:
mongodb:
default:
description: "Developer, shared VM, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
backup:
enable: true
lifecycle:
enable: true
serialization: enable
snapshot:
quota: 1

memcached:
default:
description: "Developer"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125

vblob:
default:
description: "Developer"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125

elasticsearch:
"free":
description: "Developer"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125

postgresql:
default:
description: "Developer, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
backup:
enable: false
lifecycle:
enable: false
serialization: enable
snapshot:
quota: 1

redis:
default:
description: "Developer, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
backup:
enable: false
lifecycle:
enable: false
serialization: enable
snapshot:
quota: 1


rabbit:
default:
description: "Developer, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
bandwidth_quotas:
per_second: 1
per_day: 10
time_window: 86400
backup:
enable: false
lifecycle:
enable: false
serialization: enable
snapshot:
quota: 1

mongodb_gateway:
token: f777da76-06b4-4817-a8d5-87bd77834aef
default_plan: default
supported_versions: ["2.2"]
version_aliases:
current: "2.2"
cc_api_version: v2
mongodb_node:
supported_versions: ["2.2"]
default_version: "2.2"
max_tmp: 900

memcached_gateway:
token: dc13a7d7-8276-411e-9f4a-065bfef5e4c4
supported_versions: ["1.4"]
version_aliases:
current: "1.4"
cc_api_version: v2
memcached_node:
supported_versions: ["1.4"]
default_version: "1.4"

vblob_gateway:
token: 98b4cbbe-6ef0-41ef-951c-532704645254
supported_versions: ["0.51"]
version_aliases:
current: "0.51"
cc_api_version: v2
vblob_node:
supported_versions: ["0.51"]
default_version: "0.51"

elasticsearch_gateway:
token: 7db2f57b-66d0-40ad-a45b-af43f68a9b26
supported_versions: ["0.20"]
version_aliases:
current: "0.20"
cc_api_version: v2
elasticsearch_node:
supported_versions: ["0.20"]
default_version: "0.20"

postgresql_gateway:
token: f75df200-4daf-45b5-b92a-cb7fa1a25660
default_plan: default
supported_versions: ["9.3"]
version_aliases:
current: "9.3"
cc_api_version: v2
postgresql_node:
supported_versions: ["9.3"]
default_version: "9.3"
max_tmp: 900
password: secret

redis_gateway:
token: b1d19bde-ea9c-43b5-a0c1-f000e801b8b7
default_plan: default
supported_versions: ["2.6"]
version_aliases:
current: "2.6"
cc_api_version: v2
redis_node:
supported_versions: ["2.6"]
default_version: "2.6"
max_tmp: 900

rabbit_gateway:
token: ce1e0d30-d803-4f02-895e-1fa7d09be797
default_plan: "default"
supported_versions: ["3.0"]
version_aliases:
current: "3.0"
cc_api_version: v2
rabbit_node:
supported_versions: ["3.0"]
default_version: "3.0"
max_tmp: 900
m_actions: ["restart"] #restarts crashed rabbitMQ nodes

swift_gateway:
token: 0247daa4-7689-4784-8950-89213215f0be
default_plan: "free"
supported_versions: ["1.0"]
cc_api_version: v2
swift_node:
supported_versions: ["1.0"]
default_version: "1.0"
name_suffix: 'a9s.eu'
swift_operator_role_id: '2021022271a74ecdb94ceeeeeae657ad'
admin_reseller_role_id: '3032033371a74ecdb94asedt4df896bj'

--
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

--
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

<bosh_error.txt><cf-services-list.yml>

--
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

--
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

--
GPG me!!
gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

Ok, so I pared the yaml to just what I want. I got rid of mongodb,
elasticsearch and everything else. And reduced it to just postgres (which
is what I was after in the beginning).
Although I did figure out the yaml problem I was having before I ditched
that approach. ;)
And now I'm getting this error:
Started preparing deployment > Binding releases. Failed: Release
`cf-services-contrib' doesn't exist (00:00:00)
Error 30005: Release `cf-services-contrib' doesn't exist
If I do bosh releases this is what I see:
#bosh releases
Acting as user 'director' on 'microbosh-ba846726bed7032f1fd4'
+-----------------------+----------------------+-------------+
| Name | Versions | Commit Hash |
+-----------------------+----------------------+-------------+
| cf | 208.12* | a0de569a+ |
| cf-autoscaling | 13* | 927bc7ed+ |
| cf-metrics | 34* | 22f7e1e1 |
| cf-mysql | 20* | caa23b3d+ |
| | 22* | af278086+ |
| cf-rabbitmq | 161* | 4d298aec |
| cf-riak-cs | 10* | 5e7e46c9+ |
| newrelic_broker | 1.3* | 1ce3471d+ |
| notifications-with-ui | 18* | 490b6446+ |
| push-console-release | console-du-jour-203* | d2d31585+ |
| spring-cloud-broker | 1.0.0* | efd69612 |
+-----------------------+----------------------+-------------+
(*) Currently deployed
(+) Uncommitted changes
Releases total: 10
This is my yaml file as it stands right now:
name: cf-22b9f4d62bb6f0563b71
director_uuid: fd713790-b1bc-401a-8ea1-b8209f1cc90c
releases:
- name: cf-services-contrib
version: 1
compilation:
workers: 3
network: default
reuse_compilation_vms: true
update:
canaries: 1
canary_watch_time: 30000-60000
update_watch_time: 30000-60000
max_in_flight: 4
networks:
- name: floating
type: vip
cloud_properties: {}
- name: default
type: dynamic
resource_pools:
- name: common
network: default
size: 8
stemcell:
name: bosh-vsphere-esxi-ubuntu-trusty-go_agent
version: '2865.1'
jobs:
- name: gateways
release: cf-services-contrib
templates:
- name: postgresql_gateway_ng
instances: 1
resource_pool: common
networks:
- name: default
default: [dns, gateway]
properties:
# Service credentials
uaa_client_id: "cf"
uaa_endpoint: http://uaa.devcloudwest.inbcu.com
uaa_client_auth_credentials:
username: admin
password: secret
# templates: {
# name: mongodb_service_node,
# release: cf-services-contrib,
# instances: 1,
# resource_pool: common,
# persistent_disk: 10000,
# properties - plan: default,
# networks - name: default
# }
properties:
networks:
apps: default
management: default
cc:
srv_api_uri: http://api.devcloudwest.inbcu.com
nats:
address: 100.114.130.11
port: 25555
user: nats #CHANGE
password: secret
authorization_timeout: 5
service_plans:
postgresql:
default:
description: "Developer, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
backup:
enable: false
lifecycle:
enable: false
serialization: enable
snapshot:
quota: 1
postgresql_gateway:
token: f75df200-4daf-45b5-b92a-cb7fa1a25660
default_plan: default
supported_versions: ["9.3"]
version_aliases:
current: "9.3"
cc_api_version: v2
postgresql_node:
supported_versions: ["9.3"]
default_version: "9.3"
max_tmp: 900
password: secret
So do I have to create the new release first? What is the problem that I'm
having now?
Thanks,
Tim
On Thu, Dec 31, 2015 at 2:44 PM, Tim Dunphy <bluethundr(a)gmail.com> wrote:

Schema for each job is at

http://bosh.io/docs/deployment-manifest.html#jobs

Thanks!! I'll check it out!

On Thu, Dec 31, 2015 at 2:42 PM, Dr Nic Williams <drnicwilliams(a)gmail.com>
wrote:

Schema for each job is at
http://bosh.io/docs/deployment-manifest.html#jobs




On Thu, Dec 31, 2015 at 11:38 AM, Tim Dunphy <bluethundr(a)gmail.com>
wrote:

I can't open your yml attachments from my phone (gists are good as they

are readable and syntax highlighted)
The error - somewhere you are passing "mongodb_gateway" as a value to a
key; but BOSH wants you to pass a Hash (key/value)
I think that your jobs: section should be upgraded to replace release:
and template: keys with a single templates: key; and it is a list of Hash
(name: & release:)

Ok! So this is what I have now, that seems to be causing the error:

- name: mongodb_service_node
release: cf-services-contrib
templates: mongodb_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

So if I understand you correctly, I think what bosh wants is something
like this:

templates: {
name: mongodb_service_node,
release: cf-services-contrib,
instances: 1,
resource_pool: common,
persistent_disk: 10000,
properties:
- plan: default,
networks:
- name: default
default: [dns, gateway]
}


However the last two lines are tripping me up! How would I express the
properties and networks sections in yaml?

Thanks,
Tim


On Thu, Dec 31, 2015 at 1:59 PM, Dr Nic Williams <
drnicwilliams(a)gmail.com> wrote:

I can't open your yml attachments from my phone (gists are good as they
are readable and syntax highlighted)

The error - somewhere you are passing "mongodb_gateway" as a value to a
key; but BOSH wants you to pass a Hash (key/value)

I think that your jobs: section should be upgraded to replace release:
and template: keys with a single templates: key; and it is a list of Hash
(name: & release:)




On Thu, Dec 31, 2015 at 9:43 AM, Tim Dunphy <bluethundr(a)gmail.com>
wrote:

I've made a little progress! And thanks for your suggestion to use the postgresql-docker-boshrelease.
But we're only ER 1.5.5 and I don't believe there's docker support for that
version. We're on 1.6 in our POC environment, which does support docker,
but I need to implement this in the 1.5.5 environement for now.


What I did was list the change the name of the bosh stemcell in the
manifest. And changed the word 'template' to 'templates' in the manifest
due to warning I was receiving. Lastly I changed the name of the manifest
to the current deployment.

Now I'm getting this error:

Error 40000: Object ("mongodb_gateway") did not match the required
type `Hash'


When I run a debug I get this output:

D, [2015-12-31 17:34:41 #19911] [task:2219] DEBUG --
DirectorJobRunner: SENT: hm.director.alert
{"id":"0667960d-04d6-45b0-8790-65626c1cac1f","severity":3,"title":"director
- error during update deployment","summary":"Error during update deployment
for 'cf-22b9f4d62bb6f0563b71' against Director
'fd713790-b1bc-401a-8ea1-b8209f1cc90c':
#<Bosh::Director::ValidationInvalidType: Object (\"mongodb_gateway\") did
not match the required type `Hash'>","created_at":1451583281}
E, [2015-12-31 17:34:41 #19911] [task:2219] ERROR --
DirectorJobRunner: Object ("mongodb_gateway") did not match the required
type `Hash'

This is how I have my mongodb_gateway defined:

mongodb_gateway:
token: f777da76-06b4-4817-a8d5-87bd77834aef
default_plan: default
supported_versions: ["2.2"]
version_aliases:
current: "2.2"
cc_api_version: v2
mongodb_node:
supported_versions: ["2.2"]
default_version: "2.2"
max_tmp: 900

Is there a specific process I need to follow to generate the token? I
think that's what it's barking at here.

I'm enclosing the manifest file and the debug output from the bosh
command. I'd appreciate any help I can find! :)

Thanks,
Tim



On Thu, Dec 31, 2015 at 11:30 AM, Tim Dunphy <bluethundr(a)gmail.com>
wrote:

Couple of thoughts:

1. The cf-contrib-services release is old, the gateway is not
supported in upcoming CF versions. But it is open source and perhaps you
can upgraded it.

Perhaps try postgresql-docker-boshrelease instead.

Thanks for that info! I'll check out postgresql-docker-boshrelease!

2. The "bosh-stemcell" missing is because it now has a different
name.
Run "bosh stemcells" to get the name of the stemcell you have
available. Then replace this name into your manifest.
If you switch to the boshrelease I suggested then you'll get the
stemcell name discovery for free via make_manifest script.

OK here's what I see:


#bosh stemcells
Acting as user 'director' on 'microbosh-ba846726bed7032f1fd4'


+------------------------------------------+---------------+---------+-----------------------------------------+
| Name | OS | Version
| CID |

+------------------------------------------+---------------+---------+-----------------------------------------+
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | | 2865.1*
| sc-90c410aa-7ea0-47e6-b6e2-b3e65f712331 |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3062*
| sc-abf52559-959b-49c7-98a5-2287094a50b6 |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3094*
| sc-4117bede-0db9-467d-adf2-6e01c2d35463 |
| bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3100*
| sc-bb5af5e6-4c50-4187-8961-68fbfcd244e0 |

+------------------------------------------+---------------+---------+-----------------------------------------+

(*) Currently in-use

Stemcells total: 4

I'll give that a shot. I'll try changing the name of the stemcell in
the manifest. However I notice now that I get the same error when I run a
bosh cloud check command:

#bosh cck
Acting as user 'director' on deployment 'cf-services-contrib' on
'microbosh-ba846726bed7032f1fd4'
Latest version for stemcell `bosh-stemcell' is unknown

I'll also look into the make_manifest script!

If you're on vsphere you will need to create an extra template for
your networking needs etc. Ping me directly or via the github issues if you
want help on that.

Thanks! That will be a tremendous help! As I'm not an expert on
VMWare and that's what our cloud foundry is running on. As we're having a
1/2 for the holiday today I may take that on next week. Thanks for the
offer of help!

On Thu, Dec 31, 2015 at 11:13 AM, Dr Nic Williams <
drnicwilliams(a)gmail.com> wrote:

Couple of thoughts:

1. The cf-contrib-services release is old, the gateway is not
supported in upcoming CF versions. But it is open source and perhaps you
can upgraded it.

Perhaps try postgresql-docker-boshrelease instead.

2. The "bosh-stemcell" missing is because it now has a different
name.

Run "bosh stemcells" to get the name of the stemcell you have
available. Then replace this name into your manifest.

If you switch to the boshrelease I suggested then you'll get the
stemcell name discovery for free via make_manifest script.

If you're on vsphere you will need to create an extra template for
your networking needs etc. Ping me directly or via the github issues if you
want help on that.




On Thu, Dec 31, 2015 at 7:58 AM, Tim Dunphy <bluethundr(a)gmail.com>
wrote:

Hey all,

We're attempting to get PostgreSQL as a service running in our PCF
environment. To do that, I'm trying to use this community release which
includes pgsql as well as a number of other services:


https://github.com/cloudfoundry-community/cf-services-contrib-release

I've created a yaml file that's supposed to add posgres to our
Cloud Foundry setup, but when I go to deploy the manifest, I'm getting an
error:

"Latest version for stemcell `bosh-stemcell' is unknown"

This is what the attempt looks like:

#bosh deployment cf-services.yml
Deployment set to `/Users/TimothyDunphy/test/cf-services.yml'
#bosh deploy
Acting as user 'director' on deployment 'cf-services-contrib' on
'microbosh-ba846726bed7032f1fd4'
Getting deployment properties from director...
Unable to get properties list from director, trying without it...
Latest version for stemcell `bosh-stemcell' is unknown

We're using Pivotal Cloud Foundry with Ops Manager Director v1.5.5
and Elastic Runtime 1.5.4. Bosh command line is: BOSH 1.3165.0

How can we correct this problem?

For reference, here's our yaml file:

name: cf-services-contrib
director_uuid: fd713790-b1bc-401a-8ea1-b8209f1cc90c

releases:
- name: cf-services-contrib
version: 1

compilation:
workers: 3
network: default
reuse_compilation_vms: true

update:
canaries: 1
canary_watch_time: 30000-60000
update_watch_time: 30000-60000
max_in_flight: 4

networks:
- name: floating
type: vip
cloud_properties: {}
- name: default
type: dynamic

resource_pools:
- name: common
network: default
size: 8
stemcell:
name: bosh-stemcell
version: latest

jobs:
- name: gateways
release: cf-services-contrib
template:
- elasticsearch_gateway
- mongodb_gateway
- memcached_gateway
- postgresql_gateway_ng
- redis_gateway
- rabbit_gateway
- vblob_gateway
instances: 1
resource_pool: common
networks:
- name: default
default: [dns, gateway]
properties:
# Service credentials
uaa_client_id: "cf"
uaa_endpoint: http://uaa.devcloudwest.inbcu.com
uaa_client_auth_credentials:
username: admin
password: b8b7b0917be5ce20d3e2

- name: mongodb_service_node
release: cf-services-contrib
template: mongodb_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: memcached_service_node
release: cf-services-contrib
template: memcached_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: vblob_service_node
release: cf-services-contrib
template: vblob_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: elasticsearch_service_node
release: cf-services-contrib
template: elasticsearch_node
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: "free"
networks:
- name: default
default: [dns, gateway]

- name: postgresql_service_node
release: cf-services-contrib
template: postgresql_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
postgresql_node:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: redis_service_node
release: cf-services-contrib
template: redis_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

- name: rabbit_service_node
release: cf-services-contrib
template: rabbit_node_ng
instances: 1
resource_pool: common
persistent_disk: 10000
properties:
plan: default
networks:
- name: default
default: [dns, gateway]

properties:
networks:
apps: default
management: default

cc:
srv_api_uri: http://api.devcloudwest.inbcu.com

nats:
address: 100.114.130.11
port: 25555
user: nats #CHANGE
password: ffbd63b59eb418d6a17b
authorization_timeout: 5

service_plans:
mongodb:
default:
description: "Developer, shared VM, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
backup:
enable: true
lifecycle:
enable: true
serialization: enable
snapshot:
quota: 1

memcached:
default:
description: "Developer"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125

vblob:
default:
description: "Developer"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125

elasticsearch:
"free":
description: "Developer"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125

postgresql:
default:
description: "Developer, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
backup:
enable: false
lifecycle:
enable: false
serialization: enable
snapshot:
quota: 1

redis:
default:
description: "Developer, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
backup:
enable: false
lifecycle:
enable: false
serialization: enable
snapshot:
quota: 1


rabbit:
default:
description: "Developer, 250MB storage, 10 connections"
free: true
job_management:
high_water: 230
low_water: 20
configuration:
capacity: 125
max_clients: 10
quota_files: 4
quota_data_size: 240
enable_journaling: true
bandwidth_quotas:
per_second: 1
per_day: 10
time_window: 86400
backup:
enable: false
lifecycle:
enable: false
serialization: enable
snapshot:
quota: 1

mongodb_gateway:
token: f777da76-06b4-4817-a8d5-87bd77834aef
default_plan: default
supported_versions: ["2.2"]
version_aliases:
current: "2.2"
cc_api_version: v2
mongodb_node:
supported_versions: ["2.2"]
default_version: "2.2"
max_tmp: 900

memcached_gateway:
token: dc13a7d7-8276-411e-9f4a-065bfef5e4c4
supported_versions: ["1.4"]
version_aliases:
current: "1.4"
cc_api_version: v2
memcached_node:
supported_versions: ["1.4"]
default_version: "1.4"

vblob_gateway:
token: 98b4cbbe-6ef0-41ef-951c-532704645254
supported_versions: ["0.51"]
version_aliases:
current: "0.51"
cc_api_version: v2
vblob_node:
supported_versions: ["0.51"]
default_version: "0.51"

elasticsearch_gateway:
token: 7db2f57b-66d0-40ad-a45b-af43f68a9b26
supported_versions: ["0.20"]
version_aliases:
current: "0.20"
cc_api_version: v2
elasticsearch_node:
supported_versions: ["0.20"]
default_version: "0.20"

postgresql_gateway:
token: f75df200-4daf-45b5-b92a-cb7fa1a25660
default_plan: default
supported_versions: ["9.3"]
version_aliases:
current: "9.3"
cc_api_version: v2
postgresql_node:
supported_versions: ["9.3"]
default_version: "9.3"
max_tmp: 900
password: secret

redis_gateway:
token: b1d19bde-ea9c-43b5-a0c1-f000e801b8b7
default_plan: default
supported_versions: ["2.6"]
version_aliases:
current: "2.6"
cc_api_version: v2
redis_node:
supported_versions: ["2.6"]
default_version: "2.6"
max_tmp: 900

rabbit_gateway:
token: ce1e0d30-d803-4f02-895e-1fa7d09be797
default_plan: "default"
supported_versions: ["3.0"]
version_aliases:
current: "3.0"
cc_api_version: v2
rabbit_node:
supported_versions: ["3.0"]
default_version: "3.0"
max_tmp: 900
m_actions: ["restart"] #restarts crashed rabbitMQ nodes

swift_gateway:
token: 0247daa4-7689-4784-8950-89213215f0be
default_plan: "free"
supported_versions: ["1.0"]
cc_api_version: v2
swift_node:
supported_versions: ["1.0"]
default_version: "1.0"
name_suffix: 'a9s.eu'
swift_operator_role_id: '2021022271a74ecdb94ceeeeeae657ad'
admin_reseller_role_id: '3032033371a74ecdb94asedt4df896bj'

--
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

--
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

<bosh_error.txt><cf-services-list.yml>

--
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

--
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

--
GPG me!!
gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B