Skip to content
This repository has been archived by the owner on Jan 25, 2022. It is now read-only.

Downstream improvements - including Riak + Service broker #11

Closed
james-masson opened this issue Jun 19, 2014 · 6 comments
Closed

Downstream improvements - including Riak + Service broker #11

james-masson opened this issue Jun 19, 2014 · 6 comments

Comments

@james-masson
Copy link

Hi,

we've forked this release, and have been working on improvements to support Riak (without CS).

While we've diverged a bit, we've added a few new features to the Riak bosh release you might be interested in, including:

  • Riak + CF service broker v2
  • Running Riak as vcap user
  • Compile Riak with BOSH friendly configuration.
  • More tenacious cluster join process
  • Support for the admin GUI
  • Tests to verify cluster connectivity and data persistance across node reboot + node loss
  • More use of ERB templating for Riak config files.
  • Complete BOSH deployable CI test-suite for the above.

We'd like eventually to get this all merged upstream - but our changes have been fairly extensive.

Feel free to pull whatever code you like - contact @trastle for more details, as CloudCredo will be rolling off this project shortly.

regards

James M

@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/73534762.

@tedsuo
Copy link

tedsuo commented Jun 19, 2014

Thanks a bunch! Could you provide a link to the fork?

@tedsuo & @jmtuley
Community Pair

@james-masson
Copy link
Author

Oops - forgot to include that!

Here's the Riak repo - https://github.com/FreightTrain/cf-riak-cs-release

Here's the coordinating repo - https://github.com/FreightTrain/C3-Services

Here's the jenkins server for it, including all the jobs - https://github.com/FreightTrain/C3-Services-Jenkins

What we don't have public right now are examples of manifests for the above...

@dliebreich
Copy link

ping @shalako (services PM): Should we move this issue into your tracker?

Thanks
@krishicks && @dliebreich
CF Community Pair

@shalako
Copy link
Contributor

shalako commented Jul 17, 2014

yes, thanks.

@robdimsdale
Copy link
Contributor

The upstream repo hasn't had any activity in two years, and we're not likely to merge changes at this point. Closing this issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants