I guess you need to setup the users & their shared keys within a job template

Hi, there I am able to run "bosh aws create" before, but it failed today with following error, I am wondering what might be wrong? From the output of "bosh aws create", seems it tries to "Executing

couldn't find that in there crappy documentation [:(] but thanks for the suggestion

There is also a way how automate insertion ssh key to manifest. For instance logstash boshrelease use ERB to print config file content to manifest file.

Thanks but I did'nt know that ssh was required for pgpool replication ... I think you can use the user:md5password method for the loadbalancing and replication..

You can put your public and private keys to the manifest like it is done for HAProxy <https://github.com/cloudfoundry-community/cf-boshworkspace/blob/master/templates/cf-use-haproxy.yml#L84-L112>

i wanted to create a postgres cluster with pgpool 2 and this requires passwordless ssh/scp access

Thanks everyone. The pipeline is coming in nice and handy. The one linked in the readme (also in ci/pipeline.yml) helps make final releases. Then clients have other pipelines that pick up the final

Really nice @drNic ! Really a big fan of the concourse pipeline ! Ramon.Makkelie(a)klm.com> wrote:

Just a question why using a password less ?

This is pretty awesome i'm very exited anyway i can help/contribute? greetz Ramonskie

I think that would be helpful.  We're also big fans of 2nd Quadrant who maintain the underlying BDR (bidirectional replication) solution for PG; and Hashicorp who make Consul; and Pivotal who

DrNic, Do you have any plans to offer commercial support for this release? D -- David Laing logsearch.io - build your own open source cloud logging cluster http://davidlaing.com

We're working on a Reliable Distributed PostgreSQL solution that'll be deployed by BOSH and include a CF Serivce Broker. It's in pre-prod at moment but still early times. Some docs are available;

is there a nice way to achieve password-less ssh between each bosh job/vm the only option i could think of is just generate a new ssh key and hardcode it a package. but this is a bit hacky any

i was wondering if there is already a public available working postgresql bosh job available i know there are some company's that already created this but are not allowed to publish it -- View

Thank you, Dmitry! It works. -- View this message in context: http://cf-bosh.70367.x6.nabble.com/Print-errand-logs-before-refilling-resource-pool-tp485p491.html Sent from the CF BOSH mailing list

Hi Ahmed, Sorry for the slow reply. Those errors you are getting seem like they stem from the deployment not being able to access itself. To do a `cf apps`, the CLI performs a request to the spaces

Hmm should director do this? Seems kinda scary that it just doesn’t care about deploys and updates 

Is that good? Something to fix/improve? Or should automation wanting to do deploys poll the /tasks API until there are no active tasks and  then resume destruction? wrote: