BOSH Release for Diego
Go Shell HTML Other
Latest commit c3c73d9 Jan 16, 2017 @jfmyers9 jfmyers9 committed with crhino bump bbs diego-ssh durationjson fileserver inigo rep route-emitter
[finishes #137622701]

Submodule src/code.cloudfoundry.org/bbs cd4a9486..635c361c:
  > use durationjson for time.Duration json logic
  > Revert changes made in 5006377 which degraded performance of the bbs benchmarks
Submodule src/code.cloudfoundry.org/diego-ssh 18cdb358..69d07508:
  > use durationjson for time.Duration json logic
Submodule src/code.cloudfoundry.org/durationjson 00000000...ce20a3a2 (new submodule)
Submodule src/code.cloudfoundry.org/fileserver 86368a63..212ecc74:
  > pass in configuration through json file instead of flags
Submodule src/code.cloudfoundry.org/inigo c1b7259f..36757f71:
  > use json config files for route emitter and fileserver
  > Configure inigo to use grootfs.
Submodule src/code.cloudfoundry.org/rep 5d4b9837..8833d853:
  > use durationjson time.Duration json logic
Submodule src/code.cloudfoundry.org/route-emitter 301c0cbe1..792357513:
  > route-emitter uses json configuration file instead of flags

Signed-off-by: Chris Piraino <cpiraino@pivotal.io>
Permalink
Failed to load latest commit information.
.final_builds Create final release 1.5.3 Jan 16, 2017
config Compile Diego healthcheck for Windows Dec 15, 2016
docs add manifest generation option for local route emitters Jan 4, 2017
examples update `examples/aws` to use new `uaa.ca_cert` Jan 12, 2017
git-hooks add a script to check for drifts between rep and rep_windows Dec 20, 2016
jobs bump bbs diego-ssh durationjson fileserver inigo rep route-emitter Jan 17, 2017
manifest-generation spiff merge local_route_emitter for the benchmark job Jan 16, 2017
packages bump bbs diego-ssh durationjson fileserver inigo rep route-emitter Jan 17, 2017
releases Create final release 1.5.3 Jan 16, 2017
scripts Build grootfs in scripts/ci/run-inigo when SQL_FLAVOR is postgres. Jan 16, 2017
src bump bbs diego-ssh durationjson fileserver inigo rep route-emitter Jan 17, 2017
stubs-for-cf-release Add `cloud_controller.admin` scope to ssh-proxy uaa client Jun 23, 2016
.envrc Add direnv config file Sep 15, 2014
.gitignore docs: move BOSH-Lite example to its own directory Jul 15, 2016
.gitmodules bump bbs diego-ssh durationjson fileserver inigo rep route-emitter Jan 17, 2017
CONTRIBUTING.md Remove the notion of etcd and refer to SQL as the default backing store Dec 21, 2016
LICENSE bump auction auctioneer bbs benchmark-bbs buildpack_app_lifecycle cac… Mar 25, 2016
NOTICE bump auction auctioneer bbs benchmark-bbs buildpack_app_lifecycle cac… Mar 31, 2016
README.md Update auctioneer TLS docs Dec 9, 2016

README.md

Cloud Foundry Diego (BOSH release) slack.cloudfoundry.org


This repo is a BOSH release for deploying Diego and associated tasks for testing a Diego deployment. Diego is the new container runtime system for Cloud Foundry, replacing the DEAs and Health Manager.

This release relies on a separate deployment to provide Consul, NATS, and Loggregator. In practice, these typically come from cf-release.

The Diego Design Notes present an overview of Diego, and links to the various Diego components.

Table of Contents

  1. Diego Operator Resources
    1. Deployment Examples: BOSH-Lite and AWS
    2. Deployment Requirements and Constraints
    3. Deploying Diego-Backed Cloud Foundry
    4. Security Configuration
    5. Data Store Configuration
    6. Monitoring and Inspection
  2. CF App Developer Resources
  3. Diego Contributor Resources

Diego Operator Resources

Deployment Examples: BOSH-Lite and AWS

Deployment Requirements and Constraints

  • Required BOSH Versions details the minimum BOSH director and stemcell versions required to deploy Diego correctly.
  • Deployment Constraints describes the dependencies that must be deployed before deploying the Diego cluster and restrictions on Diego instance update order and rates to ensure correct cluster operation.

Deploying Diego-Backed Cloud Foundry

Security Configuration

  • TLS Configuration describes how to generate TLS certificates for secure communication with Consul, the Diego BBS, and the Diego cell reps.
  • Upgrading the cell rep API to mutual TLS explains how to transition an existing Diego deployment to use mutual TLS for communication to the cell rep API without incurring downtime.
  • Upgrading the auctioneer API to mutual TLS explains how to transition an existing Diego deployment to use mutual TLS for communication from the BBS to the auctioneer API without incurring downtime.

Data Store Configuration

  • Supported Data Stores for Diego describes how to configure Diego to use either SQL for its data store and how to arrange automatic migration of data from etcd to MySQL or Postgres for old deployment that are using etcd.
  • Data Store Encryption explains how to manage the ring of encryption keys that Diego uses to secure data at rest.

Monitoring and Inspection

  • Diego Metrics lists the various metrics that Diego emits through the Loggregator system.
  • cfdot Setup shows how to set up the cfdot CF Diego Operator Tool CLI for use in inspecting and interacting with a Diego deployment.

CF App Developer Resources

  • Migrating to Diego describes how developers can switch from the DEAs to Diego and details various operational differences between the DEAs and Diego.
  • The Docker Support Notes describe how Diego runs Docker-image-based apps in Cloud Foundry.

Diego Contributor Resources

  • The Contribution Guidelines describes the developer workflow for making changes to Diego.
  • The CF Runtime Diego Pivotal Tracker project shows active areas of work for the Diego team in the backlog section.
  • The Diego Dev Notes provide a detailed explanation of how the Diego components and internal state machine interact, as well as information on development workstation setup.
  • The BBS Benchmarks provides information about results from the BBS benchmark tests that run in the Diego team's continuous integration testing pipeline.