v0.20.0 for PCF 1.8.0

PCF Dev v0.20.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.20.0+PCF1.8.0-<OS>.zip
   $ ./pcfdev-v0.20.0+PCF1.8.0-<OS>
   Plugin successfully upgraded. Current version: 0.20.0. For more info run: cf dev help
   $ cf dev help

Changelog

• The cf dev trust command removes all browser SSL warnings and allows you to run cf login without --skip-ssl-validation. Running cf dev untrust will revert this behavior. Running cf dev start -k will run cf dev trust automatically after starting the VM. The cf dev trust command inserts a CA certificate into your OS certificate store. For security reasons, the CA private key is never written to disk and is deleted from memory before the certificate is inserted. See "Known Issues" for limitations.
• The cf dev target command targets PCF Dev using the cf CLI and logs you in as the "user" user. Running cf dev start -t will run cf dev target automatically after starting the VM.
• Support for the Routing API and TCP Routing was added.
• The -r flag to the cf dev start command allows you to specify insecure Docker registries that the platform will allow Docker images to be pushed from.
• A beta of the .Net Core buildpack is now available in PCF Dev.
• Vagrant is now entirely removed from the OSS build of PCF Dev.
• The MySQL service broker is now present in OSS build of PCF Dev.
• A Pivotal Network API token that contains leading or trailing whitespace is now accepted.
• Networking logic is improved. The VM will now always start on the first available interface in the form 192.168.XX.11.
• VM network performance is enhanced via the virtio network driver.
• OVA downloads are now automatically retried if the network connection fails.
• The gorouter SSL certificate is now valid for a day before the VM is created. This prevents validation errors when the VM clock is slightly out of sync.
• The PCF Dev VM will now refuse to start with Virtualbox versions less than 5.0.
• The "Out of free memory" warning no longer inappropriately appears when resuming a VM. (#109)
• Apps Manager is now run as a single app instance, and the app instance is not duplicated on VM reboot. (#118)
• PCF Dev now starts correctly on Windows when the number of CPUs cannot be determined. (#115)
• Staging timeouts that prevent apps from pushing successfully should no longer occur. (#117)
• VM lockups caused by kvm-clock clocksource should no longer occur.
• Various other small bugs and typos are now fixed. (#110, #122)
• Component versions are now matched to PCF 1.8.0. (#119)

Elastic Runtime

• cf-release upgraded to v239 with custom modifications
• diego-release upgraded to v0.1480.0 with custom modifications
• garden-linux-release upgraded to v0.339.0
• etcd-release upgraded to v60
• cflinuxfs2 upgraded to v1.18.0
• routing-release added at v0.136.0

Services

• cf-mysql-release upgraded to v26.3 with custom modifications
• cf-redis-release upgraded to v424.29.0 with custom modifications
• cf-rabbitmq-release maintained at v215.4.0 with custom modifications
• Spring Cloud Services maintained at v1.1.1 with custom modifications

Tools

• Apps Manager maintained at a custom build from 6/15/2016.

Extra Buildpacks

• .Net Core Buildpack Beta added using a custom build of v1.0.0

Known Issues

• cf dev trust does not prevent SSL warnings in the Firefox web browser and in various Linux web browsers.
• cf dev trust requires user password entry on Mac OS X.
• Support for running multiple PCF Dev VMs, as well as support for custom VM IP addresses and domains will be delayed until release 0.21.0 or later.

Corresponding OVA Version: 0.317.0

v0.19.0 for PCF 1.7.12

PCF Dev v0.19.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.19.0+PCF1.7.12-<OS>.zip
   $ ./pcfdev-v0.19.0+PCF1.7.12-<OS>
   Plugin successfully upgraded. Current version: 0.19.0. For more info run: cf dev help
   $ cf dev help

Changelog

• The PCF Dev cf CLI plugin is now open source software, released under the Apache 2.0 license. The source code is available at: https://github.com/pivotal-cf/pcfdev-cli
• The cf dev import command now allows OVAs to be imported in fresh installation of PCF Dev.
• The open-vm-tools package is now included in the OVA. (#112)
• The cf dev help text clarifies that the MySQL service is always enabled. (#108)
• A race condition that would occasionally prevent gorouter from starting was fixed.
• Apps will now always trust the auto-generated, self-signed PCF Dev SSL certificate. This means that apps no longer need to disable SSL validation when communicating with other apps through app routes.
• Errors that result in invalid VM states are now always surfaced.
• The PCF Dev cf CLI plugin now accepts 200 status code responses from PivNet. This may address #101, but we were unable to replicate the issue.
• Component versions are now matched to PCF 1.7.12. This adds support for tasks to recent releases of Spring Cloud Data Flow.
• 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, but PCF 1.7.12 patches were applied
• diego-release maintained at v0.1467.0, but PCF 1.7.12 patches were applied
• 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 maintained 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 by 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 or later.

Corresponding OVA Version: 0.234.0

v0.18.0 for PCF 1.7.0

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

v0.17.0 for PCF 1.7.0

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

Changelog

• The plugin may be installed or upgraded by running it directly (as well as via cf install-plugin). (#76, #77)

  $ unzip pcfdev-v0.17.0+PCF1.7.0-<OS>.zip
  $ ./pcfdev-v0.17.0+PCF1.7.0-<OS>
  Plugin successfully upgraded, run: cf dev help
  $ cf dev help
  

• A corresponding PCF version is now included in the PCF Dev version for more clarity.

• Whitespace in proxy variables is now ignored. The delimitation of no_proxy may now include spaces. (#82)

• Apps Manager is now included with PCF Dev. Navigate to http://local.pcfdev.io in your web browser to check it out. (Your browser may warn you that the SSL certificate is self-signed.) (#12, #60)

• A default non-administrative user is now included: Email: user / Password: pass

• Application security groups are now open to private IP ranges by default. You may remove the all security group to revert to the previous behavior of only allowing access to public IP ranges. (#80, #81)

• HTTP/HTTPS proxy domains that resolve to multiple IP addresses are now supported. (#85)

• Custom OVAs may be used with the CLI plugin via the undocumented -o flag: cf dev start -o custom.ova. This will eventually replace Vagrant for booting OSS builds of PCF Dev. The source code for the CLI plugin will be released soon. (#84)

• PCF Dev VMs that fail to start may always be destroyed with cf dev destroy. Running cf dev status will report these VMs as "Invalid" and instruct you to destroy them. (#78, #79)

• The entire PCF Dev VM now lives in the ~/.pcfdev directory.

• Local network detection is significantly improved.

• Component versions are still matched to PCF 1.7.0.

• Experimental support for AWS has been discontinued temporarily. 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

Tools

• Apps Manager added using custom build from 6/15/2016.

Known Issues

• 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 custom VM IP addresses and domains has been delayed until the next release.
• Support for running multiple PCF Dev VMs on the same machine will be available soon.

Corresponding OVA Version: 0.136.0

v0.16.0 for PCF 1.7.0

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

Changelog

• PCF Dev is managed by a cf CLI plugin instead of Vagrant (for local VMs).
  Read the documentation for more info.

  $ unzip pcfdev-v0.16.0-<OS>.zip
  $ cf install-plugin pcfdev-v0.16.0-<OS>
  $ cf help dev
  

• PCF Dev is fully supported on Mac OS X, Windows, and Linux.

• Experimental support for PCF Dev on AWS is available through Vagrant. Follow the instructions in the INSTALL.md file in the PCF Dev AWS kit available from PivNet (pcfdev-aws-v0.16.0.zip).

• Boot time is reduced -- PCF Dev 0.16.0 boots 5x faster than 0.15.0.

• Syslog drains are now supported.

• PCF Dev analyzes your system memory usage and warns when starting the VM might cause your system to slow down.

• PCF Dev analyzes your local networking configuration to start on a subnet that doesn't conflict with other VMs or devices.

• Enterprise HTTP/HTTPS proxies may be set to domains as well as IP addresses.

• Component versions are still matched to PCF 1.7.

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

Known Issues

• If you get stuck in a state where you are unable to cf dev start or cf dev destroy, please open the Virtualbox UI and manually delete the PCF Dev VM. In the next release, cf dev destroy will always work.
• Support for custom VM IP addresses and domains will be available in the next release.
• Support for running multiple PCF Dev VMs on the same machine will be available soon.

Corresponding OVA Version: 0.115.0

v0.15.0 for PCF 1.7.0

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

Changelog

• Component versions matched to PCF 1.7
• Boot time significantly reduced-- PCF Dev 0.15.0 boots 1.5x - 2x faster than 0.14.0
• Route services are now provided with HTTP app URLs instead of HTTPS.
  • This means that custom route services no longer need to be configured to skip SSL validation

Elastic Runtime

• cf-release upgraded to v235, including:
  • diego-release v0.1467.0
  • garden-linux-release v0.337.0
  • etcd-release v45

Services

• cf-mysql-release maintained at v26
• cf-redis-release upgraded to v424.18.0
• cf-rabbitmq-release adjusted to v210.8.0

v0.14.0

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

Changelog

• Cloud Controller and UAA databases switched from Postgres to MySQL
• Default application memory reduced to 256 MB
• Default application disk quota reduced to 512 MB
• Stability improvements on boot

Elastic Runtime

• cf-release upgraded to v232 (with PCF "v232.6" patches), including:
  • diego-release v0.1460.0
  • garden-linux-release v0.334.0
  • etcd-release v38

Services

• cf-mysql-release maintained at v26
• cf-redis-release maintained at v424.15.0
• cf-rabbitmq-release maintained at v214.0.0

v0.13.0

PCF Dev v0.13.0 is now in open beta and is publically available on the Pivotal Network!
Feedback for the commercial version of PCF Dev may be left in the Github issues for this repository.

Changelog

• Boxes are now hosted on CloudFront CDN to improve download speeds
• Includes PowerShell start/stop scripts for Windows users
  • Validates dependencies and configuration
  • Configures VM to use first available network and respective domain (local.pcfdev.io)

Elastic Runtime

• cf-release upgraded from v230 to v231, including:
  • diego-release v0.1454.0
  • garden-linux-release v0.333.0
  • etcd-release v36

Services

• Services bind interfaces that are accessible from the host
  • Users can query services running on PCF Dev directly from their workstation
  • See cf env <app> on an app with a bound service for connection details
• cf-mysql-release upgraded from v25-95-g698a08c to v26
• cf-redis-release upgraded from v424.0.0-29-g0a260d0 to v424.15.0
• cf-rabbitmq-release upgraded from v213.0.0-27-g513d4a7 to v214.0.0

Proxy Support

• The values of the environment variables HTTP_PROXY and HTTPS_PROXY (uppercase or lowercase) at vagrant up
• Sets the proxy environment variables for apps based on the values set at vagrant up (or start-osx / start-windows.ps1)
  • HTTP_PROXY / HTTPS_PROXY (uppercase or lowercase)
  • NO_PROXY can be set during vagrant up to exclude addresses from proxy
• Custom buildpacks passed via cf push <app> -b <buildpack-repo> are downloaded via proxy
• Docker-based apps can be pushed from behind proxy
• Details on proxy support documented at http://docs.pivotal.io/pcf-dev/proxy.html

Bugfixes

• Resolved issue with failed buildpack staging during first cf push
• Fixed vagrant suspend / vagrant resume functionality
• Fixed the redirect loop on the MySQL Dashboard (link available from cf service my-mysql-service)

Interestings

• Memory footprint of the platform itself is 2GB
• Box download size is 4.5GB compressed, initial uncompressed size is 18GB
• Updated version of CF CLI in the VM to v6.16.1

Known Issues

• Default app sizing is 1GB system memory per app instance
  • We recommend cf push <app> -m 256M to reduce your VM footprint
  • Future PCF Dev releases will default app instance memory to 256M

v0.6.0

Changelog

• Bundled the MySQL service broker with MicroPCF
  • More information can be found on the MySQL for Pivotal Cloud Foundry page
  • 512mb and 1gb plans are available for the p-mysql service broker
  • Does not support High Availability (HA) for MySQL or include the switchboard
• cf-release upgraded from v228 to v230
• MicroPCF is now distributed via ZIP archive containing Vagrantfile
• cf ssh to an app container no longer requires disabling host key checking (-k option)

Interestings

• Footprint increased to 1.6 GB platform memory and 4 GB box download
• Upgraded BOSH agent from 7317c8f to version from stemcell version 3184.1

Known Issues

• The AWS provider does not currently work properly due to I/O throughput issues and has been deprecated.

Looking for a base distribution of MicroPCF without service brokers? Download here.

v0.5.0

First pre-release version of the official "MicroPCF" distro of MicroPCF.

In addition to the standard Cloud Foundry components, the MicroPCF distro now includes the Redis service broker. This allows Redis instances to be created and bound to apps running on MicroPCF. More information can be found on Redis for Pivotal Cloud Foundry.

Changelog

• cf-release upgraded from v226 to v228
• Packaged the Redis service broker with the MicroPCF distro.
• Upgraded the cf utility to v6.15.0

Bugfixes

• vagrant up waits for all buildpacks to be initialized
  • Slow I/O performance caused MicroPCF to load without all buildpacks available