v175

drnic edited this page Sep 23, 2014 · 10 revisions

Search

Contents

Community Advisory Board, PMC Schedules

Developing CF

Latest CF Releases

Roadmap and Trackers

See CFF official project list.

Roadmaps are reflected in pivotal trackers. Tracker Instructions and steps to watch stories. Here is a flat list of all trackers:

CIs

Maybe other CIs hosted on cf-app.com are mentioned in slack ?

Using CF

Running CF

Tools

Clone this wiki locally

Release Notes

The cf-release v175 was released on July 16th 2014. This release is the first release where CF Security Groups are fully implemented. Out of the box, security groups have defined rules to continue to allow applications to talk to public ip spaces. What is not enabled by default is allowing communication to the CF local IP segments. To enable this, you should update your manifest to include allow rules for the local IP cidr's needed or after deploying it use the CF latest client to create groups to enable local communication from the application container. It is strongly suggested that this update be first applied to a testing or staging environment to ensure these new networking constraints do not break applications.

Release Highlights

  • PHP buildpack reduced from 400+mb down to 64mb for droplet hello world.
  • PHP buildpack no longer including cached deps in droplet yay
  • less than 60 seconds to push a php app
  • CF Security Groups are now released and can be managed via the API or CF CLI

Upgrade Notes

From v173 to v175 (v174 was never released), must add the following to deployment manifests:

properties:
  cc:
    security_group_definitions:
      - name: public_networks
        rules:
        - protocol: all
          destination: 0.0.0.0-9.255.255.255
        - protocol: all
          destination: 11.0.0.0-169.253.255.255
        - protocol: all
          destination: 169.255.0.0-172.15.255.255
        - protocol: all
          destination: 172.32.0.0-192.167.255.255
        - protocol: all
          destination: 192.169.0.0-255.255.255.255
      - name: dns
        rules:
        - protocol: tcp
          destination: 0.0.0.0/0
          ports: '53'
        - protocol: udp
          destination: 0.0.0.0/0
          ports: '53'
    default_running_security_groups: ["public_networks", "dns"]
    default_staging_security_groups: ["public_networks", "dns"]

There are now two additional buildpacks, and an offline Java buildpack. Change the following properties:

properties:
  cc:
    install_buildpacks:
      - name: java_buildpack
        package: buildpack_java_offline
      - name: ruby_buildpack
        package: buildpack_ruby
      - name: nodejs_buildpack
        package: buildpack_nodejs
      - name: go_buildpack
        package: buildpack_go
      - name: python_buildpack
        package: buildpack_python
      - name: php_buildpack
        package: buildpack_php

Config

Deployed with

  • Bosh Version: 91
  • Stemcell Version: Lucid 2366
  • CC Api Version: 2.8.0