How to get postgres db host endpoint of existing postgres runnning in cf to use in diego ?

[deepakdefender264]

I want to use postgres db host endpoint of existing postgres running in cf to use in diego ?
Is there a way to get it. I am using bosh v2 cli and director.

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/145333557

The labels on this github issue will be updated when the story is started.

[emalm]

Hi, @deepakdefender264,

The Diego BBS's connection to its SQL database is configured with the BOSH properties under diego.bbs.sql that are listed in the BBS job spec: https://github.com/cloudfoundry/diego-release/blob/v1.15.3/jobs/bbs/spec#L100-L129. If you are using the manifest-generation scripts in the diego-release repository, those can be configured via a stub file passed to the -s argument. As an example, the manifest-generation for BOSH-Lite selects either the MySQL or the Postgres stub file in https://github.com/cloudfoundry/diego-release/blob/v1.15.3/scripts/generate-bosh-lite-manifests#L14-L37, with the Postgres stub file at https://github.com/cloudfoundry/diego-release/blob/v1.15.3/manifest-generation/bosh-lite-stubs/postgres/diego-sql.yml.

If you need to know the values to configure in that stub, you should be able to get those from the existing CF manifest if CC and UAA are using that Postgres instance for their own databases. It may end up being simply a single IP address, in which case you could also get it from the bosh instances output.

Best,
Eric, CF Diego PM

[deepakdefender264]

Hi @ematpl
Thanks for providing links. Currently I am running CF in only 1 zone and have only 1 postgres sql in our vsphere environment. I can provide postgres_z1 IP address but when I need deploy CF on 2 zones. In that case which address should I provide.
Is there any link which I can use to deploy diego release on vsphere enviroment ? I have cf running on my vsphere env.

[emalm]

Hi, @deepakdefender264,

The postgres job in cf-release does not support any sort of clustered deployment, so even if you expand your CF deployment to 2 or more availability zones you'll still only have one instance of that postgres job. You can then continue to supply the IP of that instance as the host for the Diego BBS database connection.

Alternately, the cf-mysql release supports a highly available clustered database deployment that is compatible with the Diego BBS and the other SQL-database-based components in CF. Its proxy instances are capable of being registered as Consul services and hence would be addressable via Consul under a domain name such as mysql.service.cf.internal.

If you are using the manifest-generation script and templates from diego-release, all of the infrastructure-specific configuration will be specified in the "IaaS-settings" stub file that is the argument to the -i flag on the generate-deployment-manifest script. This configuration includes networks and resource pools for the different job types in the generated manifest. An example for BOSH-Lite is located at https://github.com/cloudfoundry/diego-release/blob/v1.15.3/manifest-generation/bosh-lite-stubs/iaas-settings.yml.

Finally, if you are already using the new v2 BOSH CLI, you may be interested in cf-deployment as an alternative to the separate manifest-generation script/template systems in cf-release and diego-release that uses Diego instead of the DEAs and takes advantage of new BOSH features such as cloud-config, links, and variable generation and interpolation. It's not quite ready for all production deployments, but reaching that milestone is the next major goal for the Release Integration team that is responsible for developing it.

Best,
Eric

[mayankkaushik2]

Hi @ematpl ,
Thanks for the explanation. I got it.
Regarding cf-deployment, can I deploy windows-cells directly to my cf-release instead of going for diego-release first. Currently I am deploying diego-release over cf-release and then will go for windows-garden.

Here I am confused about these values, I am not sure what to do as I am getting errors for pem certs in updating database_z1 vm.
bbs:
active_key_label: key1
encryption_keys:
- label: key1
passphrase: "a secure passphrase"
and what are diego_credentials in property-overrides.yml
Error: Error: 'database_z1/0 (6595b96a-845e-4a4f-b33c-1335e9757054)' is not running after update. Reviewed logs for failed jobs: bbs
goroutine 1 [running]:
panic(0xc14620, 0xc42025e600)
/var/vcap/data/packages/golang/b2f1508f98daf236581e0146f0af18f55b24067e/src/runtime/panic.go:500 +0x1a1
code.cloudfoundry.org/lager.(*logger).Fatal(0xc420156180, 0xd42aa4, 0x18, 0x10e85e0, 0xc42025e600, 0x0, 0x0, 0x0)
/var/vcap/packages/bbs/src/code.cloudfoundry.org/lager/logger.go:152 +0x41c
main.main()
/var/vcap/packages/bbs/src/code.cloudfoundry.org/bbs/cmd/bbs/main.go:235 +0x313f
panic: failed to load keypair: tls: failed to find any PEM data in key input

[deepakdefender264]

Additional to @mayankkaushik2, we got below error while running diego deploy.
In task error, it is
E, [2017-05-16 16:59:39 #27717] [] ERROR -- DirectorJobRunner: Worker thread raised exception: 'cell_z1/0 (d81b6ec3-0655-4269-9ca3-ef5f621e3e4a)' is not running after update. Review logs for failed jobs: rep - /var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-261.4.0/lib/bosh/director/instance_updater/state_applier.rb:48:in `post_start'

In rep errors, we encountered this
{"timestamp":"1494953958.998428106","source":"rep","message":"rep.executor-fetching-containers-to-destroy","log_level":1,"data":{}}
{"timestamp":"1494953959.001061440","source":"rep","message":"rep.executor-fetched-containers-to-destroy","log_level":1,"data":{"num-containers":0}}
{"timestamp":"1494953959.042432547","source":"rep","message":"rep.initial-capacity","log_level":1,"data":{"capacity":{"memory_mb":3951,"disk_mb":6595,"containers":249}}}
{"timestamp":"1494953959.042812347","source":"rep","message":"rep.instance-identity-enabled","log_level":1,"data":{}}
{"timestamp":"1494953959.045436382","source":"rep","message":"rep.failed-to-initialize-executor","log_level":2,"data":{"error":"asn1: structure error: tags don't match (2 vs {class:0 tag:6 length:9 isCompound:false}) {optional:false explicit:false application:false defaultValue:\u003cnil\u003e tag:\u003cnil\u003e stringType:0 timeType:0 set:false omitEmpty:false} @2"}}
{"timestamp":"1494953999.149849415","source":"rep","message":"rep.creating-grpc-client","log_level":1,"data":{"address":"localhost:3458"}}
{"timestamp":"1494953999.152936935","source":"rep","message":"rep.wait-for-garden.ping-garden","log_level":1,"data":{"initialTime:":"2017-05-16T16:59:59.151594178Z","session":"2","wait-time-ns:":1332316}}
{"timestamp":"1494953999.154919863","source":"rep","message":"rep.wait-for-garden.ping-garden-success","log_level":1,"data":{"initialTime:":"2017-05-16T16:59:59.151594178Z","session":"2","wait-time-ns:":3322762}}

Seems interesting error.

[deepakdefender264]

Resolved, After correcting certificate values, its get resolved