Skip to content
This repository has been archived by the owner on Jul 28, 2020. It is now read-only.

v0.18.0 for PCF 1.7.0
Compare
Choose a tag to compare
@pcfdev-bot pcfdev-bot released this 23 Jul 04:46
· 222 commits to master since this release
v0.18.0
067eec6

PCF Dev v0.18.0 is an open beta release that is publicly available on the Pivotal Network.
Feedback for the proprietary version of PCF Dev may be left in the Github issues for this repository.

Installation

   $ unzip pcfdev-v0.18.0+PCF1.7.0-<OS>.zip
   $ ./pcfdev-v0.18.0+PCF1.7.0-<OS>
   Plugin successfully upgraded. Current version: 0.18.0. For more info run: cf dev help
   $ cf dev help

Changelog

  • Spring Cloud Services is now available in the commercial version of PCF Dev. You must have 6 GB of free memory to run PCF Dev with Spring Cloud Services, and you must specify that it should start when you start PCF Dev.

    $ cf dev start -s scs

    See Known Issues below for caveats.

  • The -s flag to cf dev start may be used to customize what services are started. By default, MySQL, Redis, and RabbitMQ are started. MySQL is used internally by the VM and cannot be disabled. Run cf dev help for more info.

  • The PCF Dev cf CLI plugin version and OVA version are available by running cf dev version. (#76)

  • Apps Manager services now have corresponding tile images and relevant descriptions.

  • Certain invalid VM states are now detectable. cf dev status is more reliable in this release.

  • Invalid VM states that are recoverable can be recovered with cf dev stop followed by cf dev start.

  • The vcap user in the VM can now use the cf CLI.

  • The EULA is now scrollable and disappears from your terminal after accepting it.

  • DNS resolution inside the PCF Dev VM is completely re-vamped. External resolution is now performed on the host. This may address issues where PCF Dev fails to start. (#79, #93, #102)

  • HTTP proxy support is improved. (#100)

  • Local network detection and VM IP address collision prevention is improved (#88).

  • The SSL certificate for PCF Dev matches the system domain in all cases.

  • The corresponding PCF Dev OVA (pcfdev-v0.219.0.ova for this release) may be imported from the local filesystem with cf dev import /path/to/pcfdev-v0.219.0.ova

  • Component versions are still matched to PCF 1.7.0. PCF Dev v0.19.0 will include PCF 1.7.12 components and will be available soon.

  • Experimental support for AWS continues to be discontinued. We found that many users had trouble configuring PCF Dev on AWS in a secure and usable manner. AWS support will return soon, and will be available from the AWS Marketplace. If you are a Pivotal employee, please contact us on Slack for continued AWS support.

Elastic Runtime
  • cf-release maintained at v235
  • diego-release maintained at v0.1467.0
  • garden-linux-release maintained at v0.337.0
  • etcd-release maintained at v45
Services
  • cf-mysql-release maintained at v26
  • cf-redis-release maintained at v424.18.0
  • cf-rabbitmq-release maintained at v210.8.0
  • Spring Cloud Services added at v1.1.1
Tools
  • Apps Manager maintained at a custom build from 6/15/2016.

Known Issues

  • If you experience failures while creating Spring Cloud services with cf create-service, try creating services one at a time, making sure each service is created successfully before creating the next. For example, the sample Traveler app deploy script will occasionally fail because it attempts to create a service registry and a circuit breaker dashboard simultaneously.
  • MySQL is used internally be the VM and cannot be disabled with the -s flag.
  • The Apps Manager SSL certificate is self-signed. Your browser may warn you about this when you navigate to https://local.pcfdev.io. This warning can safely be ignored.
  • Support for running multiple PCF Dev VMs, as well as support for custom VM IP addresses and domains will be delayed until release 0.20.0.

Corresponding OVA Version: 0.219.0

Assets 2
Loading