Comments (7)
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/166368428
The labels on this github issue will be updated when the story is started.
from nfs-volume-release.
@paulcwarren & @davewalter can you please provide some commentary on this issue? This is an issue for the cloud.gov platform and is blocking the deployment of volumes for customers.
from nfs-volume-release.
@mxplusb sorry for the slow response. We are a bit conflicted about this issue because we are trying to move away from direct SQL support for our broker backing store, and instead standardize on credhub as our storage backend. We currently have migration code to move MySql data into CredHub, but if we pulled this PR, we'd have to develop and test a migration for Postgres also.
Is it possible for you to use CredHub instead of SQL for your storage? That would be more future proof, and would also allow you to use Postgres under the covers without requiring direct support from nfsbroker.
from nfs-volume-release.
this ops file provides an example for how to establish a credhub identity and plumb it through to nfsbroker.
from nfs-volume-release.
Thanks for the heads up on the migration.
Is it possible for you to use CredHub instead of SQL for your storage?
No it is not. We do not use Credhub at the moment, just a vars store for now. There are eventually plans for us to move to a Config Server implementation, but it may or may not be Credhub.
we'd have to develop and test a migration for Postgres also.
I think this extra step is going to be necessary, imo. The broker was marketed with and had basic plumbing for both MySQL and PostgreSQL, so it seems (to me) to be a reasonable expectation that there should be a tested migration plan for PostrgreSQL.
Fixing the bug in PostgreSQL support should take priority so the software can support it as marketed and written, then figure out the rest of the migration story. I appreciate your recommendation of future proofing but I'm more interested in fixing the bug now than a future proof design that I can't use.
from nfs-volume-release.
Hi @mxplusb,
Given all the other issues you've posted to nfsbroker, it looks like your planned usage of the broker diverges quite significantly from the standard cf-deployment path that we actually build and test, so while I take your point that it isn't great that postgres capabilities regressed, we've already moved away from SQL in cf-deployment, quite some time ago. We are a tiny team, with very limited capacity to test non-standard configurations, so it's not really practical for us to invest in supporting capabilities that we soon plan to remove and that haven't been functional for at least a year.
I hate to suggest it, but given your various requirements, probably your best bet is going to be to maintain your own fork of the broker, so that you can make it work with your specific build and deployment requirements.
from nfs-volume-release.
Closing this, as we plan to remove all SQL support from nfsbroker in coming months, and standardize on CredHub.
from nfs-volume-release.
Related Issues (20)
- Add support for cf CLI v8 to the errands HOT 2
- App Binding NFS Service broker error: - Not allowed options: username, password HOT 3
- nfsbrokerpush errand doesn't support cflinuxfs4 HOT 6
- Diego is trying to connect to nfsv3driver that is disabled. HOT 3
- Submodules -> Versioned Deps HOT 2
- Error filling in template 'db_ca.crt.erb' (line 1: Can't find property '["nfsbrokerpush.db.ca_cert"]' HOT 3
- nfs-volume/1.6.0 support Xenial Stemcell HOT 3
- enable-nfs-volume-service.yml HOT 3
- ldap Authentication on NFS volume services HOT 8
- "Service broker error: Not allowed options: username, password" HOT 2
- ldap Authentication on NFS volume services HOT 6
- Detect stale nfs mounts and mark as unhealthy HOT 4
- UID/GID based mapping NFS-experimental HOT 2
- NFS mount Access using API Calls HOT 2
- NFS Mount issue using LDAP HOT 3
- Proxy properties ignored HOT 2
- [Question] Adopting Bionic estimation HOT 20
- Test Tracker integration removal
- nfsv3driver drain fails to complete. HOT 7
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nfs-volume-release.