cf-networking/1.0.0

CF networking features are now generally available! This release doesn’t include any major changes, just some metrics and logging enhancements and miscellaneous chores.

Try it out and give us your feedback in the #container-networking channel on cloudfoundry.slack.com.

Take a look at known issues for current limitations and known issues. Verified with the following: - CF deployment

Manifest Changes

New Properties

• The following optional parameters have been added to override the timeout values for database connections and DNS health checks for the silk controller and policy server:

  • cf_networking.silk_controller.connect_timeout_seconds
  • cf_networking.policy_server.connect_timeout_seconds

• This optional property has been added to override the metron port on the silk controller:

  • cf_networking.silk_controller.metron_port

• This optional property has been added to override the health check port on the silk controller:

  • cf_networking.silk_controller.health_check_port

Removed Properties

• The following properties have been removed from the silk-controller job, but still must be set on the silk-daemon job.
  • cf_networking.silk_daemon.ca_cert
  • cf_networking.silk_daemon.client_cert
  • cf_networking.silk_daemon.client_key

Significant Changes

Metrics

• Silk controller emits metrics for subnet usage and HTTP health
• Silk daemon emits metrics

Logging

• Standardize logging across CF networking
• As an operator, I can grep through my logs to find all the CF Networking stuff

Stability

• vxlan-policy-agent fails when policy server is not reachable on start-up
• Requests to policy server and silk controller on their internal endpoints do not hang forever when there is a network partition to their respective databases
• Expose the lease poll interval as a BOSH property

Chores

• mysql ci fails with deadlock
• Remove remaining flannel code and dependencies from cf-networking-release
• Add an integration concurrency test for the silk controller
• Policy server database reads should check for errors at the end of the loop.
• Silk controller database reads should check for errors at the end of the loop.
• An acceptance test covers that ASGs work when an app has a policy

- name: "cf-networking"
  version: "1.0.0"
  url: "https://bosh.io/d/github.com/cloudfoundry-incubator/cf-networking-release?v=1.0.0"
  sha1: "1297f615af9ed7601e21549679433337461bb432"

bosh upload-release --sha1 1297f615af9ed7601e21549679433337461bb432 \
  "https://bosh.io/d/github.com/cloudfoundry-incubator/cf-networking-release?v=1.0.0"