Release Notes for GemFire for Pivotal Cloud Foundry

Overview

GemFire for Pivotal Cloud Foundry (PCF) supports the deployment of multiple Pivotal GemFire cluster configurations to PCF to support GemFire application development and deployment. GemFire for PCF enables administrators to customize three different cluster configurations to provide coarse control over the number of locators and servers available in each GemFire instance. In addition, developers can customize the GemFire instance that is bound to their app using GemFire cluster configuration commands or a new Cloud Foundry CLI interface.

Feedback

Your feedback is welcome. Please provide any bugs, feature requests, or questions either to Pivotal Customer Support at https://support.pivotal.io or email pivotal-cf-feedback@pivotal.io.

v1.7.2.0

Release Date: 30th January 2017

New in this Release

  • Security fixes:
    • Runs gfsh process as the vcap user instead of the root user

v1.6.6.0

Release Date: 30th January 2017

New in this Release

  • Security fixes:
    • Runs gfsh process as the vcap user instead of the root user

v1.7.1.0

Release Date: 29th December 2016

New in this Release

  • Stemcell AWS 3233.6: patches Ubuntu CVEs.
  • Stemcell Azure 3233.7: patches Ubuntu CVEs.
  • Security fixes:
    • Remove public route that exposed WAN replication credentials [CVE-2016-8220]
    • Add authentication to broker endpoints [CVE-2016-9880]

v1.6.5.0

Release Date: 29th December 2016

New in this Release

  • Stemcell AWS 3233.6: patches Ubuntu CVEs.
  • Stemcell Azure 3233.7: patches Ubuntu CVEs.
  • Security fixes:
    • Remove public route that exposed WAN replication credentials [CVE-2016-8220]
    • Add authentication to broker endpoints [CVE-2016-9880]

v1.6.4.0

Release Date: 11th November 2016

New in this release

  • Bug fixes:
    • Upgraded golang to v1.7

v1.6.3.0

Release Date: 28th October 2016

New in this release

  • Stemcell AWS 3232.17: patches Ubuntu CVEs.
  • Compatibility fixes for PCF v1.7 running on vSphere and Azure.

v1.7.0.0

Release Date: 19th September 2016

New in this Release

  • Compatibility release for PCF v1.7 and PCF v1.8. The GemFire for PCF service now installs on both PCF v1.7 and PCF v1.8 without support for specific features, such as multiple availability zones.
  • IPsec support: The GemFire for PCF tile now supports IPsec.
  • Log format changed from free text to JSON
  • Bug fixes:
    • DB synch issues
    • Upgraded golang to v1.7
    • Use crypto library for certificate chain discovery
    • Use of CF_DIAL_TIMEOUT
    • Service instance route are now unique across orgs and spaces
  • Stemcell AWS 3232.17: patches Ubuntu CVEs
  • Stemcell Azure 3232.17: patches Ubuntu CVEs

Known Issues and Limitations:

  • There is a known issue where apps fail to stage when using the Java buildpacks v3.4.x, v3.5.x. To resolve this, use the latest Java buildpack.
  • Currently tile supports only a single Availability Zone (AZ).

v1.6.2

Release Date: 28th July 2016

New in this Release

  • Compatibility release for PCF v1.7. The GemFire for PCF service now installs on PCF v1.7 without support for PCF v1.7–specific features, such as multiple availability zones.

Known Issues and Limitations:

There is a known issue where apps fail to stage when using the Java buildpacks 3.4.x, 3.5.x. To resolve this, use the latest Java buildpack.

v1.6.1

Release Date: 22nd July 2016

New in this Release

  • Stemcell AWS 3232.13: patches Ubuntu CVEs.

Known Issues and Limitations:

There is a known issue where apps fail to stage when using the Java buildpacks 3.4.x and 3.5.x. To resolve this, update Java buildpack to 3.6. In Java buildpack 3.4, GemFire was upgraded from v8.0 to v8.2. GemFire v8.1 introduced a dependency on log4j, but log4j was not added to the Java buildpack v3.4. This dependency has been included in Java buildpack v3.6.

v1.6.0.0

Release Date: 31st May 2016

New in this Release

  • Stemcell AWS 3232.4: patches Ubuntu CVEs.
  • Stemcell Azure 3232.5: patches Ubuntu CVEs.

Known Issues and Limitations:

There is a known issue where apps fail to stage when using the Java buildpacks v3.4.x and v3.5.x. To resolve this, update Java buildpack to v3.6. In Java buildpack v3.4, GemFire was upgraded from v8.0 to v8.2. GemFire v8.1 introduced a dependency on log4j, but log4j was not added to the Java buildpack v3.4. This dependency has been included in Java buildpack v3.6.

v1.5.0.0

Release Date: 9th May 2016

New in this Release

  • The packaged GemFire is upgraded from v8.2.0.5 to v8.2.0.14.
  • The enable-network-partition-detection property is now enabled to prevent against data corruption in split-brain scenarios.
  • Cluster stability has been improved during restarts and during service instance deletions.
  • Default timeout of cf restart-gemfire has been increased from 120 seconds to 900 seconds to accommodate slower-than-expected startup of servers and locators.
  • When running on Azure, GemFire servers will have redundancy zones tied directly to Azure’s fault domains so that redundancy for partitioned regions is satisfied across multiple virtual server racks.
  • The cf export-gemfire command now gives feedback about missing arguments, making it easier to export your GemFire logs, cluster configs and properties.

Upgrade Warning: Downtime Required

Upgrading to v1.5.0.0 will require downtime for your GemFire for PCF deployment.

Since the enable-network-partition-detection=true property must be set on the entire cluster at the same time, we are unable to do a rolling upgrade. Previously deployed apps and service instances will continue to function normally after the upgrade, though GemFire for PCF will be unavailable during the upgrade.

For Ops Manager-deployed tiles:

  1. Upload the v1.5.0.0 GemFire for PCF tile to Ops Manager.
  2. Under Available Products > Pivotal GemFire, click Add.

    In Ops Manager, add Pivotal GemFire v1.5.0.0

  3. bosh target your Ops Manager-deployed bosh director.

  4. bosh stop your previously deployed GemFire for PCF tile. This will stop the GemFire for PCF service broker and all service instances.

  5. In Ops Manager, click Apply Changes.

    In Ops Manager, click Apply Changes

For bosh-deployed releases:

  1. bosh upload the releases contained in this tile
  2. bosh stop your existing GemFire deployment
  3. bosh deploy the manifest contained in this tile
  4. bosh start your new deployment

Known Issues and Limitations:

Upgrading to v1.5.0.0 will require downtime for your GemFire for PCF deployment as detailed in the previous section.

There is a known issue where apps fail to stage when using the Java buildpacks v3.4.x and v3.5.x. To resolve this, update Java buildpack to v3.6. In Java buildpack v3.4, GemFire was upgraded from v8.0 to v8.2. GemFire v8.1 introduced a dependency on log4j, but log4j was not added to the Java buildpack v3.4. This dependency has been included in Java buildpack v3.6.

v1.4.0.0

Release Date: 4th April 2016

New in this Release

  • Adds support for using CLI plugin with a http proxy. To enable proxy usage, follow the same instructions for the CLI.
  • Enables best practice OS tuning settings for server and locator VMs. Includes settings for:
    • fs.file-max
    • vm.swappiness
    • net.core.somaxconn
    • net.core.netdev_max_backlog
    • net.core.rmem_max
    • net.core.wmem_max
    • net.ipv4.tcp_wmem
    • net.ipv4.tcp_rmem
    • net.ipv4.tcp_syncookies
    • net.ipv4.tcp_max_syn_backlog.

Known Issues and Limitations:

There is a known issue where apps fail to stage when using the Java buildpacks v3.4.x and v3.5.x. To resolve this, update Java buildpack to v3.6. In Java buildpack v3.4, GemFire was upgraded from v8.0 to v8.2. GemFire v8.1 introduced a dependency on log4j, but log4j was not added to the Java buildpack v3.4. This dependency has been included in Java buildpack v3.6.

v1.3.0.0

Release Date: 18th March 2016

New in this Release

  • Add support for asynchronous service instance allocation and deallocation.
  • Add basic auth for Gemfire agent endpoints.
  • Improve error handling and reporting during service instance deallocation.
  • Include stack traces in error logs for the service broker.
  • Introduce log levels for the service broker. For now, they are only configurable at the release level and set to info by default. They are not exposed in the tile at this point.
  • Increase the default limit for file descriptors to 32,000 for the GemFire VM.
  • Ensure that the JVM is killed when it is Out of Memory.
  • Upgrade stemcell to 3146.10, patching USN-2929-1.

Known Issues and Limitations:

There is a known issue where apps fail to stage when using the Java buildpacks v3.4.x and v3.5.x. To resolve this, update Java buildpack to v3.6. In Java buildpack v3.4, GemFire was upgraded from v8.0 to v8.2. GemFire v8.1 introduced a dependency on log4j, but log4j was not added to the Java buildpack v3.4. This dependency has been included in Java buildpack v3.6.

v1.2.3.0

Release Date: 4th February 2016

New in this Release

  • Stemcell 3146.6: patches Ubuntu CVEs.

Known Issues and Limitations:

There is a known issue where apps fail to stage when using the Java buildpacks v3.4.x and v3.5.x. To resolve this, update Java buildpack to v3.6. In Java buildpack v3.4, GemFire was upgraded from v8.0 to v8.2. GemFire v8.1 introduced a dependency on log4j, but log4j was not added to the Java buildpack v3.4. This dependency has been included in Java buildpack v3.6.

v1.2.2.0

Release Date: 22nd January 2016

New in this Release

  • Stemcell 3146.5: resolves CVE-2016-0728.

Known Issues and Limitations:

There is a known issue where apps fail to stage when using the Java buildpacks v3.4.x and v3.5.x. To resolve this, update Java buildpack to v3.6. In Java buildpack v3.4, GemFire was upgraded from v8.0 to v8.2. GemFire v8.1 introduced a dependency on log4j, but log4j was not added to the Java buildpack v3.4. This dependency has been included in Java buildpack v3.6.

v1.2.1.0

Release Date: 12th January 2016

New in this Release

  • Stemcell 3146.2: resolves CVE USN-2857-1.

Known Issues and Limitations:

There is a known issue where apps fail to stage when using the Java buildpacks v3.4.x and v3.5.x. To resolve this, update Java buildpack to v3.6. In Java buildpack v3.4, GemFire was upgraded from v8.0 to v8.2. GemFire v8.1 introduced a dependency on log4j, but log4j was not added to the Java buildpack v3.4. This dependency has been included in Java buildpack v3.6.

v1.2.0.0

Release Date: 1st December 2015

New in this Release

  • Support for GemFire multi-site (WAN) replication.
  • Support for the “Trusted Certificates” feature in Ops Manager. The certificates from “Trusted Certificates” are deployed to all GemFire nodes, and to the GemFire service broker.

    Note on self-signed and internal CA signed certificates: If you are using a self-signed certificate or a certificate signed by an internal or other not known certificate authority (CA), you must add the certificate (or certificate chain) to the “Trusted Certificates” in Ops Manager.

  • GemFire upgraded to v8.2.0.5.

  • Drain script improvements.

  • Better error reporting for service instance allocation failures. Instead of returning “The maximum number of Service Instances already exist” message for all failures during a service instance allocation, each different type of failure returns a descriptive error message.

  • Stemcell 3144.

Known Issues and Limitations

  • Upgrading the GemFire tile on AWS can fail when the stemcell is changing as part of an upgrade. This problem usually manifests itself during the install process’ smoketest errand. The issue arises when, as part of an upgrade, a new VM has been created with the same IP but with a different MAC address. Because AWS suppresses unsolicited ARPs, other members may not know that their ARP cache has become invalid.
  • The service supports only a single PCF availability zone. Although the service enables GemFire HA features such as redundancy and persistence, a failure of the targeted availability zone can result in the loss of GemFire region data.

    Note: If there is more than one available zone, you may see deployment failures or uneven sized clusters.

  • Elastic scaling is not supported. You cannot change the number of cache servers and locators in a service plan without destroying and recreating the current service plan instances.

  • If you deploy the service and then subsequently reduce the number of clusters, all allocated instances are destroyed.

v1.1.1.0

Release Date: 5th November 2015

New in this Release

  • Support for Ops Manager v1.6 and Elastic Runtime v1.6. This release does not work with the previous releases of Ops Manager and Elastic Runtime.
  • Stemcell 3100

Known Issues and Limitations

See Known Issues and Limitations for v1.1.0.0 below.

v1.1.0.0

Release Date: 22nd September 2015

New in this Release

  • Upgraded Pivotal GemFire to v8.2
  • Upgraded Java to v8, and JRE v1.8
  • Spring-related enhancements:
    • Support for deploying a Spring XML configuration and application code to GemFire service instances.
      • If you use Spring “all the way” you can do so with GemFire service instances as well.
      • There is no need to translate the Spring configuration to GemFire XML.
      • Spring support is provided using configuration options of the GemFire for PCF CLI plug-in command, cf restart-gemfire.
  • Support for using SSL encryption to access GemFire Service Instances from outside of PCF:
    • GemFire Pulse is now accessible via HTTPS.
    • GemFire REST clients can be configured to access a service instance’s REST API endpoint via HTTPS.
    • You can configure the GemFire shell (gfsh) to access a service instance over HTTPS.
  • Additional fixes and improvements:
    • Drain script improvements
    • Improved handling of self-signed certificates
    • YAML syntax validation for cluster properties that are provided via the --properties option of the cf restart-gemfire CLI command
  • Stemcell 3062
  • Support for the experimental feature, HTTPS traffic to UAA

Known Issues and Limitations

  • Upgrading the GemFire tile on AWS can fail when the stemcell is changing as part of the upgrade. The problem usually manifests itself during the install process’ smoketest errand. The issue arises when, as part of upgrade, a new VM has been created with the same IP but a different MAC address. Because AWS suppresses unsolicited ARPs, other members may not know that their ARP cache has become invalid.
  • The service supports only a single PCF availability zone. Although the service enables GemFire HA features such as redundancy and persistence, a failure of the targeted availability zone can result in the loss of GemFire region data.

    Note: If there is more than one available zone, you may see deployment failures or uneven sized clusters.

  • The experimental HTTPS-only feature in Elastic Runtime v1.5 is not supported and may cause issues with this version of the product. Pivotal is working to provide full support for HTTPS-only traffic in a future release.

  • Elastic scaling is not supported. You cannot change the number of cache servers and locators in a service plan without destroying and recreating the current service plan instances.

  • If you deploy the service and then subsequently reduce the number of clusters, all allocated instances are destroyed.

  • GemFire WAN replication is not supported.

v1.0.0.0

Release Date: 10 August 2015

Known Issues and Limitations

  • The service supports only a single PCF availability zone. Although the service enables GemFire HA features such as redundancy and persistence, a failure of the targeted availability zone can result in the loss of GemFire region data.

    Note: If there is more than one available zone, you may see deployment failures or uneven sized clusters.

  • The experimental HTTPS-only feature in Elastic Runtime v1.5 is not supported and may cause issues with this version of the product. Pivotal is working to provide full support for HTTPS-only traffic in a future release.

  • Elastic scaling is not supported. You cannot change the number of cache servers and locators in a service plan without destroying and recreating the current service plan instances.

  • If you deploy the service and then subsequently reduce the number of clusters, all allocated instances are destroyed.

  • GemFire WAN replication is not supported.

Create a pull request or raise an issue on the source for this page in GitHub