Guys,

I have created a RethinkDB bosh release in here:
https://github.com/cloudfoundry-community/rethinkdb-boshrelease can you
please take a look and tell me if there is anything wrong or what could I
do different to improve it?

I hope that what's already there works for some of you.

Thanks,
Leandro.-

PS: Riak release is possibly coming this week also.

On a first look, it looks like it could be nice to use links (
https://bosh.io/docs/links.html) to get the addresses of the other servers
in the cluster. So rather than using a property (
https://github.com/cloudfoundry-community/rethinkdb-boshrelease/blob/master/jobs/rethinkdb/spec#L13),
you could reference the link for that job (using something like
https://bosh.io/docs/links.html#templates) in your job templates. This
would allow for greater flexibility in network usage (allowing both manual
and dynamic networks and no longer requiring static ip allocation), and
reduce the complexity of deployment manifests (along with making them more
consistent across IaaSes). I don't know RethinkDB well enough to make any
suggestions on the exact setup scripts for it though. :)

-Rob

On Thu, Apr 20, 2017 at 4:48 AM, Leandro David Cacciagioni <
leandro.21.2008(a)gmail.com> wrote:

Guys,

I have created a RethinkDB bosh release in here: https://github.com/
cloudfoundry-community/rethinkdb-boshrelease can you please take a look
and tell me if there is anything wrong or what could I do different to
improve it?

I hope that what's already there works for some of you.

Thanks,
Leandro.-

PS: Riak release is possibly coming this week also.

--
Thanks,
RDR

@Rob just make a PR no ?

On Fri, Apr 21, 2017 at 1:28 AM, Rob Day-Reynolds <rdayreynolds(a)pivotal.io>
wrote:

On a first look, it looks like it could be nice to use links (
https://bosh.io/docs/links.html) to get the addresses of the other
servers in the cluster. So rather than using a property (
https://github.com/cloudfoundry-community/rethinkdb-boshrelease/blob/
master/jobs/rethinkdb/spec#L13), you could reference the link for that
job (using something like https://bosh.io/docs/links.html#templates) in
your job templates. This would allow for greater flexibility in network
usage (allowing both manual and dynamic networks and no longer requiring
static ip allocation), and reduce the complexity of deployment manifests
(along with making them more consistent across IaaSes). I don't know
RethinkDB well enough to make any suggestions on the exact setup scripts
for it though. :)

-Rob

On Thu, Apr 20, 2017 at 4:48 AM, Leandro David Cacciagioni <
leandro.21.2008(a)gmail.com> wrote:

Guys,

I have created a RethinkDB bosh release in here: https://github.com/cloud
foundry-community/rethinkdb-boshrelease can you please take a look and
tell me if there is anything wrong or what could I do different to improve
it?

I hope that what's already there works for some of you.

Thanks,
Leandro.-

PS: Riak release is possibly coming this week also.

--
Thanks,
RDR

Thanks Rob I'll see if I can add it over the weekend.

2017-04-21 3:52 GMT+02:00 Gwenn Etourneau <getourneau(a)pivotal.io>: