Releases: cloudfoundry/nfs-volume-release
Releases · cloudfoundry/nfs-volume-release
nfs-volume v2.0.3
Release Notes
- Adds locking to nfstestserver pre-start script to allow colocation with other jobs that use debian packaging.
- Adds logic to handle legacy (nfs-volume < v1.3) service instances, fixing a bug where old NFS service instances cannot be bound to applications using a recent version of nfsbroker.
Dependencies
- The
nfsbrokerpush
errand requires thecf-cli-6-linux
job from cf-cli-release v1.6.0 to be colocated on the errand VM. - This version requires the
mapfs
job from mapfs-release >= v1.1.4 to be colocated on the Diego cell. Using older mapfs releases will cause the nfsv3driver job to fail with a missing bosh link.
nfs-volume v1.7.9
- adds logic to handle legacy (nfs-volume < v1.3) service instances, fixing a bug where old service instances cannot be bound to apps with a current service broker.
nfs-volume v1.5.7
- adds logic to handle legacy (nfs-volume < v1.3) service instances, fixing a bug where old service instances cannot be bound to apps with a current service broker.
nfs-volume v1.5.6
- Improves drain and unmount logic to allow nfsv3driver to safely clean up mounts that are busy or disconnected.
- Uses unique volume mountpoints for each application container to resolve reference counting issues that could cause volume mounts to fail when scaling apps up and down under load.
nfs-volume v2.0.2
Release Notes
- Modifies access check logic to allow mounts when the owner or group id reported from the server are ambiguous, or when
root
cannotstat
the mount. This reenables connections from some NFS servers that became broken by the access check logic was introduced in version 1.7.7.
Dependencies
- The
nfsbrokerpush
errand requires thecf-cli-6-linux
job from cf-cli-release v1.6.0 to be colocated on the errand VM. - This version requires the
mapfs
job from mapfs-release >= v1.1.4 to be colocated on the Diego cell. Using older mapfs releases will cause the nfsv3driver job to fail with a missing bosh link.
nfs-volume v1.7.8
Release Notes
- Modifies access check logic to allow mounts when the owner or group id reported from the server are ambiguous, or when
root
cannotstat
the mount. This reenables connections from some NFS servers that became broken by the access check logic was introduced in version 1.7.7.
Dependencies
- The
nfsbrokerpush
errand requires thecf-cli-6-linux
job from cf-cli-release v1.6.0 to be colocated on the errand VM. - This version requires the
mapfs
job from mapfs-release >= v1.1.4 to be colocated on the Diego cell. Using older mapfs releases will cause the nfsv3driver job to fail with a missing bosh link.
nfs-volume v2.0.1
Release Notes
- Adds logic to the
nfsbrokerpush
errand to use SQL as a backing store for the broker when CredHub properties are provided, but CredHub has been scaled down to 0 instances.
Dependencies
- The
nfsbrokerpush
errand requires thecf-cli-6-linux
job from cf-cli-release v1.6.0 to be colocated on the errand VM. - This version requires the
mapfs
job from mapfs-release >= v1.1.4 to be colocated on the Diego cell. Using older mapfs releases will cause the nfsv3driver job to fail with a missing bosh link.
nfs-volume v2.0.0
Release Notes
- Removes support for
fuse-nfs
mounts using thenfs-legacy
service. As of v2.0.0, any existing service instances still using thenfs-legacy
service will instead be mounted with the same mounting strategy as thenfs
service. - Adds logic to the
nfsbrokerpush
errand to migrate the backing store for nfsbroker from SQL to credhub, provided that credhub is available in the deployment. No special action is required. Once this migration is complete, users will be able to specifyusername
andpassword
during service instance creation (instead of service bind time) when LDAP is enabled. - Bumps golang package to 1.11.5
- Removes default NFS version from mount options. As a result, when version is not specified in the create or bind configuration, the mount operation will follow normal version negotiation conventions, and try to mount with version 4 first, then version 3.
Dependencies
- The
nfsbrokerpush
errand requires thecf-cli-6-linux
job from cf-cli-release v1.6.0 to be colocated on the errand VM. - This version requires the
mapfs
job from mapfs-release >= v1.1.4 to be colocated on the Diego cell. Using older mapfs releases will cause the nfsv3driver job to fail with a missing bosh link.
nfs-volume v1.5.5
- Updates MySql client code to allow connections to databases requiring
allowNativePassword=true
in the connection string. (This is required when using external MySql databases from Azure or GCP as the Cloud Foundry system database.)
nfs-volume v1.7.7
Release Notes
- Fixes access check logic in the NFS mounter so that we require fewer NFS RPC calls to check for read access. This solves intermittent mount failure when the network or remote NFS server is very slow.
- Updates MySql client code to allow connections to databases requiring
allowNativePassword=true
in the connection string. (This is required when using external MySql databases from Azure or GCP as the Cloud Foundry system database.) - Removes unused
ldap_test_mode
property from nfsbrokerpush errand.
Known Issues
- As of version 1.5.2, the
nfsbrokerpush
errand requires thecf-cli-6-linux
job from cf-cli-release v1.6.0 to be colocated on the errand VM. - This version requires the
mapfs
job from mapfs-release >= v1.1.1 to be colocated on the Diego cell. Using older mapfs releases will cause the nfsv3driver job to fail with a missing bosh link. - This release is incompatible with garden-runc-release < 1.3.0. Using it with an older garden release will cause read-only NFS mounts to fail.